[
https://issues.apache.org/jira/browse/BLUR-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13667148#comment-13667148
]
Aaron McCurry edited comment on BLUR-95 at 5/25/13 6:16 PM:
------------------------------------------------------------
1. Yes I agree.
2. Yes I think so.
3. If there is a table with 2 shards and you try to add rowids "2" it the
shard-00000000 (the 0 shard) it should throw an error. Rowid "1" in the same
test should pass. You can calculate this by:
BlurPartitioner partitioner = new BlurPartitioner();
System.out.println(partitioner.getShard("1", 2));
System.out.println(partitioner.getShard("2", 2));
System.out.println(partitioner.getShard("3", 2));
Thanks!
Aaron
was (Author: amccurry):
1. Yes I agree.
2. Yes I think so.
3. If there is a table with 2 shards and you try to add rowids "2" it the
shard-00000000 (the 0 shard) it should throw an error. Rowid "1" in the same
test should pass. You can calculate this by:
BlurPartitioner partitioner = new BlurPartitioner();
System.out.println(partitioner.getShard("1", 2));
System.out.println(partitioner.getShard("2", 2));
System.out.println(partitioner.getShard("3", 2));
> IndexImporter class - add a double check on the rowid to validate the index.
> ----------------------------------------------------------------------------
>
> Key: BLUR-95
> URL: https://issues.apache.org/jira/browse/BLUR-95
> Project: Apache Blur
> Issue Type: Improvement
> Affects Versions: 0.1.5
> Reporter: Aaron McCurry
> Fix For: 0.1.5
>
> Attachments: 0001-BLUR-ID-95-double-check-on-the-rowid.patch,
> 0001-BLUR-ID-95-Double-check-on-the-rowid.patch
>
>
> In the IndexImporter add a double check to the importer that validates the
> rowids in the import are valid ids for the given shard. This can be done
> when the rowids in the new index are iterated over during the delete phase.
> A BlurPartitioner class can valid the rowid should be in the given shard.
--
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
