Ehem, *_target --- *_facet.
2015-05-14 16:47 GMT+02:00 Luis Cappa Banda luisca...@gmail.com:
Hi Yonik,
Yes, they are the target from copyFields in the schema.xml. This *_target
fields are suposed to be used in some specific searchable (thus, tokenized)
fields that in the future are
Hi Yonik,
Yes, they are the target from copyFields in the schema.xml. This *_target
fields are suposed to be used in some specific searchable (thus, tokenized)
fields that in the future are candidates to be faceted to return some
stats. For example, imagine that you have a field storing a
Are the _facet fields the target of a copyField in the schema?
Realtime get either gets the values from the transaction log (and if
you didn't send it the values, they won't be there) or gets them from
the index to try and reconstruct what was sent in.
It's generally not recommended to have
On Thu, May 14, 2015 at 12:49 PM, Luis Cappa Banda luisca...@gmail.com wrote:
If you don' t mark as stored a field indexed and 'facetable', I was
expecting to not be able to return their values, so faceting has no sense.
Faceting does not use or retrieve stored field values. The labels
Yep, but those dynamic fields had a field type string, so the unique
indexed therm will be the entire field value and the faceted terms counted
will match with exactly with each field value. Thats why I was confused.
Typically I use faceting with string non tokenized field values for simple
stats
That is something I didin' t know, but I thought it was mandatory. I' ll
try to explain step by step my (I think) logical way to understand it:
- If a field is indexed, you can search by it.
- When faceting, you have to index the field (because it can be
tokenized and then you would like
On Thu, May 14, 2015 at 10:47 AM, Luis Cappa Banda luisca...@gmail.com wrote:
Hi Yonik,
Yes, they are the target from copyFields in the schema.xml. This *_target
fields are suposed to be used in some specific searchable (thus, tokenized)
fields that in the future are candidates to be faceted
Hi there,
I have the following dynamicFields definition in my schema.xml:
!-- I18n DynamicFields --
dynamicField name=i18n* type=string indexed=true stored=true / !--
DynamicFields used typically for faceting issues by copying values from
other existing fields-- dynamicField name=*_facet
