[jira] [Created] (ZEPPELIN-1184) why should cloned paragraph keep the original paragraph id when

[jacquesqiao (JIRA)]

jacquesqiao created ZEPPELIN-1184:
-

 Summary: why should cloned paragraph keep the original paragraph 
id when 
 Key: ZEPPELIN-1184
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1184
 Project: Zeppelin
  Issue Type: Bug
  Components: zeppelin-zengine
Affects Versions: 0.6.1, 0.7.0
Reporter: jacquesqiao


in Note.java  addCloneParagraph use the original paragraph id to build a new 
paragraph, what is the reason for this?

public void addCloneParagraph(Paragraph srcParagraph) {

// Keep paragraph original ID
final Paragraph newParagraph = new Paragraph(srcParagraph.getId(), this, 
this, factory);
...



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

[GitHub] zeppelin pull request #1185: Redirect home when requested a wrong notename p...

[astroshim]

GitHub user astroshim reopened a pull request:

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

Redirect home when requested a wrong notename path.

### What is this PR for?
This PR for redirecting to zeppelin home when requested wrong path.


### What type of PR is it?
Improvement


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


### How should this be tested?
put wrong path to your browser like screenshot.


### Screenshots (if appropriate)
- before

![b1](https://cloud.githubusercontent.com/assets/3348133/16835556/3b744224-49f4-11e6-84bf-6a22cc729a30.gif)

- after

![a](https://cloud.githubusercontent.com/assets/3348133/16835627/8cc590e2-49f4-11e6-878f-745ee026ef8e.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/astroshim/zeppelin feat/redirectHome

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

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


commit 8db7017742f9b579c5fe2c09ce827d1c258d5ecd
Author: astroshim 
Date:   2016-07-14T09:41:04Z

redirect home when wrong path

commit c937b90bccdc2f13877993684e637c9078859b50
Author: astroshim 
Date:   2016-07-15T03:44:20Z

fix location.path

commit eae453f5c02a990c8c92418c5b30ebffe6c7df7d
Author: astroshim 
Date:   2016-07-15T03:45:55Z

fix path




---
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 #1170: BigQuery Interpreter for Apazhe Zeppelin[ZEPPELIN-1153...

[babupe]

Github user babupe commented on the issue:

https://github.com/apache/zeppelin/pull/1170
  
Hi,

1. I have added unit tests, but the tests will work with a valid google 
project id on google compute, else it will fail. This is because the test has 
to run against the bigquery service which does not have a local build.
2. I have added a server side cancel operation. However I could not find a 
viable method to report progress. Will implement this if this becomes available 
as part of big query API in the future.
3. Implemented dynamic interpreter
4. Added BigQuery API license to the license file
5. Docs updated with BigQuery information.
6. Exceptions implemented at appropriate places.

Thanks!


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin pull request #1188: [ZEPPELIN-1183] Replace $window.location by $lo...

[corneadoug]

GitHub user corneadoug opened a pull request:

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

[ZEPPELIN-1183] Replace $window.location by $location

### What is this PR for?
There is a native service used across the app to take care of re-routing to 
different page: `$location`, however there has been a few times where 
`$window.location` is used instead, and people tend to do it in new PR too.

This convert the `$window.location` from the code to use `$location`.

Only one was kept in `app.controller.js` for Iframe, so it doesn't flicker.


### What type of PR is it?
Refactoring

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

### How should this be tested?
You can try to reproduce the couple of cases that redirection is needed,
but overall there shouldn't be any issue from that change.

### 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/corneadoug/incubator-zeppelin ZEPPELIN-1183

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

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


commit 60cd3271e9edcfb4d099cda34fcf7573be5f1837
Author: Damien CORNEAU 
Date:   2016-07-15T03:42:01Z

Remove the window.location from the code, for




---
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-1183) Remove the use of $windows.location for redirection

[CORNEAU Damien (JIRA)]

CORNEAU Damien created ZEPPELIN-1183:


 Summary: Remove the use of $windows.location for redirection
 Key: ZEPPELIN-1183
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1183
 Project: Zeppelin
  Issue Type: Improvement
Reporter: CORNEAU Damien
Assignee: CORNEAU Damien
 Fix For: 0.7.0


There is a few call to $windows.location to redirect the user to a different 
page.
However we already have a native service that we are using in the app to take 
care of that: $location.



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

[jira] [Created] (ZEPPELIN-1182) Zeppelin should have Startup and Shutdown message

[Yesha Vora (JIRA)]

Yesha Vora created ZEPPELIN-1182:


 Summary: Zeppelin should have Startup and Shutdown message
 Key: ZEPPELIN-1182
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1182
 Project: Zeppelin
  Issue Type: Improvement
  Components: zeppelin-server
Affects Versions: 0.6.0
Reporter: Yesha Vora


Zeppelin log should have startup message and shutdown message. 
Startup message should include details like Zeppelin version, hash number, host 
,classpath, etc.
Currently, zeppelin logs do not have startup and shutdown messages. Lack of 
startup / shutdown message makes debugging harder via logs. Its hard to find 
zeppelin version related information from logs and  also hard to find zeppelin 
restart from logs.




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

[GitHub] zeppelin issue #1185: Redirect home when requested a wrong notename path.

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/1185
  
@astroshim Right. And agree with @felixcheung. Let do that in separate PR 
then :)


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #1182: ZEPPELIN-1170 Handsontable fails to display data on se...

[corneadoug]

Github user corneadoug commented on the issue:

https://github.com/apache/zeppelin/pull/1182
  
Tested, LGTM


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin pull request #1172: [Zeppelin-1161] Revert precise execution time

[corneadoug]

GitHub user corneadoug reopened a pull request:

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

[Zeppelin-1161] Revert precise execution time

### What is this PR for?
It had been pointed out in the mailing list that after 
https://github.com/apache/zeppelin/pull/862, the execution time was changed to 
humanized fashion, while we would want to keep something more precise in that 
case.

This PR is rolling back to the old precise time for execution time.


### What type of PR is it?
Improvement

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

### How should this be tested?
Run a paragraph, after it is finished, it should show: `Took x seconds.` 
instead of `Took a few seconds` (or Hours, Minutes, Sec)

### Screenshot
![screen shot 2016-07-13 at 2 19 45 
pm](https://cloud.githubusercontent.com/assets/710411/16792626/0ff3ccb8-4905-11e6-89b6-a202944d66b8.png)

### Questions:
* Does the licenses files need update? Yes
* 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/corneadoug/incubator-zeppelin ZEPPELIN-1161

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

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


commit c845e90f925425ad192b4b95fc236c6271b56209
Author: Damien CORNEAU 
Date:   2016-07-13T02:27:03Z

Revert seconds ago for execution time

commit 7a2cf8ae7f7fb8e81b128bc3216b806357bfbd8f
Author: Damien CORNEAU 
Date:   2016-07-13T02:30:24Z

Fix jxcs

commit a140565a47588d21c9ff98fefa3a71423d88d981
Author: Damien CORNEAU 
Date:   2016-07-13T05:20:33Z

add moment plugin for duration

commit 243e823b0af30846976ec15147ff78a60dfab461
Author: Damien CORNEAU 
Date:   2016-07-13T06:28:12Z

Fix jscs errors

commit 77ef3f6b28d4457fa3f5b4bd6a03cf5c7710f7cf
Author: Damien CORNEAU 
Date:   2016-07-14T02:29:55Z

Add licence of new dependency




---
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 #1186: [ZEPPELIN-1179] Append scala version to maven artifact...

[lresende]

Github user lresende commented on the issue:

https://github.com/apache/zeppelin/pull/1186
  
This assumes that #747 is merged.


---
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 #1186: [ZEPPELIN-1179] Append scala version to maven a...

[lresende]

GitHub user lresende opened a pull request:

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

[ZEPPELIN-1179] Append scala version to maven artifacts

### What is this PR for?
Now that we have support for both Scala 2.10 and 2.11 we need to append 
Scala version to the maven artifact id in order to properly publish artifacts 
for both Scala releases. 

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

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


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

$ git pull https://github.com/lresende/incubator-zeppelin scala-version

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

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


commit f6da160b7b323d74703b41b498c82036c107b55f
Author: Luciano Resende 
Date:   2016-07-15T00:18:53Z

[ZEPPELIN-1179] Append scala version to maven artifacts




---
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 #1185: Redirect home when requested a wrong notename path.

[felixcheung]

Github user felixcheung commented on the issue:

https://github.com/apache/zeppelin/pull/1185
  
+1 for 404 - maybe useful but could be a separate 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.
---

[jira] [Created] (ZEPPELIN-1179) Prefix pom artifacts with scala version prefix

[Luciano Resende (JIRA)]

Luciano Resende created ZEPPELIN-1179:
-

 Summary: Prefix pom artifacts with scala version prefix
 Key: ZEPPELIN-1179
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1179
 Project: Zeppelin
  Issue Type: Bug
  Components: build
Reporter: Luciano Resende
Assignee: Luciano Resende






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

Re: [DISCUSS] Zeppelin 0.6.1 release

[Luciano Resende]

For Spark 2.0, do we need to wait for it's official release which is close
by...

On Thu, Jul 14, 2016 at 3:45 PM, moon soo Lee  wrote:

> Hi folks,
>
> We have released 0.6.0 July 2nd. During the 0.6.0 release discussion [1],
> we could see consensus that having a release 0.6.1 when Zeppelin have Spark
> 2.0 support.
>
> I have created a issue for 0.6.1 release [2]. The issue currently have
> Spark 2.0 and scala 2.11 support as a blocker.
>
> There were some bug fixes on master branch since 0.6.0 release.
> How about we discuss and backport some important bug fixes into
> branch-0.6.0? (if any)
> And how about we start release process of 0.6.1, as soon as all blockers of
> [2] being resolved?
>
>
> Thanks,
> moon
>
> [1]
>
> https://lists.apache.org/thread.html/e107c44df1a7fc4cd232144f6a24d81b32a7d988d5947093b79f05ee@1464110799@%3Cdev.zeppelin.apache.org%3E
> [2] https://issues.apache.org/jira/browse/ZEPPELIN-1177
>



-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

[DISCUSS] Zeppelin 0.6.1 release

[moon soo Lee]

Hi folks,

We have released 0.6.0 July 2nd. During the 0.6.0 release discussion [1],
we could see consensus that having a release 0.6.1 when Zeppelin have Spark
2.0 support.

I have created a issue for 0.6.1 release [2]. The issue currently have
Spark 2.0 and scala 2.11 support as a blocker.

There were some bug fixes on master branch since 0.6.0 release.
How about we discuss and backport some important bug fixes into
branch-0.6.0? (if any)
And how about we start release process of 0.6.1, as soon as all blockers of
[2] being resolved?


Thanks,
moon

[1]
https://lists.apache.org/thread.html/e107c44df1a7fc4cd232144f6a24d81b32a7d988d5947093b79f05ee@1464110799@%3Cdev.zeppelin.apache.org%3E
[2] https://issues.apache.org/jira/browse/ZEPPELIN-1177

[GitHub] zeppelin issue #1176: [Zeppelin 1165 : improve] Paragraph dynamic relationsh...

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/1176
  
z.run() currently submit paragraph into each interpreter's scheduler.

Let's say there're PARAGRAPH_1, PARAGRAPH_2, PARAGRAPH_3

```
%md
...

%spark
...

%sql
...
```

When user execute

```
z.run(P1)
z.run(P2)
z.run(P3)
```

z.run(P1) submit a job to run P1 to scheduler of Markdown interpreter.
z.run(P2) submit a job to run P2 to scheduler of Spark interpreter.
z.run(P3) submit a job to run P3 to scheduler of SparkSQL interpreter.

And each scheduler from each different interpreter works independently.
That's why P1, P2, P3 runs concurrently. (and this is why 'Run all' button 
doesn't run paragraph sequentially)

Then we can add synchronous option, such as

```
val result1 = z.runSynchronously(P1)
val result2 = z.runSynchronously(P2)
val result3 = z.runSynchronously(P3)
```

Then we can make sure P2 is not submitted before P1 finishes, P3 is not 
submitted before P2 finishes.

My points are,

- We can provide API to interpreter runs notebook or paragraph in the other 
notebook.
  So user can define workflow in programming language (i.e. scala, python, 
etc).
  It naturally gives more flexibility and power user to creates workflow, 
because programming language provides such things: conditional block, future, 
threads, and so on.
- To provide sequential job execution, we can provide synchronous api such 
as `z.runSynchronously()`
- In case of users, who are not familiar with programming language, want to 
creates workflow, we can create %workflow interpreter and invent new syntax or 
GUI on top of the same `z.run()` API internally. This is more modular and less 
confusing compare to run workflow with dynamic form syntax. 



---
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 #747: [ZEPPELIN-605] Add support for Scala 2.11

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/747
  
Merging it into master and branch-0.6


---
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 #1145: [ZEPPELIN-1012] Support Interpreter Aliases

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/1145
  
@Leemoonsoo I've reverted `refName` to `group` again. Review this PR 
finally.


---
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 #1185: Redirect home when requested a wrong notename path.

[astroshim]

Github user astroshim commented on the issue:

https://github.com/apache/zeppelin/pull/1185
  
@AhyoungRyu Thank you for your opinion. 
Your idea is great but now is redirected all to home when requested wrong 
path. (you can see the related code 
[here](https://github.com/apache/zeppelin/blob/master/zeppelin-web/src/app/app.js#L85))
so I think it's better to follow the present rule. What do you think?


---
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 #1155: [ZEPPELIN-1143] Interpreter dependencies are not downl...

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/1155
  
I also think @karup1990's way is proper. 


---
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 #1185: Redirect home when requested a wrong notename path.

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/1185
  
@astroshim Good catch! How about adding 404 page (like github does) instead 
of just redirecting `Home` without any message. In 404 page, we can add sth 
like "This is not the notebook page you are looking for" with some button for 
redirecting to home. 


---
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 #1168: [MINOR] Add formatter

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/1168
  
@bzz Thanks for the suggestion. I think we need to update docs and it's 
time to install Eclipse by myself in order to check the difference between 
Eclipse and Intellij. Thanks Alex.


---
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 #1176: [Zeppelin 1165 : improve] Paragraph dynamic relationsh...

[cloverhearts]

Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/1176
  
@corneadoug 
Your opinion is right.
 should be added to the .
But I was thinking that it must be able to control even in Note.
 to use convenient and it is true that I am expressing the 
workflow.
Satisfied.
However, I'm not sure Whether this is correct.
In particular usability and consistency.
<% Workflow> @Leemoonsoo 's idea is good.

If you have any other idea, please advise 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 pull request #1184: [ZEPPELIN-1159] Livy interpreter gets "404 not ...

[prabhjyotsingh]

GitHub user prabhjyotsingh opened a pull request:

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

[ZEPPELIN-1159] Livy interpreter gets "404 not found" error

### What is this PR for?
RestTemplate throws HttpClientErrorException exception thrown when an HTTP 
4xx is received.

http://docs.spring.io/spring/docs/current/javadoc-api/org/springframework/web/client/HttpClientErrorException.html


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

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

### How should this be tested?
Run a paragraph using livy interpreter (say sc.version), now let this 
session expire (or just restart livy server), then try running the same 
paragraph, this is result in proper error message.

### 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/prabhjyotsingh/zeppelin ZEPPELIN-1159

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

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


commit 7c58e42dc010c1ff42ca59fdbca17cb2b0542ee7
Author: Prabhjyot Singh 
Date:   2016-07-14T09:47:07Z

ZEPPELIN-1159 - catch RestTemplate exception




---
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 #1176: [Zeppelin 1165 : improve] Paragraph dynamic relationsh...

[cloverhearts]

Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/1176
  
@Leemoonsoo 
Thank you for your opinion!

 Workflow definition
I actually agree with your opinion.
The reason I made  is thought that the user wants to manage 
the workflow Note.
I am satisfied with the usability of the workflow according to the .
However, there was doubt whether this is also no problem using the .
It is not consistent usage.
Maybe @corneadoug think is right.
(add workflow feature in job menu)
Also feel the need to do to represent the workflow Paragraph well.
<% Workflow> are a good idea.
However, it is creating a new interpreter makes a number of concerns.
Maybe  is the same problem with this issue with.
This part I will try to think more.

 Alternative approach
I know of the existence of z.run.
However, z.run can not replace this function.
z.run does not guarantee the order of execution of each other for the other 
Paragraph interpreter.
Case 2 See the following image.


![seqinterpreter](https://cloud.githubusercontent.com/assets/10525473/16835379/726e9b36-49f3-11e6-826d-f6e6c32e0ff6.gif)


Thanks again for details opinion.



---
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-1176) Redirect home when requesting a wrong notename.

[Shim HyungSung (JIRA)]

Shim HyungSung created ZEPPELIN-1176:


 Summary: Redirect home when requesting a wrong notename.
 Key: ZEPPELIN-1176
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1176
 Project: Zeppelin
  Issue Type: Bug
Reporter: Shim HyungSung


If you request a wrong notename path like 
"http://localhost:8080/#/notebook/mynote; then it shows nothing.
I think it should be redirected to zeppelin home when requested wrong path.



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

[GitHub] zeppelin pull request #1183: [Zeppelin - 1174] Cleanup unused methods in rep...

[khalidhuseynov]

GitHub user khalidhuseynov reopened a pull request:

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

[Zeppelin - 1174] Cleanup unused methods in repo layer

### What is this PR for?
This is to cleanup some unused print methods from repository layer

### What type of PR is it?
Maintenance | Cleanup

### Todos
* [x] - remove unused methods

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

### How should this be tested?
CI pass

### Screenshots (if appropriate)

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


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

$ git pull https://github.com/khalidhuseynov/incubator-zeppelin 
repo/clean-unused-methods

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

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


commit 0a4e6157e4da4cc8c95ee1020d1254e95ce9d16f
Author: Khalid Huseynov 
Date:   2016-07-14T05:55:54Z

remove unused functions




---
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 #1183: [Zeppelin - 1174] Cleanup unused methods in rep...

[khalidhuseynov]

Github user khalidhuseynov closed the pull request at:

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


---
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 #1176: [Zeppelin 1165 : improve] Paragraph dynamic relationsh...

[corneadoug]

Github user corneadoug commented on the issue:

https://github.com/apache/zeppelin/pull/1176
  
I like the idea, but I also don't think that a new dynamic form is a good 
way to manage it.
I think that feature could fit better inside of the JOB page, especially 
since it is cross-notebook.
JOB page is currently only listing the Notebooks and the status of each 
paragraph, we could see it as a way to manage any workflow. (Full Notebook, or 
Custom Workflow)

I also wonder how can we handle the case of paragraphs that can run in 
parallel during one of the workflow step. (multiple sql queries for example)

There was a lot of demands to have a better 'Run all paragraphs' feature, 
and maybe we could later have a dropdown on the run button allowing to run 
multiple profile (to run some workflow related to that notebook, a bit like 
building different profile in Eclipse)



---
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 #1180: [ZEPPELIN-1059] Fix the Print CSS file

[corneadoug]

Github user corneadoug commented on the issue:

https://github.com/apache/zeppelin/pull/1180
  
Had to change some tests because of bad behaviour of `pu-elastic-input` 
with printing.

Added some functions to activate/deactivate the Implicit wait, it is mainly 
useful in the case of testing for elements that are not in the DOM.

Also added a line to handle firebug for people with higher version of 
Firefox


---
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 #1176: [Zeppelin 1165 : improve] Paragraph dynamic relationsh...

[xiufengliu]

Github user xiufengliu commented on the issue:

https://github.com/apache/zeppelin/pull/1176
  
`z.run("Paragraph1")
z.run("Paragraph2")
`
will "Paragraph1" and "Paragraph2" run sequencially? If "Paragraph1" 
failed, will ""Paragraph2"" still run?


---
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 #1162: [ZEPPELIN-909] Apply new mechanism to Elasticsearch in...

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/1162
  
@bzz Sure that make sense and thanks for clarifying it. Let me do that in 
other PR then :) 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Running Selenium tests

[Prabhjyot Singh]

https://raw.githubusercontent.com/SeleniumHQ/selenium/master/dotnet/CHANGELOG

v2.51.0 Says, they have added support for firefox 44, and the one we
are using v2.48.2 has officially support for FF31 but works till 45.

I keep both FF31 to test CI on local box, and FF-latest to do rest of the stuff.


On 14 July 2016 at 12:18, moon soo Lee  wrote:

> I don't know how much Firefox 45 and 31.0 are different.
>
> But I think it's good idea to use 31.0 for running selenium test, unless we
> update firefox version in travis ci. (travis runs selenium test with 31.0)
>
> On Wed, Jul 13, 2016 at 11:32 PM Corneau Damien 
> wrote:
>
> > Answering myself.
> > Don't update to Firefox 47, stay in 45 :)
> >
> > On Thu, Jul 14, 2016 at 2:43 PM, Corneau Damien 
> > wrote:
> >
> > > Hi,
> > >
> > > Does anybody have a good way to run Selenium tests from command line?
> > > There isn't much documentation about it, and I can't get it to run
> > anymore.
> > >
> > > I tried both:
> > >
> > > *TEST_SELENIUM="true" mvn package -DfailIfNoTests=false -pl
> > > 'zeppelin-interpreter,zeppelin-zengine,zeppelin-server'
> > > -Dtest=ParagraphActionsIT*
> > > (Next to running Zeppelin)
> > >
> > > and
> > >
> > > *PATH=~/Applications/Firefox.app/Contents/MacOS/:$PATH CI="true" mvn
> > > verify -Pspark-1.6 -Phadoop-2.3 -Ppyspark -B -pl
> > >
> >
> "zeppelin-interpreter,zeppelin-zengine,zeppelin-server,zeppelin-display,spark-dependencies,spark"
> > > -Dtest="org.apache.zeppelin.AbstractFunctionalSuite"
> > -DfailIfNoTests=false*
> > >
> > > (Just like CI)
> > > But no luck.
> > >
> > > When trying to fix tests, it can take a lot of trials, and making a
> > commit
> > > and waiting for CI isn't an option.
> > >
> >
>



-- 
Thankx and Regards,

Prabhjyot Singh

[jira] [Created] (ZEPPELIN-1175) AM log is not available for yarn-client mode

[Jeff Zhang (JIRA)]

Jeff Zhang created ZEPPELIN-1175:


 Summary: AM log is not available for yarn-client mode 
 Key: ZEPPELIN-1175
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1175
 Project: Zeppelin
  Issue Type: Bug
  Components: Interpreters
Affects Versions: 0.6.0
Reporter: Jeff Zhang


Zeppelin's log4j.properties is propagated to AM, so that the AM can not 
initialize log4j properly. Because zeppelin's log4j.properties will use 
${zeppelin.log.file} which is only for zeppelin server. 

Here's the error message in AM
{code}
log4j:ERROR setFile(null,true) call failed.
java.io.FileNotFoundException:  (No such file or directory)
at java.io.FileOutputStream.open0(Native Method)
at java.io.FileOutputStream.open(FileOutputStream.java:270)
at java.io.FileOutputStream.(FileOutputStream.java:213)
at java.io.FileOutputStream.(FileOutputStream.java:133)
at org.apache.log4j.FileAppender.setFile(FileAppender.java:294)
at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165)
at 
org.apache.log4j.DailyRollingFileAppender.activateOptions(DailyRollingFileAppender.java:223)
at 
org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307)
at 
org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:172)
at 
org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:104)
at 
org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:842)
at 
org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:768)
at 
org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:648)
at 
org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:514)
at 
org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:580)
at 
org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:526)
at org.apache.log4j.LogManager.(LogManager.java:127)
at org.apache.spark.Logging$class.initializeLogging(Logging.scala:121)
at 
org.apache.spark.Logging$class.initializeIfNecessary(Logging.scala:106)
at org.apache.spark.Logging$class.log(Logging.scala:50)
at 
org.apache.spark.executor.CoarseGrainedExecutorBackend$.log(CoarseGrainedExecutorBackend.scala:138)
at 
org.apache.spark.executor.CoarseGrainedExecutorBackend$.run(CoarseGrainedExecutorBackend.scala:149)
at 
org.apache.spark.executor.CoarseGrainedExecutorBackend$.main(CoarseGrainedExecutorBackend.scala:253)
at 
org.apache.spark.executor.CoarseGrainedExecutorBackend.main(CoarseGrainedExecutorBackend.scala)
log4j:ERROR Either File or DatePattern options are not set for appender 
[dailyfile].
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in 
[jar:file:/grid/0/hadoop/yarn/local/filecache/27/spark-hdp-assembly.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in 
[jar:file:/grid/0/hdp/2.5.0.0-965/hadoop/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
{code}



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

[GitHub] zeppelin pull request #1176: [Zeppelin 1165 : improve] Paragraph dynamic rel...

[cloverhearts]

Github user cloverhearts closed the pull request at:

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


---
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 #1176: [Zeppelin 1165 : improve] Paragraph dynamic rel...

[cloverhearts]

GitHub user cloverhearts reopened a pull request:

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

[Zeppelin 1165 : improve]  Paragraph dynamic relationship executable form

### What is this PR for?
Workflow process feature.
(To ensure the success of each paragraph, it is possible to run 
consecutively.)

 Case 1
Through a dynamic form, you can execute the order in paragraph.
There is a difference with traditional methods.
Please check the following flowchart.

![workflowdynamicformcontrol](https://cloud.githubusercontent.com/assets/10525473/16791726/a4b96ff0-48fc-11e6-8e23-9ec577066bb7.png)

 Case 2
In general, when run a plurality of Paragraph, it performs Note entire run.
This is a good way to run a lot of Paragraph contained in the Note.
However, the problem occurs if the Interpreter of Paragraph different.

![notebook_example](https://cloud.githubusercontent.com/assets/10525473/16803203/175ad01a-4940-11e6-8949-72d0c49bdf9e.png)
For Paragraph each using a different type of one of the Interpreter Note 
but run in sequence, the end is all different.

![normal notebook 
run](https://cloud.githubusercontent.com/assets/10525473/16803193/069c4d94-4940-11e6-9293-888b6c6288a0.png)
For example, Markdown is a very fast Interpreter.
The process is completed very quickly.
This is a problem in the sequential execution Paragraph.

![worklfow 
run](https://cloud.githubusercontent.com/assets/10525473/16803192/06998122-4940-11e6-8f01-43cdf64f2eef.png)
This feature ensures a certain execution order Notebook with each 
Interpreter.

# Case 3
For concurrent job in the workflow ...


![job_repl](https://cloud.githubusercontent.com/assets/10525473/16828860/96e601b8-49ce-11e6-87d0-6f7fc30ce751.png)

If the current functional design is supposed to run at the same time, as 
follows 
It is to share the results of the job.
But if the situation need to run the job at the same time, subject to their 
execution flow.

** The results will have to succeed, the following paragraph will be 
executed. **

### What type of PR is it?
Improvement

### jira
https://issues.apache.org/jira/browse/ZEPPELIN-1165
### How should this be tested?
Dynamic form
For usage, see the following: 
https://zeppelin.apache.org/docs/0.7.0-SNAPSHOT/manual/dynamicform.html

In the markdown type:
```
%md

${workflow:workflow=MyWorkflowName,NotebookId01:ParagraphId01|NotebookId02:ParagraphId02}
```
- details explain.

You can specify the title work flow.
Simply displayed on the UI. 
```
${workflow:workflow=
or
${workflow:workflow=MyWorkflow
```
title name : MyWorkflow

character a comma(,), you can start working set.

```
${workflow:workflow=MyWorkflow**,**
```

Enter your Notebook ID and Paragraph ID.
```
${workflow:workflow=MyWorkflow,2BS99R6QA:20160712-163556_1475991024}
```

In order to distinguish between the Notebook ID and Paragraph ID, 
characters <:> it is.
The example was set to run 20160712-163556_1475991024 paragraph with a 
notebook id called 2BS99R6QA.
- how to get notebook id?
https://cloud.githubusercontent.com/assets/10525473/16795411/30faab1c-4918-11e6-8ef3-8b6fc6f6f039.png;>
- how to get paragraph id?
https://cloud.githubusercontent.com/assets/10525473/16795412/31041d8c-4918-11e6-9b9f-8f472692e3e1.png;>




Through a pipe character( | ), you can add tasks consecutively.
```

${workflow:workflow=MyWorkflow,2BS99R6QA:20160712-163556_1475991024|2BS99R6QA:20160710-03221_12234323}
```

 Note run

![cap 2016-07-14 
15-11-07-036](https://cloud.githubusercontent.com/assets/10525473/16829747/732164a0-49d5-11e6-938f-9c08cfb772c1.png)


If you want to run to all Paragraph in  Note, you can:
```
NoteID : *
or
NoteID
```
```
${workflow:workflow=MyworkflowName,NotebookId}
or
${workflow:workflow=MyworkflowName,NotebookId:*}
```


for example
```
${workflow:workflow=Myworkflow,2A94M5J1Z}
```

Of course, it is possible to run a particular paragraph and mix.

```
%md

${workflow:workflow=Myworkflow,2A94M5J1Z|r|2BQWXDH1C:20160714-151024_1284650101}
```



### Screenshots (if appropriate)

![workflow](https://cloud.githubusercontent.com/assets/10525473/16830111/d54e909c-49d7-11e6-87c2-0de4a3b5b793.gif)


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


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

$ git pull https://github.com/cloverhearts/zeppelin 
ZEPPELIN-1165-paragraph-relati

[GitHub] zeppelin issue #1163: [ZEPPELIN-1149] %sh interpreter kerberos support

[rconline]

Github user rconline commented on the issue:

https://github.com/apache/zeppelin/pull/1163
  
@felixcheung as of now the interpreters are reusing zeppelin keytab. 
Typically this is case in the hadoop security world, where the keytab is 
generated at a process level, whereas the authorization is done through 
impersonation. This is then mapped to the user permissions setup on the 
underlying data system via posix users. Mature systems which implement full 
support for security + impersonation, can provide this ability. Right now with 
this change we get to the first stage which is security. To get to 
impersonation we will have to start the shell with the user's identity. I think 
that can be followup patch, in the next couple of weeks. 


---
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 #1176: [Zeppelin 1165 : improve] Paragraph dynamic relationsh...

[cloverhearts]

Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/1176
  
update

add operator : all paragraph (*)

and ui fixed.

![cap 2016-07-14 
15-11-07-036](https://cloud.githubusercontent.com/assets/10525473/16829747/732164a0-49d5-11e6-938f-9c08cfb772c1.png)


If you want to run to all Paragraph in  Note, you can:
```
NoteID : *
or
NoteID
```
```
${workflow:workflow=MyworkflowName,NotebookId}
or
${workflow:workflow=MyworkflowName,NotebookId:*}
```


for example
```
${workflow:workflow=Myworkflow,2A94M5J1Z}
```

Of course, it is possible to run a particular paragraph and mix.

```
%md

${workflow:workflow=Myworkflow,2A94M5J1Z|r|2BQWXDH1C:20160714-151024_1284650101}
```




---
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-1174) Cleanup unused methods in repository layer

[Khalid Huseynov (JIRA)]

Khalid Huseynov created ZEPPELIN-1174:
-

 Summary: Cleanup unused methods in repository layer
 Key: ZEPPELIN-1174
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1174
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Khalid Huseynov
Assignee: Khalid Huseynov
Priority: Minor
 Fix For: 0.7.0


There're some unused methods (possibly previously used, e.g. print) in 
repository layer that needs to be cleaned up.



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

[GitHub] zeppelin issue #928: [ZEPPELIN-116][WIP] Add Mahout Support for Spark Interp...

[bzz]

Github user bzz commented on the issue:

https://github.com/apache/zeppelin/pull/928
  
Got it, thank you so much for digging into it!

Let me try to look into it more this week


---
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 #1164: ZEPPELIN-1115: Python - interpreter for SQL over DataF...

[bzz]

Github user bzz commented on the issue:

https://github.com/apache/zeppelin/pull/1164
  
Thank you guys for prompt reviews! 

Have added one minor TODO item to cleanup test profiles on CI, will merge 
after #747 


---
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 #1117: [ZEPPELIN-1086] Auto Completion for Interpreter.

[astroshim]

Github user astroshim commented on the issue:

https://github.com/apache/zeppelin/pull/1117
  
@bzz I totally agree with you so I did try to remove things you mentioned 
but it's not easy.
Let me try one more. Thanks!


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] zeppelin issue #1162: [ZEPPELIN-909] Apply new mechanism to Elasticsearch in...

[bzz]

Github user bzz commented on the issue:

https://github.com/apache/zeppelin/pull/1162
  
Thank you for pointing out Lens case!

May be we could extract this error handling logic to the method and re-use 
it everywhere, so the client code would look like:

```java
this.resultSize = 
parseIntegerOrDefault(getProperty(ELASTICSEARCH_RESULT_SIZE), 10);
```

and the API

```java
class Interpreter {
  protected Integer parseIntegerOrDefault(String str, Integer defaultValue) 
{ }
}
```

This can be done in a separate PR though and include refactoring of all 
existing interpreters (this, Lense, Python, etc). 

What do you think?


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