Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Previously I was using a jdbc river to index all the data from mysql to elasticsearch. Now I have shifted to the tire bulk api, as it gives me the freedom to manipulate the data before indexing it into elasticsearch. But the indexing process using the tire bulk api takes lot of time(4 times) as compared to the jdbc river for 3M records. Is there a way to make the indexing process quicker and efficient?
IMHO, the key is that the JDBC river is launched inside Elasticsearch. So after a JDBC request, data are in memory and directly sent to ES.
With an external process, you have one network Hop more.
That said, 4 time lower is perhaps too much.