[GitHub] zeppelin issue #2181: [ZEPPELIN-2304] Fix vis Icon sizes in helium page

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2181
  
Just rebased and CI is green now.


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

[GitHub] zeppelin pull request #2197: ZEPPELIN-2324. Add property zeppelin.spark.unSu...

[zjffdu]

GitHub user zjffdu opened a pull request:

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

ZEPPELIN-2324. Add property zeppelin.spark.unSupportedVersionCheck for 
trying new spark version

### What is this PR for?
For now, every time when I want to try new spark version, I have to change 
file SparkVersion and rebuild it. It is not so convenient, so I'd like to add 
property zeppelin.spark.unSupportedVersionCheck for spark interpreter. So that 
I can try new spark version by setting this property as false, of course it is 
only for zeppelin developer.


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

### Todos
* [ ] - Task

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

### How should this be tested?
Verify it in spark master

### 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/zjffdu/zeppelin ZEPPELIN-2324

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

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


commit 94b12a723237143c549df26c7eae999619319352
Author: Jeff Zhang 
Date:   2017-03-28T05:38:08Z

ZEPPELIN-2324. Add property zeppelin.spark.unSupportedVersionCheck for 
trying new spark version




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

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

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2174
  
@AhyoungRyu Sorry for confusing. It works as described. maybe i mixed 
commits 😞 

- It would be nice if we hide `<<` and `>>` when users don't need it. (e.g 
less than 5 pages)


![image](https://cloud.githubusercontent.com/assets/4968473/24390403/a0ee9a02-13c3-11e7-9899-fbd465c3a1b8.png)


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

[jira] [Created] (ZEPPELIN-2324) Add property zeppelin.spark.unSupportedVersionCheck for trying new spark version

[Jeff Zhang (JIRA)]

Jeff Zhang created ZEPPELIN-2324:


 Summary: Add property zeppelin.spark.unSupportedVersionCheck for 
trying new spark version
 Key: ZEPPELIN-2324
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2324
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Jeff Zhang


For now, every time when I want to try new spark version, I have to change file 
SparkVersion and rebuild it. It is not so convenient, so I'd like to add 
property zeppelin.spark.unSupportedVersionCheck for spark interpreter. So that 
I can try new spark version by setting this property as false, of course it is 
only for zeppelin developer.  



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

[GitHub] zeppelin issue #2196: fix bugs for timer saver

[soralee]

Github user soralee commented on the issue:

https://github.com/apache/zeppelin/pull/2196
  
Thanks @wary for fixing this!
But, could you explain detail this PR such as `what is this PR for` and 
`How should this be test`?



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

[GitHub] zeppelin issue #2196: fix bugs for timer saver

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2196
  
Hi @wary  Thanks for contribution.

- Zeppelin build system relies on travis. So please setup your travis 
account and travis project for Zeppelin. 
- 
https://zeppelin.apache.org/contribution/contributions.html#continuous-integration
- The repository name must be `zeppelin` (not `incubator-zeppelin`, ...)
- It's not mandatory to pass all tests to be reviewed. But some reviewers 
might select passed PRs first

Please trigger travis CI by pushing new commits or amend your last commit 
(`git commit --amend` and  `git push your-remote HEAD --force`) after setup 
your travis.


---
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 #2196: fix bugs for timer saver

[wary]

GitHub user wary opened a pull request:

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

fix bugs for timer saver

### What is this PR for?
A few sentences describing the overall goals of the pull request's commits.
First time? Check out the contributing guide - 
https://zeppelin.apache.org/contribution/contributions.html


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

### Todos
* [ ] - Task

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

### How should this be tested?
Outline the steps to test the PR here.

### Screenshots (if appropriate)

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


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

$ git pull https://github.com/wary/zeppelin master

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

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


commit 3612f563d5a08f570ce724751f2a0144868b2714
Author: lei wang 
Date:   2017-03-28T01:42:35Z

fix bugs for timer saver




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

[del680202]

Github user del680202 commented on the issue:

https://github.com/apache/zeppelin/pull/2191
  
I check this PR, it works well, 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 #2193: Branch 0.7

[wary]

Github user wary closed the pull request at:

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


---
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 #2195: [ZEPPELIN-2319] new methods for ZeppelinContext

[zjffdu]

Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/2195
  
@meniluca I am a little conservative for adding new public api in 
ZeppelinContext. As new api means more overhead to maintain it and keep 
backward compatibility. Could you describe the scenario of why you need these 
api ? Maybe we could build more generate api or solution for 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] zeppelin pull request #2195: [ZEPPELIN-2319] new methods for ZeppelinContext

[meniluca]

GitHub user meniluca opened a pull request:

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

[ZEPPELIN-2319] new methods for ZeppelinContext

### What is this PR for?
Adds new methods to ZeppelinContext to run paragraphs in a more 
user-friendly mode.

```java
z.runAllBefore()
z.runAllAfter()
z.run(int... ids)
z.run(String... ids)
z.runNext(int i)
```
more details in the Jira tickets.

### What type of PR is it?
Feature

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

### How should this be tested?
They all wrap the ``run(List ids)`` method, hence can be tested in 
the same test suite.

### Screenshots (if appropriate)
Coming soon

### 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/meniluca/zeppelin master

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

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


commit 0eca6ca19f55efa814e9ffa915ab785e2f54e963
Author: Luca Menichetti 
Date:   2017-03-27T21:42:38Z

[ZEPPELIN-2319] new methods for ZeppelinContext




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

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

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2135
  
Thanks @dlukyanov for the contribution.

LGTM!


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

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

[dlukyanov]

Github user dlukyanov commented on the issue:

https://github.com/apache/zeppelin/pull/2135
  
@Leemoonsoo , done. waiting for travis.


---
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 #2188: [MINOR] Job parameters synchronization

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2188
  
Merged to master, but didn't merged to branch-0.7 because of conflict.


---
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 #2188: [MINOR] Job parameters synchronization

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #2192: [ZEPPELIN-2320] fixing test + modifying map browsing

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2192
  
LGTM


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

[GitHub] zeppelin issue #2186: [ZEPPELIN-2229] revert ndv3 version from 1.8.5 to 1.7....

[soralee]

Github user soralee commented on the issue:

https://github.com/apache/zeppelin/pull/2186
  
Let's move on #2194 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] zeppelin issue #2186: [ZEPPELIN-2229] revert ndv3 version from 1.8.5 to 1.7....

[soralee]

Github user soralee commented on the issue:

https://github.com/apache/zeppelin/pull/2186
  
I closed this PR. Because In the better way which keeps on the latest 
version, @Remilito suggested #2194, I think we don't need to talk about this PR 
any more.


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

[GitHub] zeppelin issue #2194: [ZEPPELIN-2229] Providing workaround for nvd3 voronoi

[soralee]

Github user soralee commented on the issue:

https://github.com/apache/zeppelin/pull/2194
  
@Remilito Sounds great! It looks good to me.
With this PR, we can keep on using the latest version of the nvd3. 
Personally, I like your annotations per code spot. Because it can keep remind 
us and it would be comfortable when bump up version.
Anyway, I'll check and test it out!


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

[GitHub] zeppelin issue #2191: [HOTFIX] Keep interpreter group when save and restart

[soralee]

Github user soralee commented on the issue:

https://github.com/apache/zeppelin/pull/2191
  
Tested and It works as your described, LGTM!


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

[GitHub] zeppelin issue #2186: [ZEPPELIN-2229] revert ndv3 version from 1.8.5 to 1.7....

[Remilito]

Github user Remilito commented on the issue:

https://github.com/apache/zeppelin/pull/2186
  
@soralee , @AhyoungRyu , @anthonycorbacho : proposal of workaround here, 
https://github.com/apache/zeppelin/pull/2194 . Feedbacks welcome!


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

[GitHub] zeppelin pull request #2194: [ZEPPELIN-2229] Providing workaround for nvd3 v...

[Remilito]

GitHub user Remilito opened a pull request:

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

[ZEPPELIN-2229] Providing workaround for nvd3 voronoi

### What is this PR for?
After bumping nvd3 to 1.8.5, an error was spotted due to a bug in nvd3. 
This PR provides a workaround until the proper nvd3 fix is released. 
* create a jitter and deduplicate data
* adapt axis tick format to hide the jitter
* add y label for non-numeric value
* this code can be safely removed after nvd3 
[#1934](https://github.com/novus/nvd3/pull/1934) is released ( >
  1.8.5) and bumped in zeppelin project

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

### Todos
* [ ] - When bumping nvd3 to a version > 1.8.5, remove the code marked with 
TODO

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

### How should this be tested?
See [#2186](https://github.com/apache/zeppelin/pull/2186). Switch between 
any chart and scatter chart with a large number of rows.

### Screenshots (if appropriate)
See [#2186](https://github.com/apache/zeppelin/pull/2186).

### 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/Remilito/zeppelin ZEPPELIN-2229

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

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


commit 017ab390a6a7a07055f6bd6209104d52a4144c74
Author: Remilito 
Date:   2017-03-27T16:27:39Z

[ZEPPELIN-2229] Providing workaround for nvd3 voronoi
* create a jitter and deduplicate data
* adapt axis tick format to hide the jitter
* add y label for non-numeric value
* this code can be safely removed after nvd3 #1934 is released ( >
  1.8.5) and bumped in zeppelin project




---
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 #2193: Branch 0.7

[soralee]

Github user soralee commented on the issue:

https://github.com/apache/zeppelin/pull/2193
  
@wary This branch is fault and not regarding of ZEPPELIN-2323. Could you 
close this PR and make sure your branch? 



---
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 #2193: Branch 0.7

[wary]

GitHub user wary opened a pull request:

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

Branch 0.7

### What is this PR for?
A few sentences describing the overall goals of the pull request's commits.
First time? Check out the contributing guide - 
https://zeppelin.apache.org/contribution/contributions.html


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

### Todos
* [ ] - Task

### What is the Jira issue?
* Open an issue on Jira https://issues.apache.org/jira/browse/ZEPPELIN/
* Put link here, and add [ZEPPELIN-*Jira number*] in PR title, eg. 
[ZEPPELIN-533]
[ZEPPELIN-2323]
https://issues.apache.org/jira/browse/ZEPPELIN-2323

### How should this be tested?
Outline the steps to test the PR here.

### Screenshots (if appropriate)

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


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

$ git pull https://github.com/wary/zeppelin branch-0.7

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

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


commit d91b310cbb985eac1e12ab9528a3be9e8e1b834c
Author: Prabhjyot Singh 
Date:   2017-01-07T12:37:00Z

[ZEPPELIN-1906] Use multiple InterpreterResult for displaying multiple JDBC 
queries

### What is this PR for?
Use multiple InterpreterResult for displaying multiple JDBC queries.
IMO since other sql editors allows to execute multiple sql separated with 
";" and ours display mechanism being more powerful, hence, it should also allow 
the same.

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

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

### How should this be tested?
Try running following in a paragraph (with Postgres setting) and check for 
output.

```
%jdbc
create table test_temp_table (id int);
select column_name, data_type, character_maximum_length from 
INFORMATION_SCHEMA.COLUMNS where table_name = 'test_temp_table';
SELECT table_name FROM information_schema.tables WHERE table_schema = 
'public';
drop table test_temp_table;
SELECT table_name FROM information_schema.tables WHERE table_schema = 
'public';
```

### Screenshots (if appropriate)

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

Author: Prabhjyot Singh 

Closes #1845 from prabhjyotsingh/ZEPPELIN-1906 and squashes the following 
commits:

b27352a [Prabhjyot Singh] on error show previous output.
f9fd5c6 [Prabhjyot Singh] allow last query to be without ";"
b3e742e [Prabhjyot Singh] fixing checkstyle-fail-build
ac4663d [Prabhjyot Singh] add block comment
f3da37f [Prabhjyot Singh] replace regex with slightly better logic.
e6727b5 [Prabhjyot Singh] add testcase for spliting sql.
c096e76 [Prabhjyot Singh] remove extra empty lines
e675190 [Prabhjyot Singh] user same connection instead of creating new 
everytime
f5ab796 [Prabhjyot Singh] Use multiple InterpreterResult for displaying 
multiple JDBC queries

(cherry picked from commit 8464971c7aab0734f96d0a5a11d842b8e595324a)
Signed-off-by: Prabhjyot Singh 

commit b8637f5e5fa4aab8859e6bc90fa7886ba9157b24
Author: Alexander Shoshin 
Date:   2017-01-11T08:45:31Z

[ZEPPELIN-1787] Add an example of Flink Notebook

### What is this PR for?
This PR will add an example of batch processing with Flink to Zeppelin 
tutorial notebooks. There are no any Flink notebooks in the tutorial at the 
moment.

### What type of PR is it?
Improvement

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

### How should this be tested?
You should open `Using Flink for batch processing` notebook from the 
`Zeppelin Tutorial` folder and run all paragraphs one by one

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

Author: Alexander Shoshin 

Closes #1758 from AlexanderShoshin/ZEPPELIN-1787 and squashes the following 
commits:

83cbffb [Alexander Shoshin] remove localhost url
5255e17 [Alexander Shoshin] Merge branch 'master' into ZEPPELIN-1787
0b9df56 [Alexander Shoshin] add a link for this notebook to Zeppelin 
documentation
593c47d 

[jira] [Created] (ZEPPELIN-2323) edited paragraphs are not saved in a timely manner

[LeiWang (JIRA)]

LeiWang created ZEPPELIN-2323:
-

 Summary: edited paragraphs are not saved in a timely manner
 Key: ZEPPELIN-2323
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2323
 Project: Zeppelin
  Issue Type: Bug
  Components: front-end
Affects Versions: 0.7.0
Reporter: LeiWang


the Edited paragraphs are not saved in a timely manner; when we edit a note in 
one browser, then open an other browser, the paragraph's content did not be 
synced to the other brower



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

[jira] [Created] (ZEPPELIN-2322) how can i turn off scala and just default to %pyspark

[sulphide (JIRA)]

sulphide created ZEPPELIN-2322:
--

 Summary: how can i turn off scala and just default to %pyspark
 Key: ZEPPELIN-2322
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2322
 Project: Zeppelin
  Issue Type: Bug
Reporter: sulphide


we only use %pyspark and %sql and we don't ever use scala, so would like to 
default to %pyspark and remove scale entirely, if possible. is this possible? 
thanks.



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

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

[Jongyoul Lee]

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

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

> Sorry, I need to -1 again, as I just found that ZEPPELIN-1984 is also
> needed to backport. Otherwise no error message displayed in frontend when
> interpreter fail to start.
>
>
>
> Sora Lee 于2017年3月24日周五 下午2:14写道：
>
> > I faced a error when switching the scatter chart, the error message that
> is
> > "cannot property 'x' of null" appear in web development tool of web
> > browser. so I created this PR (
> > https://github.com/apache/zeppelin/pull/2186
> > ).
> >
> > Shell we include this patch in 0.7.1 release?
> >
> > Thanks,
> > Sora
> >
> > On Fri, Mar 24, 2017 at 12:32 PM Mina Lee  wrote:
> >
> > > I propose the following RC to be released for the Apache Zeppelin 0.7.1
> > > release.
> > >
> > > The commit id is 163f6730ea91486c581f502863fe62b3cd9b06d4 which is
> > > corresponds to the tag v0.7.1-rc2:
> > >
> > >
> > https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;h=
> refs/tags/v0.7.1-rc2
> > >
> > > The release archives (tgz), signature, and checksums are here
> > > https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.7.1-rc2/
> > >
> > > The release candidate consists of the following source distribution
> > archive
> > > zeppelin-0.7.1.tgz
> > >
> > > In addition, the following supplementary binary distributions are
> > provided
> > > for user convenience at the same location
> > > zeppelin-0.7.1-bin-all.tgz
> > > zeppelin-0.7.1-bin-netinst.tgz
> > >
> > > The maven artifacts are here
> > >
> > https://repository.apache.org/content/repositories/
> orgapachezeppelin-1034
> > >
> > > You can find the KEYS file here:
> > > https://dist.apache.org/repos/dist/release/zeppelin/KEYS
> > >
> > > Release notes available at
> > >
> > >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> version=12339166=12316221
> > >
> > > Vote will be open for next 72 hours (close at 21:00 26/Mar PDT).
> > >
> > > [ ] +1 approve
> > > [ ] 0 no opinion
> > > [ ] -1 disapprove (and reason why)
> > >
> >
>



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

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

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2174
  
@felixcheung Let me check again for that 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] zeppelin issue #2174: [ZEPELIN-2209] Add pagination to Helium menu

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2174
  
@1ambda It's wired. This is what I can see when I build my branch. 

![record](https://cloud.githubusercontent.com/assets/10060731/24363529/1863c144-134b-11e7-85c7-ae5c6acc8dd7.gif)

There are two `ng-repeat` like below. And [the pagination 
DOM](https://github.com/AhyoungRyu/zeppelin/blob/7150e7cb596c2bbe9148ea2a09009c6fb273a20e/zeppelin-web/src/app/helium/helium.html#L195)
 is placed inside of the first `ng-repeat`(for pkg type checking loop) and 
outside of the second one(each type of package listing). 
https://cloud.githubusercontent.com/assets/10060731/24363549/26531e08-134b-11e7-8f05-4b71bf1b277b.png;>

FYI, the data is like this.
https://cloud.githubusercontent.com/assets/10060731/24363853/ff811018-134b-11e7-84a3-867ec956539e.png;>






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

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

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2163
  
@Leemoonsoo Thanks! 
Merge into master and branch-0.7 if there are no more comments 


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

[GitHub] zeppelin pull request #2192: [ZEPPELIN-2320] fixing test + modifying map bro...

[Remilito]

GitHub user Remilito opened a pull request:

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

[ZEPPELIN-2320] fixing test + modifying map browsing

### What is this PR for?
fixing String comparison and improving map browsing

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

### Todos
* [ ] - Task

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

### How should this be tested?
build with tests.

### 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/Remilito/zeppelin ZEPPELIN-2320

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

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


commit 9ad16bc73add8de8b4dff9eabe5d5bb95dce077e
Author: Remilito 
Date:   2017-03-27T08:43:26Z

[ZEPPELIN-2320] fixing test + modifying map browsing




---
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 #2186: [ZEPPELIN-2229] revert ndv3 version from 1.8.5 to 1.7....

[soralee]

Github user soralee commented on the issue:

https://github.com/apache/zeppelin/pull/2186
  
@Remilito @anthonycorbacho Thanks for opinions!
Yeah, I think whatever we use 1.7.1 version or 1.8.5 versions, we have a 
lot of bugs. `nvd3` release process is too slow and, I'm not sure 1.8.5 version 
has critical bugs than 1.7.1 version :disappointed:
If we don't mind those issues, we would be nice to keep the latest version! 


---
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-2321) zeppelin hungup when executing cronjob

[richard.lee (JIRA)]

richard.lee created ZEPPELIN-2321:
-

 Summary: zeppelin hungup when executing cronjob
 Key: ZEPPELIN-2321
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2321
 Project: Zeppelin
  Issue Type: Bug
  Components: Interpreters
Affects Versions: 0.7.0
 Environment: hadoop 2.7.3  
spark 2.1.0
jdk8
Reporter: richard.lee


Cannot execute other notebook when some notebook config cronjob cause request 
of '/api/helium/suggest//' response with timeout.  java 
stack trace is bellow:




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

[GitHub] zeppelin issue #2182: [ZEPPELIN-2248] Fix javax.ws.rs and cxf version mismat...

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/2182
  
I got one error from travis. It seems to be related 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.
---

[GitHub] zeppelin pull request #2187: [ZEPPELIN-2314] Fix watcher websocket origin he...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #2186: [ZEPPELIN-2229] revert ndv3 version from 1.8.5 to 1.7....

[soralee]

Github user soralee commented on the issue:

https://github.com/apache/zeppelin/pull/2186
  
@AhyoungRyu I checked [your comment about translate 
error](https://github.com/apache/zeppelin/pull/2186#issuecomment-289178564).
The error seems to be caused by incompatibility with the 1.7.1 version and 
[this 
line](https://github.com/apache/zeppelin/pull/2129/files#diff-28a8fa162a27698e421ee716f1822a33L73)
 that is after merged this #2129 in master branch.
If we decide merge, I would fix 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.
---

[GitHub] zeppelin issue #2186: [ZEPPELIN-2229] revert ndv3 version from 1.8.5 to 1.7....

[anthonycorbacho]

Github user anthonycorbacho commented on the issue:

https://github.com/apache/zeppelin/pull/2186
  
I will agree with @Remilito on this one.
I think we can come up with a workaround and keep 1.8.5.



---
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 #1976: [ZEPPELIN-2037] Restart button does not work

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/1976
  
@del680202 Thanks, if you finish to test it, we will make a new rc 
including 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] zeppelin issue #1976: [ZEPPELIN-2037] Restart button does not work

[del680202]

Github user del680202 commented on the issue:

https://github.com/apache/zeppelin/pull/1976
  
@jongyoul Thanks, I will test it later


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

[GitHub] zeppelin pull request #2191: [HOTFIX] Keep interpreter group when save and r...

[jongyoul]

GitHub user jongyoul opened a pull request:

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

[HOTFIX] Keep interpreter group when save and restart

### What is this PR for?
Not removing interpreter group reference while editing and saving 
interpreter setting.

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

### Todos
* [x] - Move `loadFromFile` into proper location

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

### How should this be tested?
1. Enable shiro for login
1. Execute sample code by %python and %pyspark
1. Switch spark interpreter from global mode to Per user mode and save it.
1. Switch python interpreter from Per user mode to global mode save it.
1. Shutdown zeppelin

### 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 
hotfix/keep-interpreter-group-when-save-and-restart

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

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


commit a11ff40d58f9f0d93035d94e09c53dcb606519d9
Author: Jongyoul Lee 
Date:   2017-03-27T08:35:07Z

Moved the location of loadFromFile during restarting process




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

[GitHub] zeppelin pull request #2134: [ZEPPELIN-2257] notification about incompletene...

[tinkoff-dwh]

Github user tinkoff-dwh closed the pull request at:

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


---
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 #2134: [ZEPPELIN-2257] notification about incompletene...

[tinkoff-dwh]

GitHub user tinkoff-dwh reopened a pull request:

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

[ZEPPELIN-2257] notification about incompleteness of data

### What is this PR for?
Added notification about exceeding the limit in the result.

### What type of PR is it?
Improvement

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

### How should this be tested?
1. Create table *test* with more than 2 records (if not exists)
2. Set parameter `common.max_count ` = 2
3. Execute 
```
%jdbc
select *from test
```
You should see message about exceeds limit

### Screenshots (if appropriate)

![6](https://cloud.githubusercontent.com/assets/25951039/23899435/f5a23e48-08d6-11e7-9cb0-1613398ce22e.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/tinkoff-dwh/zeppelin ZEPPELIN-2257

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

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


commit edeca0e10910f004978e512888a46058723325c2
Author: Tinkoff DWH 
Date:   2017-03-20T19:09:11Z

[ZEPPELIN-2257] notifications about incompleteness of data

commit d6dbe3e9fdcea5e0c4747e3a9a0bfa13438f209c
Author: Tinkoff DWH 
Date:   2017-03-20T19:40:56Z

Merge remote-tracking branch 'origin/master' into ZEPPELIN-2257

commit 2e6c97690bb288d039bfb0d04aea54bf63b23cf7
Author: Tinkoff DWH 
Date:   2017-03-24T06:19:06Z

[ZEPPELIN-2257] close button to alert

commit 3c52b52811851d70472ba027067569b662b5969a
Author: Tinkoff DWH 
Date:   2017-03-27T06:25:03Z

[ZEPPELIN-2257]  custom css class for alert




---
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 #2186: [ZEPPELIN-2229] revert ndv3 version from 1.8.5 to 1.7....

[Remilito]

Github user Remilito commented on the issue:

https://github.com/apache/zeppelin/pull/2186
  
My 2 cts here:
Yep the scatter chart bug in 1.8.5 is annoying, and unfortunately nvd3 does 
not seem to release very frequently ( 2-3 times a year or so). However I am not 
sure reverting the lib from 1.8.5 to 1.7.1 is the right move, keep in mind that 
 **a lot of bugs** were fixed between those two releases.
Reverting to 1.7.1 is very likely to reintroduce (or maintain) a lot of 
others bugs. 

I wonder if we could do something directly in Zeppelin's visualization code 
to workaround the voronoi issue you spotted until 1.8.6 is released. Your 
thoughts?


---
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 #2176: [ZEPPELIN-2300] SHOULD NOT update paragraph text when ...

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2176
  
@FRosner 

**How do I get the remote changes / discard my local changes**

- Zeppelin will synchronize text automatically. That's the reason why it 
doesn't have button for that. 
- But if Zeppelin keep local changes, we need some buttons or method for 
synchronizing text. (e.g update text for every 10 seconds if we don't have 
local change).

It will be another feature we need to develop soon. IMO, it beyond the 
scope of 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] zeppelin issue #2177: [ZEPPELIN-2301] DON'T overwrite editor text when note ...

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2177
  
@FRosner Anything would be greatly appreciated. For example trying this PR, 
suggestion for how to write test code for this, and so on.

regarding to triggering auto-save, Zeppelin send `startSavveTimer` 
broadcast message, but there is no `$scope.$on('startSaveTimer', ...)`. That's 
the reason why auto save is not working properly.

```
app/notebook/paragraph/paragraph.controller.js
602:$scope.$broadcast('startSaveTimer');
```


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

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

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2174
  
@AhyoungRyu pagination DOM should be located outside of `ng-repeat` for 
helium containers.

https://cloud.githubusercontent.com/assets/4968473/24344271/9e910240-1305-11e7-86f1-51438b9a76c3.png;>



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

[GitHub] zeppelin issue #2134: [ZEPPELIN-2257] notification about incompleteness of d...

[tinkoff-dwh]

Github user tinkoff-dwh commented on the issue:

https://github.com/apache/zeppelin/pull/2134
  
travis does not work (build was not created for last commit)


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

[GitHub] zeppelin issue #2134: [ZEPPELIN-2257] notification about incompleteness of d...

[tinkoff-dwh]

Github user tinkoff-dwh commented on the issue:

https://github.com/apache/zeppelin/pull/2134
  
@Leemoonsoo 
Yes you were right, this margin from alert (bootstreap class). fix it

![1](https://cloud.githubusercontent.com/assets/25951039/24343498/35b0d806-12e0-11e7-8da4-0f0e30ac4124.png)



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