You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are currently two bugs that need to be addressed regarding setting consistency. The first one concerns the behavior of the wildcard in searchableAttributes and displayedAttributes as thourougly described in #761.
The second is regarding the indexing position of fields registered in the setting before document addition, where the said field are given a position that is not consistent with the order in which they appear in the documents.
Motivations
This will overall improve consistency of the settings and user experience.
Explanation
The idea is to add new fields registered in the settings only in the FieldMap (known fields) and not in the IndexedPosition map, until they are first discovered in a document, and give them a IndexedPosition only then.
The searchableAttributes and displayedAttributes should rely exclusively on the fields present in the IndexedPosition map, when the value is a wildcard.
Related
This is a bug fix and does not have an impact on the documentation
The text was updated successfully, but these errors were encountered:
Summary
There are currently two bugs that need to be addressed regarding setting consistency. The first one concerns the behavior of the wildcard in
searchableAttributes
anddisplayedAttributes
as thourougly described in #761.The second is regarding the indexing position of fields registered in the setting before document addition, where the said field are given a position that is not consistent with the order in which they appear in the documents.
Motivations
This will overall improve consistency of the settings and user experience.
Explanation
The idea is to add new fields registered in the settings only in the
FieldMap
(known fields) and not in theIndexedPosition
map, until they are first discovered in a document, and give them aIndexedPosition
only then.The
searchableAttributes
anddisplayedAttributes
should rely exclusively on the fields present in theIndexedPosition
map, when the value is a wildcard.Related
This is a bug fix and does not have an impact on the documentation
The text was updated successfully, but these errors were encountered: