cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Yaskevich (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-10681) make index building pluggable via IndexBuildTask
Date Fri, 20 Nov 2015 00:04:11 GMT


Pavel Yaskevich updated CASSANDRA-10681:
    Attachment: 0001-add-table-support-for-multi-table-builds.patch

I'm attaching to alternative approaches to the problem of multi-index builds, "make index
building pluggable" just added a method to IndexBuildTask which allows SIM to group indexes
of specific class to one build task.
"add table-support" patch follows the same approach but is more explicit about the grouping

[~beobal] WDYT?

> make index building pluggable via IndexBuildTask
> ------------------------------------------------
>                 Key: CASSANDRA-10681
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Local Write-Read Paths
>            Reporter: Pavel Yaskevich
>            Assignee: Pavel Yaskevich
>            Priority: Minor
>              Labels: sasi
>             Fix For: 3.x
>         Attachments: 0001-add-table-support-for-multi-table-builds.patch, 0001-make-index-building-pluggable-via-IndexBuildTask.patch
> Currently index building assumes one and only way to build all of the indexes - through
SecondaryIndexBuilder - which merges all of the sstables together, collates columns etc. Such
works fine for built-in indexes but not for SASI since it's attaches to every SSTable individually.
We need a "IndexBuildTask" interface (based on CompactionInfo.Holder) to be returned from
Index on demand to give power to SI interface implementers to decide how build should work.
This might be less effective for CassandraIndex, since this effectively means that collation
will have to be done multiple times on the same data, but  nevertheless is a good compromise
for clean interface to outside world.

This message was sent by Atlassian JIRA

View raw message