JsonRowSerializationSchema unable to parse TIMESTAMP_LTZ fields

[Surendra Lalwani <su...@swiggy.in>]

Hi Team,

JsonRowSerializationSchema is unable to parse fields with type
TIMESTAMP_LTZ, seems like this is not handled properly. While trying to
fire a simple query Select current_timestamp from table_name , it gives
error that Could not serialize row and asks to add shaded flink dependency
for jsr-310. Seems like in the Serializer , the JavaTimeModule is not added.

-- 

IMPORTANT NOTICE: This e-mail, including any attachments, may contain 
confidential information and is intended only for the addressee(s) named 
above. If you are not the intended recipient(s), you should not 
disseminate, distribute, or copy this e-mail. Please notify the sender by 
reply e-mail immediately if you have received this e-mail in error and 
permanently delete all copies of the original message from your system. 
E-mail transmission cannot be guaranteed to be secure as it could be 
intercepted, corrupted, lost, destroyed, arrive late or incomplete, or 
contain viruses. Company accepts no liability for any damage or loss of 
confidential information caused by this email or due to any virus 
transmitted by this email or otherwise.

Re: JsonRowSerializationSchema unable to parse TIMESTAMP_LTZ fields

[Matthias Pohl <ma...@ververica.com>]

For documentation purposes: Surendra started a discussion in FLINK-25411
[1].

[1] https://issues.apache.org/jira/browse/FLINK-25411

On Wed, Dec 22, 2021 at 9:51 AM Surendra Lalwani <su...@swiggy.in>
wrote:

>
> Hi Team,
>
> JsonRowSerializationSchema is unable to parse fields with type
> TIMESTAMP_LTZ, seems like this is not handled properly. While trying to
> fire a simple query Select current_timestamp from table_name , it gives
> error that Could not serialize row and asks to add shaded flink dependency
> for jsr-310. Seems like in the Serializer , the JavaTimeModule is not added.
>
>
> ------------------------------
> IMPORTANT NOTICE: This e-mail, including any attachments, may contain
> confidential information and is intended only for the addressee(s) named
> above. If you are not the intended recipient(s), you should not
> disseminate, distribute, or copy this e-mail. Please notify the sender by
> reply e-mail immediately if you have received this e-mail in error and
> permanently delete all copies of the original message from your system.
> E-mail transmission cannot be guaranteed to be secure as it could be
> intercepted, corrupted, lost, destroyed, arrive late or incomplete, or
> contain viruses. Company accepts no liability for any damage or loss of
> confidential information caused by this email or due to any virus
> transmitted by this email or otherwise.