cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergio Bossa (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-13075) Indexer is not correctly invoked when building indexes over sstables
Date Tue, 17 Jan 2017 17:23:26 GMT


Sergio Bossa commented on CASSANDRA-13075:


I believe there are a few problems with your patch:

* [Passing|]
the partition columns for the metadata definition is subtly different than passing the columns
for the read partition, as the latter could be a subset of the former (at least according
to javadocs and a brief code inspection); I'm not sure how much it matters in practice, but
that could potentially lead to unwanted index calls.
* [Processing|]
the collected range tombstones inside the loop, piggybacking on the fact the loop itself will
do one more iteration after exhaustion, doesn't actually work, that is, it seems range tombstones
are never processed; this can be easily verified by checking range tombstones [here|]
(as this test _should_ check for range tombstones, unless I'm missing something?).
* Even if the last point worked, I believe that would lead to a duplicate {{begin}} and {{finish}}
call for range tombstones.
* [Unused|]?

> Indexer is not correctly invoked when building indexes over sstables
> --------------------------------------------------------------------
>                 Key: CASSANDRA-13075
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Sergio Bossa
>            Assignee: Alex Petrov
>            Priority: Critical
>         Attachments:
> Following CASSANDRA-12796, {{SecondaryIndexManager#indexPartition()}} calls each {{Indexer}}
{{begin}} and {{finish}} methods multiple times per partition (depending on the page size),
as {{PartitionIterators#getOnlyElement()}} returns an empty partition even when the iterator
is exhausted.
> This leads to bugs for {{Indexer}} implementations doing actual work in those  methods,
but even worse, it provides the {{Indexer}} the same input of an empty partition containing
only a non-live partition deletion, as the {{Indexer#partitionDelete()}} method is *not* actually
> My proposed solution:
> 1) Stop the iteration before the empty partition is returned and ingested into the {{Indexer}}.
> 2) Actually call the {{Indexer#partitionDelete()}} method inside {{SecondaryIndexManager#indexPartition()}}
(which requires to use a filtered iterator so it actually contains the deletion info).

This message was sent by Atlassian JIRA

View raw message