[ https://issues.apache.org/jira/browse/CASSANDRA-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13893367#comment-13893367 ]
Aleksey Yeschenko commented on CASSANDRA-6305: ---------------------------------------------- Mostly LGTM, although I'm really not a fan of running _refresh_utype_dict() after every command. Can we only trigger it upon failing to find a user type in the dictionary and ALTER/CREATE/DROP type, etc.? Obviously it's not bulletproof, since schema changes can come from anywhere at any time, but neither is the current solution. With CASSANDRA-6307 though, we'd just be able to listen to schema change events and react accordingly. > cqlsh support for User Types > ---------------------------- > > Key: CASSANDRA-6305 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6305 > Project: Cassandra > Issue Type: New Feature > Reporter: Aleksey Yeschenko > Assignee: Mikhail Stepura > Labels: cqlsh > Fix For: 2.1 > > Attachments: trunk-6305-1.patch > > > We need cqlsh support for several things: > 1. Autocomplete for UPDATE/INSERT/SELECT > 2. Autocomplete for ALTER TYPE/CREATE TYPE/DROP TYPE > 3. Proper decoding of UserType values (currently showing the encoded blob) > 4. Support UserTypes in DESCRIBE > 5. Separate DESCRIBE TYPES|TYPE <name> cmds -- This message was sent by Atlassian JIRA (v6.1.5#6160)