You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "lincoln-lil (via GitHub)" <gi...@apache.org> on 2024/08/03 15:01:13 UTC

Re: [PR] [FLINK-26939][Table SQL/API] Add TRANSLATE supported in SQL & Table API [flink]

lincoln-lil commented on PR #20342:
URL: https://github.com/apache/flink/pull/20342#issuecomment-2266758551

   @zzzzzzzs @snuyanzin I apologize for not seeing this pr until after I just merged the new #25122, I should have told @dylanhz to ask you guys first. 
   The #25122 only implements the original goal of `translate(expr, from, to)` which was parsed to `translate3` internally from calcite, and we don't implement the calcite's `translate` because it's parsed from a different call `TRANSLATE(value USING transcodingName)` which performs a totally different functionality`alter value from one base character set to transcodingName`. I think we can open another ticket to cover the `TRANSLATE(value USING transcodingName)`. 


-- 
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: issues-unsubscribe@flink.apache.org

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