Jackie-Jiang closed issue #12721: TimeSegmentPruner exception based on query
and schema datetime column format
URL: https://github.com/apache/pinot/issues/12721
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
Jackie-Jiang commented on issue #12721:
URL: https://github.com/apache/pinot/issues/12721#issuecomment-2033290879
@kelseiv Can you please take a look at the feedback from @jadami10 about the
schema doc?
--
This is an automated message from the Apache Git Service.
To respond to the
jadami10 commented on issue #12721:
URL: https://github.com/apache/pinot/issues/12721#issuecomment-2021559505
also to provide more concrete feedback for the schema docs,
https://docs.pinot.apache.org/configuration-reference/schema, there are ~1700
words on that page and all of 1 schema
jadami10 commented on issue #12721:
URL: https://github.com/apache/pinot/issues/12721#issuecomment-2021537161
between the new/old formats,
https://docs.pinot.apache.org/configuration-reference/schema#new-datetime-formats,
`1:MILLISECONDS:TIMESTAMP` isn't mentioned anywhere. Though if I
Jackie-Jiang commented on issue #12721:
URL: https://github.com/apache/pinot/issues/12721#issuecomment-2019422882
It is documented here:
https://docs.pinot.apache.org/configuration-reference/schema#datetimefieldspec
The root cause is that time value and format doesn't match. We cannot
jadami10 commented on issue #12721:
URL: https://github.com/apache/pinot/issues/12721#issuecomment-2018801634
cc @Jackie-Jiang since you've touched a lot of the pruner code recently.
Does it make sense to have the pruner do
```
try {
prune()
} catch {
return null
jadami10 opened a new issue, #12721:
URL: https://github.com/apache/pinot/issues/12721
We have the following datetime column in our schema
```
date_time_field_specs:
- name: created
data_type: TIMESTAMP
format: 1:MILLISECONDS:EPOCH
granularity: 1:HOURS
```
