Sorry for introducing bad information.
Because it happens in the json facet api, I thought it would also happen in
the facet. Soyrry again for the misunderstood.
2016-07-07 16:08 GMT-03:00 Chris Hostetter :
>
> : The problem with the shards appears in the following scenario (note that
> : the pro
: The problem with the shards appears in the following scenario (note that
: the problem below also applies in a solr standalone enviroment with
: distributed search):
:
: Shard1: DATA_SOURCE1 (3 docs), DATA_SOURCE2 (2 docs), DATA_SOURCE3 (2 docs).
: Shard2: DATA_SOURCE3 (2 docs), DATA_SOURCE2 (1
: My question specifically has to do with Facets in a SOLR
: cloud/collection (distributed environment). The core I am working with
...
: I am using the following facet query which works fine in more Core based index
:
:
http://localhost:8983/solr/gamra/select?q=*:*&rows=0&facet=true&f
As long as you don't shard your index, you will have no problem migrating
to solrcloud.
The problem with the shards appears in the following scenario (note that
the problem below also applies in a solr standalone enviroment with
distributed search):
Shard1: DATA_SOURCE1 (3 docs), DATA_SOURCE2 (2
Hello,
I have am somewhat of a novice when it comes to using SOLR in a distributed
SolrCloud environment. My team and I are doing development work with a SOLR
core. We will shortly be transitioning over to a SolrCloud environment.
My question specifically has to do with Facets in a SOLR cloud/c
