"On the other hand,
it [sic] most of the cores are idle most of the time, the 1 core/customer
setup would be give better utilization of the hardware."
This is an important point. I've seen performance go to hell when 10M, 100M,
and 1B cloud collections were consolidated in a hardware constrained
It appears that UpdateResponse.setCommitWithin is not honored when executing a
delete query against SolrCloud (SolrJ 4.6). However, setting the hard commit
parameter functions as expected. Is this a known bug?
Thanks,
-Jess
Re-reading the documentation, it seems that Solr caches the results of the fq
parameter, not lower level field constraints. This would imply that breaking a
single complex boolean filter into multiple conjunctive fq parameters would
improve the odds for cache hits. Is this correct?
fq=(a:foo o
27;t tell
>you the actual dynamic field names in the index. I don't know if we
>have anything better than a luke request for that yet.
>
>On Tue, Nov 19, 2013 at 5:56 AM, youknow...@heroicefforts.net
> wrote:
>> I'd like to get the complete field list for a collectio
I'd like to get the complete field list for a collection, including dynamic
fields. Is issuing a Luke request still the recommended way for retrieving
this data?
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Would someone help me out with the syntax for setting Tokenizer.documentFields
in the ClusteringComponent engine definition in solrconfig.xml? Carrot2 is
expecting a Collection of Strings. There's no schema definition for this XML
file and a big TODO on the Wiki wrt init params. Every permuta
