You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@lucene.apache.org by rahul_k123 <vi...@gmail.com> on 2008/12/16 21:14:32 UTC
Document.getBinaryValue returning null after upgrading to 2.4 for
the data which was indexed using 2.3.1
The data was indexed using 2.3.1 as follows
doc.add(new Field(Fields.DETAILS, byte[] bytes,
Field.Store.YES));
When i reindex this particular item using 2.4 and when i try to retrive it,
it works fine.
Then for the items which were indexed using 2.3.1 and not reindexed using
2.4
the following call
doc.getBinaryValue(Fields.DETAILS)
is returning null.
So, except for the documents which were reindexed using 2.4 the search is
failing.
One more thing when i didn't reindex any of the documents using 2.4 , the
search worked fine using 2.4.
Any ideas why this is happening.
--
View this message in context: http://www.nabble.com/Document.getBinaryValue-returning-null-after-upgrading-to-2.4-for-the-data-which-was-indexed-using-2.3.1-tp21040857p21040857.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org
Re: Document.getBinaryValue returning null after upgrading to 2.4
for the data which was indexed using 2.3.1
Posted by Andrzej Bialecki <ab...@getopt.org>.
rahul_k123 wrote:
> Thanks for the response. I guess this is the problem, but not sure whether it
> happens on optimize.
>
> This is what happening exactly
>
> the field is still present (not null) and is marked as binary, but the data
> is not there - Field.getBinaryLength() returns 0.
It may or it may not be the same bug ... I'm not sure, but the symptoms
are the same. The bug would occur also during partial merges, which
Lucene initiates itself in the background, even if you don't call
IndexWriter.optimize().
Please create a JIRA issue describing the symptoms (precisely!), and the
versions of Lucene involved.
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __________________________________
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http://www.sigram.com Contact: info at sigram dot com
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org
Re: Document.getBinaryValue returning null after upgrading to 2.4
for the data which was indexed using 2.3.1
Posted by rahul_k123 <vi...@gmail.com>.
Thanks for the response. I guess this is the problem, but not sure whether it
happens on optimize.
This is what happening exactly
the field is still present (not null) and is marked as binary, but the data
is not there - Field.getBinaryLength() returns 0.
Andrzej Bialecki wrote:
>
> rahul_k123 wrote:
>> The data was indexed using 2.3.1 as follows
>>
>> doc.add(new Field(Fields.DETAILS, byte[] bytes,
>> Field.Store.YES));
>>
>> When i reindex this particular item using 2.4 and when i try to retrive
>> it,
>> it works fine.
>>
>> Then for the items which were indexed using 2.3.1 and not reindexed using
>> 2.4
>>
>> the following call
>>
>> doc.getBinaryValue(Fields.DETAILS)
>>
>> is returning null.
>
> Is it returning null or byte[] with length of 0?
>
>> So, except for the documents which were reindexed using 2.4 the search is
>> failing.
>>
>>
>>
>> One more thing when i didn't reindex any of the documents using 2.4 , the
>> search worked fine using 2.4.
>>
>>
>> Any ideas why this is happening.
>
> No idea - but perhaps this is somehow related:
> https://issues.apache.org/jira/browse/LUCENE-1452
>
> --
> Best regards,
> Andrzej Bialecki <><
> ___. ___ ___ ___ _ _ __________________________________
> [__ || __|__/|__||\/| Information Retrieval, Semantic Web
> ___|||__|| \| || | Embedded Unix, System Integration
> http://www.sigram.com Contact: info at sigram dot com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Document.getBinaryValue-returning-null-after-upgrading-to-2.4-for-the-data-which-was-indexed-using-2.3.1-tp21040857p21043111.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org
Re: Document.getBinaryValue returning null after upgrading to 2.4
for the data which was indexed using 2.3.1
Posted by Andrzej Bialecki <ab...@getopt.org>.
rahul_k123 wrote:
> The data was indexed using 2.3.1 as follows
>
> doc.add(new Field(Fields.DETAILS, byte[] bytes,
> Field.Store.YES));
>
> When i reindex this particular item using 2.4 and when i try to retrive it,
> it works fine.
>
> Then for the items which were indexed using 2.3.1 and not reindexed using
> 2.4
>
> the following call
>
> doc.getBinaryValue(Fields.DETAILS)
>
> is returning null.
Is it returning null or byte[] with length of 0?
> So, except for the documents which were reindexed using 2.4 the search is
> failing.
>
>
>
> One more thing when i didn't reindex any of the documents using 2.4 , the
> search worked fine using 2.4.
>
>
> Any ideas why this is happening.
No idea - but perhaps this is somehow related:
https://issues.apache.org/jira/browse/LUCENE-1452
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __________________________________
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http://www.sigram.com Contact: info at sigram dot com
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org