[
https://issues.apache.org/jira/browse/FLINK-25187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17459829#comment-17459829
]
Francesco Guardiani commented on FLINK-25187:
---------------------------------------------
> It's the analogy of padding only for CHAR but not for VARCHAR nor STRING.
In CHAR we force the padding as it affects correctness, but is CHAR not padding
affecting correctness in any way? Can you show an example?
> Maybe we can also have add this constraint enforcer for the sinks as well
I think we only need the constraint enforcer, without modifying the cast rule,
per comment above
> Apply padding for BINARY(<precision>)
> -------------------------------------
>
> Key: FLINK-25187
> URL: https://issues.apache.org/jira/browse/FLINK-25187
> Project: Flink
> Issue Type: Sub-task
> Reporter: Marios Trivyzas
> Priority: Major
>
> When the resulting byte array that is generated for a *CAST(XXX AS
> BINARY(<precision>)* has *length* < {*}precision{*}, then it should be padded
> with *0* to the right, to end up with a byte array of *precision* length,
> similarly to padding with spaces for {*}CHAR(<precision>){*}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
