Github user epahomov closed the pull request at:
https://github.com/apache/zeppelin/pull/1872
---
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
Github user epahomov commented on the issue:
https://github.com/apache/zeppelin/pull/1965
Love it. Everything very clear
---
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
Github user epahomov commented on the issue:
https://github.com/apache/zeppelin/pull/1873
@Leemoonsoo , honestly speaking, I don't know. But I've tested this fix in
very isolated env(docker) and it's fixes it. I'm not saying that it's strong
argument to fix issue this way, but may
GitHub user epahomov opened a pull request:
https://github.com/apache/zeppelin/pull/1873
[ZEPPELIN-1922] Exclude jackson-core and jackson-databind from aws dep
### What is this PR for?
Master version of https://github.com/apache/zeppelin/pull/1872
### What
GitHub user epahomov opened a pull request:
https://github.com/apache/zeppelin/pull/1872
[ZEPPELIN-1922] Exclude jackson-core and jackson-databind from aws dep
### What is this PR for?
Fix jar hell around jackson. aws-java-sdk-s3 braings 2.5.3
### What type of PR
Github user epahomov commented on the issue:
https://github.com/apache/zeppelin/pull/1688
Yeaaa, I love it!
---
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
