chenboat commented on issue #3513: DATETIMECONVERT udf does not work for customized timezone and bucket size > 1 day URL: https://github.com/apache/incubator-pinot/issues/3513#issuecomment-440163118 @npawar Thanks for the investigation. It really helps. In our use cases, the client first wanted to use "1 week" as the bucket size or granularity. When they found out it did not work because 'week' is not supported, they switched to use 7 days (probably without understanding the semantics). So the ideal fix is to make **week** work as a legit bucket unit because alignment by calendar weeks is more intuitive to users. Is it possible to do it? Otherwise, we can spell out the plausible combinations of parameters in this UDF[doc](https://github.com/apache/incubator-pinot/wiki/dateTimeConvert-UDF) -- I guess the users find 1:WEEKS there. As for fixing the issue with the granularity in terms of **days**, I would say both (1) and (2) are fine as long as we define it clearly in the same UDF doc. As far as I know, there is no well known notion about how to align a general N days bucket: so most of users can accept a definition and decide if it works for them. (3) is not working for us in this case because our users do want to the Pinot feature to convert the time to a local timezone (e.g, Chicago).
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
