Thank you Alexandre, Jürgen and Erick for your replies. It is clear for me.
Regards
Olivier
2014-10-28 23:35 GMT+01:00 Erick Erickson :
> And one other consideration in addition to the two excellent responses
> so far
>
> In a SolrCloud environment, SolrJ via CloudSolrServer will automatica
And one other consideration in addition to the two excellent responses
so far
In a SolrCloud environment, SolrJ via CloudSolrServer will automatically
route the documents to the correct shard leader, saving some additional
overhead. Post.jar and cURL send the docs to a node, which in turn
forw
Hello Olivier,
for real production use, you won't really want to use any toys like
post.jar or curl. You want a decent connector to whatever data source
there is, that fetches data, possibly massages it a bit, and then feeds
it into Solr - by means of SolrJ or directly into the web service of
Sol
What is your production use? You have to answer that for yourself.
post.jar makes a couple of things easy. If your production use fits
into those (e.g. no cluster) - great, use it. It is certainly not any
worse than cURL.
But if you are running a cluster and have specific requirements, then
yes,
