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
When storing content in a multivalued field (a string array for instance), it seems that proximity is not taken into account text across the multivalued elements. This can be useful in cases the field stores chunks of a single piece of content. This should affect both the matching of phrase/near queries and the ranking score for signals that proximity is involved. For instance
element1: "The quick brown fox"
element2: "jumps over the lazy dog"
The queries that demonstrate the two issues respectively are:
phrase("brown fox jumps over")
brown fox jumps over with a ranking profile that factors proximity into the score.
It would be nice if there was an on/off switch to remove the boundaries between elements so that proximity conditionally matches across them work out of the box.
The text was updated successfully, but these errors were encountered:
When storing content in a multivalued field (a string array for instance), it seems that proximity is not taken into account text across the multivalued elements. This can be useful in cases the field stores chunks of a single piece of content. This should affect both the matching of phrase/near queries and the ranking score for signals that proximity is involved. For instance
element1: "The quick brown fox"
element2: "jumps over the lazy dog"
The queries that demonstrate the two issues respectively are:
It would be nice if there was an on/off switch to remove the boundaries between elements so that proximity conditionally matches across them work out of the box.
The text was updated successfully, but these errors were encountered: