Thanks for the response Sameer & Binoy.
Jay
On Sun, Jan 31, 2016 at 6:13 PM, Binoy Dalal wrote:
> Adding to sameer's answer, use string types when you want exact matches,
> both in terms of query and case.
> In case you want to perform additional operations on the input, like
> tokenization and
Adding to sameer's answer, use string types when you want exact matches,
both in terms of query and case.
In case you want to perform additional operations on the input, like
tokenization and applying filters, then you're better off with one of the
other text types.
You should take a look at the fi
Hi Jay,
You could use one field for both unless there is a specific requirement you
are looking for that is not being met by that one field (e.g. faceting,
etc). Typically, if you have a field that is marked as both "indexed" and
"stored", the value that is passed while indexing to that field is s
Hi,
I am trying to decide if I should use text_en or string as my field type.
The fields have to be both indexed and stored for display. One solution is
to duplicate fields, one for indexing other for display.One of the field
happens to be a description field which I would like to avoid duplicating
