I must admit I'm new to this so I find some of the information hard to understand. So sorry if I am asking stupid questions.
> On 12 Sep 2014, at 18:26, Ivan Brusic <[email protected]> wrote: > > I would strongly prefer to maintain control of the indexing side and not in > Elasticsearch. In fact, the Elasticsearch team has talked about deprecating > river plugins. I do not have any numbers, but I would suspect that the > majority of users do not use a river plugin. And yes, the correct term is the > JDBC plugin, not driver. The wrong term confused many. :) > > -- > Ivan > >> On Fri, Sep 12, 2014 at 3:24 AM, [email protected] >> <[email protected]> wrote: >> You can use either style, it is a matter of taste, or convenience. >> >> With the JDBC plugin, you can also push data instead of pull. >> >> Jörg >> >>> On Fri, Sep 12, 2014 at 12:11 PM, James <[email protected]> wrote: >>> I want to close this issue but I still do not understand if I should be >>> pushing documents from my database using the PHP client or using the JDBC >>> river to pull them into elasticsearch from the SQL database. >>> >>> They can both achieve the same thing, but what is the usecase which defines >>> when is the right time to use each implementation. >>> >>> >>> >>>> On Wednesday, September 10, 2014 10:59:18 AM UTC+1, James wrote: >>>> Hi, >>>> >>>> I'm setting up a system where I have a main SQL database which is synced >>>> with elasticsearch. My plan is to use the main PHP library for >>>> elasticsearch. >>>> >>>> I was going to have a cron run every thirty minuets to check for items in >>>> my database that not only have an "active" flag but that also do not have >>>> an "indexed" flag, that means I need to add them to the index. Then I was >>>> going to add that item to the index. Since I am using taking this path, it >>>> doesn't seem like I need the JDBC driver, as I can add items to >>>> elasticsearch using the PHP library. >>>> >>>> So, my question is, can I get away without using the JDBC driver? >>>> >>>> James >>> >>> -- >>> 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 [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/elasticsearch/6c244e00-1f89-447d-8eb5-114f0b5efcbd%40googlegroups.com. >>> >>> 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 [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHT2DcMHJwMjxBZ0RsV4_eKJyB2KjBCiqB2ZTac8fzkTg%40mail.gmail.com. >> >> For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to a topic in the Google > Groups "elasticsearch" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/elasticsearch/0dzSMbARlks/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQBvDga8q--Au8yWaX2RMGgcDTpYMhLu243tB9w7z0W0_A%40mail.gmail.com. > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/9EBFE31B-8DEA-4E05-8342-9E0013BC450B%40employ.com. For more options, visit https://groups.google.com/d/optout.
