cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Zlatanov (JIRA)" <>
Subject [jira] Updated: (CASSANDRA-764) bitmasks applied to SliceRange
Date Wed, 10 Feb 2010 19:58:38 GMT


Ted Zlatanov updated CASSANDRA-764:

    Attachment: 004-CASSANDRA-764-moretests.patch

- the strange column names were coming from cf.getComparator().getColumnsString(columns)).
 This should not be called in assertColumns() because the strings it generates don't match
the actual column names.  See assertBitmaskedColumns() in the latest patch for an example
of what it could do instead (show both the column's toString() and the actual name).  assertBitmaskedColumns()
is backwards compatible with assertColumns() so maybe it can just get called with an empty
list to simplify the test code.

- the tests pass the first stage, BEFORE the ColumnFamilyStore forceBlockingFlush().  They
don't pass the second stage so I'm researching that piece.

> bitmasks applied to SliceRange
> ------------------------------
>                 Key: CASSANDRA-764
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Ted Zlatanov
>            Priority: Minor
>         Attachments: 001-CASSANDRA-764-bitmasksparameter.patch, 002-CASSANDRA-764-bitmaskserialization.patch,
002-CASSANDRA-764-bitmaskserialization.patch, 002-CASSANDRA-764-bitmaskserialization.patch,
003-CASSANDRA-764-bitmasktests.patch, 004-CASSANDRA-764-moretests.patch
> Add bitmasks (OR of an array of ANDs) to the SliceRange.  Make them optional.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message