[
https://issues.apache.org/jira/browse/PIRK-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15390495#comment-15390495
]
Suneel Marthi commented on PIRK-11:
-----------------------------------
ElasticSearch needs Slf4J, it makes sense to switch the project to use Slf4J
Snippet from present POM
{Code}
<dependency>
<groupId>org.elasticsearch</groupId>
<artifactId>elasticsearch-hadoop</artifactId>
<version>2.1.2</version>
<exclusions>
<exclusion>
<artifactId>commons-net</artifactId>
<groupId>commons-net</groupId>
</exclusion>
<exclusion>
<groupId>org.apache.hive</groupId>
<artifactId>hive-service</artifactId>
</exclusion>
<exclusion>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-log4j12</artifactId>
</exclusion>
<exclusion>
<groupId>org.slf4j</groupId>
<artifactId>log4j-over-slf4j</artifactId>
</exclusion>
</exclusions>
</dependency>
{Code}
> Upgrade log4j to log4j2
> -----------------------
>
> Key: PIRK-11
> URL: https://issues.apache.org/jira/browse/PIRK-11
> Project: PIRK
> Issue Type: Improvement
> Reporter: Ellison Anne Williams
> Assignee: Suneel Marthi
>
> Since log4j is EOL, we should upgrade to log4j2.
> Note: There has also been some discussion on the dev list on whether we
> should also adopt Slf4j. When that decision is made, we can update the issue
> or issue a new one.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
