# Phrase suggester **URL:** \ **Category:** Elasticsearch\ **Created:** [July 31, 2013, 4:05pm UTC](https://discuss.elastic.co/t/phrase-suggester/13019 "2013-07-31T16:05:58Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\ **Post date:** [July 31, 2013, 4:05pm UTC](https://discuss.elastic.co/t/phrase-suggester/13019/1 "2013-07-31T16:05:58Z")
Is it possible to convince the phrase suggester to return the suggested phrase in such a way that I can highlight the changed words easily? I can certainly split both phrases on spaces and compare them but that really isn't going to work for non-space-delimited languages. Nik -- 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](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![simonw\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simonw_2/32/1130_2.png) [@simonw\_2](https://discuss.elastic.co/u/simonw_2)\ **Post date:** [August 2, 2013, 8:10pm UTC](https://discuss.elastic.co/t/phrase-suggester/13019/2 "2013-08-02T20:10:45Z")
Nick, there could be multiple changes in the phrase that is returned. so it's kind of unclear what you are asking for in particular. is it a list of offsets that have been changed? I'd be happy to improve the feature but I wonder how we can represent what you need. maybe you have an example? simon On Wednesday, July 31, 2013 6:05:58 PM UTC+2, Nikolas Everett wrote: > Is it possible to convince the phrase suggester to return the suggested > phrase in such a way that I can highlight the changed words easily? I can > certainly split both phrases on spaces and compare them but that really > isn't going to work for non-space-delimited languages. > > Nik -- 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](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\ **Post date:** [August 2, 2013, 9:15pm UTC](https://discuss.elastic.co/t/phrase-suggester/13019/3 "2013-08-02T21:15:47Z")
I'm happy to provide an example! This is pretty much what I'm trying to implement: > **[Search results](https://en.wikipedia.org/w/index.php?search=xorr%2Bthe%2Bgott-jewl&ns0=1)** > > There were no results matching the query. > The page "Xorr the gott-jewl" does not exist. You can create a draft and submit it for review or request that a redirect be created. See how "god" and "jewel" are highlighted? While it'd be sweet if I could ask elasticsearch to do the actual highlighting that really isn't required. All I really need is a way to get a the changed tokens. Something like this: { "text": "xorr the gott-jewl", "offset": 0, "length": 21, "options": [ { "text": "xorr the god-jewel", "score": XXXX, "changes": { "got": "god", "jewl": "jewel" } } ] } or this { "text": "xorr the gott-jewl", "offset": 0, "length": 21, "options": [ { "text": "xorr the god-jewel", "score": XXXX, "changes": [ {"was": "got", "is": "god", "from": 7, "to" 10}, {"was": "jewl", "is": "jewel", "from": 11, "to" 14}, ] } ] } One thing, though: it wouldn't be useful for me to see any shingle tokens because users don't really think of them as words. It is almost like you'd need to retokenize the text and the suggestion without the shingle filter and compare them. I was looking around the code but all the spares and byteSpares are making my head spin at the moment. Nik On Fri, Aug 2, 2013 at 4:10 PM, simonw [simon.willnauer@elasticsearch.com](mailto:simon.willnauer@elasticsearch.com)wrote: > Nick, there could be multiple changes in the phrase that is returned. so > it's kind of unclear what you are asking for in particular. is it a list of > offsets that have been changed? I'd be happy to improve the feature but I > wonder how we can represent what you need. maybe you have an example? > > simon > > On Wednesday, July 31, 2013 6:05:58 PM UTC+2, Nikolas Everett wrote: > > > Is it possible to convince the phrase suggester to return the suggested > > phrase in such a way that I can highlight the changed words easily? I can > > certainly split both phrases on spaces and compare them but that really > > isn't going to work for non-space-delimited languages. > > > > Nik > > -- > 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](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](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](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\ **Post date:** [August 5, 2013, 3:05pm UTC](https://discuss.elastic.co/t/phrase-suggester/13019/4 "2013-08-05T15:05:30Z")
simon, I put together a (probably wrong) implementation of this in [Analyze suggestions by nik9000 · Pull Request #3443 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/pull/3443) . I'd love it if you could have a look at it at some point. It still needs a lot of work but would certainly work for me. Nik On Fri, Aug 2, 2013 at 5:15 PM, Nikolas Everett [nik9000@gmail.com](mailto:nik9000@gmail.com) wrote: > I'm happy to provide an example! This is pretty much what I'm trying to > implement: > [xorr the gott-jewl - Search results - Wikipedia](http://en.wikipedia.org/w/index.php?search=xorr+the+gott-jewl) > See how "god" and "jewel" are highlighted? While it'd be sweet if I could > ask elasticsearch to do the actual highlighting that really isn't > required. All I really need is a way to get a the changed tokens. > Something like this: > { > "text": "xorr the gott-jewl", > "offset": 0, > "length": 21, > "options": [ > { > "text": "xorr the god-jewel", > "score": XXXX, > "changes": { > "got": "god", > "jewl": "jewel" > } > } > ] > } > > or this > { > "text": "xorr the gott-jewl", > "offset": 0, > "length": 21, > "options": [ > { > "text": "xorr the god-jewel", > "score": XXXX, > "changes": [ > {"was": "got", "is": "god", "from": 7, "to" 10}, > {"was": "jewl", "is": "jewel", "from": 11, "to" 14}, > ] > } > ] > } > > One thing, though: it wouldn't be useful for me to see any shingle tokens > because users don't really think of them as words. It is almost like you'd > need to retokenize the text and the suggestion without the shingle filter > and compare them. > > I was looking around the code but all the spares and byteSpares are making > my head spin at the moment. > > Nik > > On Fri, Aug 2, 2013 at 4:10 PM, simonw [simon.willnauer@elasticsearch.com](mailto:simon.willnauer@elasticsearch.com)wrote: > > > Nick, there could be multiple changes in the phrase that is returned. so > > it's kind of unclear what you are asking for in particular. is it a list of > > offsets that have been changed? I'd be happy to improve the feature but I > > wonder how we can represent what you need. maybe you have an example? > > > > simon > > > > On Wednesday, July 31, 2013 6:05:58 PM UTC+2, Nikolas Everett wrote: > > > > > Is it possible to convince the phrase suggester to return the suggested > > > phrase in such a way that I can highlight the changed words easily? I can > > > certainly split both phrases on spaces and compare them but that really > > > isn't going to work for non-space-delimited languages. > > > > > > Nik > > > > -- > > 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](mailto:elasticsearch+unsubscribe@googlegroups.com). > > For more options, visit [https://groups.google.com/groups/opt\_out](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](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![simonw\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simonw_2/32/1130_2.png) [@simonw\_2](https://discuss.elastic.co/u/simonw_2)\ **Post date:** [August 6, 2013, 7:20pm UTC](https://discuss.elastic.co/t/phrase-suggester/13019/5 "2013-08-06T19:20:20Z")
for the record, this feature is now in master simon On Monday, August 5, 2013 5:05:30 PM UTC+2, Nikolas Everett wrote: > simon, > > I put together a (probably wrong) implementation of this in > [Analyze suggestions by nik9000 · Pull Request #3443 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/pull/3443) . I'd love it > if you could have a look at it at some point. It still needs a lot of work > but would certainly work for me. > > Nik > > On Fri, Aug 2, 2013 at 5:15 PM, Nikolas Everett \<[nik...@gmail.com](mailto:nik...@gmail.com)\ > > > wrote: > > > I'm happy to provide an example! This is pretty much what I'm trying to > > implement: > > [xorr the gott-jewl - Search results - Wikipedia](http://en.wikipedia.org/w/index.php?search=xorr+the+gott-jewl) > > See how "god" and "jewel" are highlighted? While it'd be sweet if I > > could ask elasticsearch to do the actual highlighting that really isn't > > required. All I really need is a way to get a the changed tokens. > > Something like this: > > { > > "text": "xorr the gott-jewl", > > "offset": 0, > > "length": 21, > > "options": [ > > { > > "text": "xorr the god-jewel", > > "score": XXXX, > > "changes": { > > "got": "god", > > "jewl": "jewel" > > } > > } > > ] > > } > > > > or this > > { > > "text": "xorr the gott-jewl", > > "offset": 0, > > "length": 21, > > "options": [ > > { > > "text": "xorr the god-jewel", > > "score": XXXX, > > "changes": [ > > {"was": "got", "is": "god", "from": 7, "to" 10}, > > {"was": "jewl", "is": "jewel", "from": 11, "to" 14}, > > ] > > } > > ] > > } > > > > One thing, though: it wouldn't be useful for me to see any shingle tokens > > because users don't really think of them as words. It is almost like you'd > > need to retokenize the text and the suggestion without the shingle filter > > and compare them. > > > > I was looking around the code but all the spares and byteSpares are > > making my head spin at the moment. > > > > Nik > > > > On Fri, Aug 2, 2013 at 4:10 PM, simonw \<[simon.w...@elasticsearch.com](mailto:simon.w...@elasticsearch.com)\ > > > > > wrote: > > > > > Nick, there could be multiple changes in the phrase that is returned. so > > > it's kind of unclear what you are asking for in particular. is it a list of > > > offsets that have been changed? I'd be happy to improve the feature but I > > > wonder how we can represent what you need. maybe you have an example? > > > > > > simon > > > > > > On Wednesday, July 31, 2013 6:05:58 PM UTC+2, Nikolas Everett wrote: > > > > > > > Is it possible to convince the phrase suggester to return the suggested > > > > phrase in such a way that I can highlight the changed words easily? I can > > > > certainly split both phrases on spaces and compare them but that really > > > > isn't going to work for non-space-delimited languages. > > > > > > > > Nik > > > > > > -- > > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > > For more options, visit [https://groups.google.com/groups/opt\_out](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](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Amit\_Soni](https://avatars.discourse-cdn.com/v4/letter/a/c0e974/32.png) [@Amit\_Soni](https://discuss.elastic.co/u/Amit_Soni)\ **Post date:** [October 30, 2013, 7:47am UTC](https://discuss.elastic.co/t/phrase-suggester/13019/6 "2013-10-30T07:47:45Z")
Simon - Can you pl share which Elasticsearch API specifically has to be used to try this out (as explained in the above example)? -Amit. On Tue, Aug 6, 2013 at 12:20 PM, simonw [simon.willnauer@elasticsearch.com](mailto:simon.willnauer@elasticsearch.com)wrote: > for the record, this feature is now in master > > simon > > On Monday, August 5, 2013 5:05:30 PM UTC+2, Nikolas Everett wrote: > > > simon, > > > > I put together a (probably wrong) implementation of this in > > [https://github.com/\*\*elasticsearch/elasticsearch/\*\*pull/3443](https://github.com/ **elasticsearch/elasticsearch/** pull/3443)[https://github.com/elasticsearch/elasticsearch/pull/3443](https://github.com/elasticsearch/elasticsearch/pull/3443). I'd love it if you could have a look at it at some point. It still > > needs a lot of work but would certainly work for me. > > > > Nik > > > > On Fri, Aug 2, 2013 at 5:15 PM, Nikolas Everett [nik...@gmail.com](mailto:nik...@gmail.com) wrote: > > > > > I'm happy to provide an example! This is pretty much what I'm trying to > > > implement: > > > [http://en.wikipedia.org/w/\*\*index.php?search=xorr+the+\*\*gott-jewl](http://en.wikipedia.org/w/ **index.php?search=xorr+the+** gott-jewl)[http://en.wikipedia.org/w/index.php?search=xorr+the+gott-jewl](http://en.wikipedia.org/w/index.php?search=xorr+the+gott-jewl) > > > See how "god" and "jewel" are highlighted? While it'd be sweet if I > > > could ask elasticsearch to do the actual highlighting that really isn't > > > required. All I really need is a way to get a the changed tokens. > > > Something like this: > > > { > > > "text": "xorr the gott-jewl", > > > "offset": 0, > > > "length": 21, > > > "options": [ > > > { > > > "text": "xorr the god-jewel", > > > "score": XXXX, > > > "changes": { > > > "got": "god", > > > "jewl": "jewel" > > > } > > > } > > > ] > > > } > > > > > > or this > > > { > > > "text": "xorr the gott-jewl", > > > "offset": 0, > > > "length": 21, > > > "options": [ > > > { > > > "text": "xorr the god-jewel", > > > "score": XXXX, > > > "changes": [ > > > {"was": "got", "is": "god", "from": 7, "to" 10}, > > > {"was": "jewl", "is": "jewel", "from": 11, "to" > > > 14}, > > > ] > > > } > > > ] > > > } > > > > > > One thing, though: it wouldn't be useful for me to see any shingle > > > tokens because users don't really think of them as words. It is almost > > > like you'd need to retokenize the text and the suggestion without the > > > shingle filter and compare them. > > > > > > I was looking around the code but all the spares and byteSpares are > > > making my head spin at the moment. > > > > > > Nik > > > > > > On Fri, Aug 2, 2013 at 4:10 PM, simonw \wrote: > > > > > > > Nick, there could be multiple changes in the phrase that is returned. > > > > so it's kind of unclear what you are asking for in particular. is it a list > > > > of offsets that have been changed? I'd be happy to improve the feature but > > > > I wonder how we can represent what you need. maybe you have an example? > > > > > > > > simon > > > > > > > > On Wednesday, July 31, 2013 6:05:58 PM UTC+2, Nikolas Everett wrote: > > > > > > > > > Is it possible to convince the phrase suggester to return the > > > > > suggested phrase in such a way that I can highlight the changed words > > > > > easily? I can certainly split both phrases on spaces and compare them but > > > > > that really isn't going to work for non-space-delimited languages. > > > > > > > > > > Nik > > > > > > > > -- > > > > 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 elasticsearc...@\*\*[googlegroups.com](http://googlegroups.com). > > > > > > > > For more options, visit [https://groups.google.com/\*\*groups/opt\_out](https://groups.google.com/**groups/opt_out)[https://groups.google.com/groups/opt\_out](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](mailto:elasticsearch+unsubscribe@googlegroups.com). > > For more options, visit [https://groups.google.com/groups/opt\_out](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](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\ **Post date:** [October 30, 2013, 12:17pm UTC](https://discuss.elastic.co/t/phrase-suggester/13019/7 "2013-10-30T12:17:55Z")
Look on > **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)** > > Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today. the term " highlight". The big example has it here: > **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)** > > Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today. On Wed, Oct 30, 2013 at 3:47 AM, Amit Soni [amitsoni29@gmail.com](mailto:amitsoni29@gmail.com) wrote: > Simon - Can you pl share which Elasticsearch API specifically has to be > used to try this out (as explained in the above example)? > > -Amit. > > On Tue, Aug 6, 2013 at 12:20 PM, simonw \<[simon.willnauer@elasticsearch.com](mailto:simon.willnauer@elasticsearch.com) > > > wrote: > > > for the record, this feature is now in master > > > > simon > > > > On Monday, August 5, 2013 5:05:30 PM UTC+2, Nikolas Everett wrote: > > > > > simon, > > > > > > I put together a (probably wrong) implementation of this in > > > [https://github.com/\*\*elasticsearch/elasticsearch/\*\*pull/3443](https://github.com/ **elasticsearch/elasticsearch/** pull/3443)[https://github.com/elasticsearch/elasticsearch/pull/3443](https://github.com/elasticsearch/elasticsearch/pull/3443). I'd love it if you could have a look at it at some point. It still > > > needs a lot of work but would certainly work for me. > > > > > > Nik > > > > > > On Fri, Aug 2, 2013 at 5:15 PM, Nikolas Everett [nik...@gmail.com](mailto:nik...@gmail.com)wrote: > > > > > > > I'm happy to provide an example! This is pretty much what I'm trying > > > > to implement: > > > > [http://en.wikipedia.org/w/\*\*index.php?search=xorr+the+\*\*gott-jewl](http://en.wikipedia.org/w/ **index.php?search=xorr+the+** gott-jewl)[http://en.wikipedia.org/w/index.php?search=xorr+the+gott-jewl](http://en.wikipedia.org/w/index.php?search=xorr+the+gott-jewl) > > > > See how "god" and "jewel" are highlighted? While it'd be sweet if I > > > > could ask elasticsearch to do the actual highlighting that really isn't > > > > required. All I really need is a way to get a the changed tokens. > > > > Something like this: > > > > { > > > > "text": "xorr the gott-jewl", > > > > "offset": 0, > > > > "length": 21, > > > > "options": [ > > > > { > > > > "text": "xorr the god-jewel", > > > > "score": XXXX, > > > > "changes": { > > > > "got": "god", > > > > "jewl": "jewel" > > > > } > > > > } > > > > ] > > > > } > > > > > > > > or this > > > > { > > > > "text": "xorr the gott-jewl", > > > > "offset": 0, > > > > "length": 21, > > > > "options": [ > > > > { > > > > "text": "xorr the god-jewel", > > > > "score": XXXX, > > > > "changes": [ > > > > {"was": "got", "is": "god", "from": 7, "to" 10}, > > > > {"was": "jewl", "is": "jewel", "from": 11, "to" > > > > 14}, > > > > ] > > > > } > > > > ] > > > > } > > > > > > > > One thing, though: it wouldn't be useful for me to see any shingle > > > > tokens because users don't really think of them as words. It is almost > > > > like you'd need to retokenize the text and the suggestion without the > > > > shingle filter and compare them. > > > > > > > > I was looking around the code but all the spares and byteSpares are > > > > making my head spin at the moment. > > > > > > > > Nik > > > > > > > > On Fri, Aug 2, 2013 at 4:10 PM, simonw \wrote: > > > > > > > > > Nick, there could be multiple changes in the phrase that is returned. > > > > > so it's kind of unclear what you are asking for in particular. is it a list > > > > > of offsets that have been changed? I'd be happy to improve the feature but > > > > > I wonder how we can represent what you need. maybe you have an example? > > > > > > > > > > simon > > > > > > > > > > On Wednesday, July 31, 2013 6:05:58 PM UTC+2, Nikolas Everett wrote: > > > > > > > > > > > Is it possible to convince the phrase suggester to return the > > > > > > suggested phrase in such a way that I can highlight the changed words > > > > > > easily? I can certainly split both phrases on spaces and compare them but > > > > > > that really isn't going to work for non-space-delimited languages. > > > > > > > > > > > > Nik > > > > > > > > > > -- > > > > > 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 elasticsearc...@\*\*[googlegroups.com](http://googlegroups.com). > > > > > > > > > > For more options, visit [https://groups.google.com/\*\*groups/opt\_out](https://groups.google.com/**groups/opt_out)[https://groups.google.com/groups/opt\_out](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](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > For more options, visit [https://groups.google.com/groups/opt\_out](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](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](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](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:09am UTC](https://discuss.elastic.co/t/phrase-suggester/13019/8 "2017-07-06T02:09:48Z")