[
https://issues.apache.org/jira/browse/IGNITE-14545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17328580#comment-17328580
]
Aleksey Plekhanov commented on IGNITE-14545:
--------------------------------------------
# It will work much slower them standard functions for all cases (including
cases where there are no 32-bit chars in the string)
# In this case, we should write our own implementation for all string
functions in Calcite (including used SqlLibrary dialects). There are plenty of
such functions and their aliases (char_length, character_length, substring,
lpad, rpad, locate, strpos, left, right, etc) and there is a chance to miss
something, or chance that some new string function will be added to calcite.
> Calcite engine. Unicode literal not supported
> ---------------------------------------------
>
> Key: IGNITE-14545
> URL: https://issues.apache.org/jira/browse/IGNITE-14545
> Project: Ignite
> Issue Type: Bug
> Reporter: Taras Ledkov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Unicode literal not supported.
> e.g. {{SELECT <any_string_with_unicode_symbols>}}
> Tests:
> {{aggregate/aggregates/test_aggr_string.test}}
> {{types/string/test_unicode.test_ignored}}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
