Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

clp-s: Nested timestamps result in incorrect mst node names #261

Closed
gibber9809 opened this issue Feb 4, 2024 · 0 comments · Fixed by #262
Closed

clp-s: Nested timestamps result in incorrect mst node names #261

gibber9809 opened this issue Feb 4, 2024 · 0 comments · Fixed by #262
Labels
bug Something isn't working

Comments

@gibber9809
Copy link
Contributor

Bug

Ingesting records with nested timestamps using the --timestamp-key argument turns the key name in the last level of the MST into the fully qualified name. e.g. records like {"a": "ts": ...} will look like {"a": "a.ts": ...} when decompressed.

CLP version

e80cee0

Environment

Ubuntu focal clp image

Reproduction steps

  1. Ingest a dataset with nested timestamps while using the --timestamp-key argument
  2. Observe incorrect data upon decompression
@gibber9809 gibber9809 added the bug Something isn't working label Feb 4, 2024
gibber9809 added a commit that referenced this issue Feb 8, 2024
…s: (#262)

- Add new timestamp formats for clp, clp-s, and glt
- Remove obsolete FLOATDATESTRING MST node
- Handle timestamp keys in JsonParser rather than column writers (fixes #261)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant