Folding of accented to non-accented *only* — leaving symbols

I now the asciifolding filter docs are really very clear on this, but it took me an embarrassingly long time to realise I was losing my currency symbol (£) to the ASCII folding filter. Other than creating my own character map with the char map filter, does there exist something of production

Re: Pattern replace apostrophes?

analyzer at search time. -- Ivan On Tue, Oct 7, 2014 at 6:06 AM, Lee Gee lee...@gmail.com javascript: wrote: My users have issues with apostrophes: I need to index and search aaa's as it is, and without the apostrophe, as aaas. If I use a char_filter to remove apostrophes when indexing

Re: Pattern replace apostrophes?

, 2014 8:00:13 PM UTC+1, Ivan Brusic wrote: What type of query are you using? Perhaps the query you are using is not using the same analyzer at search time. -- Ivan On Tue, Oct 7, 2014 at 6:06 AM, Lee Gee lee...@gmail.com javascript: wrote: My users have issues with apostrophes: I need

Ampersand synonym in YAML?

name_synonyms: type: synonym synonyms: - 1,one # - ,and,+=and - ' = and' How can I use YAML to correctly configure a synonym for ampersands and the 'plus' symbol and the word 'and'? The above synonym for 1/one seems to work.

Pattern replace apostrophes?

My users have issues with apostrophes: I need to index and search aaa's as it is, and without the apostrophe, as aaas. If I use a char_filter to remove apostrophes when indexing and when searching, the _analyze endpoint shows me that they produce 'words' without apostrophes like this

Re: edge_ngram results

term across the whole index — what confuses me is that these are results for the same term in the same index, so shouldn't the IDF be the same...? tia lee On Wednesday, October 1, 2014 11:24:17 AM UTC+1, Lee Gee wrote: I have an ElasticSearch string field configured for autocomplete like

Re: edge_ngram results

shorter strings higher than longer ones but that's another question thanks Lee On Wednesday, October 1, 2014 11:24:17 AM UTC+1, Lee Gee wrote: I have an ElasticSearch string field configured for autocomplete like this: autocomplete_analyzer: type: custom

Sorting equal scores by field length?

Is it possible to sort equally-scored results by the length of the field? Or am I doing something else incorrectly? With an edge_ngram filter on a keyword field, with search term S, I see SUPER comes before S in my results. As a last resort, I could add a field to reflect the length of the

edge_ngram results

I have an ElasticSearch string field configured for autocomplete like this: autocomplete_analyzer: type: custom tokenizer: whitespace filter: [ lowercase, asciifolding, ending_synonym, name_synonyms, autocomplete_filter ] autocomplete_filter:

Facted navigation with totals, drilling down

I have two 'types' in an index, or two indices of different types (I'd prefer the latter but can live with the former). I'm running an aggregation by type to implement what my UX people refer to as faceted search — which makes Googling for ES help quite tricky. UX would like to filter by

Weight be position in string?

Is it possible to boost the weight a result if it is closer to the start of a string in the index? So that searching for 'bar' would weight 'foo bar baz' higher than 'foo baz bar'? I'm working with ngrams, if that helps. Thanks Lee -- You received this message because you are subscribed to

Re: Swap indexes?

I was looking for the index alias, thanks all. On Tuesday, June 17, 2014 9:31:00 AM UTC+1, Lee Gee wrote: Is it possible to have one ES instance create an index and then have a second instance use that created index, without downtime? tia lee -- You received this message because you

Re: _suggest suggestion/question

the fact that , both actual data and auto completion data are stored in different data structures. This is to make sure that the auto completion data is memory resident and thus super fast. Thanks Vineeth On Sun, Aug 17, 2014 at 3:32 PM, Lee Gee lee...@gmail.com javascript: wrote

_suggest suggestion/question

My reading, which may not be accurate, of this [1] clear and concise post, is that it is not possible to use a reference to an existing field as an argument to a suggestor's 'input' or 'payload' fields. Please would you clarify if I have missed something? If I was correct, would it be much

Re: Support for Anchoring in Elasticsearch Regex

Lucene and Elastic Search both anchor regexp by default. Lucene’s patterns are always anchored. The pattern provided must match the entire string. — http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/query-dsl-regexp-query.html#regexp-syntax On Wednesday, December 18,

Swap indexes?

Is it possible to have one ES instance create an index and then have a second instance use that created index, without downtime? tia lee -- You received this message because you are subscribed to the Google Groups elasticsearch group. To unsubscribe from this group and stop receiving emails