[
https://issues.apache.org/jira/browse/CASSANDRA-20235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18014077#comment-18014077
]
Ruslan Fomkin commented on CASSANDRA-20235:
-------------------------------------------
{quote}It's good to fix it after CASSANDRA-20389 to avoid conflicts.
{quote}
After this it's necessary to remove a check in
CreateIndexStatement.validateIndexTarget, which will be obsolete with
completing this ticket.
> Relax limitation on column names for SAI
> ----------------------------------------
>
> Key: CASSANDRA-20235
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20235
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Feature/SAI
> Reporter: Ruslan Fomkin
> Assignee: Ruslan Fomkin
> Priority: Normal
> Fix For: 5.0.x, 5.1
>
>
> For a table:
> {code:java}
> CREATE TABLE quoted (
> key text,
> "user-age" int,
> PRIMARY KEY (key)
> );{code}
> creating index:
> {code:java}
> CREATE CUSTOM INDEX quoted_userage ON quoted ("user-age")
> USING 'StorageAttachedIndex';{code}
> fails with:
> {code:java}
> InvalidRequest: Error from server: code=2200 [Invalid query] message="Column
> 'user-age' is longer than the permissible name length of 222 characters or
> contains non-alphanumeric-underscore characters"{code}
> It will improve usability if SAI can be created on column names, which are
> already supported during table creation. I.e., the above use case works.
> Is there any specific reason why a quoted column name with non-alpha-numeric
> chars will not work for SAI?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
