Hi Sujatha,
Which version of Solr are you using?
Best Wishes,
Siva
On Wed, May 30, 2012 at 12:22 AM, Sujatha Arun wrote:
> Yes ,that is correct.
>
> Regards
> Sujatha
>
> On Tue, May 29, 2012 at 7:23 PM, lboutros wrote:
>
> > Hi Suajtha,
> >
> > each webapps has its own solr home ?
> >
> > Lu
One migration strategy is to fall back to XML parser from the javabin parser,
upgrade Solrj jars to 3.4, turn off replication, upgrade master, upgrade each
of the slaves while turning on replication. Once all slaves have been
upgraded/replication turned on - switch back to javabin parser.
Best
Hi Spark,
Is it possible to store a modified time on the database record which would help
you to get the updated documents?
That way you can avoid reindexing the documents that have not been updated.
Best wishes,
Siva on 3GS
On Dec 8, 2011, at 15:40, yu shen wrote:
> Hi Mark,
>
> I did not
How about sorting over the score? Would that be possible?
On Jul 21, 2010, at 12:13 AM, Li Li wrote:
> in QueryComponent.mergeIds. It will remove document which has
> duplicated uniqueKey with others. In current implementation, it use
> the first encountered.
> String prevShard = uniqueD
Hi,
I was wondering if anyone has found any resolution to this email thread?
Thank you,
Siva Kommuri
On Dec 23, 2009, at 10:15 AM, Jon Poulton wrote:
Hi there,
I'm looking at some problems we are having with some legacy code which uses
Solr (1.3) under the hood. We seem to get rep
