You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by Jyothsna Bavisetti <jy...@oracle.com> on 2019/11/04 19:07:09 UTC

RE: Lucene index upgrade from 4.6 to 8 facing issue

Hi All,

Please help me with below error:
java.lang.IllegalStateException: unexpected docvalues type NONE for field 'case.id' (expected one of [BINARY, SORTED]). Re-index with correct docvalues type.
	at org.apache.lucene.index.DocValues.checkField(DocValues.java:317)
	at org.apache.lucene.index.DocValues.getBinary(DocValues.java:352)
	at org.apache.lucene.search.join.DocValuesTermsCollector.lambda$binaryDocValues$0(DocValuesTermsCollector.java:48)
	at org.apache.lucene.search.join.DocValuesTermsCollector.doSetNextReader(DocValuesTermsCollector.java:44)
	at org.apache.lucene.search.SimpleCollector.getLeafCollector(SimpleCollector.java:33)
	at org.apache.lucene.search.join.GenericTermsCollector$2.getLeafCollector(GenericTermsCollector.java:128)


any pointers for this issue please let me know.

Thank you!

Thanks,
Jyothsna

-----Original Message-----
From: Jyothsna Bavisetti 
Sent: Wednesday, October 2, 2019 2:49 AM
To: dev@lucene.apache.org
Subject: RE: Lucene index upgrade from 4.6 to 8 facing issue

Hi Shawn,

Any doc or links for re indexing process. We are using Lucene core 8.0.0.


Thanks,
Jyothsna

-----Original Message-----
From: Jyothsna Bavisetti
Sent: Thursday, September 26, 2019 11:51 PM
To: dev@lucene.apache.org
Subject: RE: Lucene index upgrade from 4.6 to 8 facing issue

Hi Shawn,

Re-indexing is costly transaction in my use case as it takes more than three days. Please let me know if any work around?

Thanks,
Jyothsna
-----Original Message-----
From: Shawn Heisey <el...@elyograg.org>
Sent: Thursday, September 26, 2019 11:35 PM
To: dev@lucene.apache.org
Subject: Re: Lucene index upgrade from 4.6 to 8 facing issue

On 9/26/2019 11:41 AM, Jyothsna Bavisetti wrote:
> I am trying to upgrade Lucene index from 4.6 to 8.0.0. When I'm trying 
> to upgrade tool using:
> 
> java -cp lucene-core.jar:lucene-backward-codecs.jar \
> 
> org.apache.lucene.index.IndexUpgrader-delete-prior-commits  \

<snip>

> Please let me know any option other than reindexing.

If you're upgrading more than one major version, you must reindex. 
Multiple major version upgrades have always been discouraged and never guaranteed to work, but now such upgrades are explicitly denied.

When you used the IndexUpgrader from Lucene 6, the Lucene version was written into the index.  The recorded version was preserved by the upgrader for version 7.  When the index was subsequently read by version 8, it complained because the original index was not written by version 7 or later.

Thanks,
Shawn

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org

RE: Lucene index upgrade from 4.6 to 8 facing issue

Posted by Jyothsna Bavisetti <jy...@oracle.com>.

Hi All,

Could please share some points when to go with longBitset vs FixedBitSet.

I read below Points:

BitSet of fixed length (numBits), backed by accessible (getBits()) long[], accessed with a long index. Use it only if you intend to store more than 2.1B bits, otherwise you should use FixedBitSet.
NOTE: This API is for internal purposes only and might change in incompatible ways in the next release.


Thanks,
Jyothsna
-----Original Message-----
From: Jyothsna Bavisetti
Sent: Wednesday, October 2, 2019 2:49 AM
To: dev@lucene.apache.org
Subject: RE: Lucene index upgrade from 4.6 to 8 facing issue

Hi Shawn,

Any doc or links for re indexing process. We are using Lucene core 8.0.0.


Thanks,
Jyothsna

-----Original Message-----
From: Jyothsna Bavisetti
Sent: Thursday, September 26, 2019 11:51 PM
To: dev@lucene.apache.org
Subject: RE: Lucene index upgrade from 4.6 to 8 facing issue

Hi Shawn,

Re-indexing is costly transaction in my use case as it takes more than three days. Please let me know if any work around?

Thanks,
Jyothsna
-----Original Message-----
From: Shawn Heisey <el...@elyograg.org>
Sent: Thursday, September 26, 2019 11:35 PM
To: dev@lucene.apache.org
Subject: Re: Lucene index upgrade from 4.6 to 8 facing issue

On 9/26/2019 11:41 AM, Jyothsna Bavisetti wrote:
> I am trying to upgrade Lucene index from 4.6 to 8.0.0. When I'm trying 
> to upgrade tool using:
> 
> java -cp lucene-core.jar:lucene-backward-codecs.jar \
> 
> org.apache.lucene.index.IndexUpgrader-delete-prior-commits  \

<snip>

> Please let me know any option other than reindexing.

If you're upgrading more than one major version, you must reindex. 
Multiple major version upgrades have always been discouraged and never guaranteed to work, but now such upgrades are explicitly denied.

When you used the IndexUpgrader from Lucene 6, the Lucene version was written into the index.  The recorded version was preserved by the upgrader for version 7.  When the index was subsequently read by version 8, it complained because the original index was not written by version 7 or later.

Thanks,
Shawn

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org