nub of the issue.
>
> Erick
>
> On Tue, Jun 24, 2014 at 11:14 PM, Dominik Siebel wrote:
> > Hey Suresh,
> >
> > could you get a little more specific on what solved your problem here?
> > I am currently facing the same problem and am trying to find a proper
> &
Hey Suresh,
could you get a little more specific on what solved your problem here?
I am currently facing the same problem and am trying to find a proper
solution.
Thanks!
~ Dom
2014-02-28 7:46 GMT+01:00 sureshrk19 :
> Thanks Shawn and Erick.
>
> I followed SOLR configuration document and modif
our multiple Solrs are eating up the same physical
> memory, so I'm not quite sure whether the fact that you have
> different query characteristics is best served by multiple cores
> or not.
>
> Have you measured improvements with your proposed
> architecture?
>
> Best
&
Hi,
I just found SOLR-4663 beeing patched in the latest update I did.
Does anyone know any other solution to use ONE physical index for various
purposes?
Why? I would like to use different solconfig.xmls in terms of cache sizes,
result window size, etc. per business case for optimal performance,
any experience with bugreporting or submitting patches
(just in case there really IS a bug)?
2012/10/27 Lance Norskog :
> Which database rows cause the problem? The bug report talks about fields with
> an empty string. Do your rows have empty string values?
>
> - Original Message
f the JIRA issues against the DIH from your old Solr
> capture date.
>
>
> - Original Message -
> | From: "Dominik Siebel"
> | To: solr-user@lucene.apache.org
> | Sent: Thursday, October 18, 2012 11:22:54 PM
> | Subject: Fwd: DIH throws NullPointer
Hi folks,
I am currently migrating our Solr servers from a 4.0.0 nightly build
(aprox. November 2011, which worked very well) to the newly released
4.0.0 and am running into some issues concerning the existing
DataImportHandler configuratiions. Maybe you have an idea where I am
going wrong here.
Hi folks,
I am currently migrating our Solr servers from a 4.0.0 nightly build
(aprox. November 2011, which worked very well) to the newly released
4.0.0 and am running into some issues concerning the existing
DataImportHandler configuratiions. Maybe you have an idea where I am
going wrong here.
