[GitHub] incubator-zeppelin pull request: [ZEPPELIN-716] protect the whole ...

[zhongneu]

GitHub user zhongneu opened a pull request:

https://github.com/apache/incubator-zeppelin/pull/760

[ZEPPELIN-716] protect the whole spark repl init process

### What is this PR for?
ZeppelinContext may not be initialized properly in concurrent mode:

When I create & run multiple notebooks using rest API concurrently, I can 
see such errors if the jobs trying to use ZeppelinContext:
```
:23: error: not found: value z
```

I think this issue can be reproduced by:
1. create 4 - 5 new notebooks with content: `println(z)`
2. use rest API to run the newly created notebooks concurrently

It seems the issue is gone after I expand the lock to protect the whole 
process of spark REPL initializing / binding. 

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

### Todos

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

### How should this be tested?
1. create 4 - 5 new notebooks with content: `println(z)`
2. use rest API to run the newly created notebooks concurrently

### 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/zhongneu/incubator-zeppelin 
protect-spark-repl-init

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

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


commit 3022612af45df141ce5bbfa242048e04b0fe6d7a
Author: Zhong Wang 
Date:   2016-03-04T07:00:43Z

protect the whole spark repl init process




---
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: ZEPPELIN 683 project for GSOC 2016

[Thamali Wijewardhana]

Hi Alexander,

Thanks a lot for the details and I have started working through those
details .

Thamali

On 4 March 2016 at 08:08, Alexander Bezzubov  wrote:

> Hi Thamali,
>
> thank you for your interest!
>
> First thing to do with any opensource project is to get yourself familiar
> with it, see what Zeppelin is, what it does, how it works and how to build
> it [0]. Involvement in community is the key as well -  try finding an issue
> people are having on the public mailing list [1] and help them (research,
> reproduce, fix, etc).
>
> Especially important for this project would be to read the code and
> understand how multiple NotebookRepo implementations [4] work - that might
> require engaging with community and contribution updates to the docs, which
> will be a huge bonus to your further application proposal.
>
> Next step would be - drafting a proposal or application for this project.
> Please read very carefully general advices on how to do it and what is
> expected from good proposal in 2 other threads related to GSoC [2] and [3].
>
> The main goal for this project would be - to get at least one new
> NotebookRepo implementation using p2p technology, that supports notebook
> visioning merged by the end of the summer.
>
> Important part of that work work would be comparing available p2p
> alternatives and their tech stacks on applicability for our use-case
> (available clients for JVM, read\write throughput, etc) and documenting
> that along the way in wiki and blog posts.
>
> One more potential aspect of this work is an adjustment the UI of
> Zeppelin, to fit better for the notebook visioning (which is right now only
> supported in GitNotebookRepo and does not have much UI)
>
> Hope this helps, this very interesting project indeed and I'm looking
> forward helping with proposals!
>
>  0. http://zeppelin.incubator.apache.org/docs/0.6.0-incubating-SNAPSHOT/
>  1. http://zeppelin.incubator.apache.org/community.html
>  2. http://markmail.org/thread/j53j7d4rsiisewfb
>  3. http://markmail.org/message/naocktanol5iuot3
>  4.
> http://zeppelin.incubator.apache.org/docs/0.6.0-incubating-SNAPSHOT/storage/storage.html
>
> --
> Alex
>
>
> On Thu, Mar 3, 2016 at 8:07 PM, Thamali Wijewardhana <
> thamaliw...@cse.mrt.ac.lk> wrote:
>
>> Hi,
>>
>> I am a third year Computer Science and Engineering undergraduate at
>> University of Moratuwa,Sri Lanka. I am interested in working with Apache. I
>> have worked a lot with Apache Spark ml library when doing machine learning
>> projects during my internship at WSO2. I am also interested in Zeppelin and
>> now I am studying about it.
>>
>> I am interested in this project to build a new  notebookRepo storage and
>> I would like to work with this project in GSOC 2016. Please kindly give me
>> further information on how I could proceed.
>>
>> Thanks
>>
>> Thamali
>>
>
>

[GitHub] incubator-zeppelin pull request: [ZEPPELIN-716] fix a deadlock in ...

[zhongneu]

GitHub user zhongneu opened a pull request:

https://github.com/apache/incubator-zeppelin/pull/759

[ZEPPELIN-716] fix a deadlock in RemoteInterpreter.open/init

### What is this PR for?
Fix a deadlock in RemoteInterpreter.init()


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

### Todos

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

### How should this be tested?

### 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/zhongneu/incubator-zeppelin 
remote-interpreter-deadlock

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

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


commit 3422f0c42690b20255255b28dbbcf370476a56cc
Author: Zhong Wang 
Date:   2016-03-04T05:01:33Z

fix deadlock in RemoteInterpreter.init()




---
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] incubator-zeppelin pull request: Remove duplicated java option con...

[zhongneu]

Github user zhongneu commented on the pull request:

https://github.com/apache/incubator-zeppelin/pull/749#issuecomment-192104991
  
I've reverted the change for JAVA_OPTS, which is fine, because it is not 
used by bin/interpreter.sh


---
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] incubator-zeppelin pull request: [ZEPPELIN-647] - Native Windows s...

[felixcheung]

Github user felixcheung commented on the pull request:

https://github.com/apache/incubator-zeppelin/pull/734#issuecomment-192086401
  
Hmm, interesting. Let's keep this here for now then.


---
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] incubator-zeppelin pull request: ZEPPELIN-385 Read-only mode for z...

[felixcheung]

Github user felixcheung commented on the pull request:

https://github.com/apache/incubator-zeppelin/pull/389#issuecomment-192082716
  
@babokim haven't heard from you - would you be able to continue this work?


---
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] incubator-zeppelin pull request: Zeppelin Flink Spark tutorial

[felixcheung]

Github user felixcheung commented on the pull request:

https://github.com/apache/incubator-zeppelin/pull/418#issuecomment-192082652
  
Where are we on this PR?



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
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] incubator-zeppelin pull request: Install guide modifications based...

[felixcheung]

Github user felixcheung commented on the pull request:

https://github.com/apache/incubator-zeppelin/pull/543#issuecomment-192082492
  
@dcardon @jeffsteinmetz where are we on 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] incubator-zeppelin pull request: Add finish alert with blinking ta...

[felixcheung]

Github user felixcheung commented on the pull request:

https://github.com/apache/incubator-zeppelin/pull/560#issuecomment-192082411
  
where are we on 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] incubator-zeppelin pull request: Add selenium test case to test hi...

[felixcheung]

Github user felixcheung commented on the pull request:

https://github.com/apache/incubator-zeppelin/pull/690#issuecomment-192082267
  
@ravicodder could you rebase please?



---
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] incubator-zeppelin pull request: Add selenium test case for show a...

[felixcheung]

Github user felixcheung commented on the pull request:

https://github.com/apache/incubator-zeppelin/pull/692#issuecomment-192082260
  
@ravicodder could you rebase please?



---
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] incubator-zeppelin pull request: Add new selenium test case to tes...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-zeppelin/pull/693


---
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] incubator-zeppelin pull request: [ZEPPELIN-712] Publish zeppelin-w...

[Leemoonsoo]

Github user Leemoonsoo commented on the pull request:

https://github.com/apache/incubator-zeppelin/pull/757#issuecomment-192075463
  
Merge if there're no more 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] incubator-zeppelin pull request: [ZEPPELIN-701] - Upgrade Tachyon ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-zeppelin/pull/750


---
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: ZEPPELIN 683 project for GSOC 2016

[Alexander Bezzubov]

Hi Thamali,

thank you for your interest!

First thing to do with any opensource project is to get yourself familiar
with it, see what Zeppelin is, what it does, how it works and how to build
it [0]. Involvement in community is the key as well -  try finding an issue
people are having on the public mailing list [1] and help them (research,
reproduce, fix, etc).

Especially important for this project would be to read the code and
understand how multiple NotebookRepo implementations [4] work - that might
require engaging with community and contribution updates to the docs, which
will be a huge bonus to your further application proposal.

Next step would be - drafting a proposal or application for this project.
Please read very carefully general advices on how to do it and what is
expected from good proposal in 2 other threads related to GSoC [2] and [3].

The main goal for this project would be - to get at least one new
NotebookRepo implementation using p2p technology, that supports notebook
visioning merged by the end of the summer.

Important part of that work work would be comparing available p2p
alternatives and their tech stacks on applicability for our use-case
(available clients for JVM, read\write throughput, etc) and documenting
that along the way in wiki and blog posts.

One more potential aspect of this work is an adjustment the UI of Zeppelin,
to fit better for the notebook visioning (which is right now only supported
in GitNotebookRepo and does not have much UI)

Hope this helps, this very interesting project indeed and I'm looking
forward helping with proposals!

 0. http://zeppelin.incubator.apache.org/docs/0.6.0-incubating-SNAPSHOT/
 1. http://zeppelin.incubator.apache.org/community.html
 2. http://markmail.org/thread/j53j7d4rsiisewfb
 3. http://markmail.org/message/naocktanol5iuot3
 4.
http://zeppelin.incubator.apache.org/docs/0.6.0-incubating-SNAPSHOT/storage/storage.html

--
Alex


On Thu, Mar 3, 2016 at 8:07 PM, Thamali Wijewardhana <
thamaliw...@cse.mrt.ac.lk> wrote:

> Hi,
>
> I am a third year Computer Science and Engineering undergraduate at
> University of Moratuwa,Sri Lanka. I am interested in working with Apache. I
> have worked a lot with Apache Spark ml library when doing machine learning
> projects during my internship at WSO2. I am also interested in Zeppelin and
> now I am studying about it.
>
> I am interested in this project to build a new  notebookRepo storage and I
> would like to work with this project in GSOC 2016. Please kindly give me
> further information on how I could proceed.
>
> Thanks
>
> Thamali
>

[jira] [Created] (ZEPPELIN-718) "interpreter binding" & "notebook permissions" icons are not lightened properly

[Zhong Wang (JIRA)]

Zhong Wang created ZEPPELIN-718:
---

 Summary: "interpreter binding" & "notebook permissions" icons are 
not lightened properly
 Key: ZEPPELIN-718
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-718
 Project: Zeppelin
  Issue Type: Bug
  Components: GUI
Affects Versions: 0.6.0
Reporter: Zhong Wang
Priority: Minor


1. If I click the "interpreter binding" button, both "interpreter binding" and 
"notebook permissions" icons will be lightened
2. If I click the "notebook permission" button, neither of them will be 
lightened



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ZEPPELIN-717) ZeppelinContext may not be initialized properly in concurrent mode

[Zhong Wang (JIRA)]

Zhong Wang created ZEPPELIN-717:
---

 Summary: ZeppelinContext may not be initialized properly in 
concurrent mode
 Key: ZEPPELIN-717
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-717
 Project: Zeppelin
  Issue Type: Bug
  Components: zeppelin-interpreter
Affects Versions: 0.6.0
Reporter: Zhong Wang


When I run multiple notebooks concurrently, I can see such errors when I try to 
use a ZeppelinContext:
{code}
:23: error: not found: value z
{code}

I can also see such errors:
{code}
java.lang.NoClassDefFoundError: $iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC
at $iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(:42)
at $iwC$$iwC$$iwC$$iwC$$iwC$$iwC.(:44)
at $iwC$$iwC$$iwC$$iwC$$iwC.(:46)
at $iwC$$iwC$$iwC$$iwC.(:48)
at $iwC$$iwC$$iwC.(:50)
at $iwC$$iwC.(:52)
at $iwC.(:54)
at (:56)
at .(:60)
at .()
at .(:7)
at .()
at $print()
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.apache.spark.repl.SparkIMain$ReadEvalPrint.call(SparkIMain.scala:1065)
at 
org.apache.spark.repl.SparkIMain$Request.loadAndRun(SparkIMain.scala:1346)
at 
org.apache.spark.repl.SparkIMain.loadAndRunReq$1(SparkIMain.scala:840)
at org.apache.spark.repl.SparkIMain.interpret(SparkIMain.scala:871)
at org.apache.spark.repl.SparkIMain.interpret(SparkIMain.scala:819)
at 
org.apache.zeppelin.spark.SparkInterpreter.interpretInput(SparkInterpreter.java:780)
at 
org.apache.zeppelin.spark.SparkInterpreter.interpret(SparkInterpreter.java:744)
at 
org.apache.zeppelin.spark.SparkInterpreter.interpret(SparkInterpreter.java:737)
at 
org.apache.zeppelin.interpreter.ClassloaderInterpreter.interpret(ClassloaderInterpreter.java:57)
at 
org.apache.zeppelin.interpreter.LazyOpenInterpreter.interpret(LazyOpenInterpreter.java:93)
at 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:331)
at org.apache.zeppelin.scheduler.Job.run(Job.java:171)
at 
org.apache.zeppelin.scheduler.FIFOScheduler$1.run(FIFOScheduler.java:139)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.ClassNotFoundException: 
$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC
at 
scala.tools.nsc.interpreter.AbstractFileClassLoader.findClass(AbstractFileClassLoader.scala:83)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
... 37 more
{code}

I saw the issues after a quick fix of ZEPPELIN-716. I am not sure whether they 
are related, but I will keep this radar open to keep track with.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: R interpreter in Zeppelin: further steps

[Alexander Bezzubov]

Thank you for sharing Jeff!

Now it's time to speak out for anybody, who have strong opinion against
plan A, aka just merging #208 and moving on.

I agree with Eran and Enzo - as we just building a community over code
here,
passing judgements is not the best way to do it and it's up to users to
decide which option
they are willing to use and for developers which one they want to
contribute (given it has technical merit).

I also like DuyHai approach, but making people do things does not seem
possible (at least for me).

More important thing here is our ability to be an inclusive meritocratic
community, polite and respectful to individual members, and ability to
reach a consensus.


So question: are there anybody, who have strong opinions against going on
with plan A?


--
Alex

On Thu, Mar 3, 2016 at 2:12 PM, Jeff Steinmetz 
wrote:

> I too prefer plan A - merging two different R interpreters sounds like a
> maintenance and documentation headache for end users.
>
>
> Do you or the community feel there are “specific” additional steps from a
> “technical” or “development” perspective that need to happen in order merge
> 208?
> If we know what’s holding back the merge technically (all history aside)
> we can work as a community to solve it.
>
> Olympic spirit!
> Looking forward to helping this through.
>
> 
> Jeff Steinmetz
> Principal Architect
> Akili Interactive
>
>
>
>
>
>
> On 3/2/16, 8:14 PM, "Amos Elberg"  wrote:
>
> >Alex -- the gist of my email is that we already have a consensus, and
> have had
> >a consensus since November.  The consensus was to merge 208.  That's
> "Plan A."
> >
> >With all respect, I don't see that anyone other than you believes we don't
> >have a consensus on Plan A already, or has any issue with Plan A.
> >
> >In fact, I'm going to call now for "lazy consensus" on Plan A:  End the
> debate
> >and move rapidly to merge 208, completing whatever work is necessary to do
> >that (if any).
> >
> >For the record, yes, I do object to Plan C.  Numerous users have
> complained
> >that with two different PRs, they don't know which interpreter to use.
> That's
> >a strong reason to not merge two. In fact it will confuse people more,
> because
> >one interpreter's R environment won't be shared with the other
> interpreter,
> >and you can't move variables between them. Moreover, no-one has presented
> any
> >benefit to merging the second one.
> >
> >In addition, while 208 seems to be ready to merge (waiting only on the
> work
> >you're doing on CI), the second PR is nowhere close.  So, that's another
> >reason: 208 should not have to wait for the other to be ready.
> >
> >But in any event, I disagree that there is any issue here.
> >
> >If you intend to continue this thread, then please address the issues
> raised
> >in my e-mail earlier.  Please also explain any strong objection to Plan A.
> >
> >Thanks,
> >
> >-Amos
> >
> >On Thursday, March 03, 2016 12:09:33 PM Alexander Bezzubov wrote:
> >> Guys, please let's keep the discussion focused on the subject.
> >>
> >> Amos, I do not understand, are you saying that you do object on the
> >> community proceeding with plan C? If not - there is no need to
> answer\post
> >> in this thread right now.
> >>
> >> Again, we are not debating fate\merit\features of any particular
> >> contribution here.
> >>
> >> Please post in this thread only if you strongly disagree with the
> suggested
> >> plan.
> >> I'm calling for a lazy consensus and as soon as there are no objections
> -
> >> will be ready to proceed with the plan above.
> >>
> >> Sooner we reach a consensus on the topic - sooner we can make further
> >> progress.
> >>
> >> --
> >> Alex
> >>
> >> On Thu, Mar 3, 2016 at 11:45 AM, Amos Elberg 
> wrote:
> >> > Alex - What are we still debating at this point?
> >> >
> >> > I'm starting to feel like Charlie Brown with the football here.
> >> >
> >> > The PR was submitted in August and originally reviewed at the
> beginning of
> >> > September.
> >> > In, I think, early December, it was then extensively reviewed and
> >> > discussed.  I made a few requested changes, and at that time there
> was a
> >> > decision to merge 208 pending Moon working on the CI problem.
> >> > In January the PR was reviewed again, by you and others, and I thought
> >> > you'd decided to merge pending some changes from me, and you were
> going to
> >> > work on CI.
> >> > In February, when people continued to email the list to ask what was
> up,
> >> > we
> >> > said again that the community was moving to merge 208.
> >> > The thread started a few days ago.  Nobody argued for changing the
> plan.
> >> > The discussion lapsed until, today, I responded to a technical point.
> >> >
> >> > I'm not sure why this is coming up again.  If Eric (or others) feel
> >> > strongly about the issues Eric raised with 208, which is things like
> >> > whether to link rscala or fork it (or whatever), why can't they 

[jira] [Created] (ZEPPELIN-716) Deadlock in Paragraph.jobRun when concurrent spark interpreter is allowed

[Zhong Wang (JIRA)]

Zhong Wang created ZEPPELIN-716:
---

 Summary: Deadlock in Paragraph.jobRun when concurrent spark 
interpreter is allowed
 Key: ZEPPELIN-716
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-716
 Project: Zeppelin
  Issue Type: Bug
  Components: zeppelin-interpreter, zeppelin-server
Affects Versions: 0.6.0
Reporter: Zhong Wang
Priority: Critical


There is a circular wait between 2 jobRun threads on RemoteInterpreterProcess 
and InterpreterGroup

Full stack trace will be attached



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-zeppelin pull request: ZEPPELIN-335: Apache Pig interpre...

[smartinsightsfromdata]

Github user smartinsightsfromdata commented on the pull request:

https://github.com/apache/incubator-zeppelin/pull/338#issuecomment-192011529
  
@abajwa-hw @felixcheung @bzz is the idea to have a pig interpreter dead?

It could be really useful...


---
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] incubator-zeppelin pull request: [ZEPPELIN-698] Change shortcut fo...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-zeppelin/pull/756


---
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] incubator-zeppelin pull request: [ZEPPELIN-689] Add AngularJS z ob...

[doanduyhai]

Github user doanduyhai commented on the pull request:

https://github.com/apache/incubator-zeppelin/pull/740#issuecomment-191840961
  
> In this perspective, i'm not sure it's good to embed run paragraph inside 
of z.angularBind() function in front-end side, while corresponding api in 
backend side does not.

 Ok, I see your point now. The table showing back-end and front-end API is 
quite clear. So I'll remove the `runParagraph` attribute. If user want to 
trigger paragraph execution they can use `z.runParagraph()`

> htmlElement is html Element that created by user code in the paragraph.
That's only way i know get current paragraph id from the javascript that 
defined in particular paragraph.

Your idea can work if we have a paragraph defining HTML element. But what 
if I want to bind Angular value to a SparkSQL paragraph or Cassandra paragraph ?

```sql
%sql
SELECT * FROM my_table WHERE id = ${id}
```

```sql
%cassandra
SELECT * FROM table WHERE key=${key}
```

 There is **no** HTML element so I cannot retrieve the paragraph Id using 
DOM JS function... The only way is to rely on **paragraph id**, or maybe 
**paragraph title** but we don't have **unicity guarantee** when using title ...

> paragraph id can not be simply changed, while of some features (rest api 
to run paragraph, iframe link, ...) and a lot of internal code (angulardisplay 
system, job scheduler, etc) assumes paragraph id is immutable.

 No no, I think there is a **misunderstanding** here. I don't want to 
change the paragraph id. What I want is that **on Import, we keep the original 
paragraph id** and don't generate a new one every time so that 
`z.angularBind('val', val, {paragraphId: ''})`  is re-usable and does not 
break when sharing or importing/exporting notes

 To enable this behavior, **there is very few change to the code base**, 
see the diff **[here](https://gist.github.com/doanduyhai/350ddf29cedd4ca37f45)**

The result seems working well with import/export and clone


![testimport-export_clone](https://cloud.githubusercontent.com/assets/1532977/13501070/db0a023c-e16d-11e5-97d3-d2c105d04f14.gif)

> Right, that's what i wanted to say actually :-)

 So there is no problem, we both agree that `z.angularBind()` should **bind 
value to only one paragraph** right ?

>  i can convert it to "how to initiate angularObject binding from the 
front-end code?" Because passing variable from front end to back end is already 
possible once they're binded.


 Exactly, so `z.angularBind()` is here to fill in the gap and allow to 
initiate a new binding to an Angular variable from front-end.



 So to conclude, we indeed agree on many things. I propose the following 
next steps:

 1. Rework this PR to remove `runParagraph` so we decouple 
`z.angularBind()` and `z.runParagrap()`
 2. Create another PR to keep the original paragraph id every time we 
import a note, based on the patch I showed


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

[GitHub] incubator-zeppelin pull request: [ZEPPELIN-647] - Native Windows s...

[granturing]

Github user granturing commented on the pull request:

https://github.com/apache/incubator-zeppelin/pull/734#issuecomment-191828541
  
So, interestingly enough I only see an issue with Spark (using Hadoop 2.6). 
Running Flink seems fine, but it could be dependent on the Hadoop client 
versions being used by the two. But yes, the HDFS interpreter will need to have 
the necessary Windows dependencies. You want me to pull that line out?


---
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-715) Provide version information

[Lee moon soo (JIRA)]

Lee moon soo created ZEPPELIN-715:
-

 Summary: Provide version information
 Key: ZEPPELIN-715
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-715
 Project: Zeppelin
  Issue Type: New Feature
Affects Versions: 0.5.6
Reporter: Lee moon soo


It would be nice Zeppelin provides version information from it's REST api, GUI 
and command line.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)