[GitHub] zeppelin issue #2098: [ZEPPELIN-2217] AdvancedTransformation for Visualizati...

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2098
  
@1ambda I feel so sorry for my late response. Tested this patch \w your 
Helium package: zeppelin-ultimate-line-chart. Here are some thought and 
question(?) in my head. 
 
1. "Save" & "Delete" button on top of the setting table
 - It'll be better there are some feedback after clicking these buttons 
like "Changes are successfully saved" or "Changes will be discarded". How about 
small `ngtoast` or bootstrap dialog? 

![small_btns](https://cloud.githubusercontent.com/assets/10060731/24440153/82552bcc-148d-11e7-96ee-3dd305917d21.gif)
Probably ppl can click the trash can button by mistake. Then they'll lose 
the setting. To prevent this, we can provide some alert for this. 

 - I think we can hide "Save" & "Delete" button when the setting table is 
folded. A good example is in our interpreter setting page. As you know, users 
only can save/remove the setting when they click "edit" button. So how about 
activating those disket & trash btns only when the setting table is expanded? 

2. no-group field 
 - What is difference between `no-group` and just letting `group` field as 
blank? Is there special reason for creating `no-group` field? (It's question 
actually :D)

 - `xAxis` and `yAxis` field size are different in `no-group` section.
https://cloud.githubusercontent.com/assets/10060731/24440240/0ae00fc0-148e-11e7-999b-554af8d39f72.png;>

And again, this is really cool! 



---
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 #2158: [ZEPPELIN-2279] excluded comments from SQL

[tinkoff-dwh]

Github user tinkoff-dwh commented on the issue:

https://github.com/apache/zeppelin/pull/2158
  
Ready to review


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If 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 #2134: [ZEPPELIN-2257] notification about incompleteness of d...

[tinkoff-dwh]

Github user tinkoff-dwh commented on the issue:

https://github.com/apache/zeppelin/pull/2134
  
ready to review


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If 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: [VOTE] Release Apache Zeppelin 0.7.1 (RC3)

[Jeff Zhang]

Thanks Jongyoul for explanation, let's improve it later.

+1.

* Build zeppelin from source successfully
* Run pig tutorial using tez mode successfully
* Run spark tutorial using livy interpreter successfully.
* Verify interpreter fail error can be propagated to frontend.
* Verify the restart button works in several scenarios. Works properly.




Jongyoul Lee 于2017年3月29日周三 上午11:37写道：

> Jeff,
>
> Moon and I discuss the behaviors of clicking restart buttons from notebook
> page and interpreter page. In your case, it's intended fully. For more
> detail, In case of "per user", we can do the same thing in note and
> interpreter pages, but in case of "per note", we cannot get the exact note
> when users click restart button in interpreter tab. Thus Moon and I decided
> not to change original behaviors of interpreter page. It would be changed
> when we add admin feature.
>
> Thanks for testing it.
>
> Regards,
> Jongyoul
>
> On Wed, Mar 29, 2017 at 11:47 AM, Jeff Zhang  wrote:
>
> > Might find another bug about restarting button. The restarting button on
> > note page behaves differently from that of interpreter page.  This might
> > confuse users.
> >
> > e.g. For livy interpreter, if I click the restart button in note page,
> then
> > only my livy session will be shutdown. But If I click the restart button
> in
> > interpreter page, all the sessions will be shut down. This kind of
> > differences will confuse users IMO.
> >
> >
> >
> > Mina Lee 于2017年3月28日周二 下午6:53写道：
> >
> > > I propose the following RC to be released for the Apache Zeppelin 0.7.1
> > > release.
> > >
> > > The commit id is 9eb77adfb3d9969f84d1657b78a95b58e44b5be8 which is
> > > corresponds to the tag v0.7.1-rc3:
> > >
> > > https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;h=
> > refs/tags/v0.7.1-rc3
> > >
> > > The release archives (tgz), signature, and checksums are here
> > > https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.7.1-rc3/
> > >
> > > 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-1035
> > >
> > > 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 04:00 31/Mar PDT).
> > >
> > > [ ] +1 approve
> > > [ ] 0 no opinion
> > > [ ] -1 disapprove (and reason why)
> > >
> >
>
>
>
> --
> 이종열, Jongyoul Lee, 李宗烈
> http://madeng.net
>

[GitHub] zeppelin issue #2200: [HOTFIX] Remove unintended characters from r tutorial

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2200
  
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 #2098: [ZEPPELIN-2217] AdvancedTransformation for Visualizati...

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2098
  
Let me add docs and unit tests. I guess it will take few days. Then i will 
comment. Thanks @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 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: [VOTE] Release Apache Zeppelin 0.7.1 (RC3)

[Jongyoul Lee]

Jeff,

Moon and I discuss the behaviors of clicking restart buttons from notebook
page and interpreter page. In your case, it's intended fully. For more
detail, In case of "per user", we can do the same thing in note and
interpreter pages, but in case of "per note", we cannot get the exact note
when users click restart button in interpreter tab. Thus Moon and I decided
not to change original behaviors of interpreter page. It would be changed
when we add admin feature.

Thanks for testing it.

Regards,
Jongyoul

On Wed, Mar 29, 2017 at 11:47 AM, Jeff Zhang  wrote:

> Might find another bug about restarting button. The restarting button on
> note page behaves differently from that of interpreter page.  This might
> confuse users.
>
> e.g. For livy interpreter, if I click the restart button in note page, then
> only my livy session will be shutdown. But If I click the restart button in
> interpreter page, all the sessions will be shut down. This kind of
> differences will confuse users IMO.
>
>
>
> Mina Lee 于2017年3月28日周二 下午6:53写道：
>
> > I propose the following RC to be released for the Apache Zeppelin 0.7.1
> > release.
> >
> > The commit id is 9eb77adfb3d9969f84d1657b78a95b58e44b5be8 which is
> > corresponds to the tag v0.7.1-rc3:
> >
> > https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;h=
> refs/tags/v0.7.1-rc3
> >
> > The release archives (tgz), signature, and checksums are here
> > https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.7.1-rc3/
> >
> > 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-1035
> >
> > 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 04:00 31/Mar PDT).
> >
> > [ ] +1 approve
> > [ ] 0 no opinion
> > [ ] -1 disapprove (and reason why)
> >
>



-- 
이종열, Jongyoul Lee, 李宗烈
http://madeng.net

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

[Jeff Zhang]

Might find another bug about restarting button. The restarting button on
note page behaves differently from that of interpreter page.  This might
confuse users.

e.g. For livy interpreter, if I click the restart button in note page, then
only my livy session will be shutdown. But If I click the restart button in
interpreter page, all the sessions will be shut down. This kind of
differences will confuse users IMO.



Mina Lee 于2017年3月28日周二 下午6:53写道：

> I propose the following RC to be released for the Apache Zeppelin 0.7.1
> release.
>
> The commit id is 9eb77adfb3d9969f84d1657b78a95b58e44b5be8 which is
> corresponds to the tag v0.7.1-rc3:
>
> https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;h=refs/tags/v0.7.1-rc3
>
> The release archives (tgz), signature, and checksums are here
> https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.7.1-rc3/
>
> 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-1035
>
> 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 04:00 31/Mar PDT).
>
> [ ] +1 approve
> [ ] 0 no opinion
> [ ] -1 disapprove (and reason why)
>

[jira] [Created] (ZEPPELIN-2327) Add option to dynamic form to control whether running paragraph automatically

[Jeff Zhang (JIRA)]

Jeff Zhang created ZEPPELIN-2327:


 Summary: Add option to dynamic form to control whether running 
paragraph automatically
 Key: ZEPPELIN-2327
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2327
 Project: Zeppelin
  Issue Type: Improvement
Affects Versions: 0.7.0
Reporter: Jeff Zhang


Currently, paragraph will be rerun automatically after I change the value of 
dynamic form. This is good for single control, but if I have multiple controls 
in the frontend. Usually, I want to create a button myself to trigger the 
rerun. 



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

[GitHub] zeppelin pull request #2200: [HOTFIX] Remove unintended characters from r tu...

[minahlee]

GitHub user minahlee opened a pull request:

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

[HOTFIX] Remove unintended characters from r tutorial

### What is this PR for?
If user runs **Create a R Dataframe** paragraph in **Zeppelin Tutorial/R 
(SparkR)** note, he/she will get error because of some unintended characters 
inserted.

### What type of PR is it?
Documentation | Hot Fix

### Screenshots (if appropriate)
**Before**
![screen shot 2017-03-29 at 11 07 09 
am](https://cloud.githubusercontent.com/assets/8503346/24435405/177f5c22-1470-11e7-868c-919fec07a2b3.png)


**After**
![screen shot 2017-03-29 at 11 06 52 
am](https://cloud.githubusercontent.com/assets/8503346/24435417/1d7e2568-1470-11e7-9b1f-964d3157bf0d.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/minahlee/zeppelin hotfix/fixTypo

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

https://github.com/apache/zeppelin/pull/2200.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 #2200


commit 2d2cb24837b6ff58a84fb90f9d829ce6703a827d
Author: Mina Lee 
Date:   2017-03-29T02:05:23Z

Remove unintended characters from r tutorial




---
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 #2098: [ZEPPELIN-2217] AdvancedTransformation for Visualizati...

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2098
  
@1ambda Great work!!!

Looks great to me!

I think it's worth to move usages and examples in this PR description under 
`/docs`. 
Where do you think this information can be placed?

We didn't have any unittest for pivot transformation. So it was hard to 
improve / change without any side effects. So having some basic unittest for 
advanced transformation will help other people add and improve the feature much 
faster.


---
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 #2133: [ZEPPELIN-1357][Umbrella] Text overlap in the MultiBar...

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2133
  
I tested a bit more and found some cases.

1. Label rotated when unnecessary

![image](https://cloud.githubusercontent.com/assets/1540981/24431884/7500d71a-13d3-11e7-9a0e-1b4514f86a09.png)

2. Label still overlapping when paragraph width is small

![image](https://cloud.githubusercontent.com/assets/1540981/24431897/8c620ffa-13d3-11e7-8f40-3f6e53ffbb63.png)

To address these problem, I think rotation/hide should be calculated based 
on actual chart width and combined width of all labels.
Or just providing completely manual (provide option to select 
normal/rotation/hide) could be alternative.

@soralee what do you think? Do you have any other 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
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
  
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 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-2326) Updating Geode dependencies and imports due to package rename

[William Markito Oliveira (JIRA)]

William Markito Oliveira created ZEPPELIN-2326:
--

 Summary: Updating Geode dependencies and imports due to package 
rename
 Key: ZEPPELIN-2326
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2326
 Project: Zeppelin
  Issue Type: Improvement
  Components: Interpreters
Affects Versions: 0.7.0
Reporter: William Markito Oliveira


Updating Geode dependencies to 1.1.0 and fix imports due to package rename on 
Geode (from com.gemstone.gemfire to org.apache.geode)



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

[GitHub] zeppelin pull request #2198: [ZEPPELIN-2318] Fix proxy configuration for htt...

[khalidhuseynov]

GitHub user khalidhuseynov opened a pull request:

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

[ZEPPELIN-2318] Fix proxy configuration for http client of zeppelinhub 
storage layer

### What is this PR for?
it fixes proxy configuration for http client of zeppelinhub storage layer. 
currently used jetty-client have issue with `https` over proxy 
([1](https://github.com/eclipse/jetty.project/issues/408), 
[2](https://github.com/eclipse/jetty.project/issues/827)), so new 
`httpcomponents` library have been used. 

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

### Todos
* [x] - implement whole client with proxy

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

### How should this be tested?
1. setup proxy and make system point to it (e.g. env should contain 
`https_proxy`)
2. setup storage (e.g. 
[here](https://zeppelin.apache.org/docs/0.7.0/storage/storage.html#storage-in-zeppelinhub))

### Screenshots (if appropriate)

### 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/khalidhuseynov/zeppelin fix/ZEPPELIN-2318

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

https://github.com/apache/zeppelin/pull/2198.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 #2198


commit d2dab6c9654ec2604fae661bdaa7337136e9474a
Author: Khalid Huseynov 
Date:   2017-03-28T12:57:48Z

add dependency on asyncclient

commit 16ccbb46169ca8ac546d389100d83da7597fb4f5
Author: Khalid Huseynov 
Date:   2017-03-28T12:58:59Z

add proxy client with asynclient library

commit a5711bc1dd47531b661183e02319490c8927e887
Author: Khalid Huseynov 
Date:   2017-03-28T13:00:21Z

jetty client relay to asyncclient when proxy on

commit 8cb94006c7e5ab99767fcc214a5eeba6cec2750b
Author: Khalid Huseynov 
Date:   2017-03-28T13:01:01Z

add close routine

commit db07f5b569608b9a008a8798e10c63a23df12ccf
Author: Khalid Huseynov 
Date:   2017-03-28T15:40:03Z

add ssl setup

commit 72fa4f12d98e983da1233e94609e0a57683561d5
Author: Khalid Huseynov 
Date:   2017-03-28T15:40:37Z

fix trans dependency problem

commit 409993a8ee9f15192af105499f989a94961a92aa
Author: Khalid Huseynov 
Date:   2017-03-28T16:13:09Z

fix websocket timing




---
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-2325) using %dep for spark interpreter throw npe when user impersonate is enabled

[Guillaume Van Delsen (JIRA)]

Guillaume Van Delsen created ZEPPELIN-2325:
--

 Summary: using %dep for spark interpreter throw npe when user 
impersonate is enabled
 Key: ZEPPELIN-2325
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2325
 Project: Zeppelin
  Issue Type: Bug
Affects Versions: 0.8.0
Reporter: Guillaume Van Delsen


%dep works fine in yarn-client mode except when we setup the spark interpreter 
by "instantiated per user in isolated scope" and enabled "user impersonate" 
which throws an NPE : 

ERROR [2017-03-28 15:59:52,558] ({pool-2-thread-2} Job.java[run]:183) - Job 
failed
java.lang.NullPointerException
at 
org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:352)
at 
org.apache.zeppelin.spark.dep.SparkDependencyContext.fetchArtifactWithDep(SparkDependencyContext.java:171)
at 
org.apache.zeppelin.spark.dep.SparkDependencyContext.fetch(SparkDependencyContext.java:121)
at 
org.apache.zeppelin.spark.DepInterpreter.interpret(DepInterpreter.java:245)
at 
org.apache.zeppelin.interpreter.LazyOpenInterpreter.interpret(LazyOpenInterpreter.java:95)
at 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:496)
at org.apache.zeppelin.scheduler.Job.run(Job.java:181)
at 
org.apache.zeppelin.scheduler.FIFOScheduler$1.run(FIFOScheduler.java:139)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
 INFO [2017-03-28 15:59:52,566] ({pool-2-thread-2} 
SchedulerFactory.java[jobFinished]:137) - Job remoteInterpretJob_1490716788343 
finished by scheduler org.apache.zeppelin.spark.SparkInterpreter896995192

==> zeppelin-zeppelin-cfbe-dev-cld-01.log <==
 WARN [2017-03-28 15:59:52,578] ({pool-2-thread-18} 
NotebookServer.java[afterStatusChange]:2162) - Job 20170328-151439_549179296 is 
finished, status: ERROR, exception: null, result: %text 
java.lang.NullPointerException
at 
org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:352)
at 
org.apache.zeppelin.spark.dep.SparkDependencyContext.fetchArtifactWithDep(SparkDependencyContext.java:171)
at 
org.apache.zeppelin.spark.dep.SparkDependencyContext.fetch(SparkDependencyContext.java:121)
at 
org.apache.zeppelin.spark.DepInterpreter.interpret(DepInterpreter.java:245)
at 
org.apache.zeppelin.interpreter.LazyOpenInterpreter.interpret(LazyOpenInterpreter.java:95)
at 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:496)
at org.apache.zeppelin.scheduler.Job.run(Job.java:181)
at 
org.apache.zeppelin.scheduler.FIFOScheduler$1.run(FIFOScheduler.java:139)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

 INFO [2017-03-28 15:59:52,590] ({pool-2-thread-18} 
SchedulerFactory.java[jobFinished]:137) - Job 
paragraph_1490714079715_1669235457 finished by scheduler 
org.apache.zeppelin.interpreter.remote.RemoteInterpretershared_session241139385






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

[GitHub] zeppelin issue #2192: [ZEPPELIN-2320] fixing test + modifying map browsing

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/2192
  
@astroshim Can you 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 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 #2174: [ZEPELIN-2209] Add pagination to Helium menu

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2174
  
@AhyoungRyu Yes, it would be great to hide unnecessary things


---
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 #2191: [HOTFIX] Keep interpreter group when save and r...

[jongyoul]

Github user jongyoul closed the pull request at:

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


---
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 #2174: [ZEPELIN-2209] Add pagination to Helium menu

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2174
  
@1ambda Thanks for the detailed explanation. 

![record](https://cloud.githubusercontent.com/assets/10060731/24408816/ae0257ec-1409-11e7-8534-8ef1b73a14d0.gif)



---
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 #2174: [ZEPELIN-2209] Add pagination to Helium menu

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2174
  
@AhyoungRyu more precisely,

1. If we are in page 1, we don't need `<<`


![image](https://cloud.githubusercontent.com/assets/4968473/24408510/e39c618c-1408-11e7-8451-1dc3b1249987.png)

2. If we are in some pages which can go to page 1, we need both `<<` && `>>`


![image](https://cloud.githubusercontent.com/assets/4968473/24408522/f5e9c71c-1408-11e7-9d29-09b6db161462.png)

3. the last case


![image](https://cloud.githubusercontent.com/assets/4968473/24408544/05b8cfbc-1409-11e7-8768-c2db21ca2a69.png)


---
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 #2113: [ZEPPELIN-2190] Support custom web development port

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2113
  
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 #2178: [ZEPPELIN-2302] Add info level logs when installing no...

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2178
  
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 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 #2163: [ZEPPELIN-2287] Add more test to ensure 'RunOnS...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #2174: [ZEPELIN-2209] Add pagination to Helium menu

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2174
  
@1ambda No worries :) 
Then how about 1 page ? I mean if there is only 1 page, we can hide `<<` & 
`>>`. 


---
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 #2181: [ZEPPELIN-2304] Fix vis Icon sizes in helium page

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2181
  
@1ambda I couldn't auto merge this PR into branch-0.7 since there are some 
conflicts. If you don't mind, can you create separate PR for 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
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 #2181: [ZEPPELIN-2304] Fix vis Icon sizes in helium pa...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #2181: [ZEPPELIN-2304] Fix vis Icon sizes in helium page

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2181
  
Thanks. Merging into master and branch-0.7 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 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 #2196: fix bugs for timer saver

[soralee]

Github user soralee commented on the issue:

https://github.com/apache/zeppelin/pull/2196
  
@wary No worry! It's okay! And thanks and Congrats for your contribution. 
:smile: 
Let me test it out and give you feedback.



---
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 (RC3)

[Mina Lee]

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

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

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

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-1035

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 04:00 31/Mar PDT).

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

[CANCEL][VOTE] Release Apache Zeppelin 0.7.1 (RC2)

[Mina Lee]

During the rc2 vote, we've found some critical issues:

   - Exception not propagated to front-end
   - Built-in scatter chart throws exception
   - Editing interpreter setting leaves zombie interpreter process

All issue have been resolved and I am going to open rc3 vote right after.

Cheers,
Mina

On Tue, Mar 28, 2017 at 12:27 AM Jongyoul Lee  wrote:

I cherry-picked ZEPPELIN-1984. We, however, have more issues to be merged
as an hotfix

On Fri, Mar 24, 2017 at 4:52 PM, Jeff Zhang  wrote:

> Sorry, I need to -1 again, as I just found that ZEPPELIN-1984 is also
> needed to backport. Otherwise no error message displayed in frontend when
> interpreter fail to start.
>
>
>
> Sora Lee 于2017年3月24日周五 下午2:14写道：
>
> > I faced a error when switching the scatter chart, the error message that
> is
> > "cannot property 'x' of null" appear in web development tool of web
> > browser. so I created this PR (
> > https://github.com/apache/zeppelin/pull/2186
> > ).
> >
> > Shell we include this patch in 0.7.1 release?
> >
> > Thanks,
> > Sora
> >
> > On Fri, Mar 24, 2017 at 12:32 PM Mina Lee  wrote:
> >
> > > I propose the following RC to be released for the Apache Zeppelin
0.7.1
> > > release.
> > >
> > > The commit id is 163f6730ea91486c581f502863fe62b3cd9b06d4 which is
> > > corresponds to the tag v0.7.1-rc2:
> > >
> > >
> > https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;h=
> refs/tags/v0.7.1-rc2
> > >
> > > The release archives (tgz), signature, and checksums are here
> > > https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.7.1-rc2/
> > >
> > > 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-1034
> > >
> > > 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 21:00 26/Mar PDT).
> > >
> > > [ ] +1 approve
> > > [ ] 0 no opinion
> > > [ ] -1 disapprove (and reason why)
> > >
> >
>



--
이종열, Jongyoul Lee, 李宗烈
http://madeng.net

[GitHub] zeppelin issue #2195: [ZEPPELIN-2319] new methods for ZeppelinContext

[meniluca]

Github user meniluca commented on the issue:

https://github.com/apache/zeppelin/pull/2195
  
@zjffdu I agree in principle, but if you look at the code they are few 
rather trivial new methods, all of them wrapping up the already existing 
``run()``. I have these function running in my notebooks since 1.5 versions, I 
don't think you have to worry about backwards compatibility and maintenance too 
much (they are really simple!). I'll add screenshots later, but it's easy to 
imagine what they do.

Say that I am in the middle of the notebook and I want to run all 
paragraphs before a certain point, I will run ``z.runAllBefore`` and that's it. 
In the same way if I need to run the rest of the notebook I will use 
``z.runAllAfter``. Those functionalities are really useful if you are building 
a notebook with complex dynamic forms usage and they will avoid the user to 
click repeatedly the run button.

In Jupyter buttons and shortcuts that are doing this are already present, 
hence I think that sooner or later you will need those functions.

To describe quickly the other 3 functions... Say that I have one block 
where I setup variables and I want other paragraphs to be updated, instead of 
issuing:
```scala
val maxAge = z.input("maxAge", 30) // select age and run paragraphs
z.run("parID1")
z.run("parID2")
z.run("parD3")
```
I will have
```scala
z.run("parID1","parID2","parID3")
```
or, even more useful, to avoid repetitions
```scala
val arrayIDs = Array("parID1","parID2","parID3")
z.run(arrayIDs:_*)
// in another paragraph
z.run(arrayIDs:_*)
```

Similarly the function ``z.run(int... idx)`` is doing the same thing, 
meanwhile ``z.runNext(int N)``, runs the following N paragraphs. Imagine I have 
the same groups of three blocks in sequence and every time I need to update a 
variable:

```scala
var maxAge = z.input("maxAge", 30)
z.runNext(3)
// following 3 paragraphs are executed
// ... later, in another paragraph below, $maxAge is updated
maxAge = df.where("balance > 2000").max("age").collect()(0)
z.runNext(3) 
// and so on...
```

Anyway, most of them are meant to be more user-friendly wrappers of the 
``run()`` functions, syntactic sugar. The most important are the 
runAllBefore/After in my opinion. Let me know what you think and how I can be 
of any help.

Cheers,
Luca


---
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 #2194: [ZEPPELIN-2229] Providing workaround for nvd3 v...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #2194: [ZEPPELIN-2229] Providing workaround for nvd3 voronoi

[minahlee]

Github user minahlee commented on the issue:

https://github.com/apache/zeppelin/pull/2194
  
Thank you for the contribution @Remilito. Merging 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
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 #2194: [ZEPPELIN-2229] Providing workaround for nvd3 voronoi

[soralee]

Github user soralee commented on the issue:

https://github.com/apache/zeppelin/pull/2194
  
I checked the similar issue ["TypeError: Cannot read property '1' of 
undefined" in the bar 
chart](https://issues.apache.org/jira/browse/ZEPPELIN-2273) we have. 
This error is occured when changing radio button from `Grouped` to 
`Stacked` like the following screenshot.

![z_stack_error](https://cloud.githubusercontent.com/assets/8110458/24394371/b810c2ec-13d6-11e7-8a86-5cb59b1cee8f.png)


But, Fortunately, there is no problem in this branch so, we can also 
resolve it with this PR!

![z2273_no_error](https://cloud.githubusercontent.com/assets/8110458/24394363/ad8312ee-13d6-11e7-9d2c-fb729602460d.gif)


![z2273_no_error2](https://cloud.githubusercontent.com/assets/8110458/24394543/4f9034cc-13d7-11e7-9ea5-b901d191640e.gif)



---
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 #2197: ZEPPELIN-2324. Add property zeppelin.spark.unSupported...

[zjffdu]

Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/2197
  
@Leemoonsoo @jongyoul  @felixcheung Please help review. 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If 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 #2194: [ZEPPELIN-2229] Providing workaround for nvd3 voronoi

[soralee]

Github user soralee commented on the issue:

https://github.com/apache/zeppelin/pull/2194
  
Tested it out and it works very well! 

![z_for_bumpup_check](https://cloud.githubusercontent.com/assets/8110458/24394167/deb1a44e-13d5-11e7-85b7-b1551e9750ab.gif)



---
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 #1887: [ZEPPELIN-1940] most of eslint rules are NOT applied a...

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/1887
  
I will open another PR for this. Too many conflicts 😞 


---
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 #1887: [ZEPPELIN-1940] most of eslint rules are NOT ap...

[1ambda]

Github user 1ambda closed the pull request at:

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


---
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.
---