));
}
}
}
Log.info(end of getInstance());
return INSTANCE;
}
}
[/code]
On Wednesday, 18 March 2015 22:36:58 UTC+2, Dmitry Kan wrote:
Jörg,
Following your suggestion I refactored the code like so:
[code]
public class SemanticAnalyzerTwitterLemmatizerProvider extends
Hi,
Could somebody answer, please?
On Tuesday, 17 March 2015 19:05:38 UTC+2, Dmitry Kan wrote:
Hello!
I'm a newbie in elasticsearch, so forgive if the question is lame.
I have implemented a custom plugin using a custom lemmatizer and a
tokenizer. The simplified class sequence
them.
Jörg
On Wed, Mar 18, 2015 at 4:02 PM, Dmitry Kan dmitr...@gmail.com
javascript: wrote:
Hi,
Could somebody answer, please?
On Tuesday, 17 March 2015 19:05:38 UTC+2, Dmitry Kan wrote:
Hello!
I'm a newbie in elasticsearch, so forgive if the question is lame.
I have implemented
and setup of the analyzer could be refactored to the
provider.
Jörg
On Wed, Mar 18, 2015 at 8:12 PM, Dmitry Kan dmitr...@gmail.com
javascript: wrote:
Yes, I use an analyzer provider. Here is the code:
[code]
public class SemanticAnalyzerTwitterLemmatizerProvider extends
(with a MorphAnalyzer
instance etc.), and with get() method, it creates analyzers as required.
Jörg
On Wed, Mar 18, 2015 at 6:40 PM, Dmitry Kan dmitr...@gmail.com
javascript: wrote:
Jörg,
Thanks for replying!
Here is the code of the RussianLemmatizingTwitterAnalyzer, the deepest
class
is that *with* the plugin 100M of RAM is reserved by the
JVM with no data. *Without* the plugin the JVM reserves 2M with no data.
Elasticsearch 1.3.2, Lucene 4.9.0.
Regards,
Dmitry Kan
--
You received this message because you are subscribed to the Google Groups
elasticsearch group.
To unsubscribe from
