Hi,
I saw some documentation about dynamic interpreter loading under
https://github.com/apache/zeppelin/blob/master/docs/manual/dynamicinterpreterload.md
but couldn't find the relevant codebase for the REST APIs. Are these need
to be archived or could you please point me to the proper location?
T
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1583
I thought Zeppelin does not read conf/shiro.ini.template, but it actually
does.
Therefore now default behavior is changed to require authentication and i
think it's not a minor change.
Github user anthonycorbacho commented on the issue:
https://github.com/apache/zeppelin/pull/1583
#1595 will fix this issue
---
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 minahlee commented on the issue:
https://github.com/apache/zeppelin/pull/1583
Since #1595 will fix the issue let's test it out quickly, and merge 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 pro
Hoon Park created ZEPPELIN-1617:
---
Summary: Setting null to builtin interpreter settings cause NPE
and 503
Key: ZEPPELIN-1617
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1617
Project: Zeppelin
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1596
Interpreter open in jobRun introduced in
https://github.com/apache/zeppelin/pull/1470 by @agoodm, to enable
https://github.com/apache/zeppelin/pull/1534. #1534 does not work with this
patch ap
Github user khalidhuseynov commented on the issue:
https://github.com/apache/zeppelin/pull/1595
tested and changes LGTM
---
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 an
Github user agoodm commented on the issue:
https://github.com/apache/zeppelin/pull/1596
@Leemoonsoo @zjffdu I placed the extra call to `open()` in `jobRun` because
I wanted to have a convenient place to make calls to `registerHook()`. We can't
do this in the `Interpreter` constructor
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1596
Thanks @agoodm for the explanation. Actually this PR would call open method
in `RemoteInterpreterServer.open` rather than in constructor, 2 reasons
* In semantics perspective, it should be calle
Github user agoodm commented on the issue:
https://github.com/apache/zeppelin/pull/1596
Well to be precise, the other reason I made the call to `open()` was to
make sure the hook registry was in effect before the first call to
`interpret()` from within `jobRun()`, and therefore, the f
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/928
Sorry for delay, @rawkintrevo !
Thank you for kind reminder on this great stuff. I want to mention this
work on ApacheCon, so hope we can merge this asap :)
I tied it and got `IOError
Github user zjffdu commented on the issue:
https://github.com/apache/zeppelin/pull/1596
`open()` will be called before the first call to `interpreter()`, so it
won't affect. Will wait for your test result tomorrow.
---
If your project is set up for it, you can reply to this email and
Github user nazgul33 commented on the issue:
https://github.com/apache/zeppelin/pull/1513
@jongyoul I could make it work with openLDAP server. I had no time to play
around with group settings, but at least I could authenticate user by
* ldapADGCRealm.userSearchAttributeName = cn
GitHub user khalidhuseynov opened a pull request:
https://github.com/apache/zeppelin/pull/1597
Shorten certain error logs in order to keep CI logs clear
### What is this PR for?
This is to shorten certain error logs in order to keep CI clear without
polluted logs.
Github user hkropp commented on the issue:
https://github.com/apache/zeppelin/pull/1589
Cool!
Just to be clear the test will simply be ignored with `assumeTrue` so
should be fine without any additional effort. How to use the test itself is
documented in the test class with co
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1584
---
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
Hoon Park created ZEPPELIN-1618:
---
Summary: Support ElasticSearch 5.0
Key: ZEPPELIN-1618
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1618
Project: Zeppelin
Issue Type: Improvement
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1597
Looks awesome, thank you for cleaning it up!
Let me try 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 doe
GitHub user 1ambda opened a pull request:
https://github.com/apache/zeppelin/pull/1598
[ZEPPELIN-1618] [WIP] Support ElasticSearch 5.0
### What is this PR for?
ElasticSearch just released in Oct 26 and It requires 5.x client driver but
zeppelin currently use 2.x only.
Github user minahlee commented on the issue:
https://github.com/apache/zeppelin/pull/1595
Test fails, can you fix it please?
---
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
enabl
Github user darionyaphet commented on the issue:
https://github.com/apache/zeppelin/pull/1497
Add a Screenshot
---
If your project is se
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1578
---
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 AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1577
@yoonjs2 I've tested this branch and found some issues.
**1.**
```
Liquid Warning: Liquid syntax error (line 77): Expected end_of_string but
found open_round in "{{noteName(not
Github user snowch closed the pull request at:
https://github.com/apache/zeppelin/pull/1309
---
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 minahlee opened a pull request:
https://github.com/apache/zeppelin/pull/1599
[HOTFIX] Always download spark binary package from archive
### What is this PR for?
* Not download Spark for first profile which does license check only
* Always download Spark from archi
GitHub user aspen01 opened a pull request:
https://github.com/apache/zeppelin/pull/1600
Using HDFS to backup and restore notebook
### What is this PR for?
This PR supports using HDFS to backup and restore notebook.
It is similar to https://github.com/apache/zeppelin/pull/1479
Github user aspen01 commented on the issue:
https://github.com/apache/zeppelin/pull/1479
I made a pull request : https://github.com/apache/zeppelin/pull/1600
---
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
Github user astroshim commented on the issue:
https://github.com/apache/zeppelin/pull/1538
@mfelgamal I got following error. Did i missed something?
```
$ docker pull mahmoudelgamal/zeppelin-release:0.6.1
0.6.1: Pulling from mahmoudelgamal/zeppelin-release
985c5f84712b:
Lee moon soo created ZEPPELIN-1619:
--
Summary: Let helium implement visualization API
Key: ZEPPELIN-1619
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1619
Project: Zeppelin
Issue Type:
Github user rawkintrevo commented on the issue:
https://github.com/apache/zeppelin/pull/928
I can address the 3 bullet points in the next day or two.
Re; the disk space- yea Mahout adds another 300MB or so. I recall seeing
some chat on the mailing list that Zeppelin was alread
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1534
@agoodm
I think placement of common python lib and problem printing output when
`close=False` can be handled in the separate issues. Do you mind create issues?
I have tested last c
alex zeltov created ZEPPELIN-1620:
-
Summary: livy.spark interpreter formatting breaks for scala with
new line
Key: ZEPPELIN-1620
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1620
Project: Zeppe
alex zeltov created ZEPPELIN-1621:
-
Summary: Zeppelin UI Login With LDAP
Key: ZEPPELIN-1621
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1621
Project: Zeppelin
Issue Type: Bug
Github user agoodm commented on the issue:
https://github.com/apache/zeppelin/pull/1534
@Leemoonsoo Sure, I will do that after this is merged.
As for your error, I cannot reproduce it. I tested both the latest code
from master as well as my fork after rebasing. How are you per
Github user rawkintrevo commented on the issue:
https://github.com/apache/zeppelin/pull/928
- [x] Fail fasts: changed `call` to
[`check_call`](https://docs.python.org/2/library/subprocess.html#check_call)
where it is appropriate to fail and exit.
- [x] Slang in standard out: Upda
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1534
@agoodm It's my bad, i was testing it with
https://github.com/apache/zeppelin/pull/1596 merged.
Tested just last commit in the branch again, and the error has gone.
---
If your project is
Github user agoodm commented on the issue:
https://github.com/apache/zeppelin/pull/1534
@Leemoonsoo Yep, I can confirm... right before you posted that comment, I
patched Never mind, I manually patched in the changes from that PR to my branch
and got the exact same stacktrace as you in
Github user agoodm commented on the issue:
https://github.com/apache/zeppelin/pull/1596
@zjffdu Please see the most recent comments @Leemoonsoo and I made in
#1534. With the vanilla python interpreter, I can indeed confirm that the call
to `open()` is being made at the right time. How
GitHub user Leemoonsoo opened a pull request:
https://github.com/apache/zeppelin/pull/1601
[TEST CI]
Try https://github.com/apache/zeppelin/pull/1599
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Leemoonsoo/zeppelin downloadSpar
GitHub user minahlee opened a pull request:
https://github.com/apache/zeppelin/pull/1602
Ci test
Test #1595 + #1599
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/minahlee/zeppelin ci_test
Alternatively you can review and apply
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/928
Interesting approach!
---
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 wis
Mina Lee created ZEPPELIN-1622:
--
Summary: Remove %dep deprecated warning
Key: ZEPPELIN-1622
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1622
Project: Zeppelin
Issue Type: Bug
Mina Lee created ZEPPELIN-1623:
--
Summary: Flaky Test - ParagraphActionsIT.testEditOnDoubleClick
Key: ZEPPELIN-1623
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1623
Project: Zeppelin
Issu
Lee moon soo created ZEPPELIN-1624:
--
Summary: HeliumApplicationFactoryTest fails on master
Key: ZEPPELIN-1624
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1624
Project: Zeppelin
Issue
GitHub user Leemoonsoo opened a pull request:
https://github.com/apache/zeppelin/pull/1603
[HOTFIX] HeliumApplicationFactoryTest fails on master
### What is this PR for?
HeliumApplicationFactoryTest fails on master with following error if i run
the test on local machine.
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1595
Tested and it works well. LGTM
---
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 Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1599
LGTM. Lets merge.
---
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 s
Benoy Antony created ZEPPELIN-1625:
--
Summary: Add support of user specific properties
Key: ZEPPELIN-1625
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1625
Project: Zeppelin
Issue Type
Benoy Antony created ZEPPELIN-1626:
--
Summary: Enable property substitution in Livy Interpreter
Key: ZEPPELIN-1626
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1626
Project: Zeppelin
I
Github user minahlee commented on the issue:
https://github.com/apache/zeppelin/pull/1599
Merging it as hotfix
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1599
---
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 minahlee closed the pull request at:
https://github.com/apache/zeppelin/pull/1602
---
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
Github user yoonjs2 commented on the issue:
https://github.com/apache/zeppelin/pull/1577
@AhyoungRyu OK I'll investigate and resolve them ASAP. Thanks for the
review :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user minahlee commented on the issue:
https://github.com/apache/zeppelin/pull/1595
Finally CI is green!!! I am merging 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
e
Github user anthonycorbacho commented on the issue:
https://github.com/apache/zeppelin/pull/1595
Hell yeah!!!
I allow you to merge 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 ha
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1595
---
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 Leemoonsoo closed the pull request at:
https://github.com/apache/zeppelin/pull/1601
---
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 Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1529
I have created following issue
https://issues.apache.org/jira/browse/ZEPPELIN-1619 for further work.
This patch refactor build-in visualizations. Now most of codes for rending
visualiz
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1534
@agoodm now CI has fixed on master. Could you rebase and see if CI test
goes green?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as we
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1565
---
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 anthonycorbacho commented on the issue:
https://github.com/apache/zeppelin/pull/1591
CI is failing due to `testEditOnDoubleClick`, and it is not related to this
PR.
So i am merging it :)
---
If your project is set up for it, you can reply to this email and have y
Anthony Corbacho created ZEPPELIN-1627:
--
Summary: Fix latency issue on note save in ZeppelinHubNotebook repo
Key: ZEPPELIN-1627
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1627
Project: Ze
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1591
---
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 Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1595
Looks like zeppelin-web dev mode (`grunt serve`) has some problem after the
patch.
@anthonycorbacho Could you take a look?
---
If your project is set up for it, you can reply to this email
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1339
@AhyoungRyu Could you rebase and see if CI test goes green?
---
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
Github user agoodm commented on the issue:
https://github.com/apache/zeppelin/pull/1534
@Leemoonsoo Tests are done, the only failure seems to be from a known flaky
test [ZEPPELIN-1623](https://issues.apache.org/jira/browse/ZEPPELIN-1623). Are
we good to merge?
---
If your project is
GitHub user anthonycorbacho opened a pull request:
https://github.com/apache/zeppelin/pull/1604
[HOT-FIX] - Prevent double injection of cross-origin headers from rest api
### What is this PR for?
Prevent error `XMLHttpRequest cannot load
http://localhost:8080/api/version. The 'A
Github user anthonycorbacho commented on the issue:
https://github.com/apache/zeppelin/pull/1595
@Leemoonsoo thank you for the feedback, please fix the fix under PR #1604
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1604
Tested and LGTM
---
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,
69 matches
Mail list logo
