On 10/6/2016 9:02 AM, Steven White wrote: > We currently have a component that uses SolrJ and Solr REST API to admin > Solr (adding new fields, changing handlers, etc. to customize Solr's > schema) based on customer's DB schema before we start indexing. > > If we switch over to SolrCloud: > > 1) Will our existing usage of SolrJ and REST API still work as-is?
Generally speaking, if you change from a variant like HttpSolrClient connecting to a non-cloud install to CloudSolrClient connecting to a cloud install, the rest of your SolrJ code will *probably* work with no other changes. That will largely depend on the config/schema being similar between the cloud install and the non-cloud install. > 2) Not all of our customers need that high availability of Solr. For > those, single server and single index will do just fine. In this case, can > I configure SolrCloud to single server with single core? When I do so, am > I impacting performance of Solr? You can have collections in the cloud that have a single shard and a single replica -- only one core in the entire collection. These kinds of collections are vulnerable to failures if the server with the single core goes down, of course. Aside from that, they work just like collections with more shards and/or more replicas. The "old" http API still works even in cloud mode, using collection names instead of core names in the URL -- with the added advantage that you can send such requests to ANY node in the cloud, and they will find their way to the correct location. Updates are more efficient if they are sent to the correct shard leader, which CloudSolrClient does by default. Thanks, Shawn
