[
https://issues.apache.org/jira/browse/CASSANDRA-10390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14998742#comment-14998742
]
Adam Holmberg commented on CASSANDRA-10390:
-------------------------------------------
Yes. What I did here was enough to avoid blowing up when invalid Python
identifiers appear as field names. To go as far as what you mention will
require a lot more work, and change the return type semantics. I punted on that
because of the level of effort and the fact that it's only come up once in the
years since UDTs were introduced. If we feel it's worth the effort this can be
addressed in a follow-on driver ticket.
> inconsistent quoted identifier handling in UDTs
> -----------------------------------------------
>
> Key: CASSANDRA-10390
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10390
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Environment: 2.2.1
> Reporter: Jonathan Halliday
> Assignee: Sam Tunnicliffe
> Fix For: 2.2.x
>
>
> > create keyspace test with replication = {'class': 'SimpleStrategy',
> > 'replication_factor': 1 } ;
> > create type if not exists mytype ("my.field" text);
> > desc keyspace; -- observe that mytype is listed
> > create table mytable (pk int primary key, myfield frozen<mytype>);
> > desc keyspace; -- observe that mytype is listed, but mytable is not.
> > select * from mytable;
> ValueError: Type names and field names can only contain alphanumeric
> characters and underscores: 'my.field'
> create table myothertable (pk int primary key, "my.field" text);
> select * from myothertable; -- valid
> huh? It's valid to create a field of a table, or a field of a type, with a
> quoted name containing non-alpha chars, but it's not valid to use a such a
> type in a table? I can just about live with that though it seems
> unnecessarily restrictive, but allowing creation of such a table and then
> making it invisible/unusable definitely seems wrong.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
