ZEPPELIN-337 Configurable ContextPath#385
Conversation
|
Thanks for the nice feature. Could you rebase and trigger CI? |
|
From https://s3.amazonaws.com/archive.travis-ci.org/jobs/88620950/log.txt, the build is success [INFO] Zeppelin: Packaging distribution ................... SUCCESS [ 35.204 s] Any reason for the red flag on github? Should I rebase and push again, or close/reopen to trigger the CI? |
|
it's because of issue resolved by #380. This time, you'll need rebase and push to apply #380. |
….context.path property or ZEPPELIN_CONTEXT_PATH env variable + add doc on this
There was a problem hiding this comment.
could this be ZEPPELIN_SERVER_CONTEXT_PATH?
there is a object called ZeppelinContext in the Spark interpreter group and this name might be confusing
|
Any more feedback on this? |
|
I'm not sure why CI is failing. You can trigger CI again. |
|
Please use #429 to track this. |
Allow to configure the context path of the webapp via zeppelin.server.context.path property or ZEPPELIN_SERVER_CONTEXT_PATH env variable + documentation for this. (replaces #385) Author: Eric Charles <eric@datalayer.io> This patch had conflicts when merged, resolved by Committer: Lee moon soo <moon@apache.org> Closes #429 from echarles/ZEPPELIN-337-Configurable-ContextPath and squashes the following commits: 37e07f9 [Eric Charles] Ensure context path is also setup when running with the distribution 70194fc [Eric Charles] Set /api path on servlet level, not context to fix test 54f6b07 [Eric Charles] ZEPPELIN_CONTEXT_PATH is now ZEPPELIN_SERVER_CONTEXT_PATH 9095d5d [Eric Charles] Allow to configure the context path of the webapp via zeppelin.server.context.path property or ZEPPELIN_CONTEXT_PATH env variable + add doc on this
Fix saveAsParquetFile
Allow to configure the context path of the webapp via zeppelin.server.context.path property or ZEPPELIN_CONTEXT_PATH env variable + add doc on this