Call "optimize" on your Solr 3.5 server which will write a new index
segment in v3.5 format. Such an index should be read in Solr 4.x
without any problem.
On Thu, Aug 22, 2013 at 5:00 PM, Montu v Boda
wrote:
> thanks
>
> actually the problem is that we have migrated the solr 1.4 index data to
> s
thanks
actually the problem is that we have migrated the solr 1.4 index data to
solr 3.5 using replication feature of solr 3.5. so that what ever data we
have in solr 3.5 is of solr 1.4.
so i do not think so it is work in solr 4.x.
so please suggest your view based on my above point.
Thanks & R
No one is asking you to re-index data. The Solr 3.5 index can be read
and written by a Solr 4.x installation.
On Thu, Aug 22, 2013 at 12:08 PM, Montu v Boda
wrote:
> Thanks for suggestion
>
> but as per us this is not the right way to re-index all the data each and
> every time. we mean when we m
Thanks for suggestion
but as per us this is not the right way to re-index all the data each and
every time. we mean when we migrate the sole from older to latest version.
there is some way that solr have to provide the solutions for this because
re indexing the 50 lac document is not an easy job.
I guess you are trying to index another Solr index via DIH's
SolrEntityProcessor. That processor wasn't really designed for
migrating huge indexes. You're better off re-indexing content directly
to another Solr.
As far as this error is concerned, my guess is that it is due to an
error thrown by yo
when we import the all index of solr 3.5 to 4.3 then import goes fail each
and every time due to below error.
Caused by: org.apache.solr.common.SolrException: parsing error
Caused by: org.paache.http.MalformedChunkCodingException: Unexpected content
at the end of chunk
we have 50 lac document is
