Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2495
---
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 e
Github user prabhjyotsingh commented on the issue:
https://github.com/apache/zeppelin/pull/2529
@zjffdu yes you are right, I originally thought I have a different idea,
but now I see, this will eventually be that. Will close this then.
---
If your project is set up for it, you can re
Github user prabhjyotsingh closed the pull request at:
https://github.com/apache/zeppelin/pull/2529
---
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 feat
Github user tinkoff-dwh commented on the issue:
https://github.com/apache/zeppelin/pull/2495
@Leemoonsoo @felixcheung
pls, merge PR
---
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 f
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/2480
IMO, it is not so urgent to do this. Interpreters and zeppelin server run
in different process, so theoretically it is not necessary to build them
together. After we move interpreters out of zeppel
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/2480
hmm, I did a quick check, eg, for beam it's still building against 2.10
https://github.com/apache/beam/blob/master/runners/spark/pom.xml#L229
Same for Ignite https://github.com/apache/ignit
Github user gfalcone commented on the issue:
https://github.com/apache/zeppelin/pull/2526
@felixcheung CI ok
https://travis-ci.org/gfalcone/zeppelin/builds/266447940?utm_source=email&utm_medium=notification
---
If your project is set up for it, you can reply to this email and have yo
Github user sadhen commented on the issue:
https://github.com/apache/zeppelin/pull/2539
@zjffdu
Your solution didn't solve the problem in the quoted:
`The critical part is that files under conf/ such as shiro.ini is part of
the docker image and should be immutable.`
Github user sanjaydasgupta commented on the issue:
https://github.com/apache/zeppelin/pull/2502
Thanks for the suggestions @felixcheung
I was not able to find more documentation on Jupyter's feature, but tried
it with many different variants. There are some behaviors that had
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2445
---
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 e
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2527
---
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 e
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2538
---
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 e
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/2541
---
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 e
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/2543
LGTM merge if no more discussion.
---
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
14 matches
Mail list logo
