[
https://issues.apache.org/jira/browse/IGNITE-14545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17329126#comment-17329126
]
Konstantin Orlov commented on IGNITE-14545:
-------------------------------------------
# it's true, so may be it would be better to toggle supporting somehow or even
add under different name
# it's not true. We need to override only those functions sensible to the size
of the character, like length, substring, strpos.
In fact, I don't mind to leave current solution. But then we need to create
separate ticket with lower priority to fix the rest issues related to the
strings containing 32-bit characters.
> 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)
