[
https://issues.apache.org/jira/browse/LUCENE-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12653959#action_12653959
]
Marvin Humphrey commented on LUCENE-1476:
-----------------------------------------
> It would be great if instead of relying on Lucene to manage the
> deletedDocs file, the API would be pluggable
In LUCENE-1478, "IndexComponent" was proposed, with potential subclasses
including PostingsComponent, LexiconComponent/TermDictComponent,
TermVectorsComponent, and so on. Since then, it has become apparent that
SnapshotComponent and DeletionsComponent also belong at the top level.
In Lucy/KS, these would all be specified within a Schema:
{code}
class MySchema extends Schema {
DeletionsComponent deletionsComponent() {
return new DocIdBitSetDeletionsComponent();
}
void initFields() {
addField("title", "text");
addField("content", "text");
}
Analyzer analyzer() {
return new PolyAnalyzer("en");
}
}
{code}
Mike, you were planning on managing IndexComponents via IndexReader and
IndexWriter constructor args, but won't that get unwieldy if there are too many
components? A Schema class allows you to group them together. You don't have
to use it to manage fields the way KS does -- just leave that out.
> BitVector implement DocIdSet
> ----------------------------
>
> Key: LUCENE-1476
> URL: https://issues.apache.org/jira/browse/LUCENE-1476
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Index
> Affects Versions: 2.4
> Reporter: Jason Rutherglen
> Priority: Trivial
> Attachments: LUCENE-1476.patch
>
> Original Estimate: 12h
> Remaining Estimate: 12h
>
> BitVector can implement DocIdSet. This is for making
> SegmentReader.deletedDocs pluggable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
