cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3929) Support row size limits
Date Wed, 13 Mar 2013 08:32:15 GMT


Sylvain Lebresne commented on CASSANDRA-3929:

bq. How would you use this filter interface to implement something CQL-row-aware?

I'm not sure honestly. I was suggesting that as a simpler alternative to modifying the compaction
strategy API, which wouldn't be easily CQL-aware either because both solution involve dealing
with the internal storage engine. Now, it would be possible to write something CQL-aware with
the filter interface above (except maybe that we might want to provide the CFMetaData object
too), but that would have to be done manually (typically using the ColumnCounter class, you
could reasonably easily start "dropping" columns once you reach the nth CQL-row).
> Support row size limits
> -----------------------
>                 Key: CASSANDRA-3929
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jonathan Ellis
>            Priority: Minor
>              Labels: ponies
>             Fix For: 2.0
>         Attachments: 3929_b.txt, 3929_c.txt, 3929_d.txt, 3929_e.txt, 3929_f.txt, 3929_g_tests.txt,
3929_g.txt, 3929.txt
> We currently support expiring columns by time-to-live; we've also had requests for keeping
the most recent N columns in a row.

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:

View raw message