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

Improve Date precision truncation handling #2466

Open
PSeitz opened this issue Jul 30, 2024 · 0 comments
Open

Improve Date precision truncation handling #2466

PSeitz opened this issue Jul 30, 2024 · 0 comments

Comments

@PSeitz
Copy link
Contributor

PSeitz commented Jul 30, 2024

The way we handle precision truncation of DateTime when querying is opaque and error-prone. When using a date in the inverted index we want to truncate it to seconds, since they are all stored with second precision. In the columnar storage the precision is configurable.

Currently DateTime is stored truncated in Term, but this is not great since we don't know if Term is used in the inverted index or columnar.

Ideally we would store DateTime with full precision and get a truncated version before using it in a query. E.g range queries may use the inverted index or the columnar storage.

Related: #2456
Depends on splitting term into indexing term and term: #2366

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant