[GitHub] zeppelin issue #1929: [ZEPPELIN-1997] Added derbylog in .gitignore

2017-02-01 Thread cloverhearts
Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/1929
  
@jongyoul 
Fixed :)
will not track all derby.log 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 #1886: [ZEPPELIN-1876] improved comptetion with schema/table/...

2017-01-31 Thread cloverhearts
Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/1886
  
@sotnich 
I was test.
LGTM.

I have a question.
Is it possible to only support pgsql? (actually, i am mysql/maria user)


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

2017-01-23 Thread cloverhearts
Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/1864
  
@jongyoul ping~


---
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 #1930: [ZEPPELIN-1886] implementation z.getZeppelinJob...

2017-01-22 Thread cloverhearts
Github user cloverhearts closed the pull request at:

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


---
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 #1930: [ZEPPELIN-1886] implementation z.getZeppelinJob...

2017-01-22 Thread cloverhearts
GitHub user cloverhearts reopened a pull request:

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

[ZEPPELIN-1886] implementation z.getZeppelinJobStatus 

### What is this PR for?
You can get the state of a paragraph through ZeppelinContext.
This allows you to implement code according to the paragraph condition.

related
https://github.com/apache/zeppelin/pull/1799

### What type of PR is it?
Feature

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

### How should this be tested?

1. run paragraph.
2. Record the noteid and paragraph id of the paragraph you have run.
3. You can use the following code:
for example
```
%spark
z.getJobStatus("noteID", "paragraphId").name()
z.getJobStatus("2C8D89Y9N", "20170121-042805_156018837").isFinished()
z.getJobStatus("2C8D89Y9N", "20170121-042805_156018837").isAbort()
z.getJobStatus("2C8D89Y9N", "20170121-042805_156018837").isError()
z.getJobStatus("2C8D89Y9N", "20170121-042805_156018837").isPending()
z.getJobStatus("2C8D89Y9N", "20170121-042805_156018837").isRunning()
```

### Screenshots (if appropriate)

![zeppelinstatus](https://cloud.githubusercontent.com/assets/10525473/22175433/770168b2-dfa9-11e6-8471-5dfa92e56eaa.png)

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


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

$ git pull https://github.com/cloverhearts/zeppelin 
ZEPPELIN-GET-PARAGRAPH-STATUS

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

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


commit 08f5120bc3ff7c1bc7c32d694e6f9da8185aeb8e
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2016-12-30T22:29:38Z

extends z.status on RemoteWorks

commit a522bafcad446fafea590d09ecce4a00edf4065a
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-01T05:53:09Z

implement check status logic in workflow

commit bb7308d39c3eeed2162d6fd851b3b63c82247742
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-21T15:10:10Z

add status getter

commit f2c7df4f99f8db1b2f4b0268f90079226f7c38c4
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-21T20:08:42Z

change method name

commit 995b79c57abe8c650be7a534ce3fe8601fd13c56
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-21T20:55:01Z

added test case

commit d6e0879ca2a22580aca0b5bfa9667ab30e1f30ca
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-21T21:43:09Z

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 pull request #1930: [ZEPPELIN-1886] implementation z.getZeppelinJob...

2017-01-21 Thread cloverhearts
GitHub user cloverhearts reopened a pull request:

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

[ZEPPELIN-1886] implementation z.getZeppelinJobStatus 

### What is this PR for?
You can get the state of a paragraph through ZeppelinContext.
This allows you to implement code according to the paragraph condition.

related
https://github.com/apache/zeppelin/pull/1799

### What type of PR is it?
Feature

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

### How should this be tested?

1. run paragraph.
2. Record the noteid and paragraph id of the paragraph you have run.
3. You can use the following code:
for example
```
%spark
z.getJobStatus("noteID", "paragraphId").name()
z.getJobStatus("2C8D89Y9N", "20170121-042805_156018837").isFinished()
z.getJobStatus("2C8D89Y9N", "20170121-042805_156018837").isAbort()
z.getJobStatus("2C8D89Y9N", "20170121-042805_156018837").isError()
z.getJobStatus("2C8D89Y9N", "20170121-042805_156018837").isPending()
z.getJobStatus("2C8D89Y9N", "20170121-042805_156018837").isRunning()
```

### Screenshots (if appropriate)

![zeppelinstatus](https://cloud.githubusercontent.com/assets/10525473/22175433/770168b2-dfa9-11e6-8471-5dfa92e56eaa.png)

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


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

$ git pull https://github.com/cloverhearts/zeppelin 
ZEPPELIN-GET-PARAGRAPH-STATUS

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

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


commit 08f5120bc3ff7c1bc7c32d694e6f9da8185aeb8e
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2016-12-30T22:29:38Z

extends z.status on RemoteWorks

commit a522bafcad446fafea590d09ecce4a00edf4065a
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-01T05:53:09Z

implement check status logic in workflow

commit bb7308d39c3eeed2162d6fd851b3b63c82247742
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-21T15:10:10Z

add status getter

commit f2c7df4f99f8db1b2f4b0268f90079226f7c38c4
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-21T20:08:42Z

change method name

commit 995b79c57abe8c650be7a534ce3fe8601fd13c56
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-21T20:55:01Z

added test case

commit d6e0879ca2a22580aca0b5bfa9667ab30e1f30ca
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-21T21:43:09Z

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 pull request #1930: [ZEPPELIN-1886] implementation z.getZeppelinJob...

2017-01-21 Thread cloverhearts
Github user cloverhearts closed the pull request at:

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


---
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 #1930: [ZEPPELIN-1886] implementation z.getZeppelinJob...

2017-01-21 Thread cloverhearts
GitHub user cloverhearts opened a pull request:

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

[ZEPPELIN-1886] implementation z.getZeppelinJobStatus 

### What is this PR for?
You can get the state of a paragraph through ZeppelinContext.
This allows you to implement code according to the paragraph condition.

related
https://github.com/apache/zeppelin/pull/1799

### What type of PR is it?
Feature

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

### How should this be tested?

1. run paragraph.
2. Record the noteid and paragraph id of the paragraph you have run.
3. You can use the following code:
for example
```
z.getZeppelinJobStatus("notid", "paragraphid").getStatus()
z.getZeppelinJobStatus("2C8D89Y9N", 
"20170121-042805_156018837").isFinished()
z.getZeppelinJobStatus("2C8D89Y9N", "20170121-042805_156018837").isAbort()
z.getZeppelinJobStatus("2C8D89Y9N", "20170121-042805_156018837").isError()
z.getZeppelinJobStatus("2C8D89Y9N", "20170121-042805_156018837").isPending()
z.getZeppelinJobStatus("2C8D89Y9N", "20170121-042805_156018837").isRunning()
```

### Screenshots (if appropriate)

![zeppelinstatus](https://cloud.githubusercontent.com/assets/10525473/22175433/770168b2-dfa9-11e6-8471-5dfa92e56eaa.png)

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


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

$ git pull https://github.com/cloverhearts/zeppelin 
ZEPPELIN-GET-PARAGRAPH-STATUS

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

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


commit 08f5120bc3ff7c1bc7c32d694e6f9da8185aeb8e
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2016-12-30T22:29:38Z

extends z.status on RemoteWorks

commit a522bafcad446fafea590d09ecce4a00edf4065a
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-01T05:53:09Z

implement check status logic in workflow

commit bb7308d39c3eeed2162d6fd851b3b63c82247742
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-21T15:10:10Z

add status getter




---
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 #1721: [ZEPPELIN-969] order by note name in job menu

2017-01-21 Thread cloverhearts
Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/1721
  
CI Green


---
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 #1928: ZEPPELIN-598 ] Dynamic loading for Interpreter and API

2017-01-21 Thread cloverhearts
Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/1928
  
LOG FILE Limit 4MB Over


---
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 #1929: [ZEPPELIN-1997] Added derbylog in .gitignore

2017-01-21 Thread cloverhearts
GitHub user cloverhearts opened a pull request:

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

[ZEPPELIN-1997] Added derbylog in .gitignore

### What is this PR for?
Added derbylog in .gitignore
Sometime created derby.log in bin directory.
We should stop tracking derbylog
derby.log
```
1 
2 Thu Jan 19 23:45:08 PST 2017:
3 Booting Derby version The Apache Software Foundation - Apache Derby - 
10.10.2.0 - (1582446): instance a816c00e-0159-bad6-0f44-30e6b528
4 on database directory 
/Users/cloverhearts/Source/nflabs/zeppelin/bin/metastore_db with class loader 
org.apache.spark.sql.hive.client.IsolatedClientLoader$$anon$1@74101877
5 Loaded from 
file:/Users/cloverhearts/Source/nflabs/zeppelin/interpreter/spark/dep/zeppelin-spark-dependencies_2.10-0.7.0-SNAPSHOT.jar
6 java.vendor=Oracle Corporation
7 java.runtime.version=1.8.0_101-b13
8 user.dir=/Users/cloverhearts/Source/nflabs/zeppelin/bin
9 os.name=Mac OS X
10 os.arch=x86_64
11 os.version=10.12.2
12 derby.system.home=null
13 Database Class Loader started - derby.database.classpath=''
```

### What type of PR is it?
 Improvement

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

### 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-DERBYLOG

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

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


commit e4765c9a79efc1dc60c23bdea624dcaf631b24b8
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-21T13:59:21Z

added bin/derby.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-1997) exclude source tracking for derby.log

2017-01-21 Thread CloverHearts (JIRA)
CloverHearts created ZEPPELIN-1997:
--

 Summary: exclude source tracking for derby.log
 Key: ZEPPELIN-1997
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1997
 Project: Zeppelin
  Issue Type: Bug
Reporter: CloverHearts
Assignee: CloverHearts


Sometime created derby.log in bin directory.
We should stop tracking derbylog


derby.log
  1 
  2 Thu Jan 19 23:45:08 PST 2017:
  3 Booting Derby version The Apache Software Foundation - Apache Derby - 
10.10.2.0 - (1582446): instance a816c00e-0159-bad6-0f44-30e6b528
  4 on database directory 
/Users/cloverhearts/Source/nflabs/zeppelin/bin/metastore_db with class loader 
org.apache.spark.sql.hive.client.IsolatedClientLoader$$anon$1@74101877
  5 Loaded from 
file:/Users/cloverhearts/Source/nflabs/zeppelin/interpreter/spark/dep/zeppelin-spark-dependencies_2.10-0.7.0-SNAPSHOT.jar
  6 java.vendor=Oracle Corporation
  7 java.runtime.version=1.8.0_101-b13
  8 user.dir=/Users/cloverhearts/Source/nflabs/zeppelin/bin
  9 os.name=Mac OS X
 10 os.arch=x86_64
 11 os.version=10.12.2
 12 derby.system.home=null
 13 Database Class Loader started - derby.database.classpath=''



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


[GitHub] zeppelin pull request #1928: ZEPPELIN-598 ] Dynamic loading for Interpreter ...

2017-01-21 Thread cloverhearts
Github user cloverhearts closed the pull request at:

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


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

2017-01-21 Thread cloverhearts
GitHub user cloverhearts reopened a pull request:

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

ZEPPELIN-598 ] Dynamic loading for Interpreter and API

### What is this PR for?

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

Feature

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

### How should this be tested?
1. Run to `mvn clean package -DskipTests`
2. Run to `mvn clean package -DskipTests -pl zeppelin-server --am`
3. run zeppelin.
4. move to interpreter menu on web ui.
   - check empty interpreter
5. call restapi
   
```
POST http://localhost:8080/api/interpreter/load/md/md
{"artifact":"org.apache.zeppelin:zeppelin-markdown:0.6.2", 
"className":"org.apache.zeppelin.markdown.Markdown"}
```

6. check interpreter menu to create interpreter `md` on web ui.
7. add interpreter setting `md`
8. run paragraph `md`
```
%md
Hello markdown
```
9. call unload restapi
```
DELETE 
http://localhost:8080/api/interpreter/unload/md2/md2/org.apache.zeppelin.markdown.Markdown
```
10. check delete `md` on web ui
11. restart to paragraph for `md` 
 if result is error status then well working.

### Screenshots (if appropriate)
[Click to link for 
screenshot](https://cloud.githubusercontent.com/assets/10525473/22174189/1b2cce6c-df8d-11e6-975f-333a502079ea.gif)


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


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

$ git pull https://github.com/cloverhearts/zeppelin dynamic-load-interpreter

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

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


commit 949ef81f21eb2d61441220143bcf8d558bed13a6
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-21T11:43:11Z

dynamic load interpreter rest api and interpreter factory logic

commit 1a2a75ef2db7c3a0b59bdc27d4cf427273b54621
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-21T11:55:31Z

remove meaningless return key




---
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 #1721: [ZEPPELIN-969] order by note name in job menu

2017-01-21 Thread cloverhearts
Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/1721
  
@AhyoungRyu 

![1](https://cloud.githubusercontent.com/assets/10525473/22174844/06990b72-df9d-11e6-942b-6f15102f17fc.png)

![2](https://cloud.githubusercontent.com/assets/10525473/22174843/0695b904-df9d-11e6-90d8-3b3fd0a361f5.png)

changed.

could you please review for 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 pull request #908: ZEPPELIN-598 ] Dynamic loading for Interpreter a...

2017-01-21 Thread cloverhearts
Github user cloverhearts closed the pull request at:

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


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


[GitHub] zeppelin issue #1864: [ZEPPELIN-1921] missing close in closeAndRemoveInterpr...

2017-01-21 Thread cloverhearts
Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/1864
  
@jongyoul TEST PASS
could you please review for 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 pull request #1928: ZEPPELIN-598 ] Dynamic loading for Interpreter ...

2017-01-21 Thread cloverhearts
GitHub user cloverhearts opened a pull request:

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

ZEPPELIN-598 ] Dynamic loading for Interpreter and API

### What is this PR for?

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

Feature

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

### How should this be tested?
1. Run to `mvn clean package -DskipTests`
2. Run to `mvn clean package -DskipTests -pl zeppelin-server --am`
3. run zeppelin.
4. move to interpreter menu on web ui.
   - check empty interpreter
5. call restapi
   
```
POST http://localhost:8080/api/interpreter/load/md/md
{"artifact":"org.apache.zeppelin:zeppelin-markdown:0.6.2", 
"className":"org.apache.zeppelin.markdown.Markdown"}
```

6. check interpreter menu to create interpreter `md` on web ui.
7. add interpreter setting `md`
8. run paragraph `md`
```
%md
Hello markdown
```
9. call unload restapi
```
DELETE 
http://localhost:8080/api/interpreter/unload/md2/md2/org.apache.zeppelin.markdown.Markdown
```
10. check delete `md` on web ui
11. restart to paragraph for `md` 
 if result is error status then well working.

### Screenshots (if appropriate)
[Click to link for 
screenshot](https://cloud.githubusercontent.com/assets/10525473/22174189/1b2cce6c-df8d-11e6-975f-333a502079ea.gif)


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


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

$ git pull https://github.com/cloverhearts/zeppelin dynamic-load-interpreter

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

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


commit 949ef81f21eb2d61441220143bcf8d558bed13a6
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-21T11:43:11Z

dynamic load interpreter rest api and interpreter factory logic




---
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: [VOTE] Release Apache Zeppelin 0.7.0 (RC1)

2017-01-21 Thread CloverHearts
+1

 

The Zeppelin 0.7 release includes some amazing features.

In particular, a major bug fix for the remote interpreter.

I am actively in favor of this release.

 

 

출발: Mina Lee 
회신 대상: 
날짜: 2017년 1월 21일 토요일 오전 3:17
받는 사람: , 
주제: [VOTE] Release Apache Zeppelin 0.7.0 (RC1)

 

Hi folks,

I propose the following RC to be released for the Apache Zeppelin 0.7.0 release.

The commit id is bcbe0855175f55eddd10b918303806eb5e5db091 which is
corresponds to the tag v0.7.0-rc1:

https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=commit;h=bcbe0855175f55eddd10b918303806eb5e5db091

The release archives (tgz), signature, and checksums are here
https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.7.0-rc1/

The release candidate consists of the following source distribution archive 

zeppelin-0.7.0.tgz

In addition, the following supplementary binary distributions are provided
for user convenience at the same location

zeppelin-0.7.0-bin-all.tgz
zeppelin-0.7.0-bin-netinst.tgz


The maven artifacts are here
https://repository.apache.org/content/repositories/orgapachezeppelin-1022

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=12336544=12316221

Vote will be open for next 72 hours (close at 3:30 am 24/Jan PST).

[ ] +1 approve
[ ] 0 no opinion
[ ] -1 disapprove (and reason why)



[GitHub] zeppelin pull request #1864: [ZEPPELIN-1921] missing close in closeAndRemove...

2017-01-21 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-21 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 <cloverhearts...@gmail.com>
Date:   2017-01-07T09:27:51Z

fixed missing for close

commit 2188b1bbe93b32138c9449c56a8b493d1bc7b874
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-07T11:01:21Z

change Linkedlist to LinkedHashSet

commit 59c9c761b3d5e1dc16a5bf330be082b0fcac93dc
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T05:34:03Z

implement testcase

commit 546ee8549e0c10cdc7535e5b9462f945ad888394
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T05:34:40Z

Revert "change Linkedlist to LinkedHashSet"

This reverts commit 2188b1bbe93b32138c9449c56a8b493d1bc7b874.

commit e25f3114956b9e7fc53d32615a76a0febc05463c
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T06:25:47Z

interpreter test case and replace logic

commit 2482be6c83ce4b784af20c9f69b4097d46cef035
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T06:42:05Z

container method -> isEqualInterpreterKey method

commit b0a93969df652900cf9829505322a0fd9b2091fa
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T07:16:07Z

test case and replace logic

commit a105adf68b09d0be535cd5c55e69132b2892ec74
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-09T08:48:04Z

Merge branch 'master' into ZEPPELIN-1921

commit 22473a219680b11d49649493b4615f39e32e7f00
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-16T06:51:16Z

change return logic

commit ca9ecfd46d805a2a07087a3e607435eb96c0ac22
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-17T19:28:51Z

Merge branch 'master' into ZEPPELIN-1921

# Conflicts:
#   
zeppelin-zengine/src/main/java/org/apache/zeppelin/interpreter/InterpreterSetting.java

commit d12ec573ea4fe167d85ac259bf52a2dee8bcae2d
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-17T20:12:51Z

missing brace

commit 6a2051c751d35983b5dbd804187752a9ae8b858f
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-17T20:20:30Z

method name change (master rebase)

commit 6b86dfd0ba84641a30ff5ad8e92329eeb2ceb30f
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-18T05:38:20Z

    compare logic change

commit e21287f1ea3b6c4c24c360c824f5b8c25fe4f8c4
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-18T05:47:37Z

apply other side

commit f39212c2d8f0dd0c030d4036ef841f6adb25e675
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-20T10:49:02Z

    fixed equals logic

commit 4ac76cfc5f79f7e12fd384741bdb9ed6df847951
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-20T21:38:17Z

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

2017-01-20 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 <cloverhearts...@gmail.com>
Date:   2017-01-07T09:27:51Z

fixed missing for close

commit 2188b1bbe93b32138c9449c56a8b493d1bc7b874
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-07T11:01:21Z

change Linkedlist to LinkedHashSet

commit 59c9c761b3d5e1dc16a5bf330be082b0fcac93dc
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T05:34:03Z

implement testcase

commit 546ee8549e0c10cdc7535e5b9462f945ad888394
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T05:34:40Z

Revert "change Linkedlist to LinkedHashSet"

This reverts commit 2188b1bbe93b32138c9449c56a8b493d1bc7b874.

commit e25f3114956b9e7fc53d32615a76a0febc05463c
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T06:25:47Z

interpreter test case and replace logic

commit 2482be6c83ce4b784af20c9f69b4097d46cef035
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T06:42:05Z

container method -> isEqualInterpreterKey method

commit b0a93969df652900cf9829505322a0fd9b2091fa
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T07:16:07Z

test case and replace logic

commit a105adf68b09d0be535cd5c55e69132b2892ec74
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-09T08:48:04Z

Merge branch 'master' into ZEPPELIN-1921

commit 22473a219680b11d49649493b4615f39e32e7f00
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-16T06:51:16Z

change return logic

commit ca9ecfd46d805a2a07087a3e607435eb96c0ac22
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-17T19:28:51Z

Merge branch 'master' into ZEPPELIN-1921

# Conflicts:
#   
zeppelin-zengine/src/main/java/org/apache/zeppelin/interpreter/InterpreterSetting.java

commit d12ec573ea4fe167d85ac259bf52a2dee8bcae2d
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-17T20:12:51Z

missing brace

commit 6a2051c751d35983b5dbd804187752a9ae8b858f
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-17T20:20:30Z

method name change (master rebase)

commit 6b86dfd0ba84641a30ff5ad8e92329eeb2ceb30f
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-18T05:38:20Z

    compare logic change

commit e21287f1ea3b6c4c24c360c824f5b8c25fe4f8c4
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-18T05:47:37Z

apply other side

commit f39212c2d8f0dd0c030d4036ef841f6adb25e675
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-20T10:49:02Z

fixed equals logic




---
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-20 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-20 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 <cloverhearts...@gmail.com>
Date:   2017-01-07T09:27:51Z

fixed missing for close

commit 2188b1bbe93b32138c9449c56a8b493d1bc7b874
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-07T11:01:21Z

change Linkedlist to LinkedHashSet

commit 59c9c761b3d5e1dc16a5bf330be082b0fcac93dc
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T05:34:03Z

implement testcase

commit 546ee8549e0c10cdc7535e5b9462f945ad888394
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T05:34:40Z

Revert "change Linkedlist to LinkedHashSet"

This reverts commit 2188b1bbe93b32138c9449c56a8b493d1bc7b874.

commit e25f3114956b9e7fc53d32615a76a0febc05463c
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T06:25:47Z

interpreter test case and replace logic

commit 2482be6c83ce4b784af20c9f69b4097d46cef035
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T06:42:05Z

container method -> isEqualInterpreterKey method

commit b0a93969df652900cf9829505322a0fd9b2091fa
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T07:16:07Z

test case and replace logic

commit a105adf68b09d0be535cd5c55e69132b2892ec74
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-09T08:48:04Z

Merge branch 'master' into ZEPPELIN-1921

commit 22473a219680b11d49649493b4615f39e32e7f00
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-16T06:51:16Z

change return logic

commit ca9ecfd46d805a2a07087a3e607435eb96c0ac22
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-17T19:28:51Z

Merge branch 'master' into ZEPPELIN-1921

# Conflicts:
#   
zeppelin-zengine/src/main/java/org/apache/zeppelin/interpreter/InterpreterSetting.java

commit d12ec573ea4fe167d85ac259bf52a2dee8bcae2d
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-17T20:12:51Z

missing brace

commit 6a2051c751d35983b5dbd804187752a9ae8b858f
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-17T20:20:30Z

method name change (master rebase)

commit 6b86dfd0ba84641a30ff5ad8e92329eeb2ceb30f
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-18T05:38:20Z

    compare logic change

commit e21287f1ea3b6c4c24c360c824f5b8c25fe4f8c4
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-18T05:47:37Z

apply other side

commit f39212c2d8f0dd0c030d4036ef841f6adb25e675
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-20T10:49:02Z

fixed equals logic




---
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-18 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-18 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 <cloverhearts...@gmail.com>
Date:   2017-01-07T09:27:51Z

fixed missing for close

commit 2188b1bbe93b32138c9449c56a8b493d1bc7b874
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-07T11:01:21Z

change Linkedlist to LinkedHashSet

commit 59c9c761b3d5e1dc16a5bf330be082b0fcac93dc
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T05:34:03Z

implement testcase

commit 546ee8549e0c10cdc7535e5b9462f945ad888394
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T05:34:40Z

Revert "change Linkedlist to LinkedHashSet"

This reverts commit 2188b1bbe93b32138c9449c56a8b493d1bc7b874.

commit e25f3114956b9e7fc53d32615a76a0febc05463c
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T06:25:47Z

interpreter test case and replace logic

commit 2482be6c83ce4b784af20c9f69b4097d46cef035
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T06:42:05Z

container method -> isEqualInterpreterKey method

commit b0a93969df652900cf9829505322a0fd9b2091fa
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T07:16:07Z

test case and replace logic

commit a105adf68b09d0be535cd5c55e69132b2892ec74
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-09T08:48:04Z

Merge branch 'master' into ZEPPELIN-1921

commit 22473a219680b11d49649493b4615f39e32e7f00
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-16T06:51:16Z

change return logic

commit ca9ecfd46d805a2a07087a3e607435eb96c0ac22
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-17T19:28:51Z

Merge branch 'master' into ZEPPELIN-1921

# Conflicts:
#   
zeppelin-zengine/src/main/java/org/apache/zeppelin/interpreter/InterpreterSetting.java

commit d12ec573ea4fe167d85ac259bf52a2dee8bcae2d
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-17T20:12:51Z

missing brace

commit 6a2051c751d35983b5dbd804187752a9ae8b858f
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-17T20:20:30Z

method name change (master rebase)

commit 6b86dfd0ba84641a30ff5ad8e92329eeb2ceb30f
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-18T05:38:20Z

    compare logic change

commit e21287f1ea3b6c4c24c360c824f5b8c25fe4f8c4
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-18T05:47:37Z

apply other side




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

2017-01-17 Thread cloverhearts
Github user cloverhearts commented on the issue:

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


---
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-17 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 <cloverhearts...@gmail.com>
Date:   2017-01-07T09:27:51Z

fixed missing for close

commit 2188b1bbe93b32138c9449c56a8b493d1bc7b874
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-07T11:01:21Z

change Linkedlist to LinkedHashSet

commit 59c9c761b3d5e1dc16a5bf330be082b0fcac93dc
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T05:34:03Z

implement testcase

commit 546ee8549e0c10cdc7535e5b9462f945ad888394
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T05:34:40Z

Revert "change Linkedlist to LinkedHashSet"

This reverts commit 2188b1bbe93b32138c9449c56a8b493d1bc7b874.

commit e25f3114956b9e7fc53d32615a76a0febc05463c
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T06:25:47Z

interpreter test case and replace logic

commit 2482be6c83ce4b784af20c9f69b4097d46cef035
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T06:42:05Z

container method -> isEqualInterpreterKey method

commit b0a93969df652900cf9829505322a0fd9b2091fa
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T07:16:07Z

test case and replace logic

commit a105adf68b09d0be535cd5c55e69132b2892ec74
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-09T08:48:04Z

Merge branch 'master' into ZEPPELIN-1921

commit 22473a219680b11d49649493b4615f39e32e7f00
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-16T06:51:16Z

change return logic

commit ca9ecfd46d805a2a07087a3e607435eb96c0ac22
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-17T19:28:51Z

Merge branch 'master' into ZEPPELIN-1921

# Conflicts:
#   
zeppelin-zengine/src/main/java/org/apache/zeppelin/interpreter/InterpreterSetting.java

commit d12ec573ea4fe167d85ac259bf52a2dee8bcae2d
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-17T20:12:51Z

missing brace

commit 6a2051c751d35983b5dbd804187752a9ae8b858f
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-17T20:20:30Z

method name change (master rebase)

commit 6b86dfd0ba84641a30ff5ad8e92329eeb2ceb30f
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-18T05:38:20Z

    compare logic change

commit e21287f1ea3b6c4c24c360c824f5b8c25fe4f8c4
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-18T05:47:37Z

apply other side




---
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 #1896: implementation test case for connect to exists ...

2017-01-16 Thread cloverhearts
GitHub user cloverhearts reopened a pull request:

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

implementation test case for connect to exists interpreter process

### What is this PR for?
We need test case for remote interpreter process ( connect to exists 
process)

### What type of PR is it?
[TEST case]

### What is the Jira issue?
none (jira problem now)

### 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 remoteInterpreterTEST

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

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


commit 87a5613f87b8e0e933be87a887da0206a4c6e15f
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-13T02:14:40Z

Implement test case for remote interpreter connect to exists process

commit 9d54daaea0bc3c1f771c01347c592fad13e1ac13
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-16T06:30:06Z

Merge branch 'master' into remoteInterpreterTEST

commit 1edbd1eaa9f578b6327007fe907af8885504ae16
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-16T06:35:20Z

Instance of RemoteInterpreter to mock




---
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 #1896: implementation test case for connect to exists ...

2017-01-16 Thread cloverhearts
Github user cloverhearts closed the pull request at:

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


---
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 #1896: implementation test case for connect to exists ...

2017-01-14 Thread cloverhearts
Github user cloverhearts closed the pull request at:

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


---
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 #1896: implementation test case for connect to exists ...

2017-01-14 Thread cloverhearts
GitHub user cloverhearts reopened a pull request:

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

implementation test case for connect to exists interpreter process

### What is this PR for?
We need test case for remote interpreter process ( connect to exists 
process)

### What type of PR is it?
[TEST case]

### What is the Jira issue?
none (jira problem now)

### 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 remoteInterpreterTEST

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

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


commit 87a5613f87b8e0e933be87a887da0206a4c6e15f
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-13T02:14:40Z

Implement test case for remote interpreter connect to exists 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 #1896: implementation test case for connect to exists ...

2017-01-13 Thread cloverhearts
Github user cloverhearts closed the pull request at:

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


---
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 #1896: implementation test case for connect to exists ...

2017-01-13 Thread cloverhearts
GitHub user cloverhearts reopened a pull request:

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

implementation test case for connect to exists interpreter process

### What is this PR for?
We need test case for remote interpreter process ( connect to exists 
process)

### What type of PR is it?
[TEST case]

### What is the Jira issue?
none (jira problem now)

### 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 remoteInterpreterTEST

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

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


commit 87a5613f87b8e0e933be87a887da0206a4c6e15f
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-13T02:14:40Z

Implement test case for remote interpreter connect to exists 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 #1899: [HOTFIX] Does not working settings menu in zepp...

2017-01-13 Thread cloverhearts
GitHub user cloverhearts opened a pull request:

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

[HOTFIX] Does not working settings menu in zeppelin web graph ui

### What is this PR for?
Does not working settings menu in zeppelin web graph ui

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

### How should this be tested?
1. toggle settings menu in zeppelin graph ui

### Screenshots (if appropriate)
 Before

![incorrect](https://cloud.githubusercontent.com/assets/10525473/21949815/1733ed6a-d9aa-11e6-92c8-8da98200cf43.gif)

 After

![correct](https://cloud.githubusercontent.com/assets/10525473/21949805/045c9a34-d9aa-11e6-86dc-445ce229f2a8.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/cloverhearts/zeppelin 
ZEEPELIN-SETTING-PROBLEM-WEB-UI

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

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


commit e3453b7fa41c75d10941273845a38b6a0f8f9609
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-14T00:02:55Z

invalid render life cycle for setting




---
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 #1896: implementation test case for connect to exists ...

2017-01-13 Thread cloverhearts
Github user cloverhearts closed the pull request at:

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


---
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 #1896: implementation test case for connect to exists ...

2017-01-12 Thread cloverhearts
GitHub user cloverhearts opened a pull request:

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

implementation test case for connect to exists interpreter process

### What is this PR for?
We need test case for remote interpreter process ( connect to exists 
process)

### What type of PR is it?
[TEST case]

### What is the Jira issue?
none (jira problem now)

### 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 remoteInterpreterTEST

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

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


commit 87a5613f87b8e0e933be87a887da0206a4c6e15f
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-13T02:14:40Z

Implement test case for remote interpreter connect to exists 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 issue #1879: [HOTFIX : ZEPPELIN-1932] paragraph blur error

2017-01-10 Thread cloverhearts
Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/1879
  
@soralee 
Sure :)

rebase is done.


---
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 <cloverhearts...@gmail.com>
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 #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 <cloverhearts...@gmail.com>
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 #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 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 <cloverhearts...@gmail.com>
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 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 <cloverhearts...@gmail.com>
Date:   2017-01-07T09:27:51Z

fixed missing for close

commit 2188b1bbe93b32138c9449c56a8b493d1bc7b874
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-07T11:01:21Z

change Linkedlist to LinkedHashSet

commit 59c9c761b3d5e1dc16a5bf330be082b0fcac93dc
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T05:34:03Z

implement testcase

commit 546ee8549e0c10cdc7535e5b9462f945ad888394
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T05:34:40Z

Revert "change Linkedlist to LinkedHashSet"

This reverts commit 2188b1bbe93b32138c9449c56a8b493d1bc7b874.

commit e25f3114956b9e7fc53d32615a76a0febc05463c
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T06:25:47Z

interpreter test case and replace logic

commit 2482be6c83ce4b784af20c9f69b4097d46cef035
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T06:42:05Z

container method -> isEqualInterpreterKey method

commit b0a93969df652900cf9829505322a0fd9b2091fa
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T07:16:07Z

test case and replace logic

commit a105adf68b09d0be535cd5c55e69132b2892ec74
Author: cloverhearts <cloverhearts...@gmail.com>
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 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 #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 pull request #1838: [ZEPPELIN-1832] Fixed a bug in zombie process w...

2017-01-08 Thread cloverhearts
Github user cloverhearts closed the pull request at:

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


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

2017-01-08 Thread cloverhearts
GitHub user cloverhearts reopened a pull request:

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

[ZEPPELIN-1832] Fixed a bug in zombie process when Zeppelin stopped.

### What is this PR for?
When Zeppelin stops, there is a problem.
Sometimes this happens to the test as well.
It is related to releasing the resources of the remote remote interpreter, 
and its order has been modified.

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

### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1832
### How should this be tested?
1. Zeppelin start
2. run paragraph for interpreter (for example, %spark println("Hello world")
3. Zeppelin stop
4. check to zombie process 
```
#jps 
```
When Zeppelin exits, the RemoteInterpreter process should not exist.

### 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-1832

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

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


commit f3d3406190009aefa3a24dcfef5305c743995fd6
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-05T12:11:40Z

add shutdown method

commit cabf83e8d357c784c200f211c38fd3eac1fe9d68
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-05T12:49:13Z

Zombie process issue mitigation.

commit 2e1ad7e054d9a3107861d0c6614de27fdc91696f
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-09T06:03:33Z

Merge branch 'master' into ZEPPELIN-1832




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

2017-01-08 Thread cloverhearts
Github user cloverhearts closed the pull request at:

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


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

2017-01-08 Thread cloverhearts
GitHub user cloverhearts reopened a pull request:

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

[ZEPPELIN-1832] Fixed a bug in zombie process when Zeppelin stopped.

### What is this PR for?
When Zeppelin stops, there is a problem.
Sometimes this happens to the test as well.
It is related to releasing the resources of the remote remote interpreter, 
and its order has been modified.

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

### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1832
### How should this be tested?
1. Zeppelin start
2. run paragraph for interpreter (for example, %spark println("Hello world")
3. Zeppelin stop
4. check to zombie process 
```
#jps 
```
When Zeppelin exits, the RemoteInterpreter process should not exist.

### 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-1832

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

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


commit f3d3406190009aefa3a24dcfef5305c743995fd6
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-05T12:11:40Z

add shutdown method

commit cabf83e8d357c784c200f211c38fd3eac1fe9d68
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-05T12:49:13Z

Zombie process issue mitigation.

commit 2e1ad7e054d9a3107861d0c6614de27fdc91696f
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-09T06:03:33Z

Merge branch 'master' into ZEPPELIN-1832




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

2017-01-08 Thread cloverhearts
GitHub user cloverhearts reopened a pull request:

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

[ZEPPELIN-1832] Fixed a bug in zombie process when Zeppelin stopped.

### What is this PR for?
When Zeppelin stops, there is a problem.
Sometimes this happens to the test as well.
It is related to releasing the resources of the remote remote interpreter, 
and its order has been modified.

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

### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1832
### How should this be tested?
1. Zeppelin start
2. run paragraph for interpreter (for example, %spark println("Hello world")
3. Zeppelin stop
4. check to zombie process 
```
#jps 
```
When Zeppelin exits, the RemoteInterpreter process should not exist.

### 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-1832

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

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


commit f3d3406190009aefa3a24dcfef5305c743995fd6
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-05T12:11:40Z

add shutdown method

commit cabf83e8d357c784c200f211c38fd3eac1fe9d68
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-05T12:49:13Z

Zombie process issue mitigation.

commit 2e1ad7e054d9a3107861d0c6614de27fdc91696f
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-09T06:03:33Z

Merge branch 'master' into ZEPPELIN-1832




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

2017-01-08 Thread cloverhearts
Github user cloverhearts closed the pull request at:

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


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

2017-01-08 Thread cloverhearts
GitHub user cloverhearts reopened a pull request:

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

[ZEPPELIN-1832] Fixed a bug in zombie process when Zeppelin stopped.

### What is this PR for?
When Zeppelin stops, there is a problem.
Sometimes this happens to the test as well.
It is related to releasing the resources of the remote remote interpreter, 
and its order has been modified.

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

### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1832
### How should this be tested?
1. Zeppelin start
2. run paragraph for interpreter (for example, %spark println("Hello world")
3. Zeppelin stop
4. check to zombie process 
```
#jps 
```
When Zeppelin exits, the RemoteInterpreter process should not exist.

### 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-1832

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

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


commit f3d3406190009aefa3a24dcfef5305c743995fd6
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-05T12:11:40Z

add shutdown method

commit cabf83e8d357c784c200f211c38fd3eac1fe9d68
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-05T12:49:13Z

Zombie process issue mitigation.




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

2017-01-08 Thread cloverhearts
Github user cloverhearts closed the pull request at:

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


---
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-08 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 <cloverhearts...@gmail.com>
Date:   2017-01-07T09:27:51Z

fixed missing for close

commit 2188b1bbe93b32138c9449c56a8b493d1bc7b874
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-07T11:01:21Z

change Linkedlist to LinkedHashSet

commit 59c9c761b3d5e1dc16a5bf330be082b0fcac93dc
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T05:34:03Z

implement testcase

commit 546ee8549e0c10cdc7535e5b9462f945ad888394
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T05:34:40Z

Revert "change Linkedlist to LinkedHashSet"

This reverts commit 2188b1bbe93b32138c9449c56a8b493d1bc7b874.

commit e25f3114956b9e7fc53d32615a76a0febc05463c
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T06:25:47Z

interpreter test case and replace logic

commit 2482be6c83ce4b784af20c9f69b4097d46cef035
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T06:42:05Z

container method -> isEqualInterpreterKey method

commit b0a93969df652900cf9829505322a0fd9b2091fa
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T07:16:07Z

test case and replace logic




---
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-08 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 #1862: [HOTFIX] Removed non-string properties values since it...

2017-01-08 Thread cloverhearts
Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/1862
  
@jongyoul Sure :)


---
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-08 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 <cloverhearts...@gmail.com>
Date:   2017-01-07T09:27:51Z

fixed missing for close

commit 2188b1bbe93b32138c9449c56a8b493d1bc7b874
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-07T11:01:21Z

change Linkedlist to LinkedHashSet

commit 59c9c761b3d5e1dc16a5bf330be082b0fcac93dc
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T05:34:03Z

implement testcase

commit 546ee8549e0c10cdc7535e5b9462f945ad888394
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T05:34:40Z

Revert "change Linkedlist to LinkedHashSet"

This reverts commit 2188b1bbe93b32138c9449c56a8b493d1bc7b874.

commit e25f3114956b9e7fc53d32615a76a0febc05463c
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T06:25:47Z

interpreter test case and replace logic

commit 2482be6c83ce4b784af20c9f69b4097d46cef035
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T06:42:05Z

container method -> isEqualInterpreterKey method

commit b0a93969df652900cf9829505322a0fd9b2091fa
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T07:16:07Z

test case and replace logic




---
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-08 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-07 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 <cloverhearts...@gmail.com>
Date:   2017-01-07T09:27:51Z

fixed missing for close

commit 2188b1bbe93b32138c9449c56a8b493d1bc7b874
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-07T11:01:21Z

change Linkedlist to LinkedHashSet

commit 59c9c761b3d5e1dc16a5bf330be082b0fcac93dc
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T05:34:03Z

implement testcase

commit 546ee8549e0c10cdc7535e5b9462f945ad888394
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T05:34:40Z

Revert "change Linkedlist to LinkedHashSet"

This reverts commit 2188b1bbe93b32138c9449c56a8b493d1bc7b874.

commit e25f3114956b9e7fc53d32615a76a0febc05463c
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T06:25:47Z

interpreter test case and replace logic

commit 2482be6c83ce4b784af20c9f69b4097d46cef035
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T06:42:05Z

container method -> isEqualInterpreterKey method

commit b0a93969df652900cf9829505322a0fd9b2091fa
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-08T07:16:07Z

test case and replace logic




---
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-07 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 #1721: [ZEPPELIN-969] order by note name in job menu

2017-01-07 Thread cloverhearts
GitHub user cloverhearts reopened a pull request:

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

[ZEPPELIN-969] order by note name in job menu

### What is this PR for?
we can sort by note name in job menu.
Sorting supports ascending and descending order.
Sort by note name.

### What type of PR is it?
Feature

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

### How should this be tested?
click to name order button.

### Screenshots (if appropriate)

![nameorder](https://cloud.githubusercontent.com/assets/10525473/20826460/66a7e7a6-b8ae-11e6-8e03-e2b00698e069.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/cloverhearts/zeppelin jobm/nameOrder

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

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


commit 2d9fc27aaf5f5c46d4b05ee481b81d4707d7f6d7
Author: CloverHearts <cloverhearts...@gmail.com>
Date:   2016-12-02T07:40:33Z

order by note name in job menu

commit da095273e3a564fbd3aa8a83c21e01b55c8f5f28
Author: CloverHearts <cloverhearts...@gmail.com>
Date:   2016-12-02T15:04:53Z

Rename notebook to note.

commit e8a6588cee8f635ddb18646d51aa0e859a123485
Author: CloverHearts <cloverhearts...@gmail.com>
Date:   2016-12-05T06:23:51Z

Merge branch 'master' into jobm/nameOrder

commit 3b698fbd60ec4454a22cfe2f42bf9cd86bf9dc69
Author: CloverHearts <cloverhearts...@gmail.com>
Date:   2016-12-05T06:27:33Z

change sortBy to orderby

commit 6142b8e76d5d9ffba7fa129d78e961dcc1661960
Author: CloverHearts <cloverhearts...@gmail.com>
Date:   2016-12-05T07:01:40Z

Revert "change sortBy to orderby"

This reverts commit 3b698fbd60ec4454a22cfe2f42bf9cd86bf9dc69.

commit ff442451f06c79d856888322c0528141ac3c64fa
Author: CloverHearts <cloverhearts...@gmail.com>
Date:   2016-12-09T05:34:10Z

Merge branch 'master' into jobm/nameOrder

commit 88d47081f1902a5caac928f64d920b52a2c33395
Author: CloverHearts <cloverhearts...@gmail.com>
Date:   2016-12-09T06:27:36Z

fix code style

commit 5383a2ea3731a11ffbebbd02c55e9e597978ad13
Author: CloverHearts <cloverhearts...@gmail.com>
Date:   2016-12-13T05:33:37Z

Merge branch 'master' into jobm/nameOrder

commit ead26f4b04519a913f8dd6e3b76ec8373e4a57f7
Author: CloverHearts <cloverhearts...@gmail.com>
Date:   2016-12-20T03:18:07Z

Merge branch 'master' into jobm/nameOrder

commit 57347c213320d9528905d546289ac986ed349c41
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2016-12-23T06:20:41Z

change filter icon

commit 11ffe68837c2b0d10cbf68cf005517e54513422f
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2016-12-29T05:40:14Z

Merge branch 'master' into jobm/nameOrder

commit d5bca61b54707ee061f56773f03c353bb119c186
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-07T20:00:31Z

Merge branch 'master' into jobm/nameOrder




---
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 #1814: [ZEPPELIN-1869] changed the API response to generate t...

2017-01-07 Thread cloverhearts
Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/1814
  
Fixed done.
CI is green :)


---
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 #1814: [ZEPPELIN-1869] changed the API response to gen...

2017-01-07 Thread cloverhearts
GitHub user cloverhearts reopened a pull request:

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

[ZEPPELIN-1869] changed the API response to generate to 200.

### 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?
Documentation | change

### Todos
- [x] replace to doc
- [x] change response 201 -> 200

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


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


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

$ git pull https://github.com/cloverhearts/zeppelin 
ZEPPELIN-STATUS-CHANGE-API

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

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


commit 754309ed4c68e408e48a95d53a460d80fc2935f9
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2016-12-29T06:42:07Z

Apply to api success status code 200

commit ed317886f250c246734bb9a947d0bcdfaa352f9b
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2016-12-29T07:55:08Z

refix

commit f9fcbc8fbd5a4d6686c0ef4f033694365372deaa
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2016-12-29T07:58:58Z

Revert "refix"

This reverts commit ed317886f250c246734bb9a947d0bcdfaa352f9b.

commit 7bbfcd1c24af196c596178a57e2dde33d279956e
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-07T09:01:30Z

change status value in test case http

commit cfcb6fdbe84c92a41e987ad0f026c9b47c517c47
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-07T09:30:12Z

change test case in zeppelin rest api test

commit 1be096822d15ee84786597dc83f5523375abc284
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-07T09:59:50Z

fixed more isCreated to isAllowed

commit 0f2f5bd74630dcc9702d0ecb30b86e483cb4f965
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-07T10:45:59Z

change test case in notebooksecurity




---
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 #1814: [ZEPPELIN-1869] changed the API response to gen...

2017-01-07 Thread cloverhearts
Github user cloverhearts closed the pull request at:

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


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

2017-01-07 Thread cloverhearts
Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/1864
  
I was change Linked list to Linked HashSet.


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

2017-01-07 Thread cloverhearts
Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/1864
  
Hello @jongyoul.

Could you please review for 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 pull request #1864: [ZEPPELIN-1921] missing close in closeAndRemove...

2017-01-07 Thread cloverhearts
GitHub user cloverhearts opened 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 <cloverhearts...@gmail.com>
Date:   2017-01-07T09:27:51Z

fixed missing for close




---
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-1921) Code bug, closeAndRemoveInterpreterGroup method of InterpreterSetting partially closes

2017-01-07 Thread CloverHearts (JIRA)
CloverHearts created ZEPPELIN-1921:
--

 Summary: Code bug, closeAndRemoveInterpreterGroup method of 
InterpreterSetting partially closes
 Key: ZEPPELIN-1921
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1921
 Project: Zeppelin
  Issue Type: Bug
Reporter: CloverHearts
Assignee: CloverHearts


The problem is that some code in the closeAndRemoveInterpreterGroup method of 
InterpreterSetting partially closes.



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


[GitHub] zeppelin issue #1799: [ZEPPELIN-1165 : WIP] Code-based job workflow

2017-01-07 Thread cloverhearts
Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/1799
  
@rasehorn @zjffdu 
Thank you very much!
I understand the function wait.
I will try to organize it again based on your opinion.
Thank you for your kind comments.


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


[GitHub] zeppelin issue #1862: [HOTFIX] Removed non-string properties values since it...

2017-01-07 Thread cloverhearts
Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/1862
  
Hello @felixcheung 
I have created and tested a remote interpreter.
1. Go to zeppelin/bin.
2. Run the following:
    `bin/bash ./interpreter.sh -d ../interpreter/python -p 2> / dev 
/ null`
3. Create a python interpreter group on zeppelin web. (For example, 
"mypython")
4. Click the edit button.
5. Enter `host: localhost`,` port: 2` as the remote access interpreter 
address.
6. Save and run the following in the paragraph:
`` `
%mypython
print ("helloworld")
`` `

If everything works properly, everything is working fine.
This did not work properly in the previous Master.




---
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 #1862: [HOTFIX] Removed non-string properties values since it...

2017-01-06 Thread cloverhearts
Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/1862
  
@jongyoul 
Yes, I was take look!
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 #1848: [ZEPPELIN-1812] Ace editor show/hide problem.

2017-01-06 Thread cloverhearts
GitHub user cloverhearts reopened a pull request:

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

[ZEPPELIN-1812] Ace editor show/hide problem.

### What is this PR for?
When editor hide is on and page refresh then editor is gone.
I was solve this problem.

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

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

### How should this be tested?
1. hide to editor mode on in paragraph configure.
2. page refresh (f5)
3. enable to show editor mode in paragraph configure.
4. if show editor then is correct.
### Screenshots (if appropriate)
 before

![badeditor](https://cloud.githubusercontent.com/assets/10525473/21677078/62136de2-d2ed-11e6-9418-0be4453fd839.gif)

 after

![goodeditor](https://cloud.githubusercontent.com/assets/10525473/21677092/6c8d97e8-d2ed-11e6-8966-a3b7af60c231.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/cloverhearts/zeppelin ZEPPELIN-1812

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

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


commit b7cd700eccfd2ed51f29c17285bad36579c02208
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-05T10:09:38Z

fixed ace editor hide problem

commit 037993d23257b31836ad59d8805540d30dd1c420
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-06T04:09:33Z

fixed test case

commit c3efea2b93ce2defcf822ef380b5f66cc349c81a
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-06T05:25:26Z

Revert "fixed test case"

This reverts commit 037993d23257b31836ad59d8805540d30dd1c420.

commit 4750e6fce66e95265f2eea1ad45672a673ccd2a9
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-06T08:39:22Z

fix testcase

commit d10d53d6c578d4f0749402a38c9e9337fb68e702
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-06T08:42:06Z

add element null check

commit 9c5ee63e3217e25d92080101cd21baff542ec113
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-06T09:22:46Z

add size check




---
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 #1848: [ZEPPELIN-1812] Ace editor show/hide problem.

2017-01-06 Thread cloverhearts
Github user cloverhearts closed the pull request at:

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


---
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 #1848: [ZEPPELIN-1812] Ace editor show/hide problem.

2017-01-06 Thread cloverhearts
Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/1848
  
SELENIUM TEST PASSED

Currently, Current CI issues are irrelevant to my modifications.

```
10:45:01,535 ERROR org.apache.zeppelin.search.LuceneSearch:120 - Failed to 
open index dir RAMDirectory@4cc68af8 
lockFactory=org.apache.lucene.store.SingleInstanceLockFactory@7ecdc728, make 
sure indexing finished OK
org.apache.lucene.index.IndexNotFoundException: no segments* file found in 
RAMDirectory@4cc68af8 
lockFactory=org.apache.lucene.store.SingleInstanceLockFactory@7ecdc728: files: 
[]
at 
org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:726)
at 
org.apache.lucene.index.StandardDirectoryReader.open(StandardDirectoryReader.java:50)
at org.apache.lucene.index.DirectoryReader.open(DirectoryReader.java:63)
at org.apache.zeppelin.search.LuceneSearch.query(LuceneSearch.java:104)
at 
org.apache.zeppelin.search.LuceneSearchTest.canNotSearchBeforeIndexing(LuceneSearchTest.java:147)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
10:45:01,544  INFO org.apache.zeppelin.search.LuceneSearch:305 - Indexing 2 
notebooks took 4ms
10:45:01,585  INFO org.apache.zeppelin.search.LuceneSearch:305 - Indexing 2 
notebooks took 4ms
10:45:01,632  INFO org.apache.zeppelin.search.LuceneSearch:305 - Indexing 2 
notebooks took 4ms
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.495 sec 
- in org.apache.zeppelin.search.LuceneSearchTest
Running org.apache.zeppelin.conf.ZeppelinConfigurationTest
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in 
[jar:file:/home/travis/build/apache/zeppelin/zeppelin-interpreter/target/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in 
[jar:file:/home/travis/.m2/repository/org/slf4j/slf4j-log4j12/1.7.10/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]
Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.347 sec - 
in org.apache.zeppelin.conf.ZeppelinConfigurationTest

Results :

Failed tests: 
  NotebookTest.testAbortParagraphStatusOnInterpreterRestart:760 
expected: but was:

Tests run: 153, Failures: 1, Errors: 0, Skipped: 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

[GitHub] zeppelin pull request #1848: [ZEPPELIN-1812] Ace editor show/hide problem.

2017-01-06 Thread cloverhearts
GitHub user cloverhearts reopened a pull request:

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

[ZEPPELIN-1812] Ace editor show/hide problem.

### What is this PR for?
When editor hide is on and page refresh then editor is gone.
I was solve this problem.

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

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

### How should this be tested?
1. hide to editor mode on in paragraph configure.
2. page refresh (f5)
3. enable to show editor mode in paragraph configure.
4. if show editor then is correct.
### Screenshots (if appropriate)
 before

![badeditor](https://cloud.githubusercontent.com/assets/10525473/21677078/62136de2-d2ed-11e6-9418-0be4453fd839.gif)

 after

![goodeditor](https://cloud.githubusercontent.com/assets/10525473/21677092/6c8d97e8-d2ed-11e6-8966-a3b7af60c231.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/cloverhearts/zeppelin ZEPPELIN-1812

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

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


commit b7cd700eccfd2ed51f29c17285bad36579c02208
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-05T10:09:38Z

fixed ace editor hide problem

commit 037993d23257b31836ad59d8805540d30dd1c420
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-06T04:09:33Z

fixed test case

commit c3efea2b93ce2defcf822ef380b5f66cc349c81a
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-06T05:25:26Z

Revert "fixed test case"

This reverts commit 037993d23257b31836ad59d8805540d30dd1c420.

commit 4750e6fce66e95265f2eea1ad45672a673ccd2a9
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-06T08:39:22Z

fix testcase

commit d10d53d6c578d4f0749402a38c9e9337fb68e702
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-06T08:42:06Z

add element null check

commit 9c5ee63e3217e25d92080101cd21baff542ec113
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-06T09:22:46Z

add size check




---
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 #1848: [ZEPPELIN-1812] Ace editor show/hide problem.

2017-01-06 Thread cloverhearts
Github user cloverhearts closed the pull request at:

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


---
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 #1854: [ZEPPELIN-1912] fix: Improve perosnalized mode tooltip...

2017-01-06 Thread cloverhearts
Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/1854
  
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 #1848: [ZEPPELIN-1812] Ace editor show/hide problem.

2017-01-05 Thread cloverhearts
Github user cloverhearts closed the pull request at:

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


---
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 #1848: [ZEPPELIN-1812] Ace editor show/hide problem.

2017-01-05 Thread cloverhearts
GitHub user cloverhearts reopened a pull request:

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

[ZEPPELIN-1812] Ace editor show/hide problem.

### What is this PR for?
When editor hide is on and page refresh then editor is gone.
I was solve this problem.

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

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

### How should this be tested?
1. hide to editor mode on in paragraph configure.
2. page refresh (f5)
3. enable to show editor mode in paragraph configure.
4. if show editor then is correct.
### Screenshots (if appropriate)
 before

![badeditor](https://cloud.githubusercontent.com/assets/10525473/21677078/62136de2-d2ed-11e6-9418-0be4453fd839.gif)

 after

![goodeditor](https://cloud.githubusercontent.com/assets/10525473/21677092/6c8d97e8-d2ed-11e6-8966-a3b7af60c231.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/cloverhearts/zeppelin ZEPPELIN-1812

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

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


commit b7cd700eccfd2ed51f29c17285bad36579c02208
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-05T10:09:38Z

fixed ace editor hide problem

commit 037993d23257b31836ad59d8805540d30dd1c420
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-06T04:09:33Z

fixed test case

commit c3efea2b93ce2defcf822ef380b5f66cc349c81a
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-06T05:25:26Z

Revert "fixed test case"

This reverts commit 037993d23257b31836ad59d8805540d30dd1c420.




---
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 #1851: [ZEPPELIN-1908] Invalid Typo Method name

2017-01-05 Thread cloverhearts
GitHub user cloverhearts opened a pull request:

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

[ZEPPELIN-1908] Invalid Typo Method name

### What is this PR for?
Invalid Typo Method name

closeAndRmoveAllInterpreterGroups -> closeAndRemoveAllInterpreterGroups

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

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

### Questions: no
* 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-1908

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

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


commit 0d2bbca742891aa14e4be17f97dfa79551d97c70
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-05T13:02:53Z

fixed method typo




---
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-1908) method name typo for closeAndRemoveAllInterpreterGroups

2017-01-05 Thread CloverHearts (JIRA)
CloverHearts created ZEPPELIN-1908:
--

 Summary: method name typo for closeAndRemoveAllInterpreterGroups
 Key: ZEPPELIN-1908
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1908
 Project: Zeppelin
  Issue Type: Bug
Reporter: CloverHearts


invalid method name closeAndRemoveAllInterpreterGroups in Interpreter 
setting.java and interpreterGroup.java

closeAndRmoveAllInterpreterGroups -> closeAndRemoveAllInterpreterGroups



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


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

2017-01-05 Thread cloverhearts
Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/1838
  
But actually this is a temporary resolved.
As a result, Zombie Process issues have been mitigated.

Zomebie Process is very important and risky issue.
So, I felt the need to take minimal steps.

This fix minimizes the potential for Zombie.
I forced the reference count to zero at shutdown to terminate the process.

The exact problem with the Zombie Process is:
1. Interpreter reference count management failure
2. Close failed while working on RemoteInterpreter
3. Close the RemoteInterpreter Unknown stop.
4. Termination timing issues not yet discovered ..

Therefore, I feel it is necessary to take temporary measures through this 
PR, to register detailed issues and gradually resolve them.

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 #1848: [ZEPPELIN-1812] Ace editor show/hide problem.

2017-01-05 Thread cloverhearts
Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/1848
  
ci reopen


---
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 #1848: [ZEPPELIN-1812] Ace editor show/hide problem.

2017-01-05 Thread cloverhearts
GitHub user cloverhearts reopened a pull request:

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

[ZEPPELIN-1812] Ace editor show/hide problem.

### What is this PR for?
When editor hide is on and page refresh then editor is gone.
I was solve this problem.

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

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

### How should this be tested?
1. hide to editor mode on in paragraph configure.
2. page refresh (f5)
3. enable to show editor mode in paragraph configure.
4. if show editor then is correct.
### Screenshots (if appropriate)
 before

![badeditor](https://cloud.githubusercontent.com/assets/10525473/21677078/62136de2-d2ed-11e6-9418-0be4453fd839.gif)

 after

![goodeditor](https://cloud.githubusercontent.com/assets/10525473/21677092/6c8d97e8-d2ed-11e6-8966-a3b7af60c231.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/cloverhearts/zeppelin ZEPPELIN-1812

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

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


commit b7cd700eccfd2ed51f29c17285bad36579c02208
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-05T10:09:38Z

fixed ace editor hide problem




---
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 #1814: [ZEPPELIN-1869] changed the API response to generate t...

2017-01-05 Thread cloverhearts
Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/1814
  
@Leemoonsoo Ah! sorry, i will 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 pull request #1848: [ZEPPELIN-1812] Ace editor show/hide problem.

2017-01-05 Thread cloverhearts
GitHub user cloverhearts opened a pull request:

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

[ZEPPELIN-1812] Ace editor show/hide problem.

### What is this PR for?
When editor hide is on and page refresh then editor is gone.
I was solve this problem.

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

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

### How should this be tested?
1. hide to editor mode on in paragraph configure.
2. page refresh (f5)
3. enable to show editor mode in paragraph configure.
4. if show editor then is correct.
### Screenshots (if appropriate)
 before

![badeditor](https://cloud.githubusercontent.com/assets/10525473/21677078/62136de2-d2ed-11e6-9418-0be4453fd839.gif)

 after

![goodeditor](https://cloud.githubusercontent.com/assets/10525473/21677092/6c8d97e8-d2ed-11e6-8966-a3b7af60c231.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/cloverhearts/zeppelin ZEPPELIN-1812

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

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


commit b7cd700eccfd2ed51f29c17285bad36579c02208
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-05T10:09:38Z

fixed ace editor hide problem




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

2017-01-04 Thread cloverhearts
GitHub user cloverhearts reopened a pull request:

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

[ZEPPELIN-1832] Fixed a bug in zombie process when Zeppelin stopped.

### What is this PR for?
When Zeppelin stops, there is a problem.
Sometimes this happens to the test as well.
It is related to releasing the resources of the remote remote interpreter, 
and its order has been modified.

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

### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1832
### How should this be tested?
1. Zeppelin start
2. run paragraph for interpreter (for example, %spark println("Hello world")
3. Zeppelin stop
4. check to zombie process 
```
#jps 
```
When Zeppelin exits, the RemoteInterpreter process should not exist.

### 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-1832

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

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


commit b282b9445df47d8672a51cd93b44092bb578135b
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-04T08:51:46Z

Fixed a bug in zombie process when Zeppelin stopped.




---
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-04 Thread cloverhearts
Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/1838
  
@Leemoonsoo Yes, I will :)


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

2017-01-04 Thread cloverhearts
Github user cloverhearts closed the pull request at:

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


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

2017-01-04 Thread cloverhearts
GitHub user cloverhearts reopened a pull request:

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

[ZEPPELIN-1832] Fixed a bug in zombie process when Zeppelin stopped.

### What is this PR for?
When Zeppelin stops, there is a problem.
Sometimes this happens to the test as well.
It is related to releasing the resources of the remote remote interpreter, 
and its order has been modified.

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

### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1832
### How should this be tested?
1. Zeppelin start
2. run paragraph for interpreter (for example, %spark println("Hello world")
3. Zeppelin stop
4. check to zombie process 
```
#jps 
```
When Zeppelin exits, the RemoteInterpreter process should not exist.

### 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-1832

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

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


commit b282b9445df47d8672a51cd93b44092bb578135b
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-04T08:51:46Z

Fixed a bug in zombie process when Zeppelin stopped.




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

2017-01-04 Thread cloverhearts
Github user cloverhearts closed the pull request at:

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


---
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-04 Thread cloverhearts
Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/1838
  
@AhyoungRyu @soralee Thank you :)


---
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-04 Thread cloverhearts
Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/1838
  
@minahlee @AhyoungRyu 
Hello, could you please review for 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 pull request #1838: [ZEPPELIN-1832] Fixed a bug in zombie process w...

2017-01-04 Thread cloverhearts
GitHub user cloverhearts opened a pull request:

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

[ZEPPELIN-1832] Fixed a bug in zombie process when Zeppelin stopped.

### What is this PR for?
When Zeppelin stops, there is a problem.
Sometimes this happens to the test as well.
It is related to releasing the resources of the remote remote interpreter, 
and its order has been modified.

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

### What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1832
### How should this be tested?
1. Zeppelin start
2. run paragraph for interpreter (for example, %spark println("Hello world")
3. Zeppelin stop
4. check to zombie process 
```
#jps 
```
When Zeppelin exits, the RemoteInterpreter process should not exist.

### 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-1832

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

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


commit b282b9445df47d8672a51cd93b44092bb578135b
Author: cloverhearts <cloverhearts...@gmail.com>
Date:   2017-01-04T08:51:46Z

Fixed a bug in zombie process when Zeppelin stopped.




---
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-1896) The ability to remove the result of a paragraph from your code.

2017-01-03 Thread CloverHearts (JIRA)
CloverHearts created ZEPPELIN-1896:
--

 Summary: The ability to remove the result of a paragraph from your 
code.
 Key: ZEPPELIN-1896
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1896
 Project: Zeppelin
  Issue Type: Sub-task
Reporter: CloverHearts
Assignee: CloverHearts


We need code that can delete the result of a paragraph of the form 
z.clearOutput.
This allows you to control the code by deleting the result of the paragraph.
You can always update the results of the paragraph you have executed explicitly.



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


[jira] [Created] (ZEPPELIN-1895) Get paragraph status in code

2017-01-03 Thread CloverHearts (JIRA)
CloverHearts created ZEPPELIN-1895:
--

 Summary: Get paragraph status in code
 Key: ZEPPELIN-1895
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1895
 Project: Zeppelin
  Issue Type: Sub-task
Reporter: CloverHearts
Assignee: CloverHearts


We need a ZeppelinContext to get the state of the paragraph, such as 
z.getJobStatus.
This feature allows you to implement a similar workflow.



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


<    1   2   3   4   5   6   >