[
https://issues.apache.org/jira/browse/SOLR-7539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14566084#comment-14566084
]
Ted Sullivan commented on SOLR-7539:
------------------------------------
Added logic to handle the case where a phrase match on field values can also
have a set of single term matches if that is valid. So for the use case where
"White Linen" is a brand, "perfume" is a product type, "white" is a color,
"linen" is a material and "shirts" is a product type. The query "White Linen
perfume" will be parsed to (brand:"White Linen") OR (color:white AND
material:linen)) AND product_type:perfume. This ensures that the correct match
will be returned for either this query or "white linen shirts". Without this
fix, the brand match would overrule the single term match as it has more terms.
This secondary rule only happens if a phrase match is encountered AND there is
a complete set of single term matches for that phrase.
Also made the internal field value delimiter configurable and set it to '|' by
default. The original code used ',' which can probably occur in String field
values.
> Add a QueryAutofilteringComponent for query introspection using indexed
> metadata
> --------------------------------------------------------------------------------
>
> Key: SOLR-7539
> URL: https://issues.apache.org/jira/browse/SOLR-7539
> Project: Solr
> Issue Type: New Feature
> Reporter: Ted Sullivan
> Priority: Minor
> Fix For: Trunk
>
> Attachments: SOLR-7539.patch, SOLR-7539.patch, SOLR-7539.patch
>
>
> The Query Autofiltering Component provides a method of inferring user intent
> by matching noun phrases that are typically used for faceted-navigation into
> Solr filter or boost queries (depending on configuration settings) so that
> more precise user queries can be met with more precise results.
> The algorithm uses a "longest contiguous phrase match" strategy which allows
> it to disambiguate queries where single terms are ambiguous but phrases are
> not. It will work when there is structured information in the form of String
> fields that are normally used for faceted navigation. It works across fields
> by building a map of search term to index field using the Lucene FieldCache
> (UninvertingReader). This enables users to create free text, multi-term
> queries that combine attributes across facet fields - as if they had searched
> and then navigated through several facet layers. To address the problem of
> exact-match only semantics of String fields, support for synonyms (including
> multi-term synonyms) and stemming was added.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
