Applying filters to the completion suggestor

Amit_Soni · November 20, 2013, 8:52am

Hello everyone - We have a use case where we are trying to implement 'type
ahead' functionality for data that exists for different customers. Hence
the 'type ahead' will be specific to a user based on the data that the
specific user.

What I am trying to understand is how I can apply filters to completion
suggestor so that it returns suggestions only for the filter result?

Thanks much in advance!

-Amit.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

zkidkid · November 27, 2013, 3:55am

Hi Amit,
As my understand, the completion base on FST which will process your inputs
at index time. so you could do it after you get filter result.
For your purpose, you could use phrase prefix and edgeNGram to implement
this feature.

Regards.

On Wednesday, November 20, 2013 12:52:34 AM UTC-8, amit.soni wrote:

Hello everyone - We have a use case where we are trying to implement 'type
ahead' functionality for data that exists for different customers. Hence
the 'type ahead' will be specific to a user based on the data that the
specific user.

What I am trying to understand is how I can apply filters to completion
suggestor so that it returns suggestions only for the filter result?

Thanks much in advance!

-Amit.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/5ad04dd1-60e1-42c1-b7ca-d397e6fb6156%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

spinscale · November 27, 2013, 11:08am

Hey,

right now there is possibility to filter results for the completion
suggester, because it is not executing a query like a normal search query
(the data structures used are highly different in order to ensure
performance). We are right now in the process of creating something similar
like a filter by allowing to specify a suggester context, but this is still
in the works (not even in master)

github.com/elastic/elasticsearch

Context extension of the Suggester

opened 08:24AM - 24 Oct 13 UTC

closed 11:16AM - 13 Mar 14 UTC

chilling

>feature v1.1.0 v2.0.0-beta1

The suggester API is a good choice to get simple suggestions. But these suggesti…ons may take additional informations into account. Typing in something like `restaurant` will result in restaurants all over the world. But in this case the geolocation of the request can be used to get better results, namely those which are close to point of the request. Another usecase could be a simple `type` or `group` information which allows the suggester to return results fitting this context. In general the suggester should be able to handle generic information and create result with this information taken into account.

github.com/elastic/elasticsearch

ContextSuggester

elastic:master ← chilling:ContextSuggester

opened 02:31PM - 01 Nov 13 UTC

chilling

+3021 -134

This commit extends the `CompletionSuggester` by context informations. In exampl…e such a context informations can be a simple string representing a category reducing the suggestions in order to this category. Three base implementations of these context informations have been setup in this commit. - a Category Context - a Geo Context - a Field Context All the mapping for these context informations are specified within a context field in the completion field that should use this kind of information. ## Mapping Example The following example shows the mapping for a GeoContext. ``` { "testType":{ "properties":{ "testField":{ "type":"completion", "index_analyzer":"simple", "search_analyzer":"simple", "payloads":true, "preserve_separators":false, "preserve_position_increments":true, "context":{ "geo":{ "separator":"|", "precision":8, "neighbors":true } } } } } } ``` ## Indexing During indexing a document the subfield `context` of the completion field contains the data to be used in order to provide suggestions. ``` { "testField":{ "input":[["pizza - berlin","pizza","food"]], "context":"u33dc1v0xupz" } } ``` ## Suggestion Example The Suggestion request is extended by a context value. The suggest request for a geolocation looks like ``` { "suggest":{ "text":"pizza", "completion":{ "field":"testField", "size":10, "context":{ "geo":"u33dc0cpke4q" } } } } ``` The context objects contains a field with the same name as defined in the mapping. According to the type of the context this field contains the data associated with the suggestion request. In this example the geohash of a location. ## Category Context The simplest way to use this feature is a category context. It supports a arbitrary name of a category to use with the completion suggest API. To set the context support to the category type this option must be set to `true`: ``` "testField":{ "type":"completion", "context":{ "category": true } } ``` The name of the context category then needs to be set within the suggestion context during indexing: ``` { "testField":{ "input":[["pizza - berlin","pizza","food"]], "context":"delivery" } } ``` and can be used by setting the category value: ``` { "suggest":{ "text":"pizza", "completion":{ "field":"testField", "size":10, "context":{ "category":"delivery" } } } } ``` ## Field Context The Field Context works like the category context but the value of this will context will not explicitly be set. It refers to another field in the document. In example a `category` field. ``` { "category":{ "type": "string" }, "testField":{ "type":"completion", "context":{ "field": "category" } } } ``` for indexing the field context must be set to true: ``` { "category":"delivery", "testField":{ "input":[["pizza - berlin","pizza","food"]], "context":true } } ``` and suggestions use the `context.field` value ``` { "suggest":{ "text":"pizza", "completion":{ "field":"testField", "size":10, "context": { "field": "delivery" } } } } ``` ## Geo Context The last context feature is the GeoContext. It take a location into account. For example if one searches for delivery services it might be use full to find results around the location the query was sent. This context internally works on geohashes only but the REST API allows any form defined for `geo_points` In the mapping this kind of context is configured by two parameters: - precision - neighbors The `precision` option is used to configure the range of result. If the `neighbors` option is enabled not only the given geohash cell will be used but also all it's neighbors. ``` "context":{ "geo":{ "separator":"|", "precision":8, "neighbors":true } } ``` The context during indexing is set to the location of the input: ``` { "testField":{ "input":[["pizza - berlin","pizza","food"]], "context": "u33dc1v0xupz" } } ``` To get a ist of suggestions around a specific area the `context.geo` field must contain the position of this area: ``` { "suggest":{ "text":"pizza", "completion":{ "field":"testField", "size":10, "context": { "geo": "u33dc0cpke4q" } } } } ``` Closes #3959

--Alex

On Wed, Nov 27, 2013 at 4:55 AM, kidkid zkidkid@gmail.com wrote:

Hi Amit,
As my understand, the completion base on FST which will process your
inputs at index time. so you could do it after you get filter result.
For your purpose, you could use phrase prefix and edgeNGram to implement
this feature.

Regards.

On Wednesday, November 20, 2013 12:52:34 AM UTC-8, amit.soni wrote:

Hello everyone - We have a use case where we are trying to implement
'type ahead' functionality for data that exists for different customers.
Hence the 'type ahead' will be specific to a user based on the data that
the specific user.

What I am trying to understand is how I can apply filters to completion
suggestor so that it returns suggestions only for the filter result?

Thanks much in advance!

-Amit.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/5ad04dd1-60e1-42c1-b7ca-d397e6fb6156%40googlegroups.com
.

For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAGCwEM8CN8aHo84%2BBH3cNdsZZSV0OgLYiH9q6NuHLn3dSx42fA%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Amit_Soni · November 27, 2013, 4:58pm

Thanks Sang and Alex.

Nice to know this request is in the backlog, will wait for it to be out for
use.

-Amit.

On Wed, Nov 27, 2013 at 3:08 AM, Alexander Reelsen alr@spinscale.de wrote:

Hey,

right now there is possibility to filter results for the completion
suggester, because it is not executing a query like a normal search query
(the data structures used are highly different in order to ensure
performance). We are right now in the process of creating something similar
like a filter by allowing to specify a suggester context, but this is still
in the works (not even in master)

Context extension of the Suggester · Issue #3959 · elastic/elasticsearch · GitHub
https://github.com/elasticsearch/elasticsearch/pull/4044

--Alex

On Wed, Nov 27, 2013 at 4:55 AM, kidkid zkidkid@gmail.com wrote:

Hi Amit,
As my understand, the completion base on FST which will process your
inputs at index time. so you could do it after you get filter result.
For your purpose, you could use phrase prefix and edgeNGram to implement
this feature.

Regards.

On Wednesday, November 20, 2013 12:52:34 AM UTC-8, amit.soni wrote:

Hello everyone - We have a use case where we are trying to implement
'type ahead' functionality for data that exists for different customers.
Hence the 'type ahead' will be specific to a user based on the data that
the specific user.

What I am trying to understand is how I can apply filters to completion
suggestor so that it returns suggestions only for the filter result?

Thanks much in advance!

-Amit.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/5ad04dd1-60e1-42c1-b7ca-d397e6fb6156%40googlegroups.com
.

For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAGCwEM8CN8aHo84%2BBH3cNdsZZSV0OgLYiH9q6NuHLn3dSx42fA%40mail.gmail.com
.

For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAAOGaQKdnR%3DVA2TLAX4fTn8A_NZ1VJQQb%2BQv14Te8ghkUtSW_w%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Andrea_Salvadore · January 31, 2014, 9:17am

Hi
is this feature likely to go into 1.0 release? We'd love to be able to use
the completion filter

On Wednesday, 20 November 2013 08:52:34 UTC, amit.soni wrote:

Hello everyone - We have a use case where we are trying to implement 'type
ahead' functionality for data that exists for different customers. Hence
the 'type ahead' will be specific to a user based on the data that the
specific user.

What I am trying to understand is how I can apply filters to completion
suggestor so that it returns suggestions only for the filter result?

Thanks much in advance!

-Amit.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/5816c3f7-7e24-4c38-8f23-3de4a8d8acb8%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

rakesh_goyal · February 13, 2014, 11:39am

Is there any plan to release this feature in near future.

On Friday, 31 January 2014 14:47:27 UTC+5:30, Andrea Salvadore wrote:

Hi
is this feature likely to go into 1.0 release? We'd love to be able to use
the completion filter

On Wednesday, 20 November 2013 08:52:34 UTC, amit.soni wrote:

Hello everyone - We have a use case where we are trying to implement
'type ahead' functionality for data that exists for different customers.
Hence the 'type ahead' will be specific to a user based on the data that
the specific user.

What I am trying to understand is how I can apply filters to completion
suggestor so that it returns suggestions only for the filter result?

Thanks much in advance!

-Amit.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1cb5915e-e522-4932-b612-a8b97884eefa%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Topic		Replies	Views
Auto completion using completion suggester Elasticsearch	3	405	July 6, 2017
Type Ahead Suggestions using Elastic Search Elasticsearch	2	1789	June 1, 2017
Limit Completion Suggestion Results Based on other fields Elasticsearch	6	860	July 6, 2017
Filtered autocomplete (suggester) Elasticsearch	2	336	July 6, 2017
Completion suggester with separated doc types (multiple indices?) Elasticsearch	5	496	July 6, 2017

Applying filters to the completion suggestor

Related topics