Hoss,
Thank you very much for clearly delineating the difference.
Just to be clear - My intent to move to 3.1 was driven by my desire to
improve my replication performance - Deducing from your explanation, I
believe the replication/indexing related changes/bug fixes like the
following will
: Thanks Grijesh for responding. I meant that I will use the Lucene 3.1
: jars for indexing also from now on. My current index already has a
: million docs indexed with solr 1.4.1 version, I read somewhere that
: once server is upgraded to 3.1, it is said that the first commit will
: change the in
Thanks Grijesh for responding. I meant that I will use the Lucene 3.1
jars for indexing also from now on. My current index already has a
million docs indexed with solr 1.4.1 version, I read somewhere that
once server is upgraded to 3.1, it is said that the first commit will
change the indexes to 3.
>1. Do we have to reindex all content again to use Solr 3.1 ?
>2. If we don't reindex all content are there any potential issues ? (I
>read somewhere that first commit would change the 1.4.1 format to 3.1.
>have the analyzer's behavior changed which warrants reindexing ?)
>3. Apart from deploy
Hello All,
I am planning to upgrade from Solr 1.4.1 to Solr 3.1. I
saw some deprecation warnings in the log as shown below
[#|2011-05-09T12:37:18.762-0400|WARNING|sun-appserver9.1|org.apache.solr.analysis.BaseTokenStreamFactory|_ThreadID=53;_ThreadName=httpSSLWorkerThread-9001-13
;_Re
Hi,
I am using Solr 1.4.1 in my environment. I have not used special solr
features such as replication/distributed searches. From the Solr 3.1 release
notes, I came to know, for upgrade , first we need to upgrade our slaves and
then need to update Master solr server. Since I have not used this, I
