[GitHub] [iceberg] rdblue commented on issue #417: Adding support for time-based partitioning on long column type

[GitBox <gi...@apache.org>]

rdblue commented on issue #417:
URL: https://github.com/apache/iceberg/issues/417#issuecomment-702409093


   I don't think I understand why you prefer extending partition specs instead of promoting from a long to a timestamp. To be clear, I'm not suggesting a solution that requires adding a new field set in ETL, or an additional derived field, or changing the way data is stored. I'm suggesting that you can convert an existing long field into a timestamp. New data would be written as a regular timestamp, existing data would be interpreted correctly and would appear to be a timestamp.
   
   Do you want to store data as a long directly and not use it as a timestamp? If so, what is the use case for keeping the data as it is and not using timestamp?


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org