Request
The compression job submission form has a dataset field and a timestamp key field, both of which have nuances in what are supported.
For dataset names, see:
|
Validates that the given dataset name abides by the following rules: |
|
- Its length won't cause any metadata table names to exceed MySQL's max table name length. |
|
- It only contains alphanumeric characters and underscores. |
Timestamp keys require escapes for certain characters: https://docs.yscope.com/clp/main/user-docs/reference-json-search-syntax.html#characters-that-require-escaping
Possible implementation
For dataset names, we should probably just perform similar validation in the UI as on the command line and eventually move all validation into the future API server for compression.
For timestamp keys, just document that certain characters require escapes and link to the docs.
Request
The compression job submission form has a dataset field and a timestamp key field, both of which have nuances in what are supported.
For dataset names, see:
clp/components/clp-package-utils/clp_package_utils/general.py
Lines 642 to 644 in e6d7a58
Timestamp keys require escapes for certain characters: https://docs.yscope.com/clp/main/user-docs/reference-json-search-syntax.html#characters-that-require-escaping
Possible implementation
For dataset names, we should probably just perform similar validation in the UI as on the command line and eventually move all validation into the future API server for compression.
For timestamp keys, just document that certain characters require escapes and link to the docs.