On Wed, 2012-11-28 at 03:25 +0100, Arun Rangarajan wrote:
[Sorting on 14M docs, 250 fields]
> From what I have read, I understand that restricting the number of distinct
> values on sortable Solr fields will bring down the fieldCache space. The
> values in these sortable fields can be any integer
Erick,
Thanks for your reply. So there is no easy way to get around this problem.
We have a way to rework the schema by keeping a single sort field. The
dynamic fields we have are like relevance_CLASSID. The current schema has a
unique key NODEID and a multi-valued field CLASSID - the relevance s
I sure don't see how this can work given the constraints. Just to hold the
values, assuming that each doc holds a value in 150 fields, you have 150 *
4 * 14,000,000 or 8.4G of memory required, and you just don't have that
much memory to play around with.
Sharding seems silly for 14M docs, but that
On Thu, Aug 16, 2012 at 8:00 AM, Peter Kirk wrote:
>> Hi, a question about sorting and dynamic fields in "Solr Specification
>> Version: 3.6.0.2012.04.06.11.34.07".
>>
>> I have a field defined like
>> > multiValued="false"/>
>>
>> Where type int is
>> > omitNorms="true" positionIncrementGap="0"/
On Thu, Aug 16, 2012 at 8:00 AM, Peter Kirk wrote:
> Hi, a question about sorting and dynamic fields in "Solr Specification
> Version: 3.6.0.2012.04.06.11.34.07".
>
> I have a field defined like
> multiValued="false"/>
>
> Where type int is
> omitNorms="true" positionIncrementGap="0"/>
Try add
Hi, a question about sorting and dynamic fields in "Solr Specification Version:
3.6.0.2012.04.06.11.34.07".
I have a field defined like
Where type int is
If I perform a search, which returns 13 documents, and sort by a field called
"item_group_int", then it almost produces the results I expe
