Elasticsearch河插件的替代品 [英] Alternatives to Elasticsearch river plugins

问题描述

我希望将Elasticsearch索引与SQL数据库的内容同步。 Elasticsearch JDBC河流符合我的所有要求，但在文档中，据说该插件已被弃用。

I want to synchronize an Elasticsearch index with the contents of an SQL database. The Elasticsearch JDBC river meets all my requirements, but in the documentation it is said that the plugin is deprecated.

我不想使用不会的工具在接下来的几年中得到支持。有什么选择？

I don't want to use a tool that won't be supported in the following years. What are the alternatives?

在河流的文件中，说：

注意，JDBC插件不仅是一条河流，还是一个独立的模块。因为Elasticsearch river API已被弃用，这是一个重要的功能。

Note, JDBC plugin is not only a river, but also a standalone module. Because Elasticsearch river API is deprecated, this is an important feature.

为什么这是一个重要的功能？这是否意味着我仍然可以无限期地使用它，尽管不建议，例如通过使用馈线而不是河？

Why is it an important feature? Does it mean that I can still use it indefinitely despite the deprecation, for example by using a feeder instead of a river?

推荐答案

一些替代方案：

• 仍然可以使用河流，直到Elasticsearch版本2.0。但是这不是一个长期的解决方案。


• 如同plmaheu所说，您可以编写自己的解决方案。这是一些工作，但完全符合您的计划，建议在 Elasticsearch博客上。


• 您可以将发送插入/更新/删除请求到Logstash ，而不是编写自定义代码日志，而不是使用弹性搜索。我喜欢这个解决方案，因为Logstash将为您量身打造并处理您不想自己实现的其他事情。


• 我听说可以使用ETl工具，如 Talend ，但我没有调查那个解决方案，因为它是一个付费的解决方案。


• 有一个 gatherer 插件，应该替代河流。但是从去年开始还没有更新，所以很可能该项目已被放弃。

• The rivers can still be used, until the version 2.0 of Elasticsearch. But it's not a long term solution.
• You can write your own solution, as said plmaheu. It's some work, but will fit your program perfectly and is recommended on the Elasticsearch blog.
• Instead of writing a log of custom code, you can send the insert/update/delete requests to Logstash, that will make them on Elasticsearch. I like this solution since Logstash will make bulks for you and handle other things that you don't want to implement by yourself.
• I heard that you can use an ETl tool like Talend, but I didn't investigated that solution since it's a paying solution.
• There is the gatherer plugin that was supposed to replace the rivers. However it has not been update since last year so it's likely that the project has been abandoned.

这两个解决方案在ES博客中推荐正在编写您的解决方案或使用Logstash。请选择符合您要求的一个。

The two solutions recommended on the ES blog are writing your solution or using Logstash. Choose the one that fits your requirements.

注意：目前正在开发许多很好的解决方案来替代河流， logstash-jdbc输入为例。河流的贬低是相当近期的，可以预期在未来几个月/年内将会出现许多替代品。

Note: a lot of great solutions are currently in development to replace the rivers, the logstash-jdbc input as an example. The deprecation of the rivers is quite recent and can expect that many replacements will emerge over the next months/years.

这篇关于Elasticsearch河插件的替代品的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！