<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question HBase jars with conflicting versions? in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/HBase-jars-with-conflicting-versions/m-p/165161#M49592</link>
    <description>&lt;P&gt;Can someone explain the decision to include the following jars in the HDP distribution for HBase? Is this for compatibility? Please provide some technical background on the decision.&lt;/P&gt;&lt;PRE&gt;-rw-r--r-- 1 user user   790250 Nov 15 19:41 netty-3.2.4.Final.jar
-rw-r--r-- 1 user user  1779991 Nov 15 18:11 netty-all-4.0.23.Final.jar
-rw-r--r-- 1 user user   132368 Nov 15 18:12 servlet-api-2.5-6.1.14.jar
-rw-r--r-- 1 user user   105112 Nov 15 18:05 servlet-api-2.5.jar
&lt;/PRE&gt;</description>
    <pubDate>Wed, 21 Dec 2016 07:02:28 GMT</pubDate>
    <dc:creator>aervits</dc:creator>
    <dc:date>2016-12-21T07:02:28Z</dc:date>
    <item>
      <title>HBase jars with conflicting versions?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/HBase-jars-with-conflicting-versions/m-p/165161#M49592</link>
      <description>&lt;P&gt;Can someone explain the decision to include the following jars in the HDP distribution for HBase? Is this for compatibility? Please provide some technical background on the decision.&lt;/P&gt;&lt;PRE&gt;-rw-r--r-- 1 user user   790250 Nov 15 19:41 netty-3.2.4.Final.jar
-rw-r--r-- 1 user user  1779991 Nov 15 18:11 netty-all-4.0.23.Final.jar
-rw-r--r-- 1 user user   132368 Nov 15 18:12 servlet-api-2.5-6.1.14.jar
-rw-r--r-- 1 user user   105112 Nov 15 18:05 servlet-api-2.5.jar
&lt;/PRE&gt;</description>
      <pubDate>Wed, 21 Dec 2016 07:02:28 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/HBase-jars-with-conflicting-versions/m-p/165161#M49592</guid>
      <dc:creator>aervits</dc:creator>
      <dc:date>2016-12-21T07:02:28Z</dc:date>
    </item>
    <item>
      <title>Re: HBase jars with conflicting versions?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/HBase-jars-with-conflicting-versions/m-p/165162#M49593</link>
      <description>&lt;P&gt;netty-3.2.4.Final.jar is brought in by hbase-it module.&lt;/P&gt;&lt;P&gt;It shouldn't collide with netty-all-4.0.23.Final.jar&lt;/P&gt;</description>
      <pubDate>Wed, 21 Dec 2016 07:11:39 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/HBase-jars-with-conflicting-versions/m-p/165162#M49593</guid>
      <dc:creator>tyu</dc:creator>
      <dc:date>2016-12-21T07:11:39Z</dc:date>
    </item>
    <item>
      <title>Re: HBase jars with conflicting versions?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/HBase-jars-with-conflicting-versions/m-p/165163#M49594</link>
      <description>&lt;P&gt;servlet-api-2.5.jar is brought in by transitive dependency:&lt;/P&gt;&lt;P&gt;[INFO] +- org.apache.hadoop:hadoop-mapreduce-client-core:jar:2.7.3.2.6.0.0-SNAPSHOT:compile &lt;/P&gt;&lt;P&gt;[INFO] |  +- org.apache.hadoop:hadoop-yarn-common:jar:2.7.3.2.6.0.0-SNAPSHOT:compile &lt;/P&gt;&lt;P&gt;[INFO] |  |  +- javax.xml.bind:jaxb-api:jar:2.2.2:compile &lt;/P&gt;&lt;P&gt;[INFO] |  |  |  \- javax.activation:activation:jar:1.1:compile &lt;/P&gt;&lt;P&gt;[INFO] |  |  +- javax.servlet:servlet-api:jar:2.5:compile&lt;/P&gt;</description>
      <pubDate>Wed, 21 Dec 2016 07:13:51 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/HBase-jars-with-conflicting-versions/m-p/165163#M49594</guid>
      <dc:creator>tyu</dc:creator>
      <dc:date>2016-12-21T07:13:51Z</dc:date>
    </item>
    <item>
      <title>Re: HBase jars with conflicting versions?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/HBase-jars-with-conflicting-versions/m-p/165164#M49595</link>
      <description>&lt;P&gt;Thanks Ted, what about the rest?&lt;/P&gt;</description>
      <pubDate>Wed, 21 Dec 2016 07:24:15 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/HBase-jars-with-conflicting-versions/m-p/165164#M49595</guid>
      <dc:creator>aervits</dc:creator>
      <dc:date>2016-12-21T07:24:15Z</dc:date>
    </item>
    <item>
      <title>Re: HBase jars with conflicting versions?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/HBase-jars-with-conflicting-versions/m-p/165165#M49596</link>
      <description>&lt;P&gt;I would also add to Ted's comment that netty-3.2.4 (which is required by hadoop-hdfs) and netty-all-4.0.23 are not conflicting because 3.2.4 is the old version with org.jboss.netty package while 4.0.23 has io.netty package. Actually they even have different artifact IDs (netty vs netty-all). So it's safe to use both of them in the same project. &lt;/P&gt;</description>
      <pubDate>Wed, 21 Dec 2016 08:02:48 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/HBase-jars-with-conflicting-versions/m-p/165165#M49596</guid>
      <dc:creator>ssoldatov</dc:creator>
      <dc:date>2016-12-21T08:02:48Z</dc:date>
    </item>
    <item>
      <title>Re: HBase jars with conflicting versions?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/HBase-jars-with-conflicting-versions/m-p/165166#M49597</link>
      <description>&lt;P&gt;Thank you Sergey, I wish I could accept both answers. Voting up!&lt;/P&gt;</description>
      <pubDate>Wed, 21 Dec 2016 08:22:12 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/HBase-jars-with-conflicting-versions/m-p/165166#M49597</guid>
      <dc:creator>aervits</dc:creator>
      <dc:date>2016-12-21T08:22:12Z</dc:date>
    </item>
  </channel>
</rss>

