You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
texera-web fails to start after Hadoop 3.4.3 upgrade: NoClassDefFoundError from pjfanning jersey-json #6204
After #6201 (Hadoop 3.4.3 upgrade), texera-web crashes during Dropwizard startup with NoClassDefFoundError: com/sun/jersey/core/provider/jaxb/AbstractRootElementProvider. Hadoop 3.4 replaced com.sun.jersey:jersey-json with the fork com.github.pjfanning:jersey-json, which the existing ExclusionRule(organization = "com.sun.jersey") rules in common/workflow-core/build.sbt and amber/build.sbt do not catch. Its META-INF/services entries register Jersey 1 providers whose superclasses live in the (excluded) jersey-core 1.x, so Jersey 2's ServiceFinder dies loading them. Expected: the service boots. Fix: also exclude com.github.pjfanning from the hadoop dependencies (jersey-json only serves hadoop's own web endpoints; Iceberg/HDFS paths don't need it).
How to reproduce?
On main, start texera-web (e.g. bin/local-dev.sh up texera-web); it exits during Jetty startup.
Activity
fix(deps): exclude pjfanning jersey-json from hadoop to unbreak servi…
fix(deps, v1.2): upgrade Apache Hadoop to 3.4.3 to resolve hadoop-com…
ci: add a texera-web boot smoke test in amber-integration (apache#6319)
ci: add a computing-unit-master boot smoke test in amber-integration (a…
ci: smoke-test the computing-unit cluster (master boot + worker join)
ci: smoke-test the computing-unit cluster (master boot + worker join)
ci: smoke-test the computing-unit cluster (master boot + worker join)