Automatic prefix on text fields should index offsets and term vectors if they are activated on the parent field #28994
Labels
Comments
jimczi
added
>enhancement
:Search/Search
|
Pinging @elastic/es-search-aggs |
romseygeek
added a commit
that referenced
this issue
Mar 16, 2018
…29067) The index prefix field is normally indexed as docs-only, given that it cannot be used in phrases. However, in the case that the parent field has been indexed with offsets, or has term-vector offsets, we should also store this in the index prefix field for highlighting. Note that this commit does not implement highlighting on prefix fields, but rather ensures that future work can implement this without a backwards-break in index data. Closes #28994
romseygeek
added a commit
that referenced
this issue
Mar 16, 2018
…29067) The index prefix field is normally indexed as docs-only, given that it cannot be used in phrases. However, in the case that the parent field has been indexed with offsets, or has term-vector offsets, we should also store this in the index prefix field for highlighting. Note that this commit does not implement highlighting on prefix fields, but rather ensures that future work can implement this without a backwards-break in index data. Closes #28994
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The new option
index_prefixontextfields that automatically creates a sub-field to index edge-ngrams in order to speed up prefix queries does not check the index options of the parent field.If
offsetsorterm_vectorsfor instance are indexed in the parenttextfield, they will be omitted in the prefix sub-field. Currently this sub-field only indexes doc and disables all other options, this was done to make sure that this sub-field does not use extra disk space for features that won't be used by the query. Though it could be beneficial to apply the same options than the parent field if we want to use this sub-field for highlighting prefix queries. Currently highlighting prefix queries on atextfield does not work in conjunction with this new option (we create a term query that targets a different field) but we want to handle this case in the future so it would be beneficial to create this sub-field with the index options set on the parent field if these options are used by the highlighters. This could speed up the prefix query highlighting since a prefix query on that field is a simple term query and since this feature has not been released yet we could also avoid BWC issue by adding these options in the first release of this feature (6.3).The text was updated successfully, but these errors were encountered: