[jira] [Created] (ZEPPELIN-2295) Add option for BigQuery Standard SQL

[m k (JIRA)]

m k created ZEPPELIN-2295:
-

 Summary: Add option for BigQuery Standard SQL
 Key: ZEPPELIN-2295
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2295
 Project: Zeppelin
  Issue Type: Improvement
  Components: Interpreters
Affects Versions: 0.7.0
 Environment: GCP VM , Cent7
Reporter: m k
 Fix For: 0.7.0


It seems not able to set Standard SQL at Big Query interpreter on Zeppelin.
(Legacy SQL would be implicitly used at the Big Query interpreter) 

If there is already the function available in zeppelin, let me know the way to 
set the parameter to Big Query interpreter on Zeppelin.

Ref:Standard SQL 
(https://cloud.google.com/bigquery/sql-reference/enabling-standard-sql).




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: zeppelin-web module build failure with latest 0.8.0-SNAPSHOT

[Chaoran Yu]

Maven was not able to obtain the plexus-io-2.1.2.pom file. “Connection reset” 
is the error I’m referring to.
Eventually the build of zeppelin-web component failed.

Initially I thought it’s a network problem that Maven is not able to retrieve 
the artifact, but it’s happening consistently to me while I’m able to retrieve 
other artifacts.

Maybe it’s something with Mac that’s not working. I’ve tried on Windows and the 
build worked.

Chaoran


> On Mar 21, 2017, at 11:48 PM, Ahyoung Ryu  wrote:
> 
> Hi Chaoran, 
> 
> This is what I can see in your email.  
> 
>  
> Can't see any error messages in this. Can you point me which part was the 
> problem with you exactly? 
> 
> Thanks,
> Ahyoung
> 
> On Wed, Mar 15, 2017 at 12:30 AM, Chaoran Yu  > wrote:
> I’m trying to build the latest repo i.e. version 0.8.0-SNAPSHOT, but got the 
> following error message:
> 
> [INFO] --- maven-war-plugin:2.5:war (default-war) @ zeppelin-web ---
> [INFO] Downloading: 
> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-io/2.1.3/plexus-io-2.1.3.pom
>  
> 
> Mar 12, 2017 1:01:12 PM 
> org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec 
> execute
> INFO: I/O exception (java.net.SocketException) caught when processing request 
> to {s}->https://repo.maven.apache.org:443: 
>  Connection reset
> Mar 12, 2017 1:01:12 PM 
> org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec 
> execute
> INFO: Retrying request to {s}->https://repo.maven.apache.org:443 
> 
> Mar 12, 2017 1:01:12 PM 
> org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec 
> execute
> INFO: I/O exception (java.net.SocketException) caught when processing request 
> to {s}->https://repo.maven.apache.org:443: 
>  Connection reset
> Mar 12, 2017 1:01:12 PM 
> org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec 
> execute
> INFO: Retrying request to {s}->https://repo.maven.apache.org:443 
> 
> Mar 12, 2017 1:01:12 PM 
> org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec 
> execute
> INFO: I/O exception (java.net.SocketException) caught when processing request 
> to {s}->https://repo.maven.apache.org:443: 
>  Connection reset
> Mar 12, 2017 1:01:12 PM 
> org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec 
> execute
> INFO: Retrying request to {s}->https://repo.maven.apache.org:443 
> 
> [INFO] Downloading: 
> https://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-archiver/2.6.3/plexus-archiver-2.6.3.pom
>  
> 
> Mar 12, 2017 1:01:12 PM 
> org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec 
> execute
> INFO: I/O exception (java.net.SocketException) caught when processing request 
> to {s}->https://repo.maven.apache.org:443: 
>  Connection reset
> Mar 12, 2017 1:01:12 PM 
> org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec 
> execute
> INFO: Retrying request to {s}->https://repo.maven.apache.org:443 
> 
> 
> Did anyone get the same error? I’ve also encountered the same problem with 
> version 0.7.0.
> 
> Thank you,
> Chaoran Yu
> 

[jira] [Created] (ZEPPELIN-2294) Interpreter fail exception is not propagated to frontend

[Jeff Zhang (JIRA)]

Jeff Zhang created ZEPPELIN-2294:


 Summary: Interpreter fail exception is not propagated to frontend
 Key: ZEPPELIN-2294
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2294
 Project: Zeppelin
  Issue Type: Bug
Affects Versions: 0.7.0
Reporter: Jeff Zhang






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zeppelin issue #2174: [ZEPELIN-2209] Add pagination to Helium menu

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2174
  
@1ambda Will be really appreciated if you can help review this! 


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin pull request #2174: [ZEPELIN-2209] Add pagination to Helium menu

[AhyoungRyu]

GitHub user AhyoungRyu opened a pull request:

https://github.com/apache/zeppelin/pull/2174

[ZEPELIN-2209] Add pagination to Helium menu

### What is this PR for?
Like I did in #2126, added pagination to Helium menu in Zeppelin. 
10 pkgs will be shown per 1 page. 

### What type of PR is it?
Improvement

### What is the Jira issue?
[ZEPPELIN-2209](https://issues.apache.org/jira/browse/ZEPPELIN-2209)

### How should this be tested?
1. Replace temporarily 
[ZeppelinConfiguration.java#L46](https://github.com/apache/zeppelin/blob/master/zeppelin-zengine/src/main/java/org/apache/zeppelin/conf/ZeppelinConfiguration.java#L46)
 with [this 
url](https://raw.githubusercontent.com/AhyoungRyu/spark-notebook-example/master/helium.json)

2. Build \w below command and restart Zeppelin server
```
 $ mvn clean package -DskipTests -pl 'zeppelin-zengine, zeppelin-server, 
zeppelin-interpreter'
```

3. Start web dev server under `ZEPPELIN_HOME/zeppelin-web` and browse 
`localhost:9000`
```
$ yarn run dev
```

4. Go to Helium menu -> Click `INTERPRETER` btn 
(Currently the other types of pkg are registered in online registry less 
than 10. That's why I request to change online registry URI in step 1)
5. Check the pagination works well or not

### Screenshots (if appropriate)

![record](https://cloud.githubusercontent.com/assets/10060731/24182469/58ec965e-0f05-11e7-8cf9-eca7d36c0106.gif)

### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? no


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/AhyoungRyu/zeppelin add/paginationToHeliumMenu

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zeppelin/pull/2174.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2174


commit 81a245fcd9220fee2d2a132d5a042caa41c9b454
Author: RyuAhyoung 
Date:   2017-03-22T04:35:41Z

Add pagination to Helium menu




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (ZEPPELIN-2293) Remove envName from interpreter-setting.json

[Jeff Zhang (JIRA)]

Jeff Zhang created ZEPPELIN-2293:


 Summary: Remove envName from interpreter-setting.json
 Key: ZEPPELIN-2293
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2293
 Project: Zeppelin
  Issue Type: Bug
  Components: Interpreters
Affects Versions: 0.7.0
Reporter: Jeff Zhang
Assignee: Jeff Zhang
 Fix For: 0.8.0


Environmental variable is only used in ZeppelinConfiguration. But Interpreter 
use properties to access interpreter setting instead of ZeppelinConfiguration, 
so we should remove envName from interpreter-setting.json, otherwise it would 
confuse users. 
\cc [~moon] [~jongyoul] 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

RE: [VOTE] Release Apache Zeppelin 0.7.1 (RC1)

[CloverHeartsDev]

+1

-Original Message-
From: Ahyoung Ryu [mailto:ahyoung...@apache.org] 
Sent: Wednesday, March 22, 2017 12:27 PM
To: dev@zeppelin.apache.org
Subject: Re: [VOTE] Release Apache Zeppelin 0.7.1 (RC1)

+1

On Wed, Mar 22, 2017 at 12:19 PM, Jeff Zhang  wrote:

>
> 0
>
> 1. Build it from source successfully
> 2. Run pig tutorial using tez successfully, and dynamic form works 3. 
> Run livy interpreter via 2 users, 2 livy sessions are created, and 
> restarting works in scoped per user mode 4. If interpreter fails to 
> start, the exception in interpreter is not propagated to frontend. I 
> believe this is a regression. I try it in both livy & spark 
> interpreter.
>
> Here's the error I see in frontend.
>
>
> [image: pasted1]
>
>
> Mina Lee 于2017年3月22日周三 上午9:51写道：
>
>> I propose the following RC to be released for the Apache Zeppelin 
>> 0.7.1 release.
>>
>> The commit id is 22b299b5c17c0c9ad8e54ee15bb7fde645472c65 which is 
>> corresponds to the tag v0.7.1-rc1:
>> https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;h=
>> refs/tags/v0.7.1-rc1
>>
>> The release archives (tgz), signature, and checksums are here 
>> https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.7.1-rc1/
>>
>> The release candidate consists of the following source distribution 
>> archive zeppelin-0.7.1.tgz
>>
>> In addition, the following supplementary binary distributions are 
>> provided for user convenience at the same location 
>> zeppelin-0.7.1-bin-all.tgz zeppelin-0.7.1-bin-netinst.tgz
>>
>> The maven artifacts are here
>> https://repository.apache.org/content/repositories/orgapachezeppelin-
>> 1033
>>
>> 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=12339166=12316221
>>
>> Vote will be open for next 72 hours (close at 19:00 24/Mar PDT).
>>
>> [ ] +1 approve
>> [ ] 0 no opinion
>> [ ] -1 disapprove (and reason why)
>>
>

Re: zeppelin-web module build failure with latest 0.8.0-SNAPSHOT

[Ahyoung Ryu]

Hi Chaoran,

This is what I can see in your email.
[image: Inline image 1]

Can't see any error messages in this. Can you point me which part was the
problem with you exactly?

Thanks,
Ahyoung

On Wed, Mar 15, 2017 at 12:30 AM, Chaoran Yu 
wrote:

> I’m trying to build the latest repo i.e. version 0.8.0-SNAPSHOT, but got
> the following error message:
>
> [INFO] --- maven-war-plugin:2.5:war (default-war) @ zeppelin-web ---
> [INFO] Downloading: https://repo.maven.apache.org/
> maven2/org/codehaus/plexus/plexus-io/2.1.3/plexus-io-2.1.3.pom
> Mar 12, 2017 1:01:12 PM 
> org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec
> execute
> INFO: I/O exception (java.net.SocketException) caught when processing
> request to {s}->https://repo.maven.apache.org:443: Connection reset
> Mar 12, 2017 1:01:12 PM 
> org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec
> execute
> INFO: Retrying request to {s}->https://repo.maven.apache.org:443
> Mar 12, 2017 1:01:12 PM 
> org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec
> execute
> INFO: I/O exception (java.net.SocketException) caught when processing
> request to {s}->https://repo.maven.apache.org:443: Connection reset
> Mar 12, 2017 1:01:12 PM 
> org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec
> execute
> INFO: Retrying request to {s}->https://repo.maven.apache.org:443
> Mar 12, 2017 1:01:12 PM 
> org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec
> execute
> INFO: I/O exception (java.net.SocketException) caught when processing
> request to {s}->https://repo.maven.apache.org:443: Connection reset
> Mar 12, 2017 1:01:12 PM 
> org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec
> execute
> INFO: Retrying request to {s}->https://repo.maven.apache.org:443
> [INFO] Downloading: https://repo.maven.apache.org/
> maven2/org/codehaus/plexus/plexus-archiver/2.6.3/plexus-archiver-2.6.3.pom
> Mar 12, 2017 1:01:12 PM 
> org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec
> execute
> INFO: I/O exception (java.net.SocketException) caught when processing
> request to {s}->https://repo.maven.apache.org:443: Connection reset
> Mar 12, 2017 1:01:12 PM 
> org.apache.maven.wagon.providers.http.httpclient.impl.execchain.RetryExec
> execute
> INFO: Retrying request to {s}->https://repo.maven.apache.org:443
>
> Did anyone get the same error? I’ve also encountered the same problem with
> version 0.7.0.
>
> Thank you,
> Chaoran Yu
>

Re: [VOTE] Release Apache Zeppelin 0.7.1 (RC1)

[Ahyoung Ryu]

+1

On Wed, Mar 22, 2017 at 12:19 PM, Jeff Zhang  wrote:

>
> 0
>
> 1. Build it from source successfully
> 2. Run pig tutorial using tez successfully, and dynamic form works
> 3. Run livy interpreter via 2 users, 2 livy sessions are created, and
> restarting works in scoped per user mode
> 4. If interpreter fails to start, the exception in interpreter is not
> propagated to frontend. I believe this is a regression. I try it in both
> livy & spark interpreter.
>
> Here's the error I see in frontend.
>
>
> [image: pasted1]
>
>
> Mina Lee 于2017年3月22日周三 上午9:51写道：
>
>> I propose the following RC to be released for the Apache Zeppelin 0.7.1
>> release.
>>
>> The commit id is 22b299b5c17c0c9ad8e54ee15bb7fde645472c65 which is
>> corresponds to the tag v0.7.1-rc1:
>> https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;h=
>> refs/tags/v0.7.1-rc1
>>
>> The release archives (tgz), signature, and checksums are here
>> https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.7.1-rc1/
>>
>> The release candidate consists of the following source distribution
>> archive
>> zeppelin-0.7.1.tgz
>>
>> In addition, the following supplementary binary distributions are provided
>> for user convenience at the same location
>> zeppelin-0.7.1-bin-all.tgz
>> zeppelin-0.7.1-bin-netinst.tgz
>>
>> The maven artifacts are here
>> https://repository.apache.org/content/repositories/orgapachezeppelin-1033
>>
>> 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=12339166=12316221
>>
>> Vote will be open for next 72 hours (close at 19:00 24/Mar PDT).
>>
>> [ ] +1 approve
>> [ ] 0 no opinion
>> [ ] -1 disapprove (and reason why)
>>
>

Re: [VOTE] Release Apache Zeppelin 0.7.1 (RC1)

[Jeff Zhang]

0

1. Build it from source successfully
2. Run pig tutorial using tez successfully, and dynamic form works
3. Run livy interpreter via 2 users, 2 livy sessions are created, and
restarting works in scoped per user mode
4. If interpreter fails to start, the exception in interpreter is not
propagated to frontend. I believe this is a regression. I try it in both
livy & spark interpreter.

Here's the error I see in frontend.


[image: pasted1]


Mina Lee 于2017年3月22日周三 上午9:51写道：

> I propose the following RC to be released for the Apache Zeppelin 0.7.1
> release.
>
> The commit id is 22b299b5c17c0c9ad8e54ee15bb7fde645472c65 which is
> corresponds to the tag v0.7.1-rc1:
>
> https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;h=refs/tags/v0.7.1-rc1
>
> The release archives (tgz), signature, and checksums are here
> https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.7.1-rc1/
>
> The release candidate consists of the following source distribution archive
> zeppelin-0.7.1.tgz
>
> In addition, the following supplementary binary distributions are provided
> for user convenience at the same location
> zeppelin-0.7.1-bin-all.tgz
> zeppelin-0.7.1-bin-netinst.tgz
>
> The maven artifacts are here
> https://repository.apache.org/content/repositories/orgapachezeppelin-1033
>
> 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=12339166=12316221
>
> Vote will be open for next 72 hours (close at 19:00 24/Mar PDT).
>
> [ ] +1 approve
> [ ] 0 no opinion
> [ ] -1 disapprove (and reason why)
>

[GitHub] zeppelin issue #2168: [ZEPPELIN-1889] [FIX] Multiple groups in chart doesn't...

[sravan-s]

Github user sravan-s commented on the issue:

https://github.com/apache/zeppelin/pull/2168
  
@Leemoonsoo , the bug is limited only for 'stacked' version of bar chart. 
Notice the radio button inside the chart

* This is  the grouped version

![grouped](https://cloud.githubusercontent.com/assets/11382805/24180535/6d606b4e-0edb-11e7-8320-e67df951914b.png)

* This is the buggy stacked version, in some cases, it won't even get 
rendered

![stacked](https://cloud.githubusercontent.com/assets/11382805/24180543/79855a06-0edb-11e7-9708-45e15835e68f.png)

* This is the fixed stacked version

![stacked-fix](https://cloud.githubusercontent.com/assets/11382805/24180659/38d0d75a-0edc-11e7-81e9-6ef88927bdd8.png)

p.s. I tried recording gifs, but my laptop hangs(ubuntu 16.04, but I think 
it's the hardware that's the culprit)




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin pull request #2172: [hotfix][gh-pages] Put blog post's description ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/zeppelin/pull/2172


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[VOTE] Release Apache Zeppelin 0.7.1 (RC1)

[Mina Lee]

I propose the following RC to be released for the Apache Zeppelin 0.7.1
release.

The commit id is 22b299b5c17c0c9ad8e54ee15bb7fde645472c65 which is
corresponds to the tag v0.7.1-rc1:
https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;h=refs/tags/v0.7.1-rc1

The release archives (tgz), signature, and checksums are here
https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.7.1-rc1/

The release candidate consists of the following source distribution archive
zeppelin-0.7.1.tgz

In addition, the following supplementary binary distributions are provided
for user convenience at the same location
zeppelin-0.7.1-bin-all.tgz
zeppelin-0.7.1-bin-netinst.tgz

The maven artifacts are here
https://repository.apache.org/content/repositories/orgapachezeppelin-1033

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=12339166=12316221

Vote will be open for next 72 hours (close at 19:00 24/Mar PDT).

[ ] +1 approve
[ ] 0 no opinion
[ ] -1 disapprove (and reason why)

[GitHub] zeppelin issue #2167: [ZEPPELIN-2230] .travis.yml protecting against ambiguo...

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2167
  
Thanks @Remilito for working on this issue.
Merge to master and branch-0.7 if 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 well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2150: [ZEPPELIN-2278] Env variable to configure Npm registry

[andreaTP]

Github user andreaTP commented on the issue:

https://github.com/apache/zeppelin/pull/2150
  
Please go on! 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 so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2168: [ZEPPELIN-1889] [FIX] Multiple groups in chart doesn't...

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2168
  
Thanks for working on the issue.

I have tested problem 
[ZEPPELIN-1889](https://issues.apache.org/jira/browse/ZEPPELIN-1889) in current 
master. However i couldn't reproduce the problem.


![zeppelin-1889](https://cloud.githubusercontent.com/assets/1540981/24170646/c1abf224-0e3e-11e7-9d0e-f9d553cca218.gif)

@zjffdu @sravan-s Is problem described in ZEPPELIN-1889 is reproducible?


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2150: [ZEPPELIN-2278] Env variable to configure Npm registry

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2150
  
Thanks @andreaTP for the improvement!
LGTM and merge to master if no further discussions.


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2170: [HOTFIX][ZEPPELIN-2149] correct variable name used in ...

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2170
  
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, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2172: [hotfix][gh-pages] Put blog post's description back

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2172
  
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, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin pull request #2166: [ZEPPELIN-2288] Fix Cross-Site WebSocket check

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/zeppelin/pull/2166


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin pull request #2099: [ZEPPELIN-2106] providing paragraph config in c...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/zeppelin/pull/2099


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2135: Groovy Interpreter for Apazhe Zeppelin [ZEPPELIN-2176]

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2135
  
Looks like second test matrix succeeded after the manual restart.
In this case, you also need to trigger Jenkins again to check latest build 
status.
Simply close and reopen this PR will do that.


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

GSOC2017: Any mentors for Solr engine integration

[Alexandre Rafalovitch]

Hi,

I am a committer to the Apache Solr (search engine) project and
registered as a mentor for Google Summer of Code 2017 that just
started to get student proposals. I really like the concept of the
Zeppelin project and would love to see Solr backend integration for
it. Actually, we already integrate with Zeppelin, but via the JDBC
bridge. I want a more rich integration directly with Solr.

Has anybody in the Zeppelin community joined as a GSOC mentor this
cycle? If so, I would like to propose the engine as one of the ideas
for students to pick up. I would be happy to be the secondary mentor
for such project and/or train the students (and anybody else in
Zeppelin community along them) in Solr foundations.

I have an issue open for this at
https://issues.apache.org/jira/browse/SOLR-10328 .

Regards,
   Alex.


http://www.solr-start.com/ - Resources for Solr users, new and experienced

[GitHub] zeppelin issue #2173: [ZEPPELIN-2291] Notebook commit dropdown cut-off

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2173
  
Looks like travis changed the name of option from "build pushes" to "Build 
branch updates".

Amend your last commit with `git commit --amend` and do `git push 
your-remote HEAD --force` will trigger CI job.


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin pull request #2151: [ZEPPELIN-465] Be able to run paragraph and the...

[Remilito]

GitHub user Remilito reopened a pull request:

https://github.com/apache/zeppelin/pull/2151

[ZEPPELIN-465] Be able to run paragraph and the following ones

### What is this PR for?
Allow to run a paragraph **and** the ones following. This is useful for 
instance if you are generating a dataset in a paragraph and then have others 
subsequent paragraphs relying on this dataset.
In a nutshell this PR contains:
* UI: added a command in paragraph dropdown menu
* REST: added an boolean option to runparagraph (sync & async)
* updated rest doc
* z-engine: added relevant function to Note
* also refacto some duplicated code here and there.

### What type of PR is it?
Feature

### Todos
* [ ] - Once committers agree on the visual impact, update relevant 
documentation.

### What is the Jira issue?
[ZEPPELIN-465](https://issues.apache.org/jira/browse/ZEPPELIN-465)

### How should this be tested?
* UI: click on the "run and next ones" in the dropdown menu and verify 
subsequent paragraphs are also run, and not precedent ones.
* REST: post request to 
/api/notebook/[job|run]/$noteId/$paragraphId?subsequent=true

### Screenshots (if appropriate)

![runsubsequent](https://cloud.githubusercontent.com/assets/8293897/24159054/65bc7acc-0e5e-11e7-8e41-0549cb8e3861.png)

![confirmationdialog](https://cloud.githubusercontent.com/assets/8293897/24159053/65aa31c8-0e5e-11e7-894f-2448e103b504.png)

![paragraphrunningpending](https://cloud.githubusercontent.com/assets/8293897/24159051/6598cfc8-0e5e-11e7-9f0e-c3340351ca76.png)


### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? Yes


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/Remilito/zeppelin ZEPPELIN-465

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zeppelin/pull/2151.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2151






---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin pull request #2151: [ZEPPELIN-465] Be able to run paragraph and the...

[Remilito]

Github user Remilito closed the pull request at:

https://github.com/apache/zeppelin/pull/2151


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2151: [ZEPPELIN-465] Be able to run paragraph and the follow...

[Remilito]

Github user Remilito commented on the issue:

https://github.com/apache/zeppelin/pull/2151
  
@AhyoungRyu : updated (and now building and passing tests :sweat_smile: ).
@jongyoul : I am not sure to fully understand what you mean. If you are 
talking "UI" IMO the need to run or not a sequence of paragraphs depends mostly 
on the paragraphs' contents (i.e. generation of a dataset used by following 
paragraphs), so I find it more convenient to trigger this directly in the 
paragraph view rather than putting it in the job view. WDYT? 


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #2173: [ZEPPELIN-2291] Notebook commit dropdown cut-off

[elkangaroo]

Github user elkangaroo commented on the issue:

https://github.com/apache/zeppelin/pull/2173
  
Hi, I have now swiched on 'zeppelin' repository at 
https://travis-ci.org/profile.

But I don't see this option:
> And then make sure 'Build pushes' option is enabled in the settings 
https://travis-ci.org/MyHammer/zeppelin/settings.

How can I trigger CI job again?


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (ZEPPELIN-2292) Pyspark interpreter module not found even though --files parameter provided

[Shishir Choudhary (JIRA)]

Shishir Choudhary created ZEPPELIN-2292:
---

 Summary: Pyspark interpreter module not found even though --files 
parameter provided
 Key: ZEPPELIN-2292
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2292
 Project: Zeppelin
  Issue Type: Bug
  Components: pySpark
Affects Versions: 0.7.0
 Environment: Mac OSX, Spark 2.0.2 and 2.1.0 and Built in Spark
Reporter: Shishir Choudhary


I have included my custom python library in spark submit --files option. It 
works in zeppelin 0.6.2 but fails in 0.7.0 with error module not found. 

Code in notebook 
%pyspark 
from learney import xyz
from learney import abc

In zeppelin-env.sh (0.6.2 which works)
export SPARK_HOME=/Users/shishircc/old-spark-2.0.2-bin-hadoop2.7
export SPARK_SUBMIT_OPTIONS=" --files 
/Users/shishircc/learney-pyspark/learney.zip"

In zeppelin-env.sh (0.7.0 which does not work)
export SPARK_HOME=/Users/shishircc/old-spark-2.0.2-bin-hadoop2.7
 
export SPARK_SUBMIT_OPTIONS=" --files 
/Users/shishircc/learney-pyspark/learney.zip "   

In zeppelin-env.sh (0.7.0 which does not work)
export SPARK_HOME=/Users/shishircc/old-spark-2.1.0-bin-hadoop2.7
 
export SPARK_SUBMIT_OPTIONS=" --files 
/Users/shishircc/learney-pyspark/learney.zip "   



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Roadmap for 0.8.0

[moon soo Lee]

And if i suggest simplest way for us to set quality expectation to user,
which will be labeling release in download page.

Currently releases are divided into 2 categories in download page. 'Latest
release' and 'Old releases'. I think we can treat 'Latest' as unstable and
add one more category 'Stable release'.

For example, once 0.8.0 is released,

Latest release : 0.8.0
Stable release : 0.7.1
Old release : 0.6.2, 0.6.1 

Once we feel confident about the stability of latest release, we can just
change label from latest to stable in the download page. (and previous
stable goes to old releases)
We can even include formal vote for moving release from 'latest' to
'stable' in our release process, if it is necessary.

Thanks,
moon

On Tue, Mar 21, 2017 at 6:59 AM moon soo Lee  wrote:

> Yes, having longer RC period will help.
>
> But if i recall 0.7.0 release, although 21 people participated verifying
> through 4 RC for 15days, it wasn't enough to catch all critical problems
> during the release process. After the release, we've got much more number
> of bug reports, in next few days.
>
> Basically, verifying RC is limited to people who subscribe mailing list +
> willing to contribute time to verify RC, which is much smaller number of
> people who download release from download page. So having longer RC period
> will definitely help and i think we should do, but I think it's still not
> enough to make sure the quality, considering past history.
>
> AFAIK, releasing 0.8.0-preview, calling it unstable is up to the project.
> ASF release process defines how to release source code, but it does not
> really restrict what kind of 'version' the project should have releases.
> For example, spark released spark-2.0.0-preview[1] before spark-2.0.0.
>
> Thanks,
> moon
>
> [1] http://spark.apache.org/news/spark-2.0.0-preview.html
>
>
> On Mon, Mar 20, 2017 at 11:31 PM Jongyoul Lee  wrote:
>
> I agree that it will help prolong RC period and use it actually. And also
> we need code freeze for the new features and spend time to stabilize RC.
>
> On Tue, Mar 21, 2017 at 1:25 PM, Felix Cheung 
> wrote:
>
> +1 on quality and stabilization.
>
> I'm not sure if releasing as preview or calling it unstable fits with the
> ASF release process though.
>
> Other projects have code freeze, RC (and longer RC iteration time) etc. -
> do we think those will help improve quality when the release is finally cut?
>
>
> _
> From: Jianfeng (Jeff) Zhang 
> Sent: Monday, March 20, 2017 6:13 PM
> Subject: Re: Roadmap for 0.8.0
> To: , dev 
>
>
>
> Strongly +1 for adding system test for different interpreter modes and
> focus on bug fixing than new features. I do heard from some users complain
> about the bugs of zeppelin major release. A stabilized release is very
> necessary for community.
>
>
>
>
> Best Regard,
> Jeff Zhang
>
>
> From: moon soo Lee  >>
> Reply-To: "us...@zeppelin.apache.org >"  mailto:us...@zeppelin.apache.org >>
> Date: Tuesday, March 21, 2017 at 4:10 AM
> To: "us...@zeppelin.apache.org >"  mailto:us...@zeppelin.apache.org >>, dev <
> dev@zeppelin.apache.org >>
>
> Subject: Re: Roadmap for 0.8.0
>
> Great to see discussion for 0.8.0.
> List of features for 0.8.0 looks really good.
>
> Interpreter factory refactoring
> Interpreter layer supports various behavior depends on combination of
> PerNote,PerUser / Shared,Scoped,Isolated. We'll need strong test cases for
> each combination as a first step.
> Otherwise, any pullrequest will silently break one of behavior at any time
> no matter we refactor or not. And fixing and testing this behavior is so
> hard.
> Once we have complete test cases, not only guarantee the behavior but also
> make refactoring much easier.
>
>
> 0.8.0 release
> I'd like to suggest improvements on how we release a new version.
>
> In the past, 0.6.0 and 0.7.0 release with some critical problems. (took 3
> months to stabilize 0.6 and we're working on stabilizing 0.7.0 for 2 months)
>
> I think the same thing will happen again with 0.8.0, while we're going to
> make lots of changes and add many new features.
> After we released 0.8.0, while 'Stabilizing' the new release, user who
> tried the new release may get wrong impression of the quality. Which is
> very bad and we already repeated the mistake in 0.6.0 and 0.7.0.
>
> So from 0.8.0 release, I'd suggest we improve way we release new version
> to give user proper expectation. I think there're several ways of doing it.
>
> 1. Release 

[GitHub] zeppelin pull request #2173: [ZEPPELIN-2291] Notebook commit dropdown cut-of...

[elkangaroo]

GitHub user elkangaroo opened a pull request:

https://github.com/apache/zeppelin/pull/2173

[ZEPPELIN-2291] Notebook commit dropdown cut-off

### What is this PR for?
When you have a notebook under GIT version control, the dropdown with your 
commits will be cut-off with no possibility to scroll to older commits (see 
attached screenshot).

This fixes it by applying a relative max-height and appropriate overflow 
(similar styles as for the notebooks dropdown in the navigation bar). If the 
dropdown is longer than max-height, a scrollbar will be shown :)

### What type of PR is it?
Bug Fix

### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-2291

### How should this be tested?
Create a notebook under version control and make a couple of changes & 
commits, until the dropdown gets too long to fit on one screen. If everything 
works as intended, you should now be able to scroll to older commits inside the 
dropdown.

### Screenshots (if appropriate)

![apache_zeppelin_commit_dropdown_cut_off](https://cloud.githubusercontent.com/assets/1144202/24155455/3041dcfc-0e54-11e7-8120-3617d579f29f.png)

### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? No


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/MyHammer/zeppelin 
ZEPPELIN-2291-Commit-Dropdown-Scroll

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zeppelin/pull/2173.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2173


commit 154cfaa1edb200b76409232268b347a80292244d
Author: Alexander Wenzel 
Date:   2017-03-21T15:30:09Z

[ZEPPELIN-2291] Fix cut-off revision dropdown




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Roadmap for 0.8.0

[moon soo Lee]

Yes, having longer RC period will help.

But if i recall 0.7.0 release, although 21 people participated verifying
through 4 RC for 15days, it wasn't enough to catch all critical problems
during the release process. After the release, we've got much more number
of bug reports, in next few days.

Basically, verifying RC is limited to people who subscribe mailing list +
willing to contribute time to verify RC, which is much smaller number of
people who download release from download page. So having longer RC period
will definitely help and i think we should do, but I think it's still not
enough to make sure the quality, considering past history.

AFAIK, releasing 0.8.0-preview, calling it unstable is up to the project.
ASF release process defines how to release source code, but it does not
really restrict what kind of 'version' the project should have releases.
For example, spark released spark-2.0.0-preview[1] before spark-2.0.0.

Thanks,
moon

[1] http://spark.apache.org/news/spark-2.0.0-preview.html


On Mon, Mar 20, 2017 at 11:31 PM Jongyoul Lee  wrote:

> I agree that it will help prolong RC period and use it actually. And also
> we need code freeze for the new features and spend time to stabilize RC.
>
> On Tue, Mar 21, 2017 at 1:25 PM, Felix Cheung 
> wrote:
>
> +1 on quality and stabilization.
>
> I'm not sure if releasing as preview or calling it unstable fits with the
> ASF release process though.
>
> Other projects have code freeze, RC (and longer RC iteration time) etc. -
> do we think those will help improve quality when the release is finally cut?
>
>
> _
> From: Jianfeng (Jeff) Zhang 
> Sent: Monday, March 20, 2017 6:13 PM
> Subject: Re: Roadmap for 0.8.0
> To: , dev 
>
>
>
> Strongly +1 for adding system test for different interpreter modes and
> focus on bug fixing than new features. I do heard from some users complain
> about the bugs of zeppelin major release. A stabilized release is very
> necessary for community.
>
>
>
>
> Best Regard,
> Jeff Zhang
>
>
> From: moon soo Lee  >>
> Reply-To: "us...@zeppelin.apache.org >"  mailto:us...@zeppelin.apache.org >>
> Date: Tuesday, March 21, 2017 at 4:10 AM
> To: "us...@zeppelin.apache.org >"  mailto:us...@zeppelin.apache.org >>, dev <
> dev@zeppelin.apache.org >>
>
> Subject: Re: Roadmap for 0.8.0
>
> Great to see discussion for 0.8.0.
> List of features for 0.8.0 looks really good.
>
> Interpreter factory refactoring
> Interpreter layer supports various behavior depends on combination of
> PerNote,PerUser / Shared,Scoped,Isolated. We'll need strong test cases for
> each combination as a first step.
> Otherwise, any pullrequest will silently break one of behavior at any time
> no matter we refactor or not. And fixing and testing this behavior is so
> hard.
> Once we have complete test cases, not only guarantee the behavior but also
> make refactoring much easier.
>
>
> 0.8.0 release
> I'd like to suggest improvements on how we release a new version.
>
> In the past, 0.6.0 and 0.7.0 release with some critical problems. (took 3
> months to stabilize 0.6 and we're working on stabilizing 0.7.0 for 2 months)
>
> I think the same thing will happen again with 0.8.0, while we're going to
> make lots of changes and add many new features.
> After we released 0.8.0, while 'Stabilizing' the new release, user who
> tried the new release may get wrong impression of the quality. Which is
> very bad and we already repeated the mistake in 0.6.0 and 0.7.0.
>
> So from 0.8.0 release, I'd suggest we improve way we release new version
> to give user proper expectation. I think there're several ways of doing it.
>
> 1. Release 0.8.0-preview officially and then release 0.8.0.
> 2. Release 0.8.0 with 'beta' or 'unstable' label. And keep 0.7.x as a
> 'stable' release in the download page. Once 0.8.x release becomes stable
> enough make 0.8.x release as a 'stable' and move 0.7.x to 'old' releases.
>
>
> After 0.8.0,
> Since Zeppelin projects starts, project went through some major milestone,
> like
>
> - project gets first users and first contributor
> - project went into Apache Incubator
> - project became TLP.
>
> And I think it's time to think about hitting another major milestone.
>
> Considering features we already have, features we're planning on 0.8, wide
> adoption of Zeppelin in the industry, I think it's time to focus on make
> project more mature and make a 1.0 release. Which i think big milestone for
> the project.
>
> After 0.8.0 release, I suggest we more focus on 

[GitHub] zeppelin issue #2163: [ZEPPELIN-2287] Add more test to ensure 'RunOnSelectio...

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2163
  
All CI tests have passed now. Ready for review again :) 


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Roadmap for 0.8.0

[Jongyoul Lee]

I agree that it will help prolong RC period and use it actually. And also
we need code freeze for the new features and spend time to stabilize RC.

On Tue, Mar 21, 2017 at 1:25 PM, Felix Cheung 
wrote:

> +1 on quality and stabilization.
>
> I'm not sure if releasing as preview or calling it unstable fits with the
> ASF release process though.
>
> Other projects have code freeze, RC (and longer RC iteration time) etc. -
> do we think those will help improve quality when the release is finally cut?
>
>
> _
> From: Jianfeng (Jeff) Zhang 
> Sent: Monday, March 20, 2017 6:13 PM
> Subject: Re: Roadmap for 0.8.0
> To: , dev 
>
>
>
> Strongly +1 for adding system test for different interpreter modes and
> focus on bug fixing than new features. I do heard from some users complain
> about the bugs of zeppelin major release. A stabilized release is very
> necessary for community.
>
>
>
>
> Best Regard,
> Jeff Zhang
>
>
> From: moon soo Lee  >>
> Reply-To: "us...@zeppelin.apache.org >" >>
> Date: Tuesday, March 21, 2017 at 4:10 AM
> To: "us...@zeppelin.apache.org >" >>, dev <
> dev@zeppelin.apache.org >>
>
> Subject: Re: Roadmap for 0.8.0
>
> Great to see discussion for 0.8.0.
> List of features for 0.8.0 looks really good.
>
> Interpreter factory refactoring
> Interpreter layer supports various behavior depends on combination of
> PerNote,PerUser / Shared,Scoped,Isolated. We'll need strong test cases for
> each combination as a first step.
> Otherwise, any pullrequest will silently break one of behavior at any time
> no matter we refactor or not. And fixing and testing this behavior is so
> hard.
> Once we have complete test cases, not only guarantee the behavior but also
> make refactoring much easier.
>
>
> 0.8.0 release
> I'd like to suggest improvements on how we release a new version.
>
> In the past, 0.6.0 and 0.7.0 release with some critical problems. (took 3
> months to stabilize 0.6 and we're working on stabilizing 0.7.0 for 2 months)
>
> I think the same thing will happen again with 0.8.0, while we're going to
> make lots of changes and add many new features.
> After we released 0.8.0, while 'Stabilizing' the new release, user who
> tried the new release may get wrong impression of the quality. Which is
> very bad and we already repeated the mistake in 0.6.0 and 0.7.0.
>
> So from 0.8.0 release, I'd suggest we improve way we release new version
> to give user proper expectation. I think there're several ways of doing it.
>
> 1. Release 0.8.0-preview officially and then release 0.8.0.
> 2. Release 0.8.0 with 'beta' or 'unstable' label. And keep 0.7.x as a
> 'stable' release in the download page. Once 0.8.x release becomes stable
> enough make 0.8.x release as a 'stable' and move 0.7.x to 'old' releases.
>
>
> After 0.8.0,
> Since Zeppelin projects starts, project went through some major milestone,
> like
>
> - project gets first users and first contributor
> - project went into Apache Incubator
> - project became TLP.
>
> And I think it's time to think about hitting another major milestone.
>
> Considering features we already have, features we're planning on 0.8, wide
> adoption of Zeppelin in the industry, I think it's time to focus on make
> project more mature and make a 1.0 release. Which i think big milestone for
> the project.
>
> After 0.8.0 release, I suggest we more focus on bug fixes, stability
> improvement, optimizing user experience than adding new features. And with
> subsequent minor release, 0.8.1, 0.8.2 ... moment we feel confident about
> the quality, release it as a 1.0.0 instead of 0.8.x.
>
> Once we have 1.0.0 released, then I think we can make larger, experimental
> changes on 2.0.0 branch aggressively, while we keep maintaining 1.0.x
> branch.
>
>
> Thanks,
> moon
>
> On Mon, Mar 20, 2017 at 8:55 AM Felix Cheung  mailto:felixcheun...@hotmail.com >> wrote:
> There are several pending visualization improvements/PRs that would be
> very good to get them in as well.
>
>
> 
> From: Jongyoul Lee  >>
> Sent: Sunday, March 19, 2017 9:03:24 PM
> To: dev; us...@zeppelin.apache.org >
> Subject: Roadmap for 0.8.0
>
> Hi dev & users,
>
> Recently, community submits very new features for Apache Zeppelin. I think
> it's very positive signals to improve 

[GitHub] zeppelin issue #2161: [ZEPPELIN-1697] Fix multiuser ws connection for second...

[anthonycorbacho]

Github user anthonycorbacho commented on the issue:

https://github.com/apache/zeppelin/pull/2161
  
Tested with some basic case, look 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 this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---