Thank you for your responses. I have one more question related to Solr
multi-core.
By using SolrJ I create new core for each application. When user wants to
add data or make query on his application, I create new HttpSolrServer for
this core. In this scenario there will be many running
This might help:
https://wiki.apache.org/solr/Solrj#HttpSolrServer
Note that the associated SolrRequest takes the path, I presume relative to
the base URL you initialized the HttpSolrServer with.
Best
Erick
On Mon, Jan 7, 2013 at 7:02 AM, Parvin Gasimzade parvin.gasimz...@gmail.com
wrote:
I know that but my question is different. Let me ask it in this way.
I have a solr with base url localhost:8998/solr and two solr core
as localhost:8998/solr/core1 and localhost:8998/solr/core2.
I have one baseSolr instance initialized as :
SolrServer server = new HttpSolrServer( url );
I have
number of core in Solr multi-core
I know that but my question is different. Let me ask it in this way.
I have a solr with base url localhost:8998/solr and two solr core as
localhost:8998/solr/core1 and localhost:8998/solr/core2.
I have one baseSolr instance initialized as :
SolrServer server
-
brFrom: Parvin Gasimzade [mailto:parvin.gasimz...@gmail.com]
brSent: Monday, January 07, 2013 7:00 AM
brTo: solr-user@lucene.apache.org
brSubject: Re: Max number of core in Solr multi-core
br
brI know that but my question is different. Let me ask it in this way.
br
brI have a solr with base url
This is a common approach to this problem, having separate
cores keeps the apps from influencing each other when it comes
to term frequencies etc. It also keeps the chances of returning
the wrong data do a minimum.
As to how many cores can fit, it depends (tm). There's lots of
work going on
Furthermore, if you plan to index a lot of data per application, and
you are using Solr 4.0.0+ (including Solr Cloud), you probably want to
consider creating a collection per application instead of a core per
application.
On 1/2/13 2:38 PM, Erick Erickson wrote:
This is a common approach to
