[
https://issues.apache.org/jira/browse/CASSANDRA-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792697#action_12792697
]
Eric Evans commented on CASSANDRA-642:
--------------------------------------
"Your last statement makes me feel as though I am missing something with
get_range_slice on the API. I am still coming up to speed on the types
available to the CompareWith configuration, would a correct slicing approach
have to appropriately handle whatever "AbstractType" implementation showed up?
(I may have just answered my own question there but please do let me know if I
am off on that mark)."
Well, this is what I meant when I said that the cli was not a good solution for
serious work (due to it being text-based). We pass around byte[]
representations of AbstractType extending objects for column and super column
names and translating these to and from strings isn't The Way. :)
What I was referring to in my last statement is that there are column slices
against a record (by key), and column slices against ranges of records (by
multiple keys), and both can be done with predicates. I was saying that "slice"
is generic enough command term that it should support all forms (and that that
would be Hard to do well ;).
> Implement get_range_slice in CliClient
> --------------------------------------
>
> Key: CASSANDRA-642
> URL: https://issues.apache.org/jira/browse/CASSANDRA-642
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Nate McCall
> Priority: Minor
> Fix For: 0.5
>
> Attachments: patch.txt
>
>
> Provide access to get_range_slice API method in CliClient
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
