Kevin,
Just want to be clear. You certainly can aggregate field values into the
_all field (and selectively field by field too). However, the values that
are aggregated are the raw field values from your source document. They all
appended together *and then* all analyzed uniformly by whatever i
So what you are saying is, there is no way to aggregate together into one
place all the tokens generated by one document?
I mostly wanted to do this so that an end user doesn't have to understand
what fields are in the document, or lucene query syntax to get the results
they are looking for.
T
I'm not sure your mapping actually does what you think/expect it to do.
Actually, I don't believe you can combine multiple analyzed-already tokens
from different fields into 1 field at all. Your best bet for correctness is
probably just to leave all the multi-fields alone and then run queries li
I have some documents with ~30 fields, most of which i just want to analyze
with the defaults, a couple i want to use snowballing or other custom
analyzers on.
The recommended way to do this seems to be using the index_name property to
aliase a custom _all field, such as:
curl -XPOST $elasticl