Github user bikassaha commented on the issue:
https://github.com/apache/zeppelin/pull/1787
In a different jira, should we consider removing this check for 2.1, 2.2
since its unlikely that Spark will break common APIs in dot releases. Perhaps
the policy can change to adding a check when a known incompatible Spark version
shows up (until that gets supported in Zeppelin). Thoughts?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
