Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1911
@DrIgor I agree with you. It's very easily broken. But on the other hands,
I will make a new PR for changing `ClassloaderInterpreter` because another
interpreter will fails with same issue
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1992
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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1999
Looks nice
---
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
GitHub user jongyoul opened a pull request:
https://github.com/apache/zeppelin/pull/2001
ZEPPELIN-2057 Extract InterpreterSetting functions from InterpreterFactory
### What is this PR for?
Reducing size of InterpreterFactory and divide some functions from
InterpreterFactory
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1976
@cloverhearts Can you check 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
Jongyoul Lee created ZEPPELIN-2057:
--
Summary: Extract InterpreterSetting functions from
InterpreterFactory
Key: ZEPPELIN-2057
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2057
Project
Jongyoul Lee created ZEPPELIN-2056:
--
Summary: Restructuring InterpreterFactory
Key: ZEPPELIN-2056
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2056
Project: Zeppelin
Issue Type
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1970
I didn't find a history for it but your code snippet tells us no spark
properties doesn't affect anymore in current spark. LGTM
---
If your project is set up for it, you can reply to this email
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1970
That's intended behavior because Zeppelin wants to pass some other
properties not starting "spark.". I didn't remembers exactly, but some
properties should be passed with different pre
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1946
@DrIgor The last failures looks related to this PR. Can you check it?
- https://api.travis-ci.org/jobs/197657609/log.txt?deansi=true
---
If your project is set up for it, you can reply
t; >>> > >
> > >>> > > The release archives (tgz), signature, and checksums are here
> > >>> > >
> > https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.7.0-rc4/
> > >>> > >
> > >>> > > The release candidate consists of the following source
> distribution
> > >>> > > archive
> > >>> > > zeppelin-0.7.0.tgz
> > >>> > >
> > >>> > > In addition, the following supplementary binary distributions are
> > >>> > provided
> > >>> > > for user convenience at the same location
> > >>> > > zeppelin-0.7.0-bin-all.tgz
> > >>> > > zeppelin-0.7.0-bin-netinst.tgz
> > >>> > >
> > >>> > > The maven artifacts are here
> > >>> > >
> > >>> > https://repository.apache.org/content/repositories/orgapache
> > >>> zeppelin-1027
> > >>> > >
> > >>> > > You can find the KEYS file here:
> > >>> > > https://dist.apache.org/repos/dist/release/zeppelin/KEYS
> > >>> > >
> > >>> > > Release notes available at
> > >>> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > >>> > > version=12336544=12316221
> > >>> > >
> > >>> > > Vote will be open for next 72 hours (close at 01:00 5/Feb PST).
> > >>> > >
> > >>> > > [ ] +1 approve
> > >>> > > [ ] 0 no opinion
> > >>> > > [ ] -1 disapprove (and reason why)
> > >>> > >
> > >>> >
> > >>> >
> > >>> >
> > >>>
> > >>> --
> > >>> Taejun Kim
> > >>>
> > >>> Data Mining Lab.
> > >>> School of Electrical and Computer Engineering
> > >>> University of Seoul
> > >>>
> > >>>
> > >>>
> > >>
> >
> >
>
--
이종열, Jongyoul Lee, 李宗烈
http://madeng.net
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1968
LGTM. merging if there's 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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1929
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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1961
Thanks. 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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1929
Is there any update? :-)
---
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 jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1911
Is there any update on 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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1945
@AhyoungRyu Please check the change.
---
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 jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1961
Cool. Can you tell me how to test it by myself?
---
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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1946
I merged #1937. Can you rebase it onto master and make CI 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
Jongyoul Lee created ZEPPELIN-2041:
--
Summary: Introduce a new abstraction layer for managing and
launching interpreters
Key: ZEPPELIN-2041
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2041
Jongyoul Lee created ZEPPELIN-2040:
--
Summary: ClusterManager to support launching interpreter in a
cluster
Key: ZEPPELIN-2040
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2040
Project
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1937
I'll merge this PR and will make a new PR to handle with Jeff's worries
which are reasonable and should be maintained.
---
If your project is set up for it, you can reply to this email and have
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1944
If you remove that dependency, I think you cannot compile zeppelin-server
test.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1957
If you contribute code based on master, we will review and merge it into
master and branch-0.7 if necessary.
---
If your project is set up for it, you can reply to this email and have your
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1945
I made a link. @AhyoungRyu Can you verify the doc?
---
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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1958
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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1954
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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1959
Good plan :-)
---
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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1957
Thanks for contributing new Groovy interpreter but we didn't manage the
branch-0.6 anymore. Can you rebase your contribution onto current master?
---
If your project is set up for it, you can
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1947
Will merge it onto 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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1945
@felixcheung Sounds like a good idea!
---
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 jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1944
My command only includes
`/Users/jl/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar`
which is different from `org.apache.httpclient`. Can you show me your
GitHub user jongyoul opened a pull request:
https://github.com/apache/zeppelin/pull/1947
[HOTFIX][ZEPPELIN-2013] Exceeded size of logs makes CI failed
### What is this PR for?
avoiding failure of CI due to exceeded limit of log size.
https://s3.amazonaws.com/archive.travis
Jongyoul Lee created ZEPPELIN-2013:
--
Summary: Exceeded logs fails CI
Key: ZEPPELIN-2013
URL: https://issues.apache.org/jira/browse/ZEPPELIN-2013
Project: Zeppelin
Issue Type: Sub-task
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1944
Yes, Sure. But when IntelliJ runs ZeppelinServer in debug mode, actual
command is what I mentioned before which doesn't include any httpclient
libraries but include zeppelin-{zengine,interpreter
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1911
Got it. How about wrapping it like `new ClassloaderInterpreter(new
IgniteInterpreter(props))`? It's the same logic that RemoteInterpreter want to
work. You should change this line
https
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1937
@DrIgor I know, I just ask you for making R-related PR on top of this 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
GitHub user jongyoul opened a pull request:
https://github.com/apache/zeppelin/pull/1945
[ZEPPELIN-2003] Remove PostgresqlInterpreter
### What is this PR for?
We don't have to maintain PostgresqlInterpreter because JDBCInterpreter
covers all functions of PostgresqlInterpreter
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1942
@zjffdu Can you also verify 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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1944
@Leemoonsoo Since initializing Helium, helium tried to load httpclient but
it couldn't do and error occurs like this
```
Caused by: java.lang.NoClassDefFoundError:
org/apache/http
GitHub user jongyoul opened a pull request:
https://github.com/apache/zeppelin/pull/1944
[HOTFIX][MINOR] Change the scope of httpclient to runtime from test
### What is this PR for?
When IDE runs ZeppelinServer in debugging mode, it doesn't load httpclient
because its scope
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1914
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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1937
@DrIgor Did you test this PR with `-Pr` profile? this PR looks good to me
but we need to test it. I think you can test it by running Zeppelin with r
profile. How about you?
---
If your project
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
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
https://github.com/apache/zeppelin/blob/master/zeppelin-interpreter/src/main/java/org/apache/zeppelin
t/release/zeppelin/KEYS
>
> Release notes available at
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> version=12336544=12316221
>
> Vote will be open for next 72 hours (close at 22:00 26/Jan PST).
>
> [ ] +1 approve
> [ ] 0 no opinion
> [ ] -1 disapprove (and reason why)
>
--
이종열, Jongyoul Lee, 李宗烈
http://madeng.net
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
I created https://issues.apache.org/jira/browse/ZEPPELIN-2003
On Mon, Jan 23, 2017 at 10:56 PM, Jongyoul Lee <jongy...@gmail.com> 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...@apach
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 <prabhjyotsi...@apache.org>
wrote:
> +1.
>
> Yes, agreed I too think its overhead, and all the features can be achieved
> via JDBCInterpreter.
>
> On 23 January 201
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
a bit weird but because zeppelin-zrinterpreter.jar doesn't
have to include interpreter-setting.json inside it, it's ok to have all
interpreter-setting.json in zeppelin-spark.jar. I'm willing to review your
new PR though. :-)
Regards,
Jongyoul
On Mon, Jan 23, 2017 at 7:26 PM, Igor Drozdov <igor_d
. But, now, JDBCInterpreter include all functions of
PostgresqlInterpreter and provide better functions.
How do you guys think of it? If it's accepted, 0.8.0 won't have
PostgresqlInterpreter anymore.
Regards,
Jongyoul Lee
--
이종열, Jongyoul Lee, 李宗烈
http://madeng.net
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1919
@Leemoonsoo I think to prolong timeout would be realistic solution but same
error may occurs when travis is under resources starvation. Can we handle it?
---
If your project is set up
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1896
I've missed it. I thought it was flaky tests. Got 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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1916
I see.
---
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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1918
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
eter is never loaded!
> >
> > Could anyone confirm that R interpreter does not work for now? Or it
> > is my local misconfiguration?
> >
> > Thank you,
> > Igor Drozdov
> >
>
--
이종열, Jongyoul Lee, 李宗烈
http://madeng.net
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1896
LGTM. will 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 have this feature
enabled and wishes
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1916
Is it ok to remove 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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1914
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
ke new release.
>
> Please help comment on these 4 questions and feel free to add any things
> that I miss.
>
>
> [1] https://lists.apache.org/thread.html/69f606409790d7ba11422e8c6df941
> a75c5dfae0aca63eccf2f840bf@%3Cusers.zeppelin.apache.org%3E
>
--
이종열, Jongyoul Lee, 李宗烈
http://madeng.net
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1886
There is a flaky test in the result:
```
WelcomePageSuite
```
Never mind the result. that test is being fixed now. LGTM
---
If your project is set up for it, you can
I can change some fields and types but cannot convert all tickets to
sub-task. I'll change them manually.
On Thu, Jan 19, 2017 at 4:20 PM, Jeff Zhang <zjf...@gmail.com> wrote:
> Hi Jongyoul,
>
> Could you move all these tickets under this umbrella ticket ?
>
> You can do bu
Thanks Jeff,
I made a new PR for handling this issue.
https://issues.apache.org/jira/browse/ZEPPELIN-1981
On Thu, Jan 19, 2017 at 9:47 AM, Jianfeng (Jeff) Zhang <
jzh...@hortonworks.com> wrote:
> +1
>
> Best Regard,
> Jeff Zhang
>
>
>
>
>
> On 1/1
Jongyoul Lee created ZEPPELIN-1981:
--
Summary: Fix all flaky tests
Key: ZEPPELIN-1981
URL: https://issues.apache.org/jira/browse/ZEPPELIN-1981
Project: Zeppelin
Issue Type: Task
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1902
@1ambda Can you review this PR 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 does not have this feature
> > > Fixing the flaky test may take some time and may not easy for some
> test
> > > but
> > > > I think it is worth to do that. And it is better for these people
> who
> > > > familiar with that particular test case to fix it. What do you guys
> > > think ?
> > > > Thanks
> > > >
> > > --
> > > Taejun Kim
> > >
> > > Data Mining Lab.
> > > School of Electrical and Computer Engineering
> > > University of Seoul
> > >
> >
> --
> Taejun Kim
>
> Data Mining Lab.
> School of Electrical and Computer Engineering
> University of Seoul
>
>
>
--
이종열, Jongyoul Lee, 李宗烈
http://madeng.net
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1864
@cloverhearts the failed test looks related this patch. Can you check it?
```
Failed tests:
NoteInterpreterLoaderTest.testNoteInterpreterCloseForAll:192 null
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1911
LGMT. I have a question. Is there any related issue to SparkInterpreter?
Can you take a look into it?
---
If your project is set up for it, you can reply to this email and have your
reply
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1910
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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1846
LGTM, merging if there's 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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1895
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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1898
I'm not sure the code but idea looks good to me.
---
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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1891
LGTM, I saw your description and it makes sense to me.
---
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 jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1842
Good job! @Leemoonsoo
---
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 jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1890
Good!! 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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1890
@minahlee I think `-Pr` doesn't mean anything because users cannot run R
interpreter since `-Psparkr` is enabled. How about removing `-Pr` in a script?
---
If your project is set up for it, you
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1891
Does this PR resolve flaky test that current master encounters?
---
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 jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1891
Thanks for the contribution. Can you make a test case for 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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1889
Let's merge it now. :-)
---
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 jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1840
Merged 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 feature
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1747
LGTM. Merging if there's 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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1883
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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1882
Merged 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 feature
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1884
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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1883
@minahlee You need to change `helium-dev`, 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 not have
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/725
It looks unmanaged now
---
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 jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1886
@astroshim Could you please review this 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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1846
Tests LGTM. Thanks!
---
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 jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1871
Will merge it if there's 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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1872
You don't have to make two PRs for adopting multiple branches. We can merge
it into several branches with one commit if there's no conflict. Can you please
close this PR?
---
If your project
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1875
@1ambda Does it reduce the build time of web module?
---
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
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1838
@cloverhearts The last travis doesn't look related error.
---
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 jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1871
@Leemoonsoo @AhyoungRyu @soralee Can you review this PR? you just build it
with `-Phelium-dev` and run clock example.
---
If your project is set up for it, you can reply to this email and have
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1796
CI is green. Will 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 have this feature
enabled
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1845
@astroshim Can you also review this 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 feature
Github user jongyoul commented on the issue:
https://github.com/apache/zeppelin/pull/1808
Will merge it if there's 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
801 - 900 of 1423 matches
Mail list logo
