Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1886
@sotnich Can you rebase it onto current master? Recently, we fixed some
flaky tests including your case. It would make your CI green
---
If your project is set up for it, you can reply to this
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1911
Concerning `ClassloaderInterpreter`, you can find it
https://github.com/apache/zeppelin/blob/master/zeppelin-interpreter/src/main/java/org/apache/zeppelin/interpreter/ClassloaderInterpreter.java
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1911
It actually wrap and conserve classloader for interpreter. I think you just
change this line
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1864
---
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
+1 (binding)
On Tue, Jan 24, 2017 at 2:43 PM, Mina Lee wrote:
> I propose the following RC to be released for the Apache Zeppelin 0.7.0
> release.
>
> The commit id is 48ad70e8c62975bdb00779bed5919eaca98c5b5d which is
> corresponds to the tag v0.7.0-rc3:
>
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1864
Will merge it into master and branch-0.7
---
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
I propose the following RC to be released for the Apache Zeppelin 0.7.0
release.
The commit id is 48ad70e8c62975bdb00779bed5919eaca98c5b5d which is
corresponds to the tag v0.7.0-rc3:
*https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=commit;h=48ad70e8c62975bdb00779bed5919eaca98c5b5d
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1931
---
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 asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1833
---
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 asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1921
---
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 Leemoonsoo opened a pull request:
https://github.com/apache/zeppelin/pull/1936
[ZEPPELIN-2004] List all helium packages in Zeppelin GUI
### What is this PR for?
ZEPPELIN-1973 will provides catalogue for all available helium
(visualization) packages in npm registry.
Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/1833
Thanks all you guys for testing it out!
Will merge if there are no more comments.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
GitHub user AhyoungRyu opened a pull request:
https://github.com/apache/zeppelin/pull/1935
[gh-pages][ZEPPELIN-1973] List all available Helium packages under
zeppelin.apache.org
### What is this PR for?
After #1842 merged, anyone can create his/her own `VISUALIZATION` pkg as
Github user 1ambda commented on the issue:
https://github.com/apache/zeppelin/pull/1902
@bbonnin ð
@jongyoul I will take a look more deeply :)
---
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 asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1933
---
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 asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1932
---
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 anthonycorbacho commented on the issue:
https://github.com/apache/zeppelin/pull/1934
merging 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
Github user Tagar commented on the issue:
https://github.com/apache/zeppelin/pull/1931
Tested today's master merged with #1931 and #1921 and it works great. LGTM
Thanks again.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user cloverhearts commented on the issue:
https://github.com/apache/zeppelin/pull/1864
@jongyoul ping~
---
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
I'm seeing the same behavior with the marital status drop down box on the intro
notebook on netinst build.
I think this could be a bigger problem.
_
From: Khalid Huseynov >
Sent: Sunday, January 22, 2017 8:08 PM
Subject:
I created https://issues.apache.org/jira/browse/ZEPPELIN-2003
On Mon, Jan 23, 2017 at 10:56 PM, Jongyoul Lee wrote:
> Thanks for replying it. I'll make a PR for doing it.
>
> On Mon, Jan 23, 2017 at 4:09 PM, Prabhjyot Singh <
> prabhjyotsi...@apache.org> wrote:
>
>> +1.
>>
Jongyoul Lee created ZEPPELIN-2003:
--
Summary: Remove PostgresqlInterpreter
Key: ZEPPELIN-2003
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2003
Project: Zeppelin
Issue Type: Task
Thanks for replying it. I'll make a PR for doing it.
On Mon, Jan 23, 2017 at 4:09 PM, Prabhjyot Singh
wrote:
> +1.
>
> Yes, agreed I too think its overhead, and all the features can be achieved
> via JDBCInterpreter.
>
> On 23 January 2017 at 10:45, Jongyoul Lee
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1919
@Leemoonsoo Actually, in this case, I also don't have any better idea than
what you do :-) Just worried about becoming more rare flaky test.
---
If your project is set up for it, you can reply
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1932
LGTM. @minahlee Can you merge it asap and make a new rc, too?
---
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
Hi Igor,
I think it's also good idea to change loading logic but it would be
affected all step while loading, thus you should be careful to change those
codes, especially side-effect. one good idea is to copy
interpreter-setting.json including r settings when user build it with
`-Pr`. It looks a
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1833
Tested. 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,
Thank you for reply!
I found an issue https://issues.apache.org/jira/browse/ZEPPELIN-1081. I think
It's good idea not to include R interpreter with R profile disabled.
Small changes to InterpreterFactory will allow us to load several
interpreter-settings.jsons from different jar.
Github user soralee commented on the issue:
https://github.com/apache/zeppelin/pull/1833
Tested and it works very well!
---
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 DrIgor commented on the issue:
https://github.com/apache/zeppelin/pull/1911
@Leemoonsoo @jongyoul thank you! I didn't know about ClassLoaderInterpreter
Unfortunately, our tests don't use InterpreterFactory and will use
unwrapped Interpreter instance. So It won't
Github user astroshim commented on the issue:
https://github.com/apache/zeppelin/pull/1833
LGTM it's working well.
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1808
---
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 Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1808
Merge it master and branch-0.7
---
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
Abou Haydar Elias created ZEPPELIN-2002:
---
Summary: Can not get or update progress after adding dependency in
the interpreter
Key: ZEPPELIN-2002
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2002
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1913
---
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 Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1919
@jongyoul I don't have any good idea except for change test to use less
resources when travis is under resource starvation. Do you have any good idea?
---
If your project is set up for it,
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1931
Thanks @felixcheung @Tagar reviewing it.
Merge to master if no further comments
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user asfgit closed the pull request at:
https://github.com/apache/zeppelin/pull/1908
---
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 bbonnin commented on the issue:
https://github.com/apache/zeppelin/pull/1902
It looks better now, all is 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 not have this feature
Github user soralee commented on the issue:
https://github.com/apache/zeppelin/pull/1804
Ping!
---
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
Github user soralee commented on the issue:
https://github.com/apache/zeppelin/pull/1932
LGTM! Tested as described and it worked very well.
![z2000_a](https://cloud.githubusercontent.com/assets/8110458/22195973/01e07d98-e18e-11e6-928b-1a63d29443e6.gif)
---
If your project
41 matches
Mail list logo