That's definitely strange as Solr 5.x should support all Solr 4.x indexes.
Anyway, you can somewhat force an upgrade by running a forceMerge command
after you've upgraded the libraries to 5.3.0. This will rewrite the index
into one segment whose version will be 5.3. It is usually not recommended
t
90% of my data was indexed in 4.6.1 or lower.
My goal is upgrade all data to 4.10.4 and then upgrade to 5.3
In previous test that I did with 5.3 in dev cluster, I see some strange
behaviour with data indexed with 4.6.1 that in 4.10.4 didn’t reproduce.
Some queries to data indexed in 4.
Solr 5.3 can read Solr 4.10.4 indexes as-is. Why are you trying to upgrade
the indexes in the first place?
Shai
On Thu, Sep 17, 2015 at 3:05 PM, Yago Riveiro
wrote:
> I have a very old index with more than 12T (re-index data is not an option
> ...) that I want upgrade to 5.3, I’m using lucene-c
I have a very old index with more than 12T (re-index data is not an option ...)
that I want upgrade to 5.3, I’m using lucene-core-4.10.4.jar (I’m in 4.10.4
right now) to upgrade old segments of data. With solr running I can run the
command because solr has the lock of the core.
I only want
The not-very-helpful answer is that you're using the core admin API in
a SolrCloud setup. Please do not do this as (you're well aware of this by now!)
it's far too easy to get "interesting" results.
Instead, use the Collections API, specifically the ADDREPLICA and DELETEREPLICA
commands. Under the
