Created Jira Issue
https://issues.apache.org/jira/browse/SOLR-4703 and attached the Patch. No
unit tests yet.
On Fri, Apr 12, 2013 at 12:59 AM, Mark Miller wrote:
> I was looking for this msg the other day and couldn't find it offhand…
>
> +1, please add this to JIRA so someone can look into it
I was looking for this msg the other day and couldn't find it offhand…
+1, please add this to JIRA so someone can look into it and it does not get
lost!
- Mark
On Apr 11, 2013, at 11:17 AM, Otis Gospodnetic
wrote:
> Hi Umesh,
>
> The attachment didn't make it through. Could you please add
Hi Umesh,
The attachment didn't make it through. Could you please add it to
JIRA? http://wiki.apache.org/solr/HowToContribute
Thanks,
Otis
--
Solr & ElasticSearch Support
http://sematext.com/
On Wed, Apr 10, 2013 at 9:43 PM, Umesh Prasad wrote:
> Root caused the Issue to a Code Bug / Contr
Root caused the Issue to a Code Bug / Contract Violation in SnapPuller in
solr 4.2.1 (impacts trunk as well) and Fixed by Patching the SnapPuller
locally.
fetchfilelist API expects indexversion to be specified as param.
So Call to Master should of be Form :
/solr/phcare/replication?command=filel
Hi All,
I am migrating from Solr 3.5.0 to Solr 4.2.1. And everything is running
fine and set to go, except the master slave replication.
We use master slave replication with multi cores ( 1 master, 10 slaves and
20 plus cores).
My Configuration is :
Master : Solr 3.5.0, Has existing index, a