[
https://issues.apache.org/jira/browse/IGNITE-24584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-24584:
--------------------------------------
Description:
After IGNITE-24021 IgniteNameUtils does not accept identifiers like _id, $id
and so on, but sql parser accept such identifiers.
*Need to*
We need to learn which SQL identifiers are valid from Calcite's point of view
and make IgniteNameUtils compatible with them.
*Or*
Prohibit invalid identifiers at the SQL parser level.
was:
After IGNITE-24021 IgniteNameUtils does not accept identifiers like _id, $id
and so on, but sql parser accept such identifiers.
*Need to*
We need to learn which SQL identifiers are valid from Calcite's point of view
and make IgniteNameUtils compatible with them.
*Or *
Prohibit invalid identifiers at the SQL parser level.
> Sql. IgniteNameUtils.parseIdentifier must be compatible with Calcite's sql
> identifier.
> --------------------------------------------------------------------------------------
>
> Key: IGNITE-24584
> URL: https://issues.apache.org/jira/browse/IGNITE-24584
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Reporter: Pavel Pereslegin
> Priority: Major
> Labels: ignite-3
>
> After IGNITE-24021 IgniteNameUtils does not accept identifiers like _id, $id
> and so on, but sql parser accept such identifiers.
> *Need to*
> We need to learn which SQL identifiers are valid from Calcite's point of view
> and make IgniteNameUtils compatible with them.
> *Or*
> Prohibit invalid identifiers at the SQL parser level.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
