kgyrtkirk commented on PR #17325:
URL: https://github.com/apache/druid/pull/17325#issuecomment-2505724322

   I'm a little puzzled seeing that the `parser` seem to have been 
[deprecated](https://github.com/apache/druid/blob/c1ef38b0526554bceedd78001aed8e9fb86ef126/server/src/main/java/org/apache/druid/segment/indexing/DataSchema.java#L96-L102)
 ; and the PR which did introduced `timespampSpec` was the one deprecating that 
in #8823.
   If the fix would be to move from a deprecated one to a non-deprecated one I 
wouldn't had any questions/etc...but its the other way around
   
   do you know how the inconsistency could happen with the non-deprecated 
codepath? the comparision of which field leads to the issue?
   I still feel like this is just masking the issue and not stabilizes the 
non-deprecated system to be "stable" - so that it produces the same results 
with different java versions/etc.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to