[ 
https://issues.apache.org/jira/browse/SOLR-7539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15001893#comment-15001893
 ] 

jmlucjav commented on SOLR-7539:
--------------------------------

This would be a great addition, I have used some custom handler to deal with 
these situations, wrote about it 
[here|https://medium.com/@jmlucjav/proper-handling-of-make-query-terms-in-e-commerce-search-39a9ac1bd4bc]
If I might suggest something, I would add some config to allow certain values 
to be excluded from being used as autofilters, this is useful when for example 
a brand name is also a common word that can occur naturally in other places etc.

> 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]

Reply via email to