cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T Jake Luciani (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-5184) Support server side operations on evaluating queries
Date Thu, 24 Jan 2013 15:23:12 GMT

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

T Jake Luciani updated CASSANDRA-5184:
--------------------------------------

    Description: 
Now that CQL3 makes it simple to create a table within a traditional cassandra row
there are many kind of simple operations we'd like to perform as a query is being evaluated.
 Since the query sticks to a single node and it is effectively a sequential scan.  

If we piggy back a small function to evaluate each matching column then we could implement
things like timeseries filters and efficient versions of count() min() max() and sum()

I wanted to open the door to further discussion.

  was:

Now that CQL3 makes it simple to create a table within a traditional cassandra row
there are many kind of simple operations we'd like to perform as a query is being evaluated.
 Since the query sticks to a single node and it is effectively a sequential scan.  

If we piggy back a small function to evaluate each matching column then we could implement
things like timeseries filters and efficient versions of count() min() max() and sum()

I don't have a design other than this though but I wanted to open the door to further discussion.

    
> Support server side operations on evaluating queries
> ----------------------------------------------------
>
>                 Key: CASSANDRA-5184
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5184
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: T Jake Luciani
>             Fix For: 2.0
>
>
> Now that CQL3 makes it simple to create a table within a traditional cassandra row
> there are many kind of simple operations we'd like to perform as a query is being evaluated.
 Since the query sticks to a single node and it is effectively a sequential scan.  
> If we piggy back a small function to evaluate each matching column then we could implement
things like timeseries filters and efficient versions of count() min() max() and sum()
> I wanted to open the door to further discussion.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message