[
https://issues.apache.org/jira/browse/CASSANDRA-7399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14039007#comment-14039007
]
Tyler Hobbs commented on CASSANDRA-7399:
----------------------------------------
The 2.1 patch looks good.
With the 1.2 patch, DynamicCompositeType can't be parsed (it doesn't like the
"=>" bits). I'm not sure if we care enough about DynamicComposite type to fix
this for 1.2 and 2.0, but if so, we need to patch the bundled cqltypes.py to
change:
{code}
casstype_scanner = re.Scanner((
(r'[()]', lambda s, t: t),
(r'[a-zA-Z0-9_.:]+', lambda s, t: t),
(r'[\s,]', None),
))
{code}
to
{code}
casstype_scanner = re.Scanner((
(r'[()]', lambda s, t: t),
(r'[a-zA-Z0-9_.:=>]+', lambda s, t: t),
(r'[\s,]', None),
))
{code}
> cqlsh: describe table shows wrong data type for CompositeType
> -------------------------------------------------------------
>
> Key: CASSANDRA-7399
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7399
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Reporter: Robert Stupp
> Assignee: Mikhail Stepura
> Fix For: 1.2.17, 2.0.9, 2.1 rc2
>
> Attachments: CASSANDRA-1.2-7399.patch, CASSANDRA-2.1-7399.patch
>
>
> {{DESCRIBE}} for {{CompositeType}} produces wrong output.
> Currently:
> {noformat}
> CREATE TABLE compo.comp (
> id int PRIMARY KEY,
> comp 'org.apache.cassandra.db.marshal.CompositeType'<int, text>
> )...
> {noformat}
> Correct:
> {noformat}
> CREATE TABLE compo.comp (
> id int PRIMARY KEY,
> comp 'org.apache.cassandra.db.marshal.CompositeType(Int32Type,UTF8Type)'
> )...
> {noformat}
> Means:
> 1. use normal brackets instead of {{<>}}
> 1. use C* type names instead of CQL3 names
> 1. move types inside quoted
--
This message was sent by Atlassian JIRA
(v6.2#6252)
