Is it possible to include support for showing composite columns in Data Explorer in the next version? I would also be happy to see support for composite columns in column_metadata in the schema. Now Data Explorer shows 0 keyspaces if any CF has composite columns in column_metadata field (we use it to create secondary indexes).
Support for composite columns in Data Explorer
(7 posts) (4 voices)- Started 8 months ago by alexei.bakanov
- Latest reply from mbulman
- This topic is not resolved
-
The current version of OpsCenter (2.1.2) should support composite columns in the Data Explorer. If you're already on that version, can you post your schema for any column families that you think might be breaking things. Do you see any obvious errors in opscenterd.log?
Posted 8 months ago # -
alexei.bakanov
MemberYes we are on 2.1.2
For example this schema causingProblem while calling CFDataController exceptions.TypeError: sequence item 0: expected string, tuple foundwhen clicking on column family name in data explorer:
create column family Rollup1d with column_type = 'Standard' and comparator = 'CompositeType(org.apache.cassandra.db.marshal.TimeUUIDType,org.apache.cassandra.db.marshal.AsciiType)' and default_validation_class = 'FloatType' and key_validation_class = 'AsciiType' and rows_cached = 0.0 and row_cache_save_period = 0 and row_cache_keys_to_save = 2147483647 and keys_cached = 200000.0 and key_cache_save_period = 14400 and read_repair_chance = 1.0 and gc_grace = 864000 and min_compaction_threshold = 4 and max_compaction_threshold = 32 and replicate_on_write = true and row_cache_provider = 'SerializingCacheProvider' and compaction_strategy = 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy';In our development cluster we have a column family with composite column name in column_metadata. There we get 0 Keyspaces in Data Explorer with same exception but in InspectKeyspaceController. Schema for that:
create column family Inbox with column_type = 'Standard' and comparator = 'CompositeType(org.apache.cassandra.db.marshal.TimeUUIDType,org.apache.cassandra.db.marshal.AsciiType)' and default_validation_class = 'UTF8Type' and key_validation_class = 'UTF8Type' and rows_cached = 0.0 and row_cache_save_period = 0 and row_cache_keys_to_save = 0 and keys_cached = 200000.0 and key_cache_save_period = 14400 and read_repair_chance = 1.0 and gc_grace = 864000 and min_compaction_threshold = 4 and max_compaction_threshold = 32 and replicate_on_write = true and row_cache_provider = 'SerializingCacheProvider' and compaction_strategy = 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy' and column_metadata = [ {column_name : '82b41c7a-f1b2-11e1-8122-2c768ae5fa9a:owner', validation_class : UTF8Type, index_name : 'OWNER_INDEX', index_type : 0}, {column_name : '82b41c7a-f1b2-11e1-8122-2c768ae5fa9a:label1', validation_class : UTF8Type, index_name : 'LABEL1_INDEX', index_type : 0}];Posted 8 months ago # -
thobbs
AdministratorAlexei,
There does appear to be a bug with in OpsCenter 2.x related to TimeUUIDType components inside of a CompositeType. We should be able to get a fix for that into the next release; I'll post a note here when a release that includes the fix is out.
Thanks for reporting this!
Posted 8 months ago # -
The original bug mentioned here is not fixed in 2.1.3, but will be in 3.0, which is due out in February.
hjarraya: If you're not seeing the column families at all in the data modeling section, I would suspect it's due to the fact that OpsCenter doesn't currently work with column families created via CQL3, unless the "WITH COMPACT STORAGE" directive was used. Is that the case here?
Posted 3 months ago #
Reply
You must log in to post.