Jackie-Jiang commented on issue #12612: URL: https://github.com/apache/pinot/issues/12612#issuecomment-2099335786
@GopsAB Yes. The root cause is that a lot of date time functions can only take TIMESTAMP as input. In V1, `TIMESTAMP` and `LONG` can be used interchangeable because the internal storage are the same. It is not the same case in V2 which is strong typed. Using `LONG` column as input can cause error during planning. IMO the correct fix should be to make sure all functions are SQL compatible, i.e. the return value matches the standard SQL definition -- 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: commits-unsubscr...@pinot.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For additional commands, e-mail: commits-h...@pinot.apache.org
