[GitHub] zeppelin issue #955: [ZEPPELIN-940] Allow zeppelin server to connect to alre...

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/955
  
LGTM except minor 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 #955: [ZEPPELIN-940] Allow zeppelin server to connect to alre...

[SachinJanani]

Github user SachinJanani commented on the issue:

https://github.com/apache/zeppelin/pull/955
  
@jongyoul @corneadoug Done with the docs can you please have a look.


---
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 #955: [ZEPPELIN-940] Allow zeppelin server to connect to alre...

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/955
  
@SachinJanani Yes, it's one of the best place.


---
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 #806: [ZEPPELIN-707]Automatically adds %.* of previous paragr...

[mwkang]

Github user mwkang commented on the issue:

https://github.com/apache/zeppelin/pull/806
  
@corneadoug I fix whole issue. Can you check my code?


---
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 #981: ZEPPELIN-925 Part 2. Merge Hive Interpreter into...

[jongyoul]

Github user jongyoul closed the pull request at:

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


---
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 #985: ZEPPELIN-974 Merge TajoInterpreter into JdbcInte...

[jongyoul]

GitHub user jongyoul opened a pull request:

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

ZEPPELIN-974 Merge TajoInterpreter into JdbcInterpreter

### What is this PR for?
Merging TajoInterpreter into JdbcInterpreter, and removing TajoInterprete


### What type of PR is it?
[Feature]

### Todos
* [x] - Remove TajoInterpreter and Document jdbc.md

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

### 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/jongyoul/zeppelin ZEPPELIN-974

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

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


commit dbdd90e569080aec10d99c082621bb2023da087e
Author: Jongyoul Lee 
Date:   2016-06-09T16:11:23Z

- Removed TajoInterpreter from master
- Added example for using Tajo through JDBC




---
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 #955: [ZEPPELIN-940] Allow zeppelin server to connect to alre...

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/955
  
@corneadoug Thanks, and about review, I have been worried that you have 
been pressed with all of review requests of front-side issues.


---
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 #965: [ZEPPELIN-957] Normalize note name.

[corneadoug]

Github user corneadoug commented on the issue:

https://github.com/apache/zeppelin/pull/965
  
Tested

Merging if there is 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] zeppelin issue #955: [ZEPPELIN-940] Allow zeppelin server to connect to alre...

[corneadoug]

Github user corneadoug commented on the issue:

https://github.com/apache/zeppelin/pull/955
  
@jongyoul Tested, LGTM.
What about the doc? Should it be part of this PR or a separate one?


---
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 #955: [ZEPPELIN-940] Allow zeppelin server to connect to alre...

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/955
  
@Leemoonsoo Yes, I just think there're too many requests for him, so I'm 
asking you to have another candidate.


---
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 #976: ZEPPLIN-976 ] HotFix - zeppelin server does not restart...

[cloverhearts]

Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/976
  
@bzz 
I think this is a very serious problem.
In my personal opinion, first merge this PR, and improve Credentials 
feature in future ( new pr ).

Problem situation, please refer to the screenshot.

Reproduce the problem, please note the following:
1. Click to zeppelin home for web ui.
2. Click to zeppelin Credentials.
3. 'Entity' information without writing, username and password only written 
to storage.
4. Click to zeppelin home for web ui.
5. Click to zeppelin Credentials.
and zeppelin restart.




---
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 #983: [ZEPPELIN-980] Move git repository from incubator-zeppe...

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

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

[jira] [Created] (ZEPPELIN-983) org.apache.thrift.TApplicationException: Internal error processing createInterpreter when running SparkR

[Ahyoung (JIRA)]

Ahyoung created ZEPPELIN-983:


 Summary: org.apache.thrift.TApplicationException: Internal error 
processing createInterpreter when running SparkR
 Key: ZEPPELIN-983
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-983
 Project: Zeppelin
  Issue Type: Bug
Reporter: Ahyoung


When I tried to run {code} sc <- sparkR.init() {code} using SparkR interpreter, 
I got the below error. This occurs in latest master branch. 

{code}
org.apache.thrift.TApplicationException: Internal error processing 
createInterpreter
at 
org.apache.thrift.TApplicationException.read(TApplicationException.java:111)
at org.apache.thrift.TServiceClient.receiveBase(TServiceClient.java:71)
at 
org.apache.zeppelin.interpreter.thrift.RemoteInterpreterService$Client.recv_createInterpreter(RemoteInterpreterService.java:167)
at 
org.apache.zeppelin.interpreter.thrift.RemoteInterpreterService$Client.createInterpreter(RemoteInterpreterService.java:151)
at 
org.apache.zeppelin.interpreter.remote.RemoteInterpreter.init(RemoteInterpreter.java:170)
at 
org.apache.zeppelin.interpreter.remote.RemoteInterpreter.getFormType(RemoteInterpreter.java:316)
at 
org.apache.zeppelin.interpreter.LazyOpenInterpreter.getFormType(LazyOpenInterpreter.java:104)
at org.apache.zeppelin.notebook.Paragraph.jobRun(Paragraph.java:249)
at org.apache.zeppelin.scheduler.Job.run(Job.java:176)
at 
org.apache.zeppelin.scheduler.RemoteScheduler$JobRunner.run(RemoteScheduler.java:328)
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)
{code}



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

[GitHub] zeppelin issue #955: [ZEPPELIN-940] Allow zeppelin server to connect to alre...

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/955
  
@jongyoul We have some front-end expert in the community like @corneadoug. 
But basically anyone in the community can participate review.

Thanks @SachinJanani for the contribution. It looks good to me.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have 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 #980: [ZEPPELIN-871] [WIP] spark 2.0 interpreter on scala 2.1...

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/980
  
I'm trying to combine 2.10 and 2.11 into one implementation in lresende#1


---
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 #950: [ZEPPELIN-901] Cassandra interpreter V3

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/950
  
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] zeppelin pull request #908: ZEPPELIN-598 ] Dynamic loading for Interpreter a...

[cloverhearts]

Github user cloverhearts closed the pull request at:

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


---
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 #984: [ZEPPELIN-982] Improve interpreter completion AP...

[AhyoungRyu]

GitHub user AhyoungRyu opened a pull request:

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

[ZEPPELIN-982] Improve interpreter completion API

### What is this PR for?
When people implement a new interpreter, they extend 
[interpreter.java](https://github.com/apache/zeppelin/blob/master/zeppelin-interpreter/src/main/java/org/apache/zeppelin/interpreter/Interpreter.java)
 as described in 
[here](https://zeppelin.apache.org/docs/0.6.0-SNAPSHOT/development/writingzeppelininterpreter.html).
 Among the several methods in 
[interpreter.java](https://github.com/apache/zeppelin/blob/master/zeppelin-interpreter/src/main/java/org/apache/zeppelin/interpreter/Interpreter.java),
 [completion() 
API](https://github.com/apache/zeppelin/blob/master/zeppelin-interpreter/src/main/java/org/apache/zeppelin/interpreter/Interpreter.java#L109)
 enables auto-completion.

However this API is too simple compared to other project's auto-completion 
and hard to add more at the moment. So for the aspect of further expansion, it 
would be better to separate and restructure this API before the this release( 
0.6.0 ).

### What type of PR is it?
Improvement

### Todos
* [x] - Create new structure : `InterpreterCompletion` in 
`RemoteInterpreterService.thrift` and regenerate 
`zeppelin-interpreter/src/main/java/org/apache/zeppelin/interpreter/thrift/*` 
files 
* [x] - Change all existing `List completion` -> 
`List completion` 
* [x] - Change `paragraph.controller.js` to point real `name` and `value`

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

### How should this be tested?
Since this improvement is just API change, it should work same as before. 
So after applying this patch, and check whether auto-completion works well or 
not. 

Use `. + ctrl` for auto-completion. For example,

```
%spark 
sc.version
```

When after typing `sc.` and pushing  `. + ctrl` down, `version` should be 
shown in the auto-completion list. 

### Screenshots (if appropriate)

![auto_completion](https://cloud.githubusercontent.com/assets/10060731/15952521/72937782-2e76-11e6-8246-4faf0dd77a5b.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/incubator-zeppelin ZEPPELIN-982

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

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


commit b12b056fbee3030e002a9109f80611ca6ed1d851
Author: AhyoungRyu 
Date:   2016-06-09T16:33:30Z

Define InterpreterCompletion structure to thrift file

commit c42f3b51131aaaf99d17c9046e396b08cf3320d3
Author: AhyoungRyu 
Date:   2016-06-09T16:33:56Z

Change v -> v.name & v.value in front

commit e36c2d4f426c944eed43550921bf234fcfb4f05f
Author: AhyoungRyu 
Date:   2016-06-09T16:36:28Z

Add automatically generated thrift class

commit c67a16896f9dcced6102c3b258dc8e2b381e7cbf
Author: AhyoungRyu 
Date:   2016-06-09T16:37:22Z

Apply new InterpreterCompletion class under zeppelin-interpreter/

commit 6e8340ddca8a0885c130387e9571f73402b3d877
Author: AhyoungRyu 
Date:   2016-06-09T16:37:43Z

Apply new InterpreterCompletion class under zeppelin-server/

commit f93b7c2e0b21a600567dab8d7dbe4763bea52f03
Author: AhyoungRyu 
Date:   2016-06-09T16:38:03Z

Apply new InterpreterCompletion class under zeppelin-zengine/

commit eeb5cf3f549c0de09628b26fc54dcb305c722b86
Author: AhyoungRyu 
Date:   2016-06-09T16:38:38Z

Apply new InterpreterCompletion class to all interpreter class files

commit 936e6fbfbddfacc88f7ada38998b87f2ec5b757e
Author: AhyoungRyu 
Date:   2016-06-09T17:31:49Z

Change return type

commit 476181286f00cbc3d800751f404ab37a2a35ef6f
Author: AhyoungRyu 
Date:   2016-06-10T00:35:17Z

Fix type casting error in SparkInterpreter

commit b4e2e9f7f9c5bd3861efaf93516367a5a10d8119
Author: AhyoungRyu 
Date:   2016-06-10T00:54:21Z

Remove console.log




---
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 #975: [ZEPPELIN-975] Move download data button outside...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #947: [ZEPPELIN-939] Improve notebook authorization do...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-982) Improve Interpreter completion API

[Ahyoung (JIRA)]

Ahyoung created ZEPPELIN-982:


 Summary: Improve Interpreter completion API
 Key: ZEPPELIN-982
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-982
 Project: Zeppelin
  Issue Type: Improvement
  Components: Interpreters
Affects Versions: 0.6.0
Reporter: Ahyoung
Assignee: Ahyoung
Priority: Minor


 When people implement a new interpreter, they extend 
[interpreter.java|https://github.com/apache/zeppelin/blob/master/zeppelin-interpreter/src/main/java/org/apache/zeppelin/interpreter/Interpreter.java]
 as described in [here| 
https://zeppelin.apache.org/docs/0.6.0-SNAPSHOT/development/writingzeppelininterpreter.html].
 Among the several methods in 
[interpreter.java|https://github.com/apache/zeppelin/blob/master/zeppelin-interpreter/src/main/java/org/apache/zeppelin/interpreter/Interpreter.java],
 [completion() API | 
https://github.com/apache/zeppelin/blob/master/zeppelin-interpreter/src/main/java/org/apache/zeppelin/interpreter/Interpreter.java#L109]enables
 auto-completion. 

However this API is too simple compared to other project auto-completion and 
hard to add more at the moment. So for the aspect of usage expansion, it would 
be better to separate and restructure this API before the this release( 0.6.0 
). 



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

[GitHub] zeppelin issue #983: [ZEPPELIN-980] Move git repository from incubator-zeppe...

[minahlee]

Github user minahlee commented on the issue:

https://github.com/apache/zeppelin/pull/983
  
I think it's not changed only in github ui.

you can see that you can access to https://git.apache.org/zeppelin.git/ but 
not to https://git.apache.org/incubator-zeppelin.git/


---
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 #983: [ZEPPELIN-980] Move git repository from incubator-zeppe...

[corneadoug]

Github user corneadoug commented on the issue:

https://github.com/apache/zeppelin/pull/983
  
The mirror is still pointing to 
`git://git.apache.org/incubator-zeppelin.git`
Is it safe to change this info?


---
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 #973: [ZEPPELIN-973, ZEPPELIN-954] Table rendering improvemen...

[corneadoug]

Github user corneadoug commented on the issue:

https://github.com/apache/zeppelin/pull/973
  
@jasonxh I managed to do it, 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.
---

Re: [DISCUSS] Apache Zeppelin 0.6.0 Release

[Vinay Shukla]

+1, how far along is support for Spark 2.0?

On Thursday, June 9, 2016, Trevor Grant  wrote:

> +1 to release ASAP, Spark 2.0 should not be a blocker in anyway imho.
>
> Trevor Grant
> Data Scientist
> https://github.com/rawkintrevo
> http://stackexchange.com/users/3002022/rawkintrevo
> http://trevorgrant.org
>
> *"Fortunate is he, who is able to know the causes of things."  -Virgil*
>
>
> On Thu, Jun 9, 2016 at 4:49 PM, Federico Valeri  >
> wrote:
>
> > +1
> >
> > I recently joined the project and I'll try to contribute as much as I
> can.
> > Congrats for TLP.
> > Il 09 giu 2016 11:43 PM, "DuyHai Doan"  > ha scritto:
> >
> > > +1
> > >
> > > On Thu, Jun 9, 2016 at 11:11 PM, Ahyoung Ryu  >
> > > wrote:
> > >
> > > > Big +1 for 0.6.0 release.
> > > >
> > > > @Prabhjyot Appreciate for letting us know, finally we have *Zeppelin
> > > > *repository
> > > > not incubator-zeppelin :)
> > > >
> > > > 2016년 6월 9일 (목) 오후 1:56, Khalid Huseynov  >님이 작성:
> > > >
> > > > > +1 on release.
> > > > >
> > > > > On Thu, Jun 9, 2016 at 11:13 AM, Prabhjyot Singh <
> > > > prabhjyotsi...@gmail.com 
> > > > > >
> > > > > wrote:
> > > > >
> > > > > > +1 for release.
> > > > > >
> > > > > > And just noticed https://github.com/apache/zeppelin.
> > > > > >
> > > > > >
> > > > > > On 9 June 2016 at 23:29, Alexander Bezzubov  >
> > wrote:
> > > > > >
> > > > > > > +1 for cutting a release ASAP
> > > > > > >
> > > > > > > And thank you Mina for volunteering to manage the next release!
> > > > > > >
> > > > > > > On Thu, Jun 9, 2016, 18:21 moon soo Lee  > wrote:
> > > > > > >
> > > > > > > > +1 on dedicated release manager (thanks for volunteering,
> > Mina!)
> > > > > > > >
> > > > > > > > On Thu, Jun 9, 2016 at 7:41 AM Felix Cheung <
> > > > > felixcheun...@hotmail.com 
> > > > > > >
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > +1 on release branch+1 on dedicated release manager (thanks
> > for
> > > > > > > > > volunteering, Mina!)
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > _
> > > > > > > > > From: mina lee >
> > > > > > > > > Sent: Wednesday, June 8, 2016 9:50 AM
> > > > > > > > > Subject: Re: [DISCUSS] Apache Zeppelin 0.6.0 Release
> > > > > > > > > To:  >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Moon, I think it's good idea to cut the branch on 15 June.
> > > > > > > > > As we discussed in previous release discussion thread [1],
> > > shall
> > > > we
> > > > > > > take
> > > > > > > > a
> > > > > > > > > rotation for this release?
> > > > > > > > > If so, I would like to volunteer this time.
> > > > > > > > >
> > > > > > > > > But in the end, I think it would be better to have one
> > > dedicated
> > > > > > > release
> > > > > > > > > manager like other apache projects do. It takes time for
> > every
> > > > new
> > > > > > > > release
> > > > > > > > > manager to get familiar with apache release process, set
> the
> > > > > > > environment,
> > > > > > > > > etc. And I expect for community to be more structured at
> > > release
> > > > by
> > > > > > > > having
> > > > > > > > > release manager who can takes more about release time,
> > release
> > > > > scope.
> > > > > > > > >
> > > > > > > > > regards,
> > > > > > > > > mina
> > > > > > > > >
> > > > > > > > > [1]
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> http://apache-zeppelin-dev-mailing-list.75694.x6.nabble.com/DISCUSS-Release-0-5-6-incubating-td4728i20.html
> > > > > > > > >
> > > > > > > > > On Wed, Jun 8, 2016 at 8:34 AM, Guillaume Alleon <
> > > > > > > > > guillaume.all...@gmail.com 
> > > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Ho mon
> > > > > > > > > >
> > > > > > > > > > Do we have a branch using the preview release of spark
> 2.0?
> > > > > > > > > >
> > > > > > > > > > Cheers
> > > > > > > > > > Guillaume
> > > > > > > > > >
> > > > > > > > > > Sent from a small device
> > > > > > > > > >
> > > > > > > > > > > On 08 Jun 2016, at 17:10, moon soo Lee <
> m...@apache.org >
> > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > How about we create release branch 'branch-0.6' from
> > master
> > > > on
> > > > > 15
> > > > > > > > June,
> > > > > > > > > > > 00:00 PDT, and start release process from that point?
> > > > > > > > > > >
> > > > > > > > > > > Most of TLP migration has been done (except for git
> > source
> > > > > repo /
> > > > > > > > > mirror
> > > > > > > > > > > migration) and we can always create minor release with
> > > spark
> > > > > 2.0
> > > > > > > > > support
> > > > > > > > > > if
> > > > 

Re: [DISCUSS] Apache Zeppelin 0.6.0 Release

[Trevor Grant]

+1 to release ASAP, Spark 2.0 should not be a blocker in anyway imho.

Trevor Grant
Data Scientist
https://github.com/rawkintrevo
http://stackexchange.com/users/3002022/rawkintrevo
http://trevorgrant.org

*"Fortunate is he, who is able to know the causes of things."  -Virgil*


On Thu, Jun 9, 2016 at 4:49 PM, Federico Valeri 
wrote:

> +1
>
> I recently joined the project and I'll try to contribute as much as I can.
> Congrats for TLP.
> Il 09 giu 2016 11:43 PM, "DuyHai Doan"  ha scritto:
>
> > +1
> >
> > On Thu, Jun 9, 2016 at 11:11 PM, Ahyoung Ryu 
> > wrote:
> >
> > > Big +1 for 0.6.0 release.
> > >
> > > @Prabhjyot Appreciate for letting us know, finally we have *Zeppelin
> > > *repository
> > > not incubator-zeppelin :)
> > >
> > > 2016년 6월 9일 (목) 오후 1:56, Khalid Huseynov 님이 작성:
> > >
> > > > +1 on release.
> > > >
> > > > On Thu, Jun 9, 2016 at 11:13 AM, Prabhjyot Singh <
> > > prabhjyotsi...@gmail.com
> > > > >
> > > > wrote:
> > > >
> > > > > +1 for release.
> > > > >
> > > > > And just noticed https://github.com/apache/zeppelin.
> > > > >
> > > > >
> > > > > On 9 June 2016 at 23:29, Alexander Bezzubov 
> wrote:
> > > > >
> > > > > > +1 for cutting a release ASAP
> > > > > >
> > > > > > And thank you Mina for volunteering to manage the next release!
> > > > > >
> > > > > > On Thu, Jun 9, 2016, 18:21 moon soo Lee  wrote:
> > > > > >
> > > > > > > +1 on dedicated release manager (thanks for volunteering,
> Mina!)
> > > > > > >
> > > > > > > On Thu, Jun 9, 2016 at 7:41 AM Felix Cheung <
> > > > felixcheun...@hotmail.com
> > > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > +1 on release branch+1 on dedicated release manager (thanks
> for
> > > > > > > > volunteering, Mina!)
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > _
> > > > > > > > From: mina lee 
> > > > > > > > Sent: Wednesday, June 8, 2016 9:50 AM
> > > > > > > > Subject: Re: [DISCUSS] Apache Zeppelin 0.6.0 Release
> > > > > > > > To:  
> > > > > > > >
> > > > > > > >
> > > > > > > > Moon, I think it's good idea to cut the branch on 15 June.
> > > > > > > > As we discussed in previous release discussion thread [1],
> > shall
> > > we
> > > > > > take
> > > > > > > a
> > > > > > > > rotation for this release?
> > > > > > > > If so, I would like to volunteer this time.
> > > > > > > >
> > > > > > > > But in the end, I think it would be better to have one
> > dedicated
> > > > > > release
> > > > > > > > manager like other apache projects do. It takes time for
> every
> > > new
> > > > > > > release
> > > > > > > > manager to get familiar with apache release process, set the
> > > > > > environment,
> > > > > > > > etc. And I expect for community to be more structured at
> > release
> > > by
> > > > > > > having
> > > > > > > > release manager who can takes more about release time,
> release
> > > > scope.
> > > > > > > >
> > > > > > > > regards,
> > > > > > > > mina
> > > > > > > >
> > > > > > > > [1]
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> http://apache-zeppelin-dev-mailing-list.75694.x6.nabble.com/DISCUSS-Release-0-5-6-incubating-td4728i20.html
> > > > > > > >
> > > > > > > > On Wed, Jun 8, 2016 at 8:34 AM, Guillaume Alleon <
> > > > > > > > guillaume.all...@gmail.com
> > > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Ho mon
> > > > > > > > >
> > > > > > > > > Do we have a branch using the preview release of spark 2.0?
> > > > > > > > >
> > > > > > > > > Cheers
> > > > > > > > > Guillaume
> > > > > > > > >
> > > > > > > > > Sent from a small device
> > > > > > > > >
> > > > > > > > > > On 08 Jun 2016, at 17:10, moon soo Lee 
> > > > wrote:
> > > > > > > > > >
> > > > > > > > > > How about we create release branch 'branch-0.6' from
> master
> > > on
> > > > 15
> > > > > > > June,
> > > > > > > > > > 00:00 PDT, and start release process from that point?
> > > > > > > > > >
> > > > > > > > > > Most of TLP migration has been done (except for git
> source
> > > > repo /
> > > > > > > > mirror
> > > > > > > > > > migration) and we can always create minor release with
> > spark
> > > > 2.0
> > > > > > > > support
> > > > > > > > > if
> > > > > > > > > > spark 2.0 support is not ready when we cut the release
> > > branch.
> > > > > > > > > >
> > > > > > > > > > Thanks,
> > > > > > > > > > moon
> > > > > > > > > >
> > > > > > > > > >> On Wed, May 25, 2016 at 1:09 PM Vinay Shukla <
> > > > > > vinayshu...@gmail.com
> > > > > > > >
> > > > > > > > > wrote:
> > > > > > > > > >>
> > > > > > > > > >> Agree, let's make our first release as a TLP.
> > > > > > > > > >>
> > > > > > > > > >> On Wednesday, May 25, 2016, Felix Cheung <
> > > > > > felixcheun...@hotmail.com
> > > > > > > >
> > > > > > > > > >> wrote:
> > > > > > > > > >>
> > > > > > > > > 

[jira] [Created] (ZEPPELIN-981) Sometimes error information is provided, sometimes not provided.

[Matt (JIRA)]

Matt created ZEPPELIN-981:
-

 Summary: Sometimes error information is provided, sometimes not 
provided.
 Key: ZEPPELIN-981
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-981
 Project: Zeppelin
  Issue Type: Task
Reporter: Matt


Hello,

Why is it when I run a Cassandra query on Zeppelin and there's an error - 
sometimes it gives me the error feedback and sometimes it is blank.  How do I 
expose the errors?



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

Re: [DISCUSS] Apache Zeppelin 0.6.0 Release

[Ahyoung Ryu]

Big +1 for 0.6.0 release.

@Prabhjyot Appreciate for letting us know, finally we have *Zeppelin
*repository
not incubator-zeppelin :)

2016년 6월 9일 (목) 오후 1:56, Khalid Huseynov 님이 작성:

> +1 on release.
>
> On Thu, Jun 9, 2016 at 11:13 AM, Prabhjyot Singh  >
> wrote:
>
> > +1 for release.
> >
> > And just noticed https://github.com/apache/zeppelin.
> >
> >
> > On 9 June 2016 at 23:29, Alexander Bezzubov  wrote:
> >
> > > +1 for cutting a release ASAP
> > >
> > > And thank you Mina for volunteering to manage the next release!
> > >
> > > On Thu, Jun 9, 2016, 18:21 moon soo Lee  wrote:
> > >
> > > > +1 on dedicated release manager (thanks for volunteering, Mina!)
> > > >
> > > > On Thu, Jun 9, 2016 at 7:41 AM Felix Cheung <
> felixcheun...@hotmail.com
> > >
> > > > wrote:
> > > >
> > > > > +1 on release branch+1 on dedicated release manager (thanks for
> > > > > volunteering, Mina!)
> > > > >
> > > > >
> > > > >
> > > > > _
> > > > > From: mina lee 
> > > > > Sent: Wednesday, June 8, 2016 9:50 AM
> > > > > Subject: Re: [DISCUSS] Apache Zeppelin 0.6.0 Release
> > > > > To:  
> > > > >
> > > > >
> > > > > Moon, I think it's good idea to cut the branch on 15 June.
> > > > > As we discussed in previous release discussion thread [1], shall we
> > > take
> > > > a
> > > > > rotation for this release?
> > > > > If so, I would like to volunteer this time.
> > > > >
> > > > > But in the end, I think it would be better to have one dedicated
> > > release
> > > > > manager like other apache projects do. It takes time for every new
> > > > release
> > > > > manager to get familiar with apache release process, set the
> > > environment,
> > > > > etc. And I expect for community to be more structured at release by
> > > > having
> > > > > release manager who can takes more about release time, release
> scope.
> > > > >
> > > > > regards,
> > > > > mina
> > > > >
> > > > > [1]
> > > > >
> > > > >
> > > >
> > >
> >
> http://apache-zeppelin-dev-mailing-list.75694.x6.nabble.com/DISCUSS-Release-0-5-6-incubating-td4728i20.html
> > > > >
> > > > > On Wed, Jun 8, 2016 at 8:34 AM, Guillaume Alleon <
> > > > > guillaume.all...@gmail.com
> > > > > > wrote:
> > > > >
> > > > > > Ho mon
> > > > > >
> > > > > > Do we have a branch using the preview release of spark 2.0?
> > > > > >
> > > > > > Cheers
> > > > > > Guillaume
> > > > > >
> > > > > > Sent from a small device
> > > > > >
> > > > > > > On 08 Jun 2016, at 17:10, moon soo Lee 
> wrote:
> > > > > > >
> > > > > > > How about we create release branch 'branch-0.6' from master on
> 15
> > > > June,
> > > > > > > 00:00 PDT, and start release process from that point?
> > > > > > >
> > > > > > > Most of TLP migration has been done (except for git source
> repo /
> > > > > mirror
> > > > > > > migration) and we can always create minor release with spark
> 2.0
> > > > > support
> > > > > > if
> > > > > > > spark 2.0 support is not ready when we cut the release branch.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > moon
> > > > > > >
> > > > > > >> On Wed, May 25, 2016 at 1:09 PM Vinay Shukla <
> > > vinayshu...@gmail.com
> > > > >
> > > > > > wrote:
> > > > > > >>
> > > > > > >> Agree, let's make our first release as a TLP.
> > > > > > >>
> > > > > > >> On Wednesday, May 25, 2016, Felix Cheung <
> > > felixcheun...@hotmail.com
> > > > >
> > > > > > >> wrote:
> > > > > > >>
> > > > > > >>> +1 on release.If we could sort out Spark 2.0 great, if not we
> > > > should
> > > > > > have
> > > > > > >>> a release anyway.
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>
> > > > > > >>>_
> > > > > > >>> From: Alexander Bezzubov >
> > > > > > >>> Sent: Tuesday, May 24, 2016 4:44 PM
> > > > > > >>> Subject: Re: [DISCUSS] Apache Zeppelin 0.6.0 Release
> > > > > > >>> To:  >
> > > > > > >>>
> > > > > > >>>
> > > > > > >>> Thank you Moon for starting discussion,
> > > > > > >>> I can not agree more - it's time for another release, our
> first
> > > one
> > > > > as
> > > > > > >> TLP!
> > > > > > >>>
> > > > > > >>> As you said - there are many improvements, more then enough
> > for a
> > > > new
> > > > > > >>> release, but having Spark 2.0 profile there would be awesome.
> > > > > > >>>
> > > > > > >>> --
> > > > > > >>> Alex
> > > > > > >>>
> > > > > > >>> On Wed, May 25, 2016, 03:34 Luciano Resende <
> > > luckbr1...@gmail.com
> > > > > > >>> > wrote:
> > > > > > >>>
> > > > > >  On Tue, May 24, 2016 at 11:30 AM, Jonathan Kelly <
> > > > > > >> jonathaka...@gmail.com
> > > > > > >>> >
> > > > > >  wrote:
> > > > > > 
> > > > > > > Of course, but it would still be possible for Zeppelin to
> > > support
> > > > > > >> Spark
> > > > > >  2.0
> > > > > > > using a 

Re: [DISCUSS] Apache Zeppelin 0.6.0 Release

[Khalid Huseynov]

+1 on release.

On Thu, Jun 9, 2016 at 11:13 AM, Prabhjyot Singh 
wrote:

> +1 for release.
>
> And just noticed https://github.com/apache/zeppelin.
>
>
> On 9 June 2016 at 23:29, Alexander Bezzubov  wrote:
>
> > +1 for cutting a release ASAP
> >
> > And thank you Mina for volunteering to manage the next release!
> >
> > On Thu, Jun 9, 2016, 18:21 moon soo Lee  wrote:
> >
> > > +1 on dedicated release manager (thanks for volunteering, Mina!)
> > >
> > > On Thu, Jun 9, 2016 at 7:41 AM Felix Cheung  >
> > > wrote:
> > >
> > > > +1 on release branch+1 on dedicated release manager (thanks for
> > > > volunteering, Mina!)
> > > >
> > > >
> > > >
> > > > _
> > > > From: mina lee 
> > > > Sent: Wednesday, June 8, 2016 9:50 AM
> > > > Subject: Re: [DISCUSS] Apache Zeppelin 0.6.0 Release
> > > > To:  
> > > >
> > > >
> > > > Moon, I think it's good idea to cut the branch on 15 June.
> > > > As we discussed in previous release discussion thread [1], shall we
> > take
> > > a
> > > > rotation for this release?
> > > > If so, I would like to volunteer this time.
> > > >
> > > > But in the end, I think it would be better to have one dedicated
> > release
> > > > manager like other apache projects do. It takes time for every new
> > > release
> > > > manager to get familiar with apache release process, set the
> > environment,
> > > > etc. And I expect for community to be more structured at release by
> > > having
> > > > release manager who can takes more about release time, release scope.
> > > >
> > > > regards,
> > > > mina
> > > >
> > > > [1]
> > > >
> > > >
> > >
> >
> http://apache-zeppelin-dev-mailing-list.75694.x6.nabble.com/DISCUSS-Release-0-5-6-incubating-td4728i20.html
> > > >
> > > > On Wed, Jun 8, 2016 at 8:34 AM, Guillaume Alleon <
> > > > guillaume.all...@gmail.com
> > > > > wrote:
> > > >
> > > > > Ho mon
> > > > >
> > > > > Do we have a branch using the preview release of spark 2.0?
> > > > >
> > > > > Cheers
> > > > > Guillaume
> > > > >
> > > > > Sent from a small device
> > > > >
> > > > > > On 08 Jun 2016, at 17:10, moon soo Lee  wrote:
> > > > > >
> > > > > > How about we create release branch 'branch-0.6' from master on 15
> > > June,
> > > > > > 00:00 PDT, and start release process from that point?
> > > > > >
> > > > > > Most of TLP migration has been done (except for git source repo /
> > > > mirror
> > > > > > migration) and we can always create minor release with spark 2.0
> > > > support
> > > > > if
> > > > > > spark 2.0 support is not ready when we cut the release branch.
> > > > > >
> > > > > > Thanks,
> > > > > > moon
> > > > > >
> > > > > >> On Wed, May 25, 2016 at 1:09 PM Vinay Shukla <
> > vinayshu...@gmail.com
> > > >
> > > > > wrote:
> > > > > >>
> > > > > >> Agree, let's make our first release as a TLP.
> > > > > >>
> > > > > >> On Wednesday, May 25, 2016, Felix Cheung <
> > felixcheun...@hotmail.com
> > > >
> > > > > >> wrote:
> > > > > >>
> > > > > >>> +1 on release.If we could sort out Spark 2.0 great, if not we
> > > should
> > > > > have
> > > > > >>> a release anyway.
> > > > > >>>
> > > > > >>>
> > > > > >>>
> > > > > >>>_
> > > > > >>> From: Alexander Bezzubov >
> > > > > >>> Sent: Tuesday, May 24, 2016 4:44 PM
> > > > > >>> Subject: Re: [DISCUSS] Apache Zeppelin 0.6.0 Release
> > > > > >>> To:  >
> > > > > >>>
> > > > > >>>
> > > > > >>> Thank you Moon for starting discussion,
> > > > > >>> I can not agree more - it's time for another release, our first
> > one
> > > > as
> > > > > >> TLP!
> > > > > >>>
> > > > > >>> As you said - there are many improvements, more then enough
> for a
> > > new
> > > > > >>> release, but having Spark 2.0 profile there would be awesome.
> > > > > >>>
> > > > > >>> --
> > > > > >>> Alex
> > > > > >>>
> > > > > >>> On Wed, May 25, 2016, 03:34 Luciano Resende <
> > luckbr1...@gmail.com
> > > > > >>> > wrote:
> > > > > >>>
> > > > >  On Tue, May 24, 2016 at 11:30 AM, Jonathan Kelly <
> > > > > >> jonathaka...@gmail.com
> > > > > >>> >
> > > > >  wrote:
> > > > > 
> > > > > > Of course, but it would still be possible for Zeppelin to
> > support
> > > > > >> Spark
> > > > >  2.0
> > > > > > using a Maven profile, right? (Handwaving the difficulty of
> > doing
> > > > so.
> > > > > >>> I'm
> > > > > > mainly just saying that we shouldn't say, "nah, can't do it
> > > because
> > > > > >>> Spark
> > > > > > 2.0 isn't GA yet.")
> > > > > 
> > > > >  Agree.
> > > > > 
> > > > > 
> > > > > >
> > > > > > Otherwise, if Zeppelin 0.6.0 is released before Spark 2.0,
> and
> > we
> > > > > >> don't
> > > > > > make Zeppelin 0.6.0 compatible with Spark 2.0, it may be
> > several
> 

Re: [DISCUSS] Apache Zeppelin 0.6.0 Release

[Prabhjyot Singh]

+1 for release.

And just noticed https://github.com/apache/zeppelin.


On 9 June 2016 at 23:29, Alexander Bezzubov  wrote:

> +1 for cutting a release ASAP
>
> And thank you Mina for volunteering to manage the next release!
>
> On Thu, Jun 9, 2016, 18:21 moon soo Lee  wrote:
>
> > +1 on dedicated release manager (thanks for volunteering, Mina!)
> >
> > On Thu, Jun 9, 2016 at 7:41 AM Felix Cheung 
> > wrote:
> >
> > > +1 on release branch+1 on dedicated release manager (thanks for
> > > volunteering, Mina!)
> > >
> > >
> > >
> > > _
> > > From: mina lee 
> > > Sent: Wednesday, June 8, 2016 9:50 AM
> > > Subject: Re: [DISCUSS] Apache Zeppelin 0.6.0 Release
> > > To:  
> > >
> > >
> > > Moon, I think it's good idea to cut the branch on 15 June.
> > > As we discussed in previous release discussion thread [1], shall we
> take
> > a
> > > rotation for this release?
> > > If so, I would like to volunteer this time.
> > >
> > > But in the end, I think it would be better to have one dedicated
> release
> > > manager like other apache projects do. It takes time for every new
> > release
> > > manager to get familiar with apache release process, set the
> environment,
> > > etc. And I expect for community to be more structured at release by
> > having
> > > release manager who can takes more about release time, release scope.
> > >
> > > regards,
> > > mina
> > >
> > > [1]
> > >
> > >
> >
> http://apache-zeppelin-dev-mailing-list.75694.x6.nabble.com/DISCUSS-Release-0-5-6-incubating-td4728i20.html
> > >
> > > On Wed, Jun 8, 2016 at 8:34 AM, Guillaume Alleon <
> > > guillaume.all...@gmail.com
> > > > wrote:
> > >
> > > > Ho mon
> > > >
> > > > Do we have a branch using the preview release of spark 2.0?
> > > >
> > > > Cheers
> > > > Guillaume
> > > >
> > > > Sent from a small device
> > > >
> > > > > On 08 Jun 2016, at 17:10, moon soo Lee  wrote:
> > > > >
> > > > > How about we create release branch 'branch-0.6' from master on 15
> > June,
> > > > > 00:00 PDT, and start release process from that point?
> > > > >
> > > > > Most of TLP migration has been done (except for git source repo /
> > > mirror
> > > > > migration) and we can always create minor release with spark 2.0
> > > support
> > > > if
> > > > > spark 2.0 support is not ready when we cut the release branch.
> > > > >
> > > > > Thanks,
> > > > > moon
> > > > >
> > > > >> On Wed, May 25, 2016 at 1:09 PM Vinay Shukla <
> vinayshu...@gmail.com
> > >
> > > > wrote:
> > > > >>
> > > > >> Agree, let's make our first release as a TLP.
> > > > >>
> > > > >> On Wednesday, May 25, 2016, Felix Cheung <
> felixcheun...@hotmail.com
> > >
> > > > >> wrote:
> > > > >>
> > > > >>> +1 on release.If we could sort out Spark 2.0 great, if not we
> > should
> > > > have
> > > > >>> a release anyway.
> > > > >>>
> > > > >>>
> > > > >>>
> > > > >>>_
> > > > >>> From: Alexander Bezzubov >
> > > > >>> Sent: Tuesday, May 24, 2016 4:44 PM
> > > > >>> Subject: Re: [DISCUSS] Apache Zeppelin 0.6.0 Release
> > > > >>> To:  >
> > > > >>>
> > > > >>>
> > > > >>> Thank you Moon for starting discussion,
> > > > >>> I can not agree more - it's time for another release, our first
> one
> > > as
> > > > >> TLP!
> > > > >>>
> > > > >>> As you said - there are many improvements, more then enough for a
> > new
> > > > >>> release, but having Spark 2.0 profile there would be awesome.
> > > > >>>
> > > > >>> --
> > > > >>> Alex
> > > > >>>
> > > > >>> On Wed, May 25, 2016, 03:34 Luciano Resende <
> luckbr1...@gmail.com
> > > > >>> > wrote:
> > > > >>>
> > > >  On Tue, May 24, 2016 at 11:30 AM, Jonathan Kelly <
> > > > >> jonathaka...@gmail.com
> > > > >>> >
> > > >  wrote:
> > > > 
> > > > > Of course, but it would still be possible for Zeppelin to
> support
> > > > >> Spark
> > > >  2.0
> > > > > using a Maven profile, right? (Handwaving the difficulty of
> doing
> > > so.
> > > > >>> I'm
> > > > > mainly just saying that we shouldn't say, "nah, can't do it
> > because
> > > > >>> Spark
> > > > > 2.0 isn't GA yet.")
> > > > 
> > > >  Agree.
> > > > 
> > > > 
> > > > >
> > > > > Otherwise, if Zeppelin 0.6.0 is released before Spark 2.0, and
> we
> > > > >> don't
> > > > > make Zeppelin 0.6.0 compatible with Spark 2.0, it may be
> several
> > > > >> months
> > > > > after the Spark 2.0 release before the next version of Zeppelin
> > is
> > > > > releasable and supports Spark 2.0.
> > > >  I think releasing Zeppelin as a TLP will be much more easy now
> :)
> > So
> > > > >>> there
> > > >  is always the possibility to have a minor release with Spark 2.0
> > > > >> support
> > > > >>> if
> > > >  we don't get it on this one.
> > > 

Re: [DISCUSS] Apache Zeppelin 0.6.0 Release

[Alexander Bezzubov]

+1 for cutting a release ASAP

And thank you Mina for volunteering to manage the next release!

On Thu, Jun 9, 2016, 18:21 moon soo Lee  wrote:

> +1 on dedicated release manager (thanks for volunteering, Mina!)
>
> On Thu, Jun 9, 2016 at 7:41 AM Felix Cheung 
> wrote:
>
> > +1 on release branch+1 on dedicated release manager (thanks for
> > volunteering, Mina!)
> >
> >
> >
> > _
> > From: mina lee 
> > Sent: Wednesday, June 8, 2016 9:50 AM
> > Subject: Re: [DISCUSS] Apache Zeppelin 0.6.0 Release
> > To:  
> >
> >
> > Moon, I think it's good idea to cut the branch on 15 June.
> > As we discussed in previous release discussion thread [1], shall we take
> a
> > rotation for this release?
> > If so, I would like to volunteer this time.
> >
> > But in the end, I think it would be better to have one dedicated release
> > manager like other apache projects do. It takes time for every new
> release
> > manager to get familiar with apache release process, set the environment,
> > etc. And I expect for community to be more structured at release by
> having
> > release manager who can takes more about release time, release scope.
> >
> > regards,
> > mina
> >
> > [1]
> >
> >
> http://apache-zeppelin-dev-mailing-list.75694.x6.nabble.com/DISCUSS-Release-0-5-6-incubating-td4728i20.html
> >
> > On Wed, Jun 8, 2016 at 8:34 AM, Guillaume Alleon <
> > guillaume.all...@gmail.com
> > > wrote:
> >
> > > Ho mon
> > >
> > > Do we have a branch using the preview release of spark 2.0?
> > >
> > > Cheers
> > > Guillaume
> > >
> > > Sent from a small device
> > >
> > > > On 08 Jun 2016, at 17:10, moon soo Lee  wrote:
> > > >
> > > > How about we create release branch 'branch-0.6' from master on 15
> June,
> > > > 00:00 PDT, and start release process from that point?
> > > >
> > > > Most of TLP migration has been done (except for git source repo /
> > mirror
> > > > migration) and we can always create minor release with spark 2.0
> > support
> > > if
> > > > spark 2.0 support is not ready when we cut the release branch.
> > > >
> > > > Thanks,
> > > > moon
> > > >
> > > >> On Wed, May 25, 2016 at 1:09 PM Vinay Shukla  >
> > > wrote:
> > > >>
> > > >> Agree, let's make our first release as a TLP.
> > > >>
> > > >> On Wednesday, May 25, 2016, Felix Cheung  >
> > > >> wrote:
> > > >>
> > > >>> +1 on release.If we could sort out Spark 2.0 great, if not we
> should
> > > have
> > > >>> a release anyway.
> > > >>>
> > > >>>
> > > >>>
> > > >>>_
> > > >>> From: Alexander Bezzubov >
> > > >>> Sent: Tuesday, May 24, 2016 4:44 PM
> > > >>> Subject: Re: [DISCUSS] Apache Zeppelin 0.6.0 Release
> > > >>> To:  >
> > > >>>
> > > >>>
> > > >>> Thank you Moon for starting discussion,
> > > >>> I can not agree more - it's time for another release, our first one
> > as
> > > >> TLP!
> > > >>>
> > > >>> As you said - there are many improvements, more then enough for a
> new
> > > >>> release, but having Spark 2.0 profile there would be awesome.
> > > >>>
> > > >>> --
> > > >>> Alex
> > > >>>
> > > >>> On Wed, May 25, 2016, 03:34 Luciano Resende  > > >>> > wrote:
> > > >>>
> > >  On Tue, May 24, 2016 at 11:30 AM, Jonathan Kelly <
> > > >> jonathaka...@gmail.com
> > > >>> >
> > >  wrote:
> > > 
> > > > Of course, but it would still be possible for Zeppelin to support
> > > >> Spark
> > >  2.0
> > > > using a Maven profile, right? (Handwaving the difficulty of doing
> > so.
> > > >>> I'm
> > > > mainly just saying that we shouldn't say, "nah, can't do it
> because
> > > >>> Spark
> > > > 2.0 isn't GA yet.")
> > > 
> > >  Agree.
> > > 
> > > 
> > > >
> > > > Otherwise, if Zeppelin 0.6.0 is released before Spark 2.0, and we
> > > >> don't
> > > > make Zeppelin 0.6.0 compatible with Spark 2.0, it may be several
> > > >> months
> > > > after the Spark 2.0 release before the next version of Zeppelin
> is
> > > > releasable and supports Spark 2.0.
> > >  I think releasing Zeppelin as a TLP will be much more easy now :)
> So
> > > >>> there
> > >  is always the possibility to have a minor release with Spark 2.0
> > > >> support
> > > >>> if
> > >  we don't get it on this one.
> > > 
> > > 
> > > 
> > >  --
> > >  Luciano Resende
> > >  http://twitter.com/lresende1975
> > >  http://lresende.blogspot.com/
> > > >>
> > >
> >
> >
> >
> >
>

[GitHub] incubator-zeppelin issue #980: [ZEPPELIN-871] [WIP] spark 2.0 interpreter on...

[echarles]

Github user echarles commented on the issue:

https://github.com/apache/incubator-zeppelin/pull/980
  
Sure, we can wait on #747 merge.

I see there is a 
`spark/src/main/scala-2.11/org/apache/zeppelin/spark/SparkInterpreter.java`: 
does this mean that there will be 2 separate implementations: one for 2.10 et 
and for 2.11?



---
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 issue #980: [ZEPPELIN-871] [WIP] spark 2.0 interpreter on...

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/incubator-zeppelin/pull/980
  
@echarles Thanks for the contribution.

How about we divide problem into
 - scala 2.11 support
 - spark 2.0 support
 - reimplement spark interpreter in scala

@lresende is working on scala 2.11 support on #747. I'm also trying to help 
merge code for scala 2.10 and 2.11 into one via 
https://github.com/lresende/incubator-zeppelin/pull/1
One of the goal in #747 is support scala 2.11 and 2.10 from the single 
Zeppelin binary package.
Once #747 is done, this PR can take scala 2.11 support from #747.

Regarding spark 2.0 and reimplementation in scala,
How do you think about support spark 2.0 as well as spark 1.x while many 
users will use Zeppelin with spark 1.x for a some time?


---
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 issue #747: [ZEPPELIN-605][WIP] Add support for Scala 2.1...

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/incubator-zeppelin/pull/747
  
Still working in progress, created a pullrequest to this branch, 
https://github.com/lresende/incubator-zeppelin/pull/1 which is trying to merge 
2.10 and 2.11 code using reflection


---
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: [DISCUSS] Apache Zeppelin 0.6.0 Release

[moon soo Lee]

+1 on dedicated release manager (thanks for volunteering, Mina!)

On Thu, Jun 9, 2016 at 7:41 AM Felix Cheung 
wrote:

> +1 on release branch+1 on dedicated release manager (thanks for
> volunteering, Mina!)
>
>
>
> _
> From: mina lee 
> Sent: Wednesday, June 8, 2016 9:50 AM
> Subject: Re: [DISCUSS] Apache Zeppelin 0.6.0 Release
> To:  
>
>
> Moon, I think it's good idea to cut the branch on 15 June.
> As we discussed in previous release discussion thread [1], shall we take a
> rotation for this release?
> If so, I would like to volunteer this time.
>
> But in the end, I think it would be better to have one dedicated release
> manager like other apache projects do. It takes time for every new release
> manager to get familiar with apache release process, set the environment,
> etc. And I expect for community to be more structured at release by having
> release manager who can takes more about release time, release scope.
>
> regards,
> mina
>
> [1]
>
> http://apache-zeppelin-dev-mailing-list.75694.x6.nabble.com/DISCUSS-Release-0-5-6-incubating-td4728i20.html
>
> On Wed, Jun 8, 2016 at 8:34 AM, Guillaume Alleon <
> guillaume.all...@gmail.com
> > wrote:
>
> > Ho mon
> >
> > Do we have a branch using the preview release of spark 2.0?
> >
> > Cheers
> > Guillaume
> >
> > Sent from a small device
> >
> > > On 08 Jun 2016, at 17:10, moon soo Lee  wrote:
> > >
> > > How about we create release branch 'branch-0.6' from master on 15 June,
> > > 00:00 PDT, and start release process from that point?
> > >
> > > Most of TLP migration has been done (except for git source repo /
> mirror
> > > migration) and we can always create minor release with spark 2.0
> support
> > if
> > > spark 2.0 support is not ready when we cut the release branch.
> > >
> > > Thanks,
> > > moon
> > >
> > >> On Wed, May 25, 2016 at 1:09 PM Vinay Shukla 
> > wrote:
> > >>
> > >> Agree, let's make our first release as a TLP.
> > >>
> > >> On Wednesday, May 25, 2016, Felix Cheung 
> > >> wrote:
> > >>
> > >>> +1 on release.If we could sort out Spark 2.0 great, if not we should
> > have
> > >>> a release anyway.
> > >>>
> > >>>
> > >>>
> > >>>_
> > >>> From: Alexander Bezzubov >
> > >>> Sent: Tuesday, May 24, 2016 4:44 PM
> > >>> Subject: Re: [DISCUSS] Apache Zeppelin 0.6.0 Release
> > >>> To:  >
> > >>>
> > >>>
> > >>> Thank you Moon for starting discussion,
> > >>> I can not agree more - it's time for another release, our first one
> as
> > >> TLP!
> > >>>
> > >>> As you said - there are many improvements, more then enough for a new
> > >>> release, but having Spark 2.0 profile there would be awesome.
> > >>>
> > >>> --
> > >>> Alex
> > >>>
> > >>> On Wed, May 25, 2016, 03:34 Luciano Resende  > >>> > wrote:
> > >>>
> >  On Tue, May 24, 2016 at 11:30 AM, Jonathan Kelly <
> > >> jonathaka...@gmail.com
> > >>> >
> >  wrote:
> > 
> > > Of course, but it would still be possible for Zeppelin to support
> > >> Spark
> >  2.0
> > > using a Maven profile, right? (Handwaving the difficulty of doing
> so.
> > >>> I'm
> > > mainly just saying that we shouldn't say, "nah, can't do it because
> > >>> Spark
> > > 2.0 isn't GA yet.")
> > 
> >  Agree.
> > 
> > 
> > >
> > > Otherwise, if Zeppelin 0.6.0 is released before Spark 2.0, and we
> > >> don't
> > > make Zeppelin 0.6.0 compatible with Spark 2.0, it may be several
> > >> months
> > > after the Spark 2.0 release before the next version of Zeppelin is
> > > releasable and supports Spark 2.0.
> >  I think releasing Zeppelin as a TLP will be much more easy now :) So
> > >>> there
> >  is always the possibility to have a minor release with Spark 2.0
> > >> support
> > >>> if
> >  we don't get it on this one.
> > 
> > 
> > 
> >  --
> >  Luciano Resende
> >  http://twitter.com/lresende1975
> >  http://lresende.blogspot.com/
> > >>
> >
>
>
>
>

[GitHub] incubator-zeppelin pull request #974: ZEPPELIN-614 Part 1. Merge PostgresqlI...

[jongyoul]

GitHub user jongyoul reopened a pull request:

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

ZEPPELIN-614 Part 1. Merge PostgresqlInterpreter's sql completer into JDBC 
Interpreter

### What is this PR for?
Supporting Sql completer into JDBC Interpreter which is merged by the 
function of Postgresql Interpreter. And this is the first step to merge 
Postgresql into generic JDBC Interpreter

### What type of PR is it?
[Improvement]

### Todos
* [x] - Adopted the function of auto completion

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

### How should this be tested?

### Screenshots (if appropriate)
https://cloud.githubusercontent.com/assets/3612566/15884224/e241f6b4-2d89-11e6-9746-8c8951ef6708.png;>
https://cloud.githubusercontent.com/assets/3612566/15884229/e7993e24-2d89-11e6-9f5b-018e6eac7f6a.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/jongyoul/incubator-zeppelin ZEPPELIN-614

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

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


commit 6491cba0d319a7f520fae10c820a9d233d3e593c
Author: Jongyoul Lee 
Date:   2016-06-08T05:50:18Z

Added auto completion from PostgresqlInterpreter

commit e49f73c3b03310351ba525d956d1c10de0185cf3
Author: Jongyoul Lee 
Date:   2016-06-08T05:54:54Z

Updated original documentation

commit d4823957bc784ede3d926eb844bcecabba4dbbd5
Author: Jongyoul Lee 
Date:   2016-06-09T13:58:56Z

Fixed typo and coding style

commit 99ce452b68c757c1959b9d4b7983f7d81000256e
Author: Jongyoul Lee 
Date:   2016-06-09T14:13:21Z

Updated license document

commit 998352c4e746c1e97f49487d176aa84d1abf79ce
Author: Jongyoul Lee 
Date:   2016-06-09T14:17:24Z

Fixed old styles




---
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 #974: ZEPPELIN-614 Part 1. Merge PostgresqlI...

[jongyoul]

Github user jongyoul closed the pull request at:

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


---
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 #917: [ZEPPELIN-840] Scalding interpreter th...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #982: ZEPPELIN-934 Merge Phoenix interpreter...

[jongyoul]

GitHub user jongyoul opened a pull request:

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

ZEPPELIN-934 Merge Phoenix interpreter into JDBC interpreter

### What is this PR for?
Removing Phoenix interpreter and adding example for using it through JDBC

### What type of PR is it?
[Feature]

### Todos
* [x] - Merge it into JDBC

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

### 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/jongyoul/incubator-zeppelin ZEPPELIN-934

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

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


commit ffcb2da364f271ecf9d6e04022576e5a49d7fc1e
Author: Jongyoul Lee 
Date:   2016-06-09T15:48:29Z

- Removed Phoenix Interpreter
- Updated example for using Apache Phoenix




---
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 #974: ZEPPELIN-614 Part 1. Merge PostgresqlI...

[jongyoul]

GitHub user jongyoul reopened a pull request:

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

ZEPPELIN-614 Part 1. Merge PostgresqlInterpreter's sql completer into JDBC 
Interpreter

### What is this PR for?
Supporting Sql completer into JDBC Interpreter which is merged by the 
function of Postgresql Interpreter. And this is the first step to merge 
Postgresql into generic JDBC Interpreter

### What type of PR is it?
[Improvement]

### Todos
* [x] - Adopted the function of auto completion

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

### How should this be tested?

### Screenshots (if appropriate)
https://cloud.githubusercontent.com/assets/3612566/15884224/e241f6b4-2d89-11e6-9746-8c8951ef6708.png;>
https://cloud.githubusercontent.com/assets/3612566/15884229/e7993e24-2d89-11e6-9f5b-018e6eac7f6a.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/jongyoul/incubator-zeppelin ZEPPELIN-614

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

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


commit 6491cba0d319a7f520fae10c820a9d233d3e593c
Author: Jongyoul Lee 
Date:   2016-06-08T05:50:18Z

Added auto completion from PostgresqlInterpreter

commit e49f73c3b03310351ba525d956d1c10de0185cf3
Author: Jongyoul Lee 
Date:   2016-06-08T05:54:54Z

Updated original documentation

commit d4823957bc784ede3d926eb844bcecabba4dbbd5
Author: Jongyoul Lee 
Date:   2016-06-09T13:58:56Z

Fixed typo and coding style

commit 99ce452b68c757c1959b9d4b7983f7d81000256e
Author: Jongyoul Lee 
Date:   2016-06-09T14:13:21Z

Updated license document

commit 998352c4e746c1e97f49487d176aa84d1abf79ce
Author: Jongyoul Lee 
Date:   2016-06-09T14:17:24Z

Fixed old styles




---
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 #974: ZEPPELIN-614 Part 1. Merge PostgresqlI...

[jongyoul]

Github user jongyoul closed the pull request at:

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


---
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 #981: ZEPPELIN-925 Part 2. Merge Hive Interp...

[jongyoul]

GitHub user jongyoul opened a pull request:

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

ZEPPELIN-925 Part 2. Merge Hive Interpreter into JDBC

### What is this PR for?
Fixed some wrong documentation and settings. This is minor issue.

### What type of PR is it?
[Feature | Documentation]

### Todos
* [x] - Remove settings about Hive and documentation

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

### 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/jongyoul/incubator-zeppelin ZEPPELIN-925-1

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

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


commit eab4338613cdd103a2fe27a29ff432e5567d7180
Author: Jongyoul Lee 
Date:   2016-06-09T14:50:18Z

Removed unused settings and description




---
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 issue #919: support changing tabsize of paragraph

[astroshim]

Github user astroshim commented on the issue:

https://github.com/apache/incubator-zeppelin/pull/919
  
@corneadoug Thank you for your concern! I'm thinking to find right way how 
to handle this issue.


---
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: [DISCUSS] Apache Zeppelin 0.6.0 Release

[Felix Cheung]

+1 on release branch+1 on dedicated release manager (thanks for volunteering, 
Mina!)



_
From: mina lee 
Sent: Wednesday, June 8, 2016 9:50 AM
Subject: Re: [DISCUSS] Apache Zeppelin 0.6.0 Release
To:  


Moon, I think it's good idea to cut the branch on 15 June.
As we discussed in previous release discussion thread [1], shall we take a
rotation for this release?
If so, I would like to volunteer this time.

But in the end, I think it would be better to have one dedicated release
manager like other apache projects do. It takes time for every new release
manager to get familiar with apache release process, set the environment,
etc. And I expect for community to be more structured at release by having
release manager who can takes more about release time, release scope.

regards,
mina

[1]
http://apache-zeppelin-dev-mailing-list.75694.x6.nabble.com/DISCUSS-Release-0-5-6-incubating-td4728i20.html

On Wed, Jun 8, 2016 at 8:34 AM, Guillaume Alleon  wrote:

> Ho mon
>
> Do we have a branch using the preview release of spark 2.0?
>
> Cheers
> Guillaume
>
> Sent from a small device
>
> > On 08 Jun 2016, at 17:10, moon soo Lee  wrote:
> >
> > How about we create release branch 'branch-0.6' from master on 15 June,
> > 00:00 PDT, and start release process from that point?
> >
> > Most of TLP migration has been done (except for git source repo / mirror
> > migration) and we can always create minor release with spark 2.0 support
> if
> > spark 2.0 support is not ready when we cut the release branch.
> >
> > Thanks,
> > moon
> >
> >> On Wed, May 25, 2016 at 1:09 PM Vinay Shukla 
> wrote:
> >>
> >> Agree, let's make our first release as a TLP.
> >>
> >> On Wednesday, May 25, 2016, Felix Cheung 
> >> wrote:
> >>
> >>> +1 on release.If we could sort out Spark 2.0 great, if not we should
> have
> >>> a release anyway.
> >>>
> >>>
> >>>
> >>>    _
> >>> From: Alexander Bezzubov >
> >>> Sent: Tuesday, May 24, 2016 4:44 PM
> >>> Subject: Re: [DISCUSS] Apache Zeppelin 0.6.0 Release
> >>> To:  >
> >>>
> >>>
> >>> Thank you Moon for starting discussion,
> >>> I can not agree more - it's time for another release, our first one as
> >> TLP!
> >>>
> >>> As you said - there are many improvements, more then enough for a new
> >>> release, but having Spark 2.0 profile there would be awesome.
> >>>
> >>> --
> >>> Alex
> >>>
> >>> On Wed, May 25, 2016, 03:34 Luciano Resende  >>> > wrote:
> >>>
>  On Tue, May 24, 2016 at 11:30 AM, Jonathan Kelly <
> >> jonathaka...@gmail.com
> >>> >
>  wrote:
> 
> > Of course, but it would still be possible for Zeppelin to support
> >> Spark
>  2.0
> > using a Maven profile, right? (Handwaving the difficulty of doing so.
> >>> I'm
> > mainly just saying that we shouldn't say, "nah, can't do it because
> >>> Spark
> > 2.0 isn't GA yet.")
> 
>  Agree.
> 
> 
> >
> > Otherwise, if Zeppelin 0.6.0 is released before Spark 2.0, and we
> >> don't
> > make Zeppelin 0.6.0 compatible with Spark 2.0, it may be several
> >> months
> > after the Spark 2.0 release before the next version of Zeppelin is
> > releasable and supports Spark 2.0.
>  I think releasing Zeppelin as a TLP will be much more easy now :) So
> >>> there
>  is always the possibility to have a minor release with Spark 2.0
> >> support
> >>> if
>  we don't get it on this one.
> 
> 
> 
>  --
>  Luciano Resende
>  http://twitter.com/lresende1975
>  http://lresende.blogspot.com/
> >>
>

[GitHub] incubator-zeppelin pull request #980: [ZEPPELIN-871] [WIP] spark 2.0 interpr...

[echarles]

GitHub user echarles opened a pull request:

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

[ZEPPELIN-871] [WIP] spark 2.0 interpreter on scala 2.11

### What is this PR for?
Spark interpreter for spark version 2.0.0 and scala 2.11 (implemented in 
Scala)

### What type of PR is it?
[Feature]

### Todos
* [ ] - Clean code
* [ ] - Test SQL
* [ ] - Test Python
* [ ] - Test R


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

### How should this be tested?
Build it with 
```
mvn install   -Pscala-2.11 -Dscala.binary.version=2.11 
-Dscala.version=2.11.8   -Pspark-2.0 -Dspark.version=2.0.0-SNAPSHOT   
-Phadoop-2.6 -Dhadoop.version=2.7.2 -Pyarn   -Dmaven.findbugs.enable=false   
-Drat.skip=true   -Ppyspark   -Psparkr   -Dcheckstyle.skip=true   
-Dcobertura.skip=true   -Pbuild-distr   -pl 
'!alluxio,!cassandra,!elasticsearch,!file,!flink,!hbase,!hive,!ignite,!jdbc,!kylin,!lens,!phoenix,!postgresql,!tajo'
   -DskipTests
```
Run and test the spark paragraph.

### Screenshots (if appropriate)

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


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

$ git pull https://github.com/datalayer/zeppelin-datalayer spark-2.0

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

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


commit f041ec3e4b524594a2a32692c5418e04f7335323
Author: Eric Charles 
Date:   2016-06-09T14:31:50Z

Initial implemenation for spark 2.0 interpreter on scala 2.11




---
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 issue #974: ZEPPELIN-614 Part 1. Merge PostgresqlInterpre...

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/incubator-zeppelin/pull/974
  
@bzz I updated license files. could you please check it again?


https://github.com/apache/incubator-zeppelin/pull/974/commits/99ce452b68c757c1959b9d4b7983f7d81000256e


---
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 #943: ZEPPELIN-925 Merge HiveInterpreter int...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #979: Alert message when trying to delete la...

[astroshim]

GitHub user astroshim opened a pull request:

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

Alert message when trying to delete last paragraph.

### What is this PR for?
This PR is for giving proper information to users and blocking unnecessary 
communication with zeppelin server when trying to delete last paragraph because 
the last paragraph can't be deleted.


### What type of PR is it?
Improvement 


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


### How should this be tested?
You can try to remove last paragraph of a notebook.


### Screenshots (if appropriate)

![image](https://cloud.githubusercontent.com/assets/3348133/15929252/0edaa6d2-2e87-11e6-9baa-8f2b5f63d592.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/astroshim/incubator-zeppelin ZEPPELIN-979

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

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


commit faa7067c9db8bf34cceaac08d46d42bdda24cd8f
Author: astroshim 
Date:   2016-06-09T12:03:17Z

alert message when trying to delete last paragraph.




---
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 #908: ZEPPELIN-598 ] Dynamic loading for Int...

[cloverhearts]

Github user cloverhearts closed the pull request at:

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


---
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 #908: ZEPPELIN-598 ] Dynamic loading for Int...

[cloverhearts]

GitHub user cloverhearts reopened a pull request:

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

ZEPPELIN-598 ] Dynamic loading for Interpreter and API

### What is this PR for?
Use of external libraries that are included in the Roadmap,
The interpreter needs related to dynamic loading capabilities.


### What type of PR is it?
Feature

### Todos
* [x] - Dynamic load
* [x] - make api
* [x] - Modified according to feedback 
(https://github.com/apache/incubator-zeppelin/pull/631)

### ScreenShots

![markdown_test](https://cloud.githubusercontent.com/assets/10525473/15452508/d786f276-202b-11e6-95e5-0e2b898cb6c7.gif)


### Is there a relevant Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-598

### How should this be tested?
By annotating the interpreter setting items below, try using the 
loadDynamicInterpreter method.
Or create a new interpreter loads created in the local Maven repository.

Step 1.
markdown interpreter to local distribute
```
mvn install -pl 
'!spark-dependencies,!spark,!flink,!ignite,!lens,!hive,!phoenix,!postgresql,!tajo,!cassandra,!kylin,!elasticsearch,!zeppelin-distribution'
 -DskipTests
```
Step 2.
Comment out the markdown

incubator-zeppelin/zeppelin-zengine/src/main/java/org/apache/zeppelin/conf/ZeppelinConfiguration.java
``` java 
ZEPPELIN_INTERPRETERS("zeppelin.interpreters", 
"org.apache.zeppelin.spark.SparkInterpreter,"
+ "org.apache.zeppelin.spark.PySparkInterpreter,"
+ "org.apache.zeppelin.spark.SparkSqlInterpreter,"
+ "org.apache.zeppelin.spark.DepInterpreter,"
// + "org.apache.zeppelin.markdown.Markdown,"
...
```
Step 3.
and build.
For example.
```
mvn clean package -Pspark-1.6 -Phadoop-2.4 -Pyarn -Ppyspark -DskipTests
```
Step 4.
remove to interpreter/md
```
rm -rf interpreter/md
```
option.
fixed conf/zeppelin-env.sh(cmd) download interpreter directory.
```
export ZEPPELIN_INTERPRETER_DOWNLOAD_DIR=MyZeppelinInterpreter
```
Step 5.
and API Call (load interpreter) example load markdown 
```
Content-Type: application/json
```

```
POST http://127.0.0.1:8080/api/interpreter/load/md/markdown
{
  "artifact": 
"org.apache.zeppelin:zeppelin-markdown:0.6.0-incubating-SNAPSHOT",
  "className": "org.apache.zeppelin.markdown.Markdown",
  "repository": {
"url": "http://dl.bintray.com/spark-packages/maven;,
"snapshot" : true
  }
}
```

Step 6. 
In interperter menu for zeppelin web, you can new setting information for 
md.

### 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/cloverhearts/incubator-zeppelin 
feat/ZEPPELIN-598

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

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


commit 3d0a9d4c3781dce264b186aa862d8dddeb52518d
Author: CloverHearts 
Date:   2016-05-22T05:42:48Z

Implement feat. dynamic load interpreter class

commit 599639fb0ced60e26807e9f771fe8f127945596c
Author: CloverHearts 
Date:   2016-05-23T05:17:49Z

fixed invalid result for dynamic interpreter

commit 1b598b7c0ba52d8a2a639ea65d735d92b6486f5c
Author: CloverHearts 
Date:   2016-06-04T14:47:27Z

Merge branch 'master' into feat/ZEPPELIN-598

Conflicts:
conf/zeppelin-env.cmd.template
conf/zeppelin-env.sh.template

commit 3965f740787a7acd5a6219c5228fa3fdc2109c76
Author: CloverHearts 
Date:   2016-06-04T13:49:52Z

add config in zeppelin env - dynamic interperter

commit 1bb3a0c138e38e602ed487fa59075c557687df62
Author: CloverHearts 
Date:   2016-06-04T14:05:46Z

add path for interpreter download path at doc/install/install.md

commit 377393aad7a36c919b8f86875f7aac30708e14ab
Author: CloverHearts 
Date:   2016-06-04T14:23:25Z

add interpreter download dir for zeppelin-site.xml.template

commit 43ad199a348f009915891d133dc832e10d700a03
Author: CloverHearts 
Date:   2016-06-08T02:20:06Z

Merge branch 'master' into feat/ZEPPELIN-598

commit 04d84d30ff57cb2c8d1c63e95233e2ffa3eae4f8
Author: CloverHearts 
Date:   2016-06-09T05:53:55Z

add exception for dynamic loading

commit b10b64d557ab68cda8ce352be16bd8740117fd15
Author: CloverHearts 

[GitHub] incubator-zeppelin issue #966: [ZEPPELIN-958] Support syntax highlight for p...

[bzz]

Github user bzz commented on the issue:

https://github.com/apache/incubator-zeppelin/pull/966
  
Merging if there is no further discussion


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have 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 issue #971: [ZEPPELIN-961] Longer names to the notebook m...

[sagarkulkarni3592]

Github user sagarkulkarni3592 commented on the issue:

https://github.com/apache/incubator-zeppelin/pull/971
  
@minahlee Thank you for that suggestion.
What if we push all the buttons to the new div present on next line, like :
![screen shot 2016-06-09 at 3 44 20 
pm](https://cloud.githubusercontent.com/assets/12127192/15926332/199afe9c-2e59-11e6-9dc0-350497576c43.png)
This will change the look.
If not, then we could adjust the shown name size.



---
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 issue #978: [ZEPPELIN-869] Search notebook to handle empt...

[bzz]

Github user bzz commented on the issue:

https://github.com/apache/incubator-zeppelin/pull/978
  
@ravicodder thank you for improvement!

\cc @felizbear as original author of search frontend for a 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] incubator-zeppelin pull request #978: [ZEPPELIN-869] Search notebook to hand...

[ravicodder]

GitHub user ravicodder opened a pull request:

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

[ZEPPELIN-869] Search notebook to handle empty result.

### What is this PR for?
Search notebook to handle empty result.

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


### What is the Jira issue?

[ZEPPELIN-869](https://issues.apache.org/jira/browse/ZEPPELIN-869?jql=project%20%3D%20ZEPPELIN%20AND%20text%20~%20%22empty%22)

### How should this be tested?
1. Try to search something which should return empty result, you should get 
proper message for that.
2. search box should get cleared when clicked on any other link.



### Screenshots (if appropriate)
Before:
![screen shot 2016-06-09 at 3 44 53 
pm](https://cloud.githubusercontent.com/assets/7026661/15926338/25f8924e-2e59-11e6-8c10-2dd9542f5258.png)

After:
![screen shot 2016-06-09 at 3 34 47 
pm](https://cloud.githubusercontent.com/assets/7026661/15926303/f1412d7c-2e58-11e6-9dd3-1ecccb938a26.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/ravicodder/incubator-zeppelin ZEPPELIN-869

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

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


commit 152efbba3093f93fcc41cd386bd7907cd10fdb65
Author: Ravi Ranjan 
Date:   2016-06-09T10:08:26Z

Handle empty search




---
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 issue #974: ZEPPELIN-614 Part 1. Merge PostgresqlInterpre...

[bzz]

Github user bzz commented on the issue:

https://github.com/apache/incubator-zeppelin/pull/974
  
Great work @jongyoul ! 

Looks good to me except minor things listed above


---
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-978) grunt build fails

[shruti (JIRA)]

shruti created ZEPPELIN-978:
---

 Summary: grunt build fails 
 Key: ZEPPELIN-978
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-978
 Project: Zeppelin
  Issue Type: Bug
 Environment: linux AMI of aws instance
Reporter: shruti
Priority: Blocker






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

[GitHub] incubator-zeppelin issue #966: [ZEPPELIN-958] Support syntax highlight for p...

[bzz]

Github user bzz commented on the issue:

https://github.com/apache/incubator-zeppelin/pull/966
  
Looks great to me, let's merge as a short term solution. 

And yes, as @felixcheung mentioned - in a mid\long term, it would be great 
for interpreter to encapsulate this knowledge!


---
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 issue #977: [ZEPPELIN-911] Apply new mechanism to FlinkIn...

[bzz]

Github user bzz commented on the issue:

https://github.com/apache/incubator-zeppelin/pull/977
  
Looks great to me, @rerngvit thank you for contribution!
Have update JIRA issues assignment.


---
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 issue #947: [ZEPPELIN-939] Improve notebook authorization...

[corneadoug]

Github user corneadoug commented on the issue:

https://github.com/apache/incubator-zeppelin/pull/947
  
No problem of rendering with the new "theme"
Merging if there is 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 issue #973: [ZEPPELIN-973, ZEPPELIN-954] Table rendering ...

[corneadoug]

Github user corneadoug commented on the issue:

https://github.com/apache/incubator-zeppelin/pull/973
  
@jasonxh I can't find you somehow on the JIRA user id.
Could you give it 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.
---

[GitHub] incubator-zeppelin pull request #973: [ZEPPELIN-973, ZEPPELIN-954] Table ren...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 issue #955: [ZEPPELIN-940] Allow zeppelin server to conne...

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/incubator-zeppelin/pull/955
  
@Leemoonsoo Who's proper reviewer for UI part?


---
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 issue #975: [ZEPPELIN-975] Move download data button outs...

[corneadoug]

Github user corneadoug commented on the issue:

https://github.com/apache/incubator-zeppelin/pull/975
  
Merging if there is no more discussion


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have 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 issue #977: [ZEPPELIN-911] Apply new mechanism to FlinkIn...

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/incubator-zeppelin/pull/977
  
I've tested it and worked well. LGTM. Merging if there's no more 
discussion. @rerngvit Could you please your jira id? I cannot assign you as a 
contributor


---
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 #817: [ZEPPELIN-792]Misspelt words and Wrong...

[zuny25]

Github user zuny25 closed the pull request at:

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


---
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 #817: [ZEPPELIN-792]Misspelt words and Wrong...

[zuny25]

GitHub user zuny25 reopened a pull request:

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

[ZEPPELIN-792]Misspelt words and Wrong method parameters

### What is this PR for?
Fix misspelt words and wrong method parameter on zeppelin-interpreter
https://issues.apache.org/jira/browse/ZEPPELIN-792


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

### Todos
 * [x] - Fix misspelt variable
 * [x] - Fix wrong method parameter

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

### How should this be tested?
 1. Edit Interpreter dep package
 2. Run DependencyResolverTest

### 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/zuny25/incubator-zeppelin 
feature/InterpreterDependency

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

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


commit d1e6da31a9b32d4124bb51d36911b13f61dc71d5
Author: Rusty Phillips 
Date:   2016-04-06T02:13:45Z

errata
classpathFlter -> classpathFilter

commit d174f1c0346cd9a445d2907bc6c5d774dfdc98de
Author: haden.kim 
Date:   2016-04-06T02:18:36Z

Method Usage Fix

org.sonatype.aether/aether-api/1.12 / 
org.sonatype.aether.repository.RemoteRepository
public RemoteRepository setPolicy( boolena snapshot, RepositoryPolicy 
policy)

org.sonatype.aether/aether-api/1.12 / 
org.sonatype.aether.repository.RepositoryPolicy
public More ...RepositoryPolicy( boolean enabled, String updatePolicy, 
String checksumPolicy )

I think two paraemter have to changed its position




---
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 issue #908: ZEPPELIN-598 ] Dynamic loading for Interprete...

[cloverhearts]

Github user cloverhearts commented on the issue:

https://github.com/apache/incubator-zeppelin/pull/908
  
Merge master branch into 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 issue #955: [ZEPPELIN-940] Allow zeppelin server to conne...

[SachinJanani]

Github user SachinJanani commented on the issue:

https://github.com/apache/incubator-zeppelin/pull/955
  
@jongyoul Yes you are right.But this changes will allow user to connect to 
existing remote process instead of zeppelin running the interpreter.I think we 
should create a separate jira for starting zeppelin interpreter on different 
machine.


---
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 #975: [ZEPPELIN-975] Move download data butt...

[corneadoug]

Github user corneadoug closed the pull request at:

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


---
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 issue #904: [ZEPPELIN-835]Don't persist authentication in...

[corneadoug]

Github user corneadoug commented on the issue:

https://github.com/apache/incubator-zeppelin/pull/904
  
@mwkang It's fine, we can always reopen it if necessary. Just wanted 
@Leemoonsoo go to close it since he was the one to report it


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes 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 #946: ZEPPELIN-937 : broken layout of Interp...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 issue #904: [ZEPPELIN-835]Don't persist authentication in...

[mwkang]

Github user mwkang commented on the issue:

https://github.com/apache/incubator-zeppelin/pull/904
  
Oh.. I closed JIRA issue.
I am so sorry that I act at my discretion.


---
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 issue #904: [ZEPPELIN-835]Don't persist authentication in...

[corneadoug]

Github user corneadoug commented on the issue:

https://github.com/apache/incubator-zeppelin/pull/904
  
@Leemoonsoo Can we close this JIRA issue then? 
https://issues.apache.org/jira/browse/ZEPPELIN-835


---
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 issue #955: [ZEPPELIN-940] Allow zeppelin server to conne...

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/incubator-zeppelin/pull/955
  
@SachinJanani Thanks for sharing. I also think we should consider running 
Zeppelin's interpreters in a different machine. This would be a starting point 
to do 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 issue #904: [ZEPPELIN-835]Don't persist authentication in...

[mwkang]

Github user mwkang commented on the issue:

https://github.com/apache/incubator-zeppelin/pull/904
  
Related PR: https://github.com/apache/incubator-zeppelin/pull/860
Related Issue: https://issues.apache.org/jira/browse/ZEPPELIN-828


---
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 #904: [ZEPPELIN-835]Don't persist authentica...

[mwkang]

Github user mwkang closed the pull request at:

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


---
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 issue #904: [ZEPPELIN-835]Don't persist authentication in...

[mwkang]

Github user mwkang commented on the issue:

https://github.com/apache/incubator-zeppelin/pull/904
  
While I rebase this PR, I found this issue was been resolved 
[AuthenticationInfo in master].
So I closed PR.

[AuthenticationInfo in master]: 
https://github.com/apache/incubator-zeppelin/blob/master/zeppelin-zengine/src/main/java/org/apache/zeppelin/notebook/Paragraph.java#L53


---
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 issue #955: [ZEPPELIN-940] Allow zeppelin server to conne...

[SachinJanani]

Github user SachinJanani commented on the issue:

https://github.com/apache/incubator-zeppelin/pull/955
  
@jongyoul There can be scenarios where user is starting RemoteInterpreter 
embedded in his service by calling
`RemoteInterpreterServer server = new RemoteInterpreterServer(port)
server.start()` 
So this changes will help user to specify the host and port on which 
interpreter is executing and zeppelin will connect to that interpreter.This 
changes will also be helpful when 
ClusterManager(https://cwiki.apache.org/confluence/display/ZEPPELIN/Cluster+Manager+Proposal)
 will be implemented.We are starting ZeppelinInterpreter on remote host along 
with our service.
You are right that when we stop Zeppelin all interpreter will be stop but 
it can be handled by overriding the RemoteInterpreterServer


---
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 issue #955: [ZEPPELIN-940] Allow zeppelin server to conne...

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/incubator-zeppelin/pull/955
  
That failure is related to 
https://issues.apache.org/jira/browse/ZEPPELIN-878, but I have a question. What 
kind of procedure do you do while you run Zeppelin? Generally, when you stop 
Zeppelin, all interpreters also stop. Could you please share your cases? This 
PR will work, but because Zeppelin's interpreter will not be started by itself 
yet.


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