[vpj][all] Create a new module for offline components to reduce leaka…

…ge (#1205)

Recently, we moved some shared classes into "venice-common" to share common functionality. To do this, we added "hadoop-common" library into "venice-common". However, this leaks "hadoop-common" into online components too which is not desired. Moved these classes into a "venice-hadoop-common" package.

clients/venice-push-job/build.gradle

@@ -8,6 +8,8 @@ dependencies {
     exclude module: ':internal:alpini'
   }
 
+  implementation project(':internal:venice-hadoop-common')
+
   implementation (libraries.avro) {
     exclude group: 'org.mortbay.jetty' // jetty 6 conflicts with spark-java used in controller api
   }

internal/venice-common/build.gradle

@@ -30,12 +30,6 @@ dependencies {
     exclude group: 'com.linkedin.container', module: 'container-eventbus-factory' // Keeping' it clean.
   }
 
-  implementation (libraries.hadoopCommon) {
-    // Exclude transitive dependency
-    exclude group: 'org.apache.avro'
-    exclude group: 'javax.servlet'
-  }
-
   implementation project(':clients:venice-thin-client')
 
   implementation libraries.avroUtilCompatHelper

internal/venice-hadoop-common/build.gradle

@@ -0,0 +1,12 @@
+dependencies {
+    implementation project(':internal:venice-common')
+    implementation libraries.log4j2api
+    implementation (libraries.hadoopCommon) {
+        // Exclude transitive dependency
+        exclude group: 'org.apache.avro'
+        exclude group: 'javax.servlet'
+    }
+
+    testImplementation platform('org.junit:junit-bom:5.9.1')
+    testImplementation 'org.junit.jupiter:junit-jupiter'
+}

settings.gradle

@@ -54,6 +54,7 @@ include 'services:venice-standalone'
 include 'internal:venice-avro-compatibility-test'
 include 'internal:venice-client-common'
 include 'internal:venice-common'
+include 'internal:venice-hadoop-common'
 include 'internal:venice-jdk-compatibility-test'
 include 'internal:venice-test-common'