You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2019/11/04 06:53:50 UTC
[GitHub] [flink] KurtYoung commented on issue #10035:
[FLINK-14080][table-planner-blink] Introduce SqlTimestamp as internal
representation of TIMESTAMP_WITHOUT_TIME_ZONE
KurtYoung commented on issue #10035: [FLINK-14080][table-planner-blink] Introduce SqlTimestamp as internal representation of TIMESTAMP_WITHOUT_TIME_ZONE
URL: https://github.com/apache/flink/pull/10035#issuecomment-549239819
One question just pop up, what responsibility of `precision` field inside `SqlTimestampSerializer`?
Let's say I created a SqlTimestamp with `fromEpochMillis(123)`, and created a `SqlTimestampSerializer` with precision 2. And after I serialize and deserialize, I still get a SqlTimestamp which actually still can get 123 millis out of it.
I'm wondering what kind of purpose does precision in SqlTimestampSerializer want to achieve?
----------------------------------------------------------------
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
With regards,
Apache Git Services