[GitHub] zeppelin issue #3074: [ZEPPELIN-3610] Cluster Raft module design

2018-07-22 Thread jongyoul
Github user jongyoul commented on the issue: https://github.com/apache/zeppelin/pull/3074 Got it. I hope not to spend much time merging this feature into the master branch after finishing implementations. On Mon, Jul 23, 2018 at 3:22 PM, Jeff Zhang wrote: > @j

[GitHub] zeppelin issue #3074: [ZEPPELIN-3610] Cluster Raft module design

2018-07-22 Thread zjffdu
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/3074 @jongyoul This is for the zeppelin HA feature which will involve many PRs. Here's the pros and cons of creating new branch. Pros. 1. Move fast of implementing this feature 2. Keep the ma

[GitHub] zeppelin issue #3077: [ZEPPELIN-3631] Increase the maven-shade-plugin versio...

2018-07-22 Thread jongyoul
Github user jongyoul commented on the issue: https://github.com/apache/zeppelin/pull/3077 Can you rebase your PRs from the latest master branch? We have fixed CI and you might get green. ---

[GitHub] zeppelin issue #3001: [ZEPPELIN-3524] Replace the Amazon json libs with org....

2018-07-22 Thread jongyoul
Github user jongyoul commented on the issue: https://github.com/apache/zeppelin/pull/3001 Sorry for the late reply. As you mentioned, Zeppelin already has two or more json dependencies at the same time, but I don't think it's good and we can fix it when we can do and have a chance. Ho

[GitHub] zeppelin issue #3074: [ZEPPELIN-3610] Cluster Raft module design

2018-07-22 Thread jongyoul
Github user jongyoul commented on the issue: https://github.com/apache/zeppelin/pull/3074 BTW, it looks hard to maintain a new branch for a new feature. we already use github's PR and we can test it by pulling PR with dev/test_pr WDYT? On Mon, Jul 23, 2018

[GitHub] zeppelin issue #3074: [ZEPPELIN-3610] Cluster Raft module design

2018-07-22 Thread zjffdu
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/3074 It make sense @liuxunorg , I will create a new branch for this feature. ---

[GitHub] zeppelin issue #3074: [ZEPPELIN-3610] Cluster Raft module design

2018-07-22 Thread liuxunorg
Github user liuxunorg commented on the issue: https://github.com/apache/zeppelin/pull/3074 @Tagar @jongyoul @zjffdu If the community feels that zeppelin has been added to the clustering feature, the changes are relatively large. Is it possible to add a new code branch? This can b

[GitHub] zeppelin issue #3074: [ZEPPELIN-3610] Cluster Raft module design

2018-07-22 Thread liuxunorg
Github user liuxunorg commented on the issue: https://github.com/apache/zeppelin/pull/3074 hi @Tagar , Increasing the service state consistency of the system through zookeeper is a common practice in distributed systems. But this will cause zeppelin to rely on an external service zook

[GitHub] zeppelin issue #3074: [ZEPPELIN-3610] Cluster Raft module design

2018-07-22 Thread Tagar
Github user Tagar commented on the issue: https://github.com/apache/zeppelin/pull/3074 Just out of curiosity, why Raft Protocol? Have you considered alternatives, for example, Zookeeper could do here, I guess. I think what the design document is missing is some sort of pros and cons c

Re: Revert ZEPPELIN-3593

2018-07-22 Thread Jeff Zhang
Thanks Jongyoul Jongyoul Lee 于2018年7月23日周一 下午1:26写道: > Hi, > > I've reverted ZEPPELIN-3593 as it doesn't look stable for the production > environment. I'll create a new PR after adding an option setting to enable > it. It will be disabled by default. > > Regards, > JL > > -- > 이종열, Jongyoul Lee,

[GitHub] zeppelin pull request #3088: [HOTFIX] Disable some flaky tests

2018-07-22 Thread jongyoul
Github user jongyoul closed the pull request at: https://github.com/apache/zeppelin/pull/3088 ---

[GitHub] zeppelin issue #3088: [HOTFIX] Disable some flaky tests

2018-07-22 Thread jongyoul
Github user jongyoul commented on the issue: https://github.com/apache/zeppelin/pull/3088 Will close and make several PR to replace them ---

Revert ZEPPELIN-3593

2018-07-22 Thread Jongyoul Lee
Hi, I've reverted ZEPPELIN-3593 as it doesn't look stable for the production environment. I'll create a new PR after adding an option setting to enable it. It will be disabled by default. Regards, JL -- 이종열, Jongyoul Lee, 李宗烈 http://madeng.net

[GitHub] zeppelin issue #3088: [HOTFIX] Disable some flaky tests

2018-07-22 Thread jongyoul
Github user jongyoul commented on the issue: https://github.com/apache/zeppelin/pull/3088 @zjffdu https://travis-ci.org/jongyoul/zeppelin/builds/406977293 Jenkins seems to become bad ---

[GitHub] zeppelin pull request #3088: [HOTFIX] Disable some flaky tests

2018-07-22 Thread jongyoul
GitHub user jongyoul reopened a pull request: https://github.com/apache/zeppelin/pull/3088 [HOTFIX] Disable some flaky tests ### What is this PR for? Some tests become failed due to https://issues.apache.org/jira/browse/ZEPPELIN-3593 BTW, it looks like a timing issue. I saw som

[GitHub] zeppelin pull request #3088: [HOTFIX] Disable some flaky tests

2018-07-22 Thread jongyoul
Github user jongyoul closed the pull request at: https://github.com/apache/zeppelin/pull/3088 ---

[GitHub] zeppelin pull request #3088: [HOTFIX] Disable some flaky tests

2018-07-22 Thread jongyoul
GitHub user jongyoul opened a pull request: https://github.com/apache/zeppelin/pull/3088 [HOTFIX] Disable some flaky tests ### What is this PR for? Some tests become failed due to https://issues.apache.org/jira/browse/ZEPPELIN-3593 BTW, it looks like a timing issue. I saw some

[GitHub] zeppelin issue #3087: [ZEPPELIN-3644]: Adding SPARQL query language support ...

2018-07-22 Thread zjffdu
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/3087 @padmacs Can you describe more details about this PR ? What features does this PR provide ? Screenshot will be helpful. ---

[jira] [Created] (ZEPPELIN-3650) Fix this bug that show output twice "sometimes" after refreshing browser

2018-07-22 Thread Jongyoul Lee (JIRA)
Jongyoul Lee created ZEPPELIN-3650: -- Summary: Fix this bug that show output twice "sometimes" after refreshing browser Key: ZEPPELIN-3650 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3650 Proj

[GitHub] zeppelin issue #3035: [ZEPPELIN-3553] Fix URLs on "Multi-user Support" page

2018-07-22 Thread zjffdu
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/3035 I plan to have 0.8.1 release for critical bug fixes. So please merge to branch-0.8 as well ---

[GitHub] zeppelin issue #3035: [ZEPPELIN-3553] Fix URLs on "Multi-user Support" page

2018-07-22 Thread felixcheung
Github user felixcheung commented on the issue: https://github.com/apache/zeppelin/pull/3035 we don't have a 0.9 branch or plan yet. should we backport to 0.8? are we having another release, like 0.8.1? ---

[GitHub] zeppelin issue #3035: [ZEPPELIN-3553] Fix URLs on "Multi-user Support" page

2018-07-22 Thread felixcheung
Github user felixcheung commented on the issue: https://github.com/apache/zeppelin/pull/3035 I don't this is ported to 0.8 https://github.com/apache/zeppelin/commits/branch-0.8 ---

[GitHub] zeppelin issue #3066: [ZEPPELIN-3618] ZeppelinContext methods z.run and z.ru...

2018-07-22 Thread felixcheung
Github user felixcheung commented on the issue: https://github.com/apache/zeppelin/pull/3066 can you comment on my comment: `this doesn't seem quite right, we are ignoring all IOException from running the paragraph?`? ---

[jira] [Created] (ZEPPELIN-3649) When multiple people edit the same note, there is no prompt message.

2018-07-22 Thread liuxun (JIRA)
liuxun created ZEPPELIN-3649: Summary: When multiple people edit the same note, there is no prompt message. Key: ZEPPELIN-3649 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3649 Project: Zeppelin

[jira] [Created] (ZEPPELIN-3648) Implement new methods related to handling ZeppelinContext via paragraph

2018-07-22 Thread Jongyoul Lee (JIRA)
Jongyoul Lee created ZEPPELIN-3648: -- Summary: Implement new methods related to handling ZeppelinContext via paragraph Key: ZEPPELIN-3648 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3648 Proje

[jira] [Created] (ZEPPELIN-3647) Implement InterpreterModeActionsIT again not to use IntegrationTest

2018-07-22 Thread Jongyoul Lee (JIRA)
Jongyoul Lee created ZEPPELIN-3647: -- Summary: Implement InterpreterModeActionsIT again not to use IntegrationTest Key: ZEPPELIN-3647 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3647 Project: