tbonelee commented on PR #5095: URL: https://github.com/apache/zeppelin/pull/5095#issuecomment-3368735681
I looked into the failing Selenium test to find the cause. My working hypothesis is that `maven-shade-plugin` is rewriting a string-literal, the default value of `ZEPPELIN_CONFIG_STORAGE_CLASS` inside `zeppelin-interpreter`'s `ZeppelinConfiguration`. I didn't directly inspect the effective classpath, but the behavior suggests that when the shaded class is resolved first, the rewritten default appears, and when the original class is resolved first the unmodified default remains. This inference comes from the two checks below. 1. **Shade raw-string check** : Adding `<rawString>true</rawString>` in the relocation option makes the `ZEPPELIN_CONFIG_STORAGE_CLASS` default value to remain as the original literal value. 2. **Classpath order check** : Reordering dependencies so that `zeppelin-server` appears before `spark-interpreter` also gives the same result as 1. Before the zengine and server merge, the `zeppelin-zengine` dependency also appeared before `spark-interpreter`. Sharing these observations in case they help fix the failing Selenium test. https://github.com/apache/zeppelin/blob/190ecd6a2febd58616e0fdbb2686fbd2b2ea7e7a/zeppelin-interpreter/src/main/java/org/apache/zeppelin/conf/ZeppelinConfiguration.java#L1037 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
