Hi Joerg, You are right about analyzer. I have also a little different case or maybe I missed something (and analyzer-way can also handle my case).
I'd like to process a query and add additional filter to each of queries. To build this filter external service should be queried to fetch additional data and use this data to build proper filter. Filter can be build for a few fields: for example fileld1:foo AND field2:bar AND field3:test. Do you have any suggestions? -- Paweł On Thu, Aug 21, 2014 at 10:31 AM, joergpra...@gmail.com < joergpra...@gmail.com> wrote: > I would rather use the analyzer/token filter machinery of Lucene for > search/index extensions, plugging this into ES is a breeze. > > If you want field specific mangling, I would use the field mapper to > create a new field type. There, you have read access to the whole > (immutable) document source and you can pre-process the field input data in > the given document context before indexing. > > Jörg > > > On Wed, Aug 20, 2014 at 12:00 PM, Otis Gospodnetic < > otis.gospodne...@gmail.com> wrote: > >> Hi, >> >> What is the best way to pre-process a query a bit before ES executes it? >> (e.g. I want to shingle the query string a bit and expand/rewrite a query >> before letting ES execute it) >> >> I can create a custom Rest Action and a new API endpoint, but I'd prefer >> to hide custom query pre-processing behind the standard ES query API. >> >> Is there any way to do that? >> >> Thanks, >> Otis >> -- >> Elasticsearch Performance Monitoring * Log Management * Search Analytics >> http://sematext.com/ >> >> -- >> 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+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/e99854af-65e1-42c0-9dab-e384c8c281e6%40googlegroups.com >> <https://groups.google.com/d/msgid/elasticsearch/e99854af-65e1-42c0-9dab-e384c8c281e6%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- > 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+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/CAKdsXoFzggLcxBa0axOcyZ2v5CxG8v9NmquFcmHp%2ByiS8Z0F4w%40mail.gmail.com > <https://groups.google.com/d/msgid/elasticsearch/CAKdsXoFzggLcxBa0axOcyZ2v5CxG8v9NmquFcmHp%2ByiS8Z0F4w%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAF9ZkbMx70HZ2rOyU%3D%3DQh63j9wYVvjju%2BJMZsO1DQxKnZjN8Xw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
