cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Semeria (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-3340) Add a default range to queries
Date Mon, 10 Oct 2011 15:03:29 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-3340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Semeria updated CASSANDRA-3340:
-------------------------------------

    Description: 
Often we find ourselves having to make two nearly identical queries when in theory one could
suffice.

Assuming we're storing json properites in discrete columns, a typical user row might look
like this:

default:name, default:age,... address:street, address:number,...  contacts:email, contacts,phone,
contacts:mobile....

To extract the contacts for a given user we would pass startCol = 'contacts', endCol = 'contacts'
+ charAfter(':')

However, we frequently also need to retrieve the properties under the 'default' key. To do
this we currently need to make a second nearly identical query, with the only difference that
startCol and endCol now refer to 'default'

It would be nice if we could pass in a default range along with the standard range during
queries. 

It seems inefficient to make Cassandra extract the same row(s) twice, with the only difference
being how they are filtered.

I'm not in a position to estimate how many other users might find this functionality useful,
all I can say is that we certainly would.

Thanks. 


  was:
Often we find ourselves having to make two nearly identical queries when in theory one could
suffice.

Assuming we're storing json properites in discrete columns, a typical user row might look
like this:

default:name, default:age,... address:street, address:number,...  contacts:email, contacts,phone,
contacts:mobile....

To extract the contacts for a given user we would pass startCol = 'contacts', endCol = 'contacts'
+ charAfter(':')

However, we frequently also need to retrieve the properties under the 'default' key. To do
this we currently need to make a second nearly identical query, with the only difference that
startCol and endCol now refer to 'default'

It would be nice if we could pass in a default range along with the standard range during
queries. 

It seems inefficient to make Cassandra extract the same row(s) twice, with the only difference
being how they are filtered.

I'm not in a position to estimate how many other users might find this functionality, all
I can say is that we certainly would.

Thanks. 


    
> Add a default range to queries
> ------------------------------
>
>                 Key: CASSANDRA-3340
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3340
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: David Semeria
>            Priority: Minor
>
> Often we find ourselves having to make two nearly identical queries when in theory one
could suffice.
> Assuming we're storing json properites in discrete columns, a typical user row might
look like this:
> default:name, default:age,... address:street, address:number,...  contacts:email, contacts,phone,
contacts:mobile....
> To extract the contacts for a given user we would pass startCol = 'contacts', endCol
= 'contacts' + charAfter(':')
> However, we frequently also need to retrieve the properties under the 'default' key.
To do this we currently need to make a second nearly identical query, with the only difference
that startCol and endCol now refer to 'default'
> It would be nice if we could pass in a default range along with the standard range during
queries. 
> It seems inefficient to make Cassandra extract the same row(s) twice, with the only difference
being how they are filtered.
> I'm not in a position to estimate how many other users might find this functionality
useful, all I can say is that we certainly would.
> Thanks. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message