vectordotdev / vectordotdev/vector
Ability to store sub-second precision in ClickHouse
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 22.6k
- Forks
- 2.3k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 146
Description
Clickhouse's DateTime data type only allows for second precision, we can get around this by storing nanoseconds in a separate field as described here.
Before we begin work, we should think carefully about how this would work exactly. For example, it might make more sense to allow the Vector user to split the field in a transform instead of doing this automatically.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the ClickHouse DateTime limitation described in the issue and read the linked Vector discussion about storing nanoseconds separately. Compare automatic field splitting with letting users split the field in a transform. The issue does not define an implementation location or a completion criterion, so an accepted design and behavior would be needed before coding.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clickhouse
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100