Position offset gap in objects

Hi I have mapping like below. { "field": { "type": "object", "properties": { "subfield": { "type": "string", * "position_offset_gap": 500* } }, "*position_offset_gap": 50* } } I insert document like

Plugin datasource singleton

Hi, I have query parser plugin. This plugin also implements transport action. Both: query parser and transport action should share the same data source object (with cache). Unfortunately when I run a query and parser is called I see one instance of data source. When transport action is called I se

Re: Custom cluster action

llow existing plugins. > > Cheers, > > Ivan > > On Wed, Nov 12, 2014 at 3:50 PM, Pawel wrote: > >> Hi, >> I'm thinking about building custom ClusterAction. I see that I can build >> custom classes for Request, NodeResponse and NodesRespone but it is not

Custom cluster action

Hi, I'm thinking about building custom ClusterAction. I see that I can build custom classes for Request, NodeResponse and NodesRespone but it is not clear to me how I can register my custom action. In case of Rest action it was quite easy because in plugin i simply use public void onModule(Re

Plugin - cache invalidation in Query parser

Hi, I implemented query parser plugin. While query is parsed a few costly operations have to be performed. I decided to cache sub-results of this operation and reuse it when needed. This works fine. The problem begins when cache should be invalidated. I built REST API (BaseRestAction) for cache in

Re: Plugin version

lt;http://Elasticsearch.com>* > @dadoonet <https://twitter.com/dadoonet> | @elasticsearchfr > <https://twitter.com/elasticsearchfr> | @scrutmydocs > <https://twitter.com/scrutmydocs> > > > > Le 11 nov. 2014 à 20:12, Pawel a écrit : > > Hi, > I

Plugin version

Hi, I implemented ES plugin and set its version in es-plugin.properties. version=${project.version} I build project using maven but when I start plugin in ES and check plugin version using ES API I see version without resolved "project.version" property. Do you have any idea how I can avoid hardc

Re: Get analyzer from client

ce injector. For example: > > > https://github.com/elasticsearch/elasticsearch/blob/master/src/test/java/org/elasticsearch/index/analysis/CharFilterTests.java > > Cheers, > > Ivan > On Oct 5, 2014 10:48 AM, "Pawel" wrote: > >> Hi, >> >> I have a

Get analyzer from client

Hi, I have a java application which uses Elasticsearch client (transport client). I need to analyze string taking mapping which is used by ES. I know I can prepare analyze request to elasticsearch but it means a lot of requests to ES. Is it possible to get somehow Lucene Analyzer from client objec

Re: Single node job

ocument TTLs that > might suit, but they are resource intensive. > > A plugin could work as you could leverage the quartz scheduler libraries > to handle running it. > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: ma...@campaignmonitor.c

Single node job

Hi, I'm have to prepare a mechanism which is able to run a scheduled job in ES. This job will be responsible for periodical remove of unused documents. I think it is easy to achieve in simple plugin. The only problem I see is synchronization. I think it is reasonable that at a time only one job is

Re: Query pre-processing before execution?

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

Custom query parser

Hi, I'd like to prepare new query parser which will be triggered for each query sent to ES. I already implemented a query parser and attached it to AnalysisService but I have to run it by { "query" : { "custom_query : { } } } I'd like to avoid this. ES has multiple clients for m

Query post processing

Hi, I need an elasticsearch plugin which will build and add filter to each query passed to Elasticsearch. Above short scenario is showed: 1. Query string is sent to Elasticsearch 2. Query is parsed and prepared to execute on cluster 3. A filter is build based eg. on query, current time etc. and ad