date:20170126

Github user DrIgor commented on the issue:

https://github.com/apache/zeppelin/pull/1949
  
```
Tests in error: 
  InterpreterRestApiTest.testRestartInterpreterPerNote:303 NullPointer
```

It's a known bug https://issues.apache.org/jira/browse/ZEPPELIN-1856


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes 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 #1949: [MINOR] Refactor to modern apis

Github user DrIgor closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes 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 #1949: [MINOR] Refactor to modern apis

GitHub user DrIgor reopened a pull request:

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

[MINOR] Refactor to modern apis

### What is this PR for?
Use modern api to write less and try-with-resources to close file in case 
of errors

### What type of PR is it?
Refactoring

### 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/DrIgor/zeppelin file-loading-refactoring

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

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


commit d1ee8a1f96f7426efd01b53148e98db16f856554
Author: Igor Drozdov 
Date:   2017-01-26T13:22:45Z

Refactor to modern apis




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes 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 #1945: [ZEPPELIN-2003] Remove PostgresqlInterpreter

2017-01-26 Thread prabhjyotsingh

Github user prabhjyotsingh commented on the issue:

https://github.com/apache/zeppelin/pull/1945
  
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 #1948: [ZEPPELIN-2016] add test case for cron job scheduler r...

2017-01-26 Thread prabhjyotsingh

Github user prabhjyotsingh commented on the issue:

https://github.com/apache/zeppelin/pull/1948
  
CI green! 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 #1902: [ZEPPELIN-1821] Add HTTP client to elasticsearch inter...

2017-01-26 Thread jaspinderdineout

Github user jaspinderdineout commented on the issue:

https://github.com/apache/zeppelin/pull/1902
  
When will this be merged?


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

[GitHub] zeppelin issue #1949: [MINOR] Refactor to modern apis

Github user DrIgor commented on the issue:

https://github.com/apache/zeppelin/pull/1949
  
@Leemoonsoo Of course! Unfortunately, build log is truncated and I can't 
find out why it failed


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes 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 #1949: [MINOR] Refactor to modern apis

GitHub user DrIgor reopened a pull request:

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

[MINOR] Refactor to modern apis

### What is this PR for?
Use modern api to write less and try-with-resources to close file in case 
of errors

### What type of PR is it?
Refactoring

### 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/DrIgor/zeppelin file-loading-refactoring

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

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


commit d1ee8a1f96f7426efd01b53148e98db16f856554
Author: Igor Drozdov 
Date:   2017-01-26T13:22:45Z

Refactor to modern apis




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes 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 #1949: [MINOR] Refactor to modern apis

Github user DrIgor closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes 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 #1598: [ZEPPELIN-1618] [WIP] Support ElasticSearch 5.0

2017-01-26 Thread 1ambda

Github user 1ambda closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes 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 #1598: [ZEPPELIN-1618] [WIP] Support ElasticSearch 5.0

2017-01-26 Thread 1ambda

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/1598
  
@jaspinderdineout Hi :)

Zeppelin doesn't support es 5.0 currently as i know. 
I will close this PR. This issue can be easily handled after #1902. 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes 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 #1950: ZEPPELIN-2015 Improve parsing logic of livy sql output

Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/1950
  
I think it is flaky test as this PR only change the code of livy 
interpreter, didn't touch other components of zeppelin. And I believe I see 
this flaky test before. 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes 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 #1742: [ZEPPELIN-1781] Failed to run the script 'test_...

2017-01-26 Thread asfgit

Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes 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 #1742: [ZEPPELIN-1781] Failed to run the script 'test_zeppeli...

2017-01-26 Thread felixcheung

Github user felixcheung commented on the issue:

https://github.com/apache/zeppelin/pull/1742
  
merged to master. thanks!


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

[GitHub] zeppelin issue #1950: ZEPPELIN-2015 Improve parsing logic of livy sql output

2017-01-26 Thread felixcheung

Github user felixcheung commented on the issue:

https://github.com/apache/zeppelin/pull/1950
  
@zjffdu do you know why this failed 
https://travis-ci.org/apache/zeppelin/jobs/195755531

merging if no more comment


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes 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 #1950: ZEPPELIN-2015 Improve parsing logic of livy sql output

2017-01-26 Thread felixcheung

Github user felixcheung commented on the issue:

https://github.com/apache/zeppelin/pull/1950
  
ok a couple of things to open JIRA for?
- SparkR app id
- disabled tests
- move livy interpreter export to interpreter.sh

looks good otherwise


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes 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 #1948: [ZEPPELIN-2016] add test case for cron job scheduler r...

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/1948
  
@khalidhuseynov Cool!
LGTM and merge to master if no more comments!




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

[jira] [Created] (ZEPPELIN-2022) Make SparkInterpreter directly access TableData in ResourcePool

Lee moon soo created ZEPPELIN-2022:
--

 Summary: Make SparkInterpreter directly access TableData in 
ResourcePool
 Key: ZEPPELIN-2022
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2022
 Project: Zeppelin
  Issue Type: Sub-task
Reporter: Lee moon soo
 Fix For: 0.8.0


Implement [spark 
datasource|https://github.com/apache/spark/blob/master/sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/DataSource.scala]
 for TableData in ResourcePool.

Then Spark will able to query any TableData available in the ResourcePool.



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

[GitHub] zeppelin issue #1950: ZEPPELIN-2015 Improve parsing logic of livy sql output

Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/1950
  
Failure CI is not relevant.

```
Tests in error: 
  NotebookTest.testRunAll:323 NullPointer
```


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes 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 #1952: [ZEPPELIN-753] TableData abstraction

GitHub user Leemoonsoo opened a pull request:

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

[ZEPPELIN-753] TableData abstraction

### What is this PR for?
This PR implements TableData abstraction that every interpreter can use to 
share data through resource pool.

This PR is made on top of #1951. Once #1951 is merged, this PR will be 
rebased to master.
Meanwhile, to review, 

TableData.java - Definition of TableData abstraction
TableDataProxy.java - Proxy object of TableData. This enables data access 
through ResourcePool
InterpreterResultTableData - Convert Table type interpret result into 
TableData. Each interpreter can implement it's own TableData abstraction. For 
example JDBCTableData, DataFrameTableData, and so on.

### What type of PR is it?
Feature

### Todos
* [x] - TableData
* [x] - TableDataProxy
* [x] - Unittest

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

### How should this be tested?
Unittest included

### 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/Leemoonsoo/zeppelin ZEPPELIN-753

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

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


commit 74b502e9c89aebe09c932f0798817a1c5398bead
Author: Lee moon soo 
Date:   2017-01-26T00:39:42Z

Support method invocation on the resource in local,remote resource pool

commit 30e62f23eebfe8ca441f3c36c00605132b3779cf
Author: Lee moon soo 
Date:   2017-01-26T02:12:03Z

make RemoteResource.invokeMethod returns Resource when return resource name 
is specified

commit 75a9b32357eb911d923d76a1c331e17d9d4ad4ce
Author: Lee moon soo 
Date:   2017-01-25T17:41:29Z

TableData abstraction

commit 1751ee015b5bdb936e45f442c5bb9e2ec2fc52b2
Author: Lee moon soo 
Date:   2017-01-26T02:38:45Z

Proxy for tabledata




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes 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 #1942: [ZEPPELIN-1982] When using the 'Select * ...' statemen...

2017-01-26 Thread minahlee

Github user minahlee commented on the issue:

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


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

[GitHub] zeppelin issue #1598: [ZEPPELIN-1618] [WIP] Support ElasticSearch 5.0

Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/1598
  
\cc @1ambda 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes 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 #1940: [ZEPPELIN-2008] Introduce Spell

Github user Leemoonsoo commented on the issue:

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

Thanks @1ambda for contributing very interesting new feature.
I've play around with it and have couple of feedbacks.

### Couldn't make Spell as display system work
> The most important thing is, spell is not only interpreter but also
display system. Because it runs on browser. This enable us to combine existing
backend interpreters with spell like

So i tried following but couldn't make it work. Am i missing something?

![image](https://cloud.githubusercontent.com/assets/1540981/22355380/9d932722-e46d-11e6-8d80-af5e7657d910.png)

### Configuring Display order of Spell doesn't make sense

Enabled spells are displayed in 'Helium' menu like below.

![image](https://cloud.githubusercontent.com/assets/1540981/22355499/37ea7ef6-e46e-11e6-8a41-8083f836d07e.png)

Which is designed to change display order of visualization package when
they displayed in chart selector inside of the paragraph.
As far as i understand, Spell does not have to be listed in the chart
selector and does not have to be listed there and change order. So i think
reordering should be only for 'Visualization' type package.

I think Spell can create another section just below enabled visualization
buttons, to list enabled spells.

### Display keyword of the spell

Each spell has keyword to invoke. For example `markdown-spell`'s keyword is
`%markdown`, `flowchart-spell`'s keyword is `%flowchart`. However, i couldn't
find these keyword anywhere but the source code.

So it'll be nice if 'Helium' menu displays keyword of the Spell type
packages.

### Example for example spells

If there's some informations or example that how to use (syntax, etc)
included example Spells, (e.g. in description section or somewhere) it'll be
more convenient.

---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes 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: Build on Windows getting stuck

2017-01-26 Thread Andrii Pelekh

I want to follow up on below.

I will create a new ticket for this problem if this appears to be a common
issue.

Thanks,
Andrii

On Jan 25, 2017 05:45, "Igor Drozdov"  wrote:

> I have the same issue with npm-run-all clean on windows 10
>
> Igor Drozdov
>
> From: Andrii Pelekh [mailto:pelek...@gmail.com]
> Sent: Wednesday, January 25, 2017 7:56 AM
> To: dev@zeppelin.apache.org
> Subject: Build on Windows getting stuck
>
> Hi all,
>
> I'm trying to reproduce a defect from Jira ticket on Windows7 x64 but my
> build getting stuck on the "npm-run-all clean" step. Please see log file
> attached. I tried to build on another Windows PC and it got stuck too on
> the same step. I have dual boot and everything works fine for me on Ubuntu.
>
> Another thing to note is two node processes which I observe during the
> hang up phase (see screenshot attached). One of the processes (yarn.js run
> build) does not terminate even after I cancel the build.
>
> Have anyone had anything similar?
>
> Thanks,
> Andrii
>

[GitHub] zeppelin issue #1936: [ZEPPELIN-2004] List all helium packages in Zeppelin G...

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/1936
  
@AhyoungRyu Updated the doc


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes 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-2021) Flaky test - PySparkInterpreterTest.testCompletion

Lee moon soo created ZEPPELIN-2021:
--

 Summary: Flaky test - PySparkInterpreterTest.testCompletion
 Key: ZEPPELIN-2021
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2021
 Project: Zeppelin
  Issue Type: Sub-task
Reporter: Lee moon soo


Example 
[log|https://s3.amazonaws.com/archive.travis-ci.org/jobs/195639051/log.txt] 
from [build|https://travis-ci.org/apache/zeppelin/jobs/195639051]

{code}
testCompletion(org.apache.zeppelin.spark.PySparkInterpreterTest)  Time elapsed: 
0.102 sec  <<< FAILURE!
java.lang.AssertionError: null
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at 
org.apache.zeppelin.spark.PySparkInterpreterTest.testCompletion(PySparkInterpreterTest.java:121)

17/01/26 19:23:23 INFO SparkContext: Invoking stop() from shutdown hook
17/01/26 19:23:23 INFO SparkUI: Stopped Spark web UI at http://172.17.0.6:4040
17/01/26 19:23:23 INFO MapOutputTrackerMasterEndpoint: 
MapOutputTrackerMasterEndpoint stopped!
17/01/26 19:23:23 INFO MemoryStore: MemoryStore cleared
17/01/26 19:23:23 INFO BlockManager: BlockManager stopped
17/01/26 19:23:23 INFO BlockManagerMaster: BlockManagerMaster stopped
17/01/26 19:23:23 INFO OutputCommitCoordinator$OutputCommitCoordinatorEndpoint: 
OutputCommitCoordinator stopped!
17/01/26 19:23:23 INFO RemoteActorRefProvider$RemotingTerminator: Shutting down 
remote daemon.
17/01/26 19:23:23 INFO SparkContext: Successfully stopped SparkContext
17/01/26 19:23:23 INFO ShutdownHookManager: Shutdown hook called
17/01/26 19:23:23 INFO ShutdownHookManager: Deleting directory 
/tmp/spark-416c693f-9290-428b-830a-d0bb5c0da703/pyspark-6c48736e-37c2-4747-8a38-5d0bf104b4fa
17/01/26 19:23:23 INFO ShutdownHookManager: Deleting directory 
/tmp/spark-9ce929d5-8400-410d-9729-9a3caefd8b2c
17/01/26 19:23:23 INFO RemoteActorRefProvider$RemotingTerminator: Remote daemon 
shut down; proceeding with flushing remote transports.
17/01/26 19:23:23 INFO ShutdownHookManager: Deleting directory 
/tmp/spark-508bdc3a-9777-486b-901b-b72d0ba42250
17/01/26 19:23:23 INFO ShutdownHookManager: Deleting directory 
/tmp/spark-416c693f-9290-428b-830a-d0bb5c0da703

Results :

Failed tests: 
  PySparkInterpreterTest.testCompletion:121 null

Tests run: 7, Failures: 1, Errors: 0, Skipped: 0
{code}



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

[GitHub] zeppelin issue #1804: [ZEPPELIN-1578] notes list in customizing zeppelin hom...

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/1804
  
It's nit. But do you mind change some file name?

`zeppelin-web/src/app/home/customer/customHome.html` -> 
`zeppelin-web/src/app/home/notebook.html`
I think we don't need `customer` in the path and `notebook.html` is more 
appropriate than `customHome.html` because the template is printing note list, 
inside of user created custom Note.


`zeppelin-web/src/app/home/home-template.html` -> 
`zeppelin-web/src/app/home/notebook-template.html`
Also, i think `notebook-template.html` is more appropriate name than 
`home-template.html` because it's printing note lists, not entire home page.



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes 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 #1892: [MINOR] broken logo url in web dev mode

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/1892
  
cc @1ambda 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes 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 #1902: [ZEPPELIN-1821] Add HTTP client to elasticsearch inter...

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/1902
  
LGTM @1ambda do you have any comment?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes 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 #1949: [MINOR] Refactor to modern apis

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/1949
  
@DrIgor Thanks for the contribution!
CI fails with known flaky test 
https://issues.apache.org/jira/browse/ZEPPELIN-1856. @DrIgor Could you trigger 
ci again and see if it passes?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes 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 #1924: [Pyspark] checking nhooks count.

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/1924
  
@astroshim do you mind create a JIRA issue?


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

[GitHub] zeppelin issue #1924: [Pyspark] checking nhooks count.

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/1924
  
LGTM and merge to master and branch-0.7


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes 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 #1951: [ZEPPELIN-2020] Invoke method from resource

GitHub user Leemoonsoo opened a pull request:

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

[ZEPPELIN-2020] Invoke method from resource

### What is this PR for?
This PR provides a way to invoke method remotely against the resource in 
the resource pool.
This will be particularly useful the object in the resource pool is 
non-serializable (like jdbc connection, spark dataframe).

This PR extends data access API of Resource from

```
class Resource {
  // get object
  public Object get();
}
```

to 
```
class Resource {
  // get object
  public Object get()

  // call method of object and get return value
  public Object invokeMethod(String methodName, Class [] paramTypes, Object 
[] params);

  // call method of object and save return value into resourcepool
  public Object invokeMethod(String methodName, Class [] paramTypes, Object 
[] params, String returnResourceName);
}


### What type of PR is it?
Feature

### Todos
* [x] - API for remote method invocation and get result
* [x] - API for remote method invocation and store result into resource pool
* [x] - Unittest

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

### How should this be tested?
Unittest included 

### 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/Leemoonsoo/zeppelin 
invoke_method_from_resource

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

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


commit 74b502e9c89aebe09c932f0798817a1c5398bead
Author: Lee moon soo 
Date:   2017-01-26T00:39:42Z

Support method invocation on the resource in local,remote resource pool

commit a0adbde37f5aa79ef63a422e5a38ca95f8127f2a
Author: Lee moon soo 
Date:   2017-01-26T02:12:03Z

make RemoteResource.invokeMethod returns Resource when return resource name 
is specified




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes 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-2020) Remote method invocation for Resource in ResourcePool

Lee moon soo created ZEPPELIN-2020:
--

 Summary: Remote method invocation for Resource in ResourcePool
 Key: ZEPPELIN-2020
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2020
 Project: Zeppelin
  Issue Type: Sub-task
Reporter: Lee moon soo
Assignee: Lee moon soo
 Fix For: 0.8.0


Currently, ResourcePool provides a way to store Serializable and 
Non-Serializable object.

In case of Non-Serializable object is stored in resource pool, other 
interpreter process can not read the object.

This is limitation for storing object like jdbc connection, spark dataframe in 
the resourcepool. For non-serialiable object in the resource pool, we can think 
about

* Call method remotely and get return
* Call method remotely and save return into resource pool.



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

[jira] [Created] (ZEPPELIN-2019) [Umbrella] Query dataset across different interpreter

Lee moon soo created ZEPPELIN-2019:
--

 Summary: [Umbrella] Query dataset across different interpreter
 Key: ZEPPELIN-2019
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2019
 Project: Zeppelin
  Issue Type: New Feature
Reporter: Lee moon soo
 Fix For: 0.8.0


h3. Motivation

Zeppelin connects various backend data processing system through Interpreter.

While Zeppelin is central place that those heterogeneous systems connected, it 
is really great Zeppelin gives possibility of query data across different 
backend system.

So, such job "joining jdbc table and spark dataframe" would be possible.



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

[GitHub] zeppelin issue #1663: ZEPPELIN-1692: Ability to access Spark jobs UI from th...

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/1663
  
Sorry for coming back late.
Tested the last commit and looks good to me.
@karuppayya could you merge master and resolve the conflict and see if CI 
becomes green? Then i'd like to merge it to master.

I've found one behavior from last commit which can be addressed in either 
this PR or following PR

![sparkui](https://cloud.githubusercontent.com/assets/1540981/22344975/9f522eb8-e441-11e6-9608-a57212c1b02b.gif)
 



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes 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 #1944: [HOTFIX][MINOR] Change the scope of httpclient to runt...

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/1944
  
my command is 

```
/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/bin/java 
-agentlib:jdwp=transport=dt_socket,address=127.0.0.1:6,suspend=y,server=n 
-Dlog4j.configuration=file:///Users/moon/Projects/zeppelin/conf/log4j_dev.properties
 -Dfile.encoding=UTF-8 -classpath 
/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/lib/ant-javafx.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/lib/dt.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/lib/javafx-doclet.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/lib/javafx-mx.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/lib/jconsole.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/lib/sa-jdi.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/lib/tools.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre/lib/charsets.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre/lib/depl
 
oy.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre/lib/htmlconverter.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre/lib/javaws.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre/lib/jce.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre/lib/jfr.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre/lib/jfxrt.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre/lib/jsse.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre/lib/management-agent.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre/lib/plugin.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre/lib/resources.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre/lib/rt.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre/lib/ext/dnsns.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre
 
/lib/ext/localedata.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre/lib/ext/sunec.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre/lib/ext/sunjce_provider.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre/lib/ext/sunpkcs11.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_79.jdk/Contents/Home/jre/lib/ext/zipfs.jar:/Users/moon/Projects/zeppelin/zeppelin-server/target/classes:/Users/moon/.m2/repository/junit/junit/4.11/junit-4.11.jar:/Users/moon/.m2/repository/org/hamcrest/hamcrest-core/1.3/hamcrest-core-1.3.jar:/Users/moon/.m2/repository/xml-apis/xml-apis/1.4.01/xml-apis-1.4.01.jar:/Users/moon/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar:/Users/moon/.m2/repository/commons-logging/commons-logging/1.1.1/commons-logging-1.1.1.jar:/Users/moon/.m2/repository/com/google/code/gson/gson/2.2/gson-2.2.jar:/Users/moon/.m2/repository/org/seleniumhq/selenium/selenium-java/2.48.2/selenium-java-
 
2.48.2.jar:/Users/moon/.m2/repository/org/seleniumhq/selenium/selenium-chrome-driver/2.48.2/selenium-chrome-driver-2.48.2.jar:/Users/moon/.m2/repository/org/seleniumhq/selenium/selenium-remote-driver/2.48.2/selenium-remote-driver-2.48.2.jar:/Users/moon/.m2/repository/cglib/cglib-nodep/2.1_3/cglib-nodep-2.1_3.jar:/Users/moon/.m2/repository/org/seleniumhq/selenium/selenium-api/2.48.2/selenium-api-2.48.2.jar:/Users/moon/.m2/repository/com/google/guava/guava/15.0/guava-15.0.jar:/Users/moon/.m2/repository/org/apache/httpcomponents/httpclient/4.3.6/httpclient-4.3.6.jar:/Users/moon/.m2/repository/org/apache/httpcomponents/httpcore/4.3.3/httpcore-4.3.3.jar:/Users/moon/.m2/repository/commons-codec/commons-codec/1.5/commons-codec-1.5.jar:/Users/moon/.m2/repository/org/apache/commons/commons-exec/1.3/commons-exec-1.3.jar:/Users/moon/.m2/repository/net/java/dev/jna/jna/4.1.0/jna-4.1.0.jar:/Users/moon/.m2/repository/net/java/dev/jna/jna-platform/4.1.0/jna-platform-4.1.0.jar:/Users/moon/.m2/repos

[jira] [Created] (ZEPPELIN-2018) Improve selenium test stability & speed. All tests are repaired.

2017-01-26 Thread Sergey_Sokur (JIRA)

Sergey_Sokur created ZEPPELIN-2018:
--

 Summary: Improve selenium test stability & speed. All tests are 
repaired.
 Key: ZEPPELIN-2018
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2018
 Project: Zeppelin
  Issue Type: Bug
Affects Versions: 0.8.0
Reporter: Sergey_Sokur
Assignee: Sergey_Sokur


The main part of my idea is to make tests more stable and faster. I'm planning 
to do it in a few steps.

Every step should not destroy tests. And also each step is an independent 
pull-request.(They will be presented as a sub-tasks).

Step 1. Move all selenium tests into new module - "zeppelin-webtests".
Step 2. Update travis configuration ".travis.yml" to run test from this module.
Step 3. Remove unnecessary dependency from  module "zeppelin-server". Add new 
framework etc. to "zeppelin-webtests" pom file.
Step 4. Too large, but its easy to check (test on CI should be green). Rewrite 
all selenium tests (do it more stable and faster). Do code more cleaner and 
easily to read. (It’s already done locally). Result is awesome.




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

[GitHub] zeppelin issue #1598: [ZEPPELIN-1618] [WIP] Support ElasticSearch 5.0

2017-01-26 Thread jaspinderdineout

Github user jaspinderdineout commented on the issue:

https://github.com/apache/zeppelin/pull/1598
  
Is it live? Does zeppelin support elasricsearch 5.0 ???


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

[GitHub] zeppelin issue #1950: ZEPPELIN-2015 Improve parsing logic of livy sql output

Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/1950
  
@felixcheung @prabhjyotsingh Please help review and try to get it into 0.7. 
 And I may not reponse in the next few days due to Chinese Spring Festival  


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes 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 #1950: ZEPPELIN-2015 Improve parsing logic of livy sql...

GitHub user zjffdu opened a pull request:

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

ZEPPELIN-2015 Improve parsing logic of livy sql output

### What is this PR for?
This PR is trying to resolve the table display issue related with #1942. 
But when I do this PR, I find other 2 issues in livy interpreter.
* livy integration is never run due to refactoring of travis script in 
#1786.
* pyspark integration would fail


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

### Todos
* [ ] - Task

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


### Screenshots (if appropriate)

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


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

$ git pull https://github.com/zjffdu/zeppelin ZEPPELIN-2015

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

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


commit ba6aab2c391ca72ca97e1ccfa79dc368b1ad96d2
Author: Chin Tzulin 
Date:   2017-01-25T05:34:28Z

[ZEPPELIN-1982] When using the 'Select * ...' statement doesn't show the 
response In %sql interpreter

commit 4667eef79ecb16b93d2a187dfdf3b4004dc5a77c
Author: Jeff Zhang 
Date:   2017-01-26T09:30:49Z

ZEPPELIN-2015. Improve parsing logic of livy sql output

commit 98b1d96e4e031d438268834840ab2761e5012c6a
Author: Jeff Zhang 
Date:   2017-01-26T14:47:56Z

Fix appId and webui extraction for pyspark




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes 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 #1949: [MINOR] Refactor to modern apis

GitHub user DrIgor opened a pull request:

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

[MINOR] Refactor to modern apis

### What is this PR for?
Use modern api to write less and try-with-resources to close file in case 
of errors

### What type of PR is it?
Refactoring

### 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/DrIgor/zeppelin file-loading-refactoring

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

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


commit d1ee8a1f96f7426efd01b53148e98db16f856554
Author: Igor Drozdov 
Date:   2017-01-26T13:22:45Z

Refactor to modern apis




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes 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-2017) Graph Mode set in 'Update paragraph configuration' in Notebook REST API not working.

2017-01-26 Thread Ramesh Madhavan (JIRA)

Ramesh Madhavan created ZEPPELIN-2017:
-

 Summary: Graph Mode set in 'Update paragraph configuration' in 
Notebook REST API not working.
 Key: ZEPPELIN-2017
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2017
 Project: Zeppelin
  Issue Type: Bug
  Components: rest-api
Affects Versions: 0.7.0
Reporter: Ramesh Madhavan


We tried using the Notebook rest API to update the type of graph in a Zeppelin 
Notebook. The value given for 'mode' in the 'graph' element is not getting 
reflected in the Notebook.

Looking at the code changes in  
https://github.com/apache/zeppelin/pull/1592.patch, the unit test only seems to 
validate the 'colWidth' element. So there could be bug in the handling of the 
graph mode element.



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

[GitHub] zeppelin issue #1944: [HOTFIX][MINOR] Change the scope of httpclient to runt...

Github user DrIgor commented on the issue:

https://github.com/apache/zeppelin/pull/1944
  
Hello! I have the same issue

I checked dependency:tree output, 
`org.apache.httpcomponents:httpclient:jar:4.3.6` has `test` scope in 
`zeppelin-server` module.




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

[GitHub] zeppelin issue #1942: [ZEPPELIN-1982] When using the 'Select * ...' statemen...

2017-01-26 Thread minahlee

Github user minahlee commented on the issue:

https://github.com/apache/zeppelin/pull/1942
  
@del680202 thanks for the contribution, do you mind to retrigger CI to be 
sure?
You can retrigger it by closing and opening this PR or `git commit --amend 
## ; git push -f repoName branchName`


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes 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 #1948: [ZEPPELIN-2016] add test case for cron job sche...

2017-01-26 Thread khalidhuseynov

GitHub user khalidhuseynov opened a pull request:

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

[ZEPPELIN-2016] add test case for cron job scheduler resource depletion

### What is this PR for?
followup test case after https://issues.apache.org/jira/browse/ZEPPELIN-2009

### What type of PR is it?
Improvement | test

### Todos
* [x] - add test

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

### How should this be tested?
CI pass

### Screenshots (if appropriate)

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


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

$ git pull https://github.com/khalidhuseynov/incubator-zeppelin 
test/cron-scheduler

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

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


commit eb555fbe64a8ca4f98b437da2aaf780acfec651b
Author: Khalid Huseynov 
Date:   2017-01-26T00:41:24Z

add complete cron scheduler test

takes at least 13 * 1100 +  1100 ms




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes 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-2016) Test case for cron job complete test for resource pool depletion

2017-01-26 Thread Khalid Huseynov (JIRA)

Khalid Huseynov created ZEPPELIN-2016:
-

 Summary: Test case for cron job complete test for resource pool 
depletion
 Key: ZEPPELIN-2016
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2016
 Project: Zeppelin
  Issue Type: Test
Reporter: Khalid Huseynov
Assignee: Khalid Huseynov


after https://issues.apache.org/jira/browse/ZEPPELIN-2009 is fixed there's 
still need for test case in order not repeat this kind of bugs



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

[GitHub] zeppelin issue #1942: [ZEPPELIN-1982] When using the 'Select * ...' statemen...