date:20170109

[GitHub] zeppelin issue #1861: ZEPPELIN-1293. Livy Interpreter: Automatically attach ...

2017-01-09 Thread felixcheung

Github user felixcheung commented on the issue:

https://github.com/apache/zeppelin/pull/1861
  
LGTM.
what is the bug in LivySparkSQLInterpreter - should we have a JIRA 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 issue #1879: [HOTFIX : ZEPPELIN-1932] paragraph blur error

2017-01-09 Thread minahlee

Github user minahlee commented on the issue:

https://github.com/apache/zeppelin/pull/1879
  
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 #1880: ZEPPELIN-1918. Fix build with Spark 2.1.0

2017-01-09 Thread zjffdu

GitHub user zjffdu opened a pull request:

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

ZEPPELIN-1918. Fix build with Spark 2.1.0

### What is this PR for?
It's my misunderstanding of `SPARK_VER` in travis. It is only used for 
downloading spark distribution. We need to specify spark profile explicitly for 
building with specific version of spark. This PR add new profile for spark 2.1 
and fix the build issue with spark 2.1.0 because `SecurityManager` changes its 
constructor signature in spark 2.1 



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

### Todos
* [ ] - Task

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

### How should this be tested?
Build with spark 2.1.0 and tested it manually as below screenshot.

### Screenshots (if appropriate)

![image](https://cloud.githubusercontent.com/assets/164491/21797414/d586aa04-d749-11e6-8c6f-3b12e9e2ae2d.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/zjffdu/zeppelin ZEPPELIN-1918

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

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


commit e4d0e294d2fef45906b54cb8245fac5e8248e4eb
Author: Jeff Zhang 
Date:   2017-01-10T07:09:49Z

ZEPPELIN-1918. Fix build with Spark 2.1.0




---
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 #1879: [HOTFIX : ZEPPELIN-1932] paragraph blur error

2017-01-09 Thread cloverhearts

GitHub user cloverhearts reopened a pull request:

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

[HOTFIX : ZEPPELIN-1932] paragraph blur error

### What is this PR for?
When one or more hidden editors are present, clicking on the editor will 
cause a blur error.
This means that when a paragraph is hidden through ng-if,
Caused by calling the blur method in the absence of an editor object.

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

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

### How should this be tested?
1. create paragraph and open debug console.
2. enable hide paragraph.
3. page refresh
4. click to anywhere paragraph.

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


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

$ git pull https://github.com/cloverhearts/zeppelin 
hotfix/paragraphOnfocusEvent

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

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


commit c2f99adbab3e7a8b51543d2e04a5c09bc28955d5
Author: cloverhearts 
Date:   2017-01-10T06:18:14Z

bug fixed when paragraph for not rendering onReceived broadcast event




---
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 #1879: [HOTFIX : ZEPPELIN-1932] paragraph blur error

2017-01-09 Thread cloverhearts

Github user cloverhearts closed the pull request at:

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


---
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 #1850: [ZEPPELIN-1731] Fix unexpected EditOnDoubleClic...

2017-01-09 Thread asfgit

Github user asfgit closed the pull request at:

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


---
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 #1845: [ZEPPELIN-1906] Use multiple InterpreterResult for dis...

2017-01-09 Thread prabhjyotsingh

Github user prabhjyotsingh commented on the issue:

https://github.com/apache/zeppelin/pull/1845
  
@astroshim do you have some cycle to review this?


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

[GitHub] zeppelin issue #1787: ZEPPELIN-1815. Support Spark 2.1

2017-01-09 Thread zjffdu

Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/1787
  
Sure, let me fix 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 #1787: ZEPPELIN-1815. Support Spark 2.1

2017-01-09 Thread felixcheung

Github user felixcheung commented on the issue:

https://github.com/apache/zeppelin/pull/1787
  
Let's get this fix ASAP - we are going to cut 0.7 release in 2 days



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

branch-0.7 cut

2017-01-09 Thread Mina Lee

Hi,

It's been almost 3 month since we did 0.6.2 release and there were number
of improvements and bug fixes.
Most of the items that we planned for 0.7.0 release [1] are ready
so I am planning to cut branch-0.7 on 10th Jan 11pm(PST).

After branch cut, bug fixes, documentation patches and issues linked as a
blocker in jira [2] will be merged both to branch-0.7, master branch but
new features will be merged only to master branch.

Thanks,
Mina

[1] https://cwiki.apache.org/confluence/display/ZEPPELIN/Zeppelin+Roadmap
[2] https://issues.apache.org/jira/browse/ZEPPELIN-1795

[GitHub] zeppelin pull request #1879: [HOTFIX : ZEPPELIN-1932] paragraph blur error

2017-01-09 Thread cloverhearts

GitHub user cloverhearts opened a pull request:

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

[HOTFIX : ZEPPELIN-1932] paragraph blur error

### What is this PR for?
When one or more hidden editors are present, clicking on the editor will 
cause a blur error.
This means that when a paragraph is hidden through ng-if,
Caused by calling the blur method in the absence of an editor object.

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

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

### How should this be tested?
1. create paragraph and open debug console.
2. enable hide paragraph.
3. page refresh
4. click to anywhere paragraph.

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


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

$ git pull https://github.com/cloverhearts/zeppelin 
hotfix/paragraphOnfocusEvent

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

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


commit c2f99adbab3e7a8b51543d2e04a5c09bc28955d5
Author: cloverhearts 
Date:   2017-01-10T06:18:14Z

bug fixed when paragraph for not rendering onReceived broadcast event




---
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 #1787: ZEPPELIN-1815. Support Spark 2.1

2017-01-09 Thread zjffdu

Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/1787
  
ping @ejono Do you want to contribute it ? If not, I will fix 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 #1842: [ZEPPELIN-1619] Load js package as a plugin visualizat...

2017-01-09 Thread 1ambda

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/1842
  
Let me review this PR. I wil comment again :) 


---
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 #1842: [ZEPPELIN-1619] Load js package as a plugin visualizat...

2017-01-09 Thread cloverhearts

Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/1842
  
Awesome! 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 #1877: [ZEPPELIN-1930](HotFix) PythonInterpreter syntax error...

2017-01-09 Thread cloverhearts

Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/1877
  
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 #1877: [ZEPPELIN-1930](HotFix) PythonInterpreter syntax error...

2017-01-09 Thread Leemoonsoo

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/1877
  
LGTM and merge to master if there're no more discussions


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

[GitHub] zeppelin issue #1875: [ZEPPELIN-1926] Remove grunt googlefonts task

2017-01-09 Thread 1ambda

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/1875
  
@Leemoonsoo I moved all font-related licenses from `bin_license` to 
`/LICENSE`
Aldo remove rat exclusion in `zeppeiln-web/pom.xml` for `google-fonts.css` 
because it is managed by us now.


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

[GitHub] zeppelin issue #1877: [ZEPPELIN-1930](HotFix) PythonInterpreter syntax error...

2017-01-09 Thread khalidhuseynov

Github user khalidhuseynov commented on the issue:

https://github.com/apache/zeppelin/pull/1877
  
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 #1878: add yarn_error.log in gitignore

2017-01-09 Thread cloverhearts

GitHub user cloverhearts opened a pull request:

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

add yarn_error.log in gitignore

### What is this PR for?
Currently zeppelin is built from yarn.
Therefore, we need to add a log to gitignore.

### What type of PR is it?
Improvement

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

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


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

$ git pull https://github.com/cloverhearts/zeppelin ZEPPELIN-1931

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

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


commit 7561abb6789336e28964949099f2d11778d64028
Author: cloverhearts 
Date:   2017-01-09T20:22:08Z

add yarn_error.log in gitignore




---
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-1931) we should be add yarn_error.log on gitignore.

2017-01-09 Thread CloverHearts (JIRA)

CloverHearts created ZEPPELIN-1931:
--

 Summary: we should be add yarn_error.log on gitignore.
 Key: ZEPPELIN-1931
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1931
 Project: Zeppelin
  Issue Type: Improvement
Reporter: CloverHearts
Assignee: CloverHearts


currently,
Currently zeppelin is built from yarn.
Therefore, we need to add a log to gitignore.




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

[GitHub] zeppelin issue #1789: [MINOR] Optimize watchers of paragraph results

2017-01-09 Thread Leemoonsoo

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/1789
  
Tested and LGTM. Thanks @cuspymd for the nice optimization!

Merge to master if no more discussions.


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

[GitHub] zeppelin issue #1852: [ZEPPELIN-1910] DON'T show the same dialogs multiple t...

2017-01-09 Thread Leemoonsoo

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/1852
  
Thanks @1ambda for the fix.
LGTM and merge if 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 #1877: [ZEPPELIN-1930](HotFix) PythonInterpreter synta...

2017-01-09 Thread astroshim

GitHub user astroshim reopened a pull request:

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

[ZEPPELIN-1930](HotFix) PythonInterpreter syntax error.

### What is this PR for?
This PR fixes syntax error of PythonInterpreter.


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


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

### How should this be tested?
Please run following code on the paragraph of PythonInterpreter.
```
for x in range(0,3):  print ("hi")
```

### Screenshots (if appropriate)
- before

![image](https://cloud.githubusercontent.com/assets/3348133/21763102/fdf3fada-d610-11e6-8e92-310aec1968ad.png)

- after

![image](https://cloud.githubusercontent.com/assets/3348133/21763159/4a0aec26-d611-11e6-955b-be0b86455a34.png)


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


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

$ git pull https://github.com/astroshim/zeppelin ZEPPELIN-1930

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

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


commit 5a7e1b3cbaf2d98f1b38fa6c3449b2aa73ff9e65
Author: astroshim 
Date:   2017-01-09T10:08:48Z

fix syntax error.

commit 573140fe3ccecd7331e71ece53202d51ca2c2ab3
Author: astroshim 
Date:   2017-01-09T14:49:27Z

add test-case




---
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 #1877: [ZEPPELIN-1930](HotFix) PythonInterpreter synta...

2017-01-09 Thread astroshim

Github user astroshim closed the pull request at:

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


---
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 #1877: [ZEPPELIN-1930](HotFix) PythonInterpreter syntax error...

2017-01-09 Thread astroshim

Github user astroshim commented on the issue:

https://github.com/apache/zeppelin/pull/1877
  
@agoodm pyspark interpreter is working well.

![image](https://cloud.githubusercontent.com/assets/3348133/21768320/e79bebe0-d62d-11e6-8878-3c837fb7938f.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 #1877: [ZEPPELIN-1930](HotFix) PythonInterpreter syntax error...

2017-01-09 Thread 1ambda

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/1877
  
I faced the same problem too. Thanks for fix!


---
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 #1868: [ZEPPELIN-1917] Improve python.conda interpreter

2017-01-09 Thread 1ambda

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/1868
  
@Leemoonsoo Thanks for review! 

If https://github.com/apache/zeppelin/pull/1874 is merged soon, I can 
rewrite the whole `conda env *` commands based on #1874 
since current implementation requires some formatting. 


---
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 #1877: [ZEPPELIN-1930](HotFix) PythonInterpreter syntax error...

2017-01-09 Thread agoodm

Github user agoodm commented on the issue:

https://github.com/apache/zeppelin/pull/1877
  
I am on vacation right now so I can't thoroughly examine this, but have you 
confirmed that this isn't a problem for the pyspark interpreter? 


---
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 #1864: [ZEPPELIN-1921] missing close in closeAndRemove...

2017-01-09 Thread cloverhearts

Github user cloverhearts closed the pull request at:

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


---
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 #1864: [ZEPPELIN-1921] missing close in closeAndRemove...

2017-01-09 Thread cloverhearts

GitHub user cloverhearts reopened a pull request:

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

[ZEPPELIN-1921] missing close in closeAndRemoveInterpreterGroup method

### What is this PR for?
The problem is that some code in the closeAndRemoveInterpreterGroup method 
of InterpreterSetting partially closes.

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

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

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


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

$ git pull https://github.com/cloverhearts/zeppelin ZEPPELIN-1921

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

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


commit 0ebed445e44dff3538e546e4dae92c76851d9033
Author: cloverhearts 
Date:   2017-01-07T09:27:51Z

fixed missing for close

commit 2188b1bbe93b32138c9449c56a8b493d1bc7b874
Author: cloverhearts 
Date:   2017-01-07T11:01:21Z

change Linkedlist to LinkedHashSet

commit 59c9c761b3d5e1dc16a5bf330be082b0fcac93dc
Author: cloverhearts 
Date:   2017-01-08T05:34:03Z

implement testcase

commit 546ee8549e0c10cdc7535e5b9462f945ad888394
Author: cloverhearts 
Date:   2017-01-08T05:34:40Z

Revert "change Linkedlist to LinkedHashSet"

This reverts commit 2188b1bbe93b32138c9449c56a8b493d1bc7b874.

commit e25f3114956b9e7fc53d32615a76a0febc05463c
Author: cloverhearts 
Date:   2017-01-08T06:25:47Z

interpreter test case and replace logic

commit 2482be6c83ce4b784af20c9f69b4097d46cef035
Author: cloverhearts 
Date:   2017-01-08T06:42:05Z

container method -> isEqualInterpreterKey method

commit b0a93969df652900cf9829505322a0fd9b2091fa
Author: cloverhearts 
Date:   2017-01-08T07:16:07Z

test case and replace logic

commit a105adf68b09d0be535cd5c55e69132b2892ec74
Author: cloverhearts 
Date:   2017-01-09T08:48:04Z

Merge branch 'master' into ZEPPELIN-1921




---
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 #1747: [MINOR] Remove unused import. Naming convention.

2017-01-09 Thread bitchelov

Github user bitchelov commented on the issue:

https://github.com/apache/zeppelin/pull/1747
  
@lresende is it right?


---
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 #1846: ZEPPELIN-1770. Restart only the client user's interpre...

2017-01-09 Thread Leemoonsoo

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/1846
  
@zjffdu Thanks for the patch!

I also think this PR deserves a unittest to make sure correct restart 
behavior, like @felixcheung mentioned, if it is not too much difficult.


---
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 #1877: [ZEPPELIN-1930](HotFix) PythonInterpreter syntax error...

2017-01-09 Thread Leemoonsoo

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/1877
  
Thanks for the fix. \cc @agoodm 

How about add an unittest for this case in 
https://github.com/apache/zeppelin/blob/master/python/src/test/java/org/apache/zeppelin/python/PythonInterpreterTest.java,
 if it is not too difficult?


---
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 #1860: [ZEPPELIN-1848] add option for S3 KMS key region

2017-01-09 Thread Leemoonsoo

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/1860
  
LGTM and merge to master if no further discussions


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

[GitHub] zeppelin pull request #1877: [ZEPPELIN-1930](HotFix) PythonInterpreter synta...

2017-01-09 Thread astroshim

GitHub user astroshim opened a pull request:

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

[ZEPPELIN-1930](HotFix) PythonInterpreter syntax error.

### What is this PR for?
This PR fixes syntax error of PythonInterpreter.


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


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

### How should this be tested?
Please run following code on the paragraph of PythonInterpreter.
```
for x in range(0,3):  print ("hi")
```

### Screenshots (if appropriate)
- before

![image](https://cloud.githubusercontent.com/assets/3348133/21763102/fdf3fada-d610-11e6-8e92-310aec1968ad.png)

- after

![image](https://cloud.githubusercontent.com/assets/3348133/21763159/4a0aec26-d611-11e6-955b-be0b86455a34.png)


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


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

$ git pull https://github.com/astroshim/zeppelin ZEPPELIN-1930

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

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


commit 5a7e1b3cbaf2d98f1b38fa6c3449b2aa73ff9e65
Author: astroshim 
Date:   2017-01-09T10:08:48Z

fix syntax error.




---
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 #1812: [ZEPPELIN-1850] Use yarn instead of npm to redu...

2017-01-09 Thread asfgit

Github user asfgit closed the pull request at:

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


---
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 #1834: [ZEPPELIN-1864] Improvement to show folder and note af...

2017-01-09 Thread soralee

Github user soralee commented on the issue:

https://github.com/apache/zeppelin/pull/1834
  
@AhyoungRyu I updated the filter of Navbar. 
But, the folder of notes in navbar don't have previous status. Because If 
using the hidden value of the note, it works together both the filter in the 
home and navbar.

![z1834_u](https://cloud.githubusercontent.com/assets/8110458/21762702/9350b578-d69d-11e6-9284-03e14c207f3b.gif)
I think it will take more time to add this feature so it would be nice to 
improve this part by separating 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-1930) SyntaxError on PythonInterpreter

2017-01-09 Thread Shim HyungSung (JIRA)

Shim HyungSung created ZEPPELIN-1930:


 Summary: SyntaxError on PythonInterpreter
 Key: ZEPPELIN-1930
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1930
 Project: Zeppelin
  Issue Type: Bug
Affects Versions: 0.7.0
Reporter: Shim HyungSung


I got {code}SyntaxError: invalid syntax{code} when running for statement like 
following.

{code}
%python.python
for x in range(0,3):  print ("... aaa")
{code}

The output is 
{code}
File "", line 2
z._displayhook()
^
SyntaxError: invalid syntax
{code}



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

[GitHub] zeppelin issue #1872: [ZEPPELIN-1922] Exclude jackson-core and jackson-datab...

2017-01-09 Thread jongyoul

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/1872
  
You don't have to make two PRs for adopting multiple branches. We can merge 
it into several branches with one commit if there's no conflict. Can you please 
close 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 #1861: ZEPPELIN-1293. Livy Interpreter: Automatically attach ...

2017-01-09 Thread prabhjyotsingh

Github user prabhjyotsingh commented on the issue:

https://github.com/apache/zeppelin/pull/1861
  
Tested locally, looks good.


---
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 #1864: [ZEPPELIN-1921] missing close in closeAndRemove...

2017-01-09 Thread cloverhearts

Github user cloverhearts closed the pull request at:

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


---
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 #1875: [ZEPPELIN-1926] Remove grunt googlefonts task

2017-01-09 Thread jongyoul

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/1875
  
@1ambda Does it reduce the build time of web module?


---
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 #1874: [ZEPPELIN-1914] Preserve spaces, newlines in text outp...

2017-01-09 Thread Leemoonsoo

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/1874
  
LGTM and merge to master if no further discussions.


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

[jira] [Created] (ZEPPELIN-1929) need to fix the output format of PythonInterpreter

2017-01-09 Thread Shim HyungSung (JIRA)

Shim HyungSung created ZEPPELIN-1929:


 Summary: need to fix the output format of PythonInterpreter 
 Key: ZEPPELIN-1929
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1929
 Project: Zeppelin
  Issue Type: Bug
Reporter: Shim HyungSung


When i execute following command in python paragraph, 
```
%python.python
def myfn():
  for x in range(0,3):
  
  
  
  
print ("aaa")

myfn()
```

the output of paragraph is like below.
```
... ... ... ... ... ... ... aaa
aaa
aaa
```




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

[GitHub] zeppelin issue #1868: [ZEPPELIN-1917] Improve python.conda interpreter

2017-01-09 Thread Leemoonsoo

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/1868
  
Great improvement! Tested and LGTM.

Is it on purpose not supporting `conda env remove` ?


---
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 #1861: ZEPPELIN-1293. Livy Interpreter: Automatically attach ...

2017-01-09 Thread zjffdu

Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/1861
  
@felixcheung I have addressed the comments and also fix one bug in 
LivySparkSQLInterpreter, and update the screenshot of testing in PR 
description. 


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

[GitHub] zeppelin issue #1838: [ZEPPELIN-1832] Fixed a bug in zombie process when Zep...

2017-01-09 Thread minahlee

Github user minahlee commented on the issue:

https://github.com/apache/zeppelin/pull/1838
  
Thx for the fix. I will merge this one as temporary fix, but I will keep 
the jira issue open until we come up with better solution.


---
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 #1876: [ZEPPELIN-1927] Remove useless function wrapping in al...

2017-01-09 Thread cloverhearts

Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/1876
  
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 #1758: [ZEPPELIN-1787] Add an example of Flink Notebook

2017-01-09 Thread AlexanderShoshin

Github user AlexanderShoshin commented on the issue:

https://github.com/apache/zeppelin/pull/1758
  
Sorry, I was not able to work on this issue during last weeks.
@AhyoungRyu, I will make the corrections soon.
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 #1030: [ZEPPELIN-1023] Add more credential apis.

2017-01-09 Thread ChrisAdvance

Github user ChrisAdvance commented on the issue:

https://github.com/apache/zeppelin/pull/1030
  
Does the "Connection refused" problem fixed yet?


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

[GitHub] zeppelin issue #1875: [ZEPPELIN-1926] Remove grunt googlefonts task

2017-01-09 Thread 1ambda

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/1875
  
@Leemoonsoo Thanks for detailed explanation. I will take a look.


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

[GitHub] zeppelin issue #1875: [ZEPPELIN-1926] Remove grunt googlefonts task

2017-01-09 Thread Leemoonsoo

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/1875
  
This PR makes zeppelin source distribution package contains font files.
Therefore, related font license should be moved from 
[`/zeppelin-distribution/src/bin-license/LICENSE`](https://github.com/apache/zeppelin/blob/master/zeppelin-distribution/src/bin_license/LICENSE)
 to [`/LICENSE`](https://github.com/apache/zeppelin/blob/master/LICENSE).

And license of each font may different. So each license of font need to be 
listed in [`/LICENSE`](https://github.com/apache/zeppelin/blob/master/LICENSE) 
file. 

@1ambda Could you take care of license? 


---
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 #1838: [ZEPPELIN-1832] Fixed a bug in zombie process when Zep...

2017-01-09 Thread jongyoul

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/1838
  
@cloverhearts The last travis doesn't look related error.


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

53 matches

Mail list logo