I've found the answer. I am using the CustomScoreQuery and the doc id
inconsistency is because of the segment based IndexReader concept.
On Fri, Jul 27, 2012 at 3:56 PM, Phanindra R wrote:
>
> Hi,
> This is the first time I am encountering this kind of scenario. Lack
> o
Hi,
This is the first time I am encountering this kind of scenario. Lack
of knowledge might be the reason for my surprise.
- I am using myIndexWriter.explain(Query q, int docId).
- For the same query, the explanation for most of the docs is exactly what
it's supposed to be. However, for som
Thanks a lot Aditya and Andrzej .. Your responses were really helpful.
On Fri, Jul 27, 2012 at 6:15 AM, Andrzej Bialecki wrote:
> On 26/07/2012 22:04, Phanindra R wrote:
>
>> Thanks for the reply Abdul.
>>
>> I was exploring the API and I think we can retrieve all t
) So, we have the term-doc pairs at this point.
Is there any better approach other than the above forever-taking procedure?
Thanks,
Phanindra
On Thu, Jul 26, 2012 at 11:46 AM, in.abdul wrote:
> No , it's not possible to get the data which not stored ..
> On Jul 26, 2012 10:27 PM, &
Hi,
I've an index to analyze (manually). Unfortunately, I cannot rebuild
the index. Some of the fields are 'unstored'. I was wondering whether
there's any way to get the terms from an unstored field for each doc.
Positional information is not necessary. Lucene version is 3.5.
The reason am tr
