Upgrade Spark / Hadoop / Zeppelin (Issue #535) #590
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Zarquan
reviewed
Dec 3, 2021
Comment on lines
+203
to
+207
| <property> | ||
| <name>zeppelin.interpreter.exclude</name> | ||
| <value>angular,livy,alluxio,file,psql,flink,ignite,lens,cassandra,geode,kylin,elasticsearch,scalding,jdbc,hbase,bigquery,beam,groovy,flink-cmd,hazelcastjet,influxdb,java,jupyter,kotlin,ksql,mongodb,neo4j,pig,r,sap,spark-submit,sparql,submarine</value> | ||
| <description>All the inteprreters that you would like to exclude. You can only specify either 'zeppelin.interpreter.include' or 'zeppelin.interpreter.exclude'. Specifying them together is not allowed.</description> | ||
| </property> |
There was a problem hiding this comment.
Why are these excluded ?
In might be better to explicitly list the interpreters we do want in zeppelin.interpreter.include rather than excluding an arbitrary list in zeppelin.interpreter.exclude.
I've created an issue to follow this up #593.
Zarquan
reviewed
Dec 3, 2021
Comment on lines
+249
to
+250
| # After some investigation, it looks like the new Zeppelin runs Spark jobs as the logged in Zeppelin user, and fails because it lacks permission. | ||
| # Turn this off for now, so that everything is sent as the main Zeppelin user (After this change Spark notebooks work) |
There was a problem hiding this comment.
How do we turn this ON/OFF ?
There was a problem hiding this comment.
We will need to re-visit this.Created a new issue to follow this up #594.
Zarquan
approved these changes
Dec 3, 2021
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR upgrades the versions of our components as described below:
What Issue is this related to:
#535
What type of PR is it?
Upgrade
Has this been tested:
Yes. This was tested using the Benchmarking suite that was introduced here: #583
Probably shouldn't have included the same change here, the reason for including them in the first place is that it was used for testing this branch, and the notes are based on a version that includes the benchmarker.