[
https://issues.apache.org/jira/browse/CASSANDRA-10390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14998712#comment-14998712
]
Jonathan Halliday commented on CASSANDRA-10390:
-----------------------------------------------
3.0.0> select * from mytable;
pk | myfield
----+-------------------
1 | {field_0_: 'foo'}
well, at least it renders something now, that's progress. I'd expect
{"my.field": 'foo'} rather than the weird field_0_ synthetic identifier, but
it's good enough for what I need. thanks!
> 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)
