Rivers have been deprecated Read https www elastic co blog deprecating rivers – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 1.7-1.7

Briefly, this error occurs when you’re trying to use Elasticsearch Rivers, a feature that has been deprecated since Elasticsearch version 1.5. Rivers were used for data import from external systems into Elasticsearch. To resolve this issue, you can use Logstash or Beats for data ingestion, or write your own custom plugin. Alternatively, you can use the Bulk API for large scale data import. It’s also important to upgrade your Elasticsearch to the latest version to enjoy new features and improvements.

This guide will help you check for common problems that cause the log ” rivers have been deprecated. Read https://www.elastic.co/blog/deprecating_rivers ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “rivers have been deprecated. Read https://www.elastic.co/blog/deprecating_rivers” classname is RiversService.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

         if (riversInjectors.containsKey(riverName)) {
            logger.warn("ignoring river [{}][{}] creation; already exists"; riverName.type(); riverName.name());

        logger.info("rivers have been deprecated. Read https://www.elastic.co/blog/deprecating_rivers");
        logger.debug("creating river [{}][{}]"; riverName.type(); riverName.name());

        try {
            ModulesBuilder modules = new ModulesBuilder();
            modules.add(new RiverNameModule(riverName));


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?