[
https://issues.apache.org/jira/browse/LUCENE-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12881500#action_12881500
]
Trejkaz commented on LUCENE-2348:
---------------------------------
That does solve the specific issue I resolved... I wonder if I need to open a
new ticket now for our real problem, because there are two things not solved by
that approach:
1. If your filterable data is in another store (e.g. a database), then you
would still need either some way to get to the top level reader or a way to
know what its offset is, but there is no way to get that information from the
reader which was passed in.
2. If you want to return the *newest* item instead of the *oldest* item, it
will be too late if getStatefulDocIdSet for an earlier call has already
returned the older one.
> DuplicateFilter incorrectly handles multiple calls to getDocIdSet for segment
> readers
> -------------------------------------------------------------------------------------
>
> Key: LUCENE-2348
> URL: https://issues.apache.org/jira/browse/LUCENE-2348
> Project: Lucene - Java
> Issue Type: Bug
> Components: contrib/*
> Affects Versions: 2.9.2
> Reporter: Trejkaz
> Attachments: LUCENE-2348.patch
>
>
> DuplicateFilter currently works by building a single doc ID set, without
> taking into account that getDocIdSet() will be called once per segment and
> only with each segment's local reader.
--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
