On Mon, Feb 26, 2018 at 7:14 PM, Erick Erickson
wrote:
>
> Faceting works on multivalued fields, perhaps you can do something with
> that?
>
> The main difference I see in this case between facets and groups is that
groups are sorted by score, so most relevant group comes first.
Which is very use
Of course, and in that use-case you'd want a particular document to
appear in all three categories.
Another client may want the doc to appear in only the "most important"
category, however that's defined.
Another client may want the doc to appear in "the more recent" day
(assuming we're grouping
Hi Erick,
please consider this case where there is a group products that are
televisions.
Now I have only one category per product, but in same cases like the
television I could have more than one.
Some products should be available simultaneously in more categories, thats
why the field I was try
What does "group by" mean on a field with more than one value? Say I
have "A" and "B" in the field in a single document. What group does it
go in, one labeld "A" or one labeled "B"?
So IIUC, rather than do something which will be wrong it throws an
error if the field is defined as multiValued. And
Hi Amrit,
thanks for your help.
I know that only 5/10% of documents in the collection have more than one
value for the field I was trying to group by.
So there isn't a particular memory usage in this case. Do you know if there
is any other counter-indication I have to be aware of?
I was thinkin
Vincenzo,
As I read the source code; SchemaField.java
/**
* Sanity checks that the properties of this field type are plausible
* for a field that may be used to get a FieldCacheSource, throwing
* an appropriate exception (including the field name) if it is not.
* FieldType subclasses can cho
Hi,
while trying to run a group query on a multivalue field I received this
error:
can not use FieldCache on multivalued field:
true
400
4
org.apache.solr.common.SolrException
org.apache.solr.common.SolrException
can not use FieldCache on multivalued field:
categoryLe