On Jan 10, 2013, at 12:06 PM, Shawn Heisey s...@elyograg.org wrote:
On 1/9/2013 8:54 PM, Mark Miller wrote:
I'd put everything into one. You can upload different named sets of config
files and point collections either to the same sets or different sets.
You can really think about it the
: Setting up new SolrCloud - need some guidance
On Jan 10, 2013, at 12:06 PM, Shawn Heisey s...@elyograg.org wrote:
On 1/9/2013 8:54 PM, Mark Miller wrote:
I'd put everything into one. You can upload different named sets of config
files and point collections either to the same sets
On 1/11/2013 9:15 AM, Markus Jelsma wrote:
FYI: XInclude works fine. We have all request handlers in solrconfig in
separate files and include them via XInclude on a running SolrCloud cluster.
Good to know. I'm still deciding whether I want to recombine or
continue to use xinclude. Is the
On 1/9/2013 8:54 PM, Mark Miller wrote:
I'd put everything into one. You can upload different named sets of config
files and point collections either to the same sets or different sets.
You can really think about it the same way you would setting up a single node
with multiple cores. The main
I have a lot of experience with Solr, starting with 1.4.0 and currently
running 3.5.0 in production. I am working on a 4.1 upgrade, but I have
not touched SolrCloud at all.
I now need to set up a brand new Solr deployment to replace a custom
Lucene system, and due to the way the client
I'd put everything into one. You can upload different named sets of config
files and point collections either to the same sets or different sets.
You can really think about it the same way you would setting up a single node
with multiple cores. The main difference is that it's easier to share
