Hey Isabella,
I suppose that you are a contractor for a company and that your contract is to build a plugin, right?
A river plugin is a plugin. So you respect the contract.
That said, I would really recommend that you give advices to your client that it could really be better to have that logic outside elasticsearch itself.
My 2 cents.
--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr
Le 18 novembre 2013 at 11:11:45, Isabella (isi.huber90@gmail.com) a écrit:
Thanks for your answers.
Unfortunately I don't know, why it has to be a normal plugin instead of a river plugin. I only got the instructions, that it has to be a normal plugin which synchronizes data from postgresql.
I have to implement a normal plugin, that should read the properties to connect with the database out of a config file. For instance, how it is done in the hadoop plugin. https://github.com/elasticsearch/elasticsearch-hadoop
Is there a possibility to configure the database connection properties in such a config file?
My second problem is, that I don't know which module I have to use for my plugin, so that my plugin actually does something when I start ES. Is there any list of available modules for ES? I only know a few modules like, RiverModule, AnalysisModule, ScriptModule and RestModule, but I don't think that these modules are the right for my plugin. Another problem is how can I address my plugin? Do I need a mapping to say ES that my plugin should do something?
I am sorry about my stupid and mabye a litte bit confusing questions. But my problem is, that I don't know how to initialize my plugin. If it would be a river plugin, I have to define a mapping with a type, that is also defined in the java code, when the riverModule is registered, am I right? But if I have a normal plugin I don't know which module I have to take or which modules are available.
I really would appreciate any help.
Thanks a lot.
Best Regards,
Isabella
Am Donnerstag, 14. November 2013 21:16:25 UTC+1 schrieb Itamar Syn-Hershko:
We like to call this a "shoveller" (or shoveler, depends on your locale), as in "shovelling data into ES"
On Thu, Nov 14, 2013 at 4:56 PM, David Pilato da...@pilato.fr wrote:
Question is "why a plugin?"
It does not bring so much value to elasticsearch internals.
I would start with a simple Main() class (let's say a batch for example).
--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr
Le 14 novembre 2013 at 13:27:52, Isabella (isi.h...@gmail.com) a écrit:
Hello!
I have to make an plugin which indexes data from my postgresql database, but it should not be a River Plugin. My problem is, that I don't know how to let my plugin know, that I have created a mapping, that defines my jdbc driver, url, password etc. and how to get those properties to connect to my database in my plugin java code?
Does anyone know if I can define those jdbc properties in a mapping and read it out or do I have to do it in another way?
I really would appreciate your help!
Thanks a lot.
Regards
Isabella
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.
For more options, visit 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 elasticsearc...@googlegroups.com.
For more options, visit 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.
For more options, visit 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.
For more options, visit https://groups.google.com/groups/opt_out.