Mapped dependency name to for license notice check – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” Mapped dependency name to for license notice check ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: task.

Log Context

Log “mapped dependency name {} to {} for license/notice check” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             String depName = regex.matcher(jarName).replaceFirst("");

            validateSha(shaFiles; dependency; jarName; depName);

            String dependencyName = getDependencyName(mappings; depName);
  "mapped dependency name {} to {} for license/notice check"; depName; dependencyName);
            checkFile(dependencyName; jarName; licenses; "LICENSE");
            checkFile(dependencyName; jarName; notices; "NOTICE");


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content