Looks like jetty version was causing an issue for me. Fixed the same by excluding jetty-util artifact from hudi-client dependency in hudi-utilities pom.
In version 9.4.15, Container class is an interface while in lower version 7.6.0, it is a class. This conflict of versions was causing mentioned exception for me. On Fri, Nov 29, 2019 at 5:37 PM Pratyaksh Sharma <pratyaks...@gmail.com> wrote: > Hi Lamberken, > > Here are the details - > > MacOS Mojave version 10.14.6 > Java version - 1.8.0_212 > Docker version - 19.03.5 > > Please let me know if anything else is needed. > > On Fri, Nov 29, 2019 at 5:21 PM lamberken <lamber...@163.com> wrote: > >> >> >> Hi, Pratyaksh Sharma >> >> >> In order to solve the problem better, please provides the running >> environment. >> For example, what is your operating system or the java version and so on. >> thanks >> >> >> >> >> >> >> >> >> >> >> >> At 2019-11-29 18:15:45, "Pratyaksh Sharma" <pratyaks...@gmail.com> wrote: >> >Hi, >> > >> >Every time I try to run test cases of TestHoodieDeltaStreamer class >> >individually, I get the following error - >> > >> >java.lang.InstantiationError: org.eclipse.jetty.util.component.Container >> > >> >at org.eclipse.jetty.server.Server.<init>(Server.java:66) >> >at org.apache.hive.http.HttpServer.<init>(HttpServer.java:98) >> >at org.apache.hive.http.HttpServer.<init>(HttpServer.java:80) >> >at org.apache.hive.http.HttpServer$Builder.build(HttpServer.java:133) >> >at org.apache.hive.service.server.HiveServer2.init(HiveServer2.java:227) >> >at >> >> >org.apache.hudi.hive.util.HiveTestService.startHiveServer(HiveTestService.java:214) >> >at >> org.apache.hudi.hive.util.HiveTestService.start(HiveTestService.java:106) >> >at >> >> >org.apache.hudi.utilities.UtilitiesTestBase.initClass(UtilitiesTestBase.java:88) >> >at >> >> >org.apache.hudi.utilities.TestHoodieDeltaStreamer.initClass(TestHoodieDeltaStreamer.java:91) >> > >> >All other test cases run fine. If I try to run using the command man >> clean >> >install -DskipITs, everything seems to be fine. >> > >> >Has anyone faced a similar issue? >> >
