[
https://issues.apache.org/jira/browse/CASSANDRA-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12898071#action_12898071
]
Jonathan Ellis commented on CASSANDRA-1383:
-------------------------------------------
possibly splitting this into
describe_keyspaces (returns set of strings)
describe_keyspace (returns KsDef for single KS)
would be more convenient.
> Change describe_keyspace and describe_keyspaces to return hashed arrays or
> hashed maps instead of numerically indexed arrays
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-1383
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1383
> Project: Cassandra
> Issue Type: Improvement
> Affects Versions: 0.7 beta 1
> Environment: CentOD 5.2
> Reporter: Arya Goudarzi
>
> I noticed a recent change in the structure of data returned from
> describe_keyspaces and describe_keyspaces API calls. They now return all
> information associated with them in a numerically indexed arrays, vs before
> they used to return a hashmap with Keyspace/CF name as the key. The old
> method was useful because the developer could do lookups by names which is
> significantly faster. Now developer has to iterate through the entire KsDef
> object to detect if some Ks or CF exists. This is inefficient. I recommend
> the structure returned by the above two service calls to be hashed by the
> actual Ks/CF name.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
