yuxiqian commented on PR #3511: URL: https://github.com/apache/flink-cdc/pull/3511#issuecomment-2272462085
Seems Flink TIMESTAMP has a range limit from 0000-01-01 00:00:00.000000000 to 9999-12-31 23:59:59.999999999[1]. According to current binary encoding format, the millisecond part will be `253,402,300,799,999` at most, far less than the long limit (`9,223,372,036,854,775,807`). The higher 16 bits of `long` is actually wasted. Is it possible to encode the "is compact or not" information on these unused higher bits? Ignore my comment if it's too hard to implement. [1] https://nightlies.apache.org/flink/flink-docs-release-1.19/docs/dev/table/types/ -- 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]
