[GitHub] zeppelin issue #1595: [ZEPPELIN-1615] - Zeppelin should be able to run witho...

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/1595
  
Looks like zeppelin-web dev mode (`grunt serve`) has some problem after the 
patch.
@anthonycorbacho Could you take a look?


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

[GitHub] zeppelin pull request #1601: [TEST CI]

[Leemoonsoo]

Github user Leemoonsoo closed the pull request at:

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


---
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 #1595: [ZEPPELIN-1615] - Zeppelin should be able to run witho...

[minahlee]

Github user minahlee commented on the issue:

https://github.com/apache/zeppelin/pull/1595
  
Finally CI is green!!! I am merging it


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

[GitHub] zeppelin issue #1577: [ZEPPELIN-1554] Update jekyll version to 3.2.1 with it...

[yoonjs2]

Github user yoonjs2 commented on the issue:

https://github.com/apache/zeppelin/pull/1577
  
@AhyoungRyu OK I'll investigate and resolve them ASAP. Thanks for the 
review :)


---
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 #1602: Ci test

[minahlee]

Github user minahlee closed the pull request at:

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


---
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 #1534: ZEPPELIN-1345 - Create a custom matplotlib backend tha...

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/1534
  
@agoodm It's my bad, i was testing it with 
https://github.com/apache/zeppelin/pull/1596 merged.
Tested just last commit in the branch again, and the error has gone.


---
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 #1534: ZEPPELIN-1345 - Create a custom matplotlib backend tha...

[agoodm]

Github user agoodm commented on the issue:

https://github.com/apache/zeppelin/pull/1534
  
@Leemoonsoo Sure, I will do that after this is merged.

As for your error, I cannot reproduce it. I tested both the latest code 
from master as well as my fork after rebasing. How are you performing the maven 
build? I use:
```
mvn clean package -Pbuild-distr -Ppyspark -DskipTests
```
without modifying any of the configuration files.


---
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 #1497: [ZEPPELIN-1233] Support Redis interpreter

[darionyaphet]

Github user darionyaphet commented on the issue:

https://github.com/apache/zeppelin/pull/1497
  
Add a Screenshot 

![1539610b-0afe-4cd0-9a3a-abb208adfb7d](https://cloud.githubusercontent.com/assets/4414314/20008000/c05f9b44-a2d9-11e6-9d30-0d09ae275fd7.PNG)



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

[GitHub] zeppelin issue #1589: [Zeppelin-1611] - Support PAM (System User) Authentica...

[hkropp]

Github user hkropp commented on the issue:

https://github.com/apache/zeppelin/pull/1589
  
Cool!

Just to be clear the test will simply be ignored with `assumeTrue` so 
should be fine without any additional effort. How to use the test itself is 
documented in the test class with comments.

Concerning the licenses we should be fairly save. libpam4j mainly 
dependence on JNA and maven. JNA version >4 is available as Apache and actually 
was already introduced with selenium dependency in this project.

I rebased and pulled in a way that created a little mess here. What I could 
do is create a new branch with cherry-picked changes and created a new PR based 
on this, or? Let me know?

I think the Travis build failed because of issue with the other changes, or?


---
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 #1513: ZEPPELIN-1472 - Create new LdapRealm based on Apache K...

[nazgul33]

Github user nazgul33 commented on the issue:

https://github.com/apache/zeppelin/pull/1513
  
@jongyoul I could make it work with openLDAP server. I had no time to play 
around with group settings, but at least I could authenticate user by
* ldapADGCRealm.userSearchAttributeName = cn
* ldapADGCRealm.userSearchAttributeName = uid

and the followings are settings I had to modify when I'm using phpldapadmin 
to manage users.
ldapADGCRealm.contextFactory.authenticationMechanism = simple
ldapADGCRealm.userObjectClass = posixAccount
ldapADGCRealm.groupObjectClass = posixGroup
ldapADGCRealm.memberAttribute = memberUid

for me, it works.


---
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 #1596: ZEPPELIN-1616. Interpreter open happens in jobRun

[zjffdu]

Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/1596
  
`open()` will be called before the first call to `interpreter()`, so it 
won't affect. Will wait for your test result tomorrow.


---
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 #928: [ZEPPELIN-116] Add Apache Mahout Interpreter

[bzz]

Github user bzz commented on the issue:

https://github.com/apache/zeppelin/pull/928
  
Sorry for delay, @rawkintrevo ! 

Thank you for kind reminder on this great stuff. I want to mention this 
work on ApacheCon, so hope we can merge this asap :)

I tied it and got `IOError: [Errno 28] No space left on device` while 
downloading Mahout. While I'm cleaning the space, here are few things that I 
noticed:
  - script does not "fail fast", meaning that if downloading of Mahout 
failed due to disk space, it went on trying to create dirs, update .json, etc. 
How do you think, is it worth adding it?

  - output uses the term `terp`

  ```
created new terp 'sparkMahout' from terp 'spark
created new terp 'flinkMahout' from terp 'flink
  ```
  I assume it's used instead of longer `interpreter`. But other users may 
get confused at this point, as documentation does not mention such term. Do you 
think we use `interpreter` consistently here as well?

- is `python scripts/mahout/add_mahout.py` idempotent? 

  Meaning, if it failed once for some reason, is it safe to re-run again 
with same args and not get 2 more interpreters created?

I will clean up some space and try it again and post back.


---
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 #1596: ZEPPELIN-1616. Interpreter open happens in jobRun

[agoodm]

Github user agoodm commented on the issue:

https://github.com/apache/zeppelin/pull/1596
  
@Leemoonsoo @zjffdu I placed the extra call to `open()` in `jobRun` because 
I wanted to have a convenient place to make calls to `registerHook()`. We can't 
do this in the `Interpreter` constructor since the `InterpreterGroup` (which 
stores the hook registry) will not necessarily be set yet. The only other way I 
can think of doing this without another rewrite of the hook system would be to 
instead override the `setInterpreterGroup()` method to call `registerHook() 
after setting the `InterpreterGroup`. Not very elegant, but it will probably 
get the job done (pun not intended). Actually, it might be the better approach 
to what we are doing now since we would no longer have to worry about checking 
for null pointers.

That being said, could you explain why this change is in itself necessary? 
IIRC, the `client.open()` call you have added to `RemoteInterpreter.java` was 
not there before any of the changes I made.


---
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 #1596: ZEPPELIN-1616. Interpreter open happens in jobRun

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/1596
  
Interpreter open in jobRun introduced in 
https://github.com/apache/zeppelin/pull/1470 by @agoodm, to enable 
https://github.com/apache/zeppelin/pull/1534. #1534 does not work with this 
patch applied. 

@agoodm @zjffdu what do you think? Shell we keep open in jobRun or find 
other way to do?


---
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-1617) Setting null to builtin interpreter settings cause NPE and 503

[Hoon Park (JIRA)]

Hoon Park created ZEPPELIN-1617:
---

 Summary: Setting null to builtin interpreter settings cause NPE 
and 503
 Key: ZEPPELIN-1617
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1617
 Project: Zeppelin
  Issue Type: Bug
  Components: Interpreters
Reporter: Hoon Park


Setting null to interpreter `properties` field cause NPE and 503

You can reproduce this issue by modifying 
`markdown/src/main/resources/interpreter-setting.json` like 

```json
[
  {
"group": "md",
...

"properties": null,
...
  }
```

Then you can get NPE stacktrace and 503 errors



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

[GitHub] zeppelin issue #1583: [MINOR] Turn on authenticaiton in shiro.ini.template b...

[anthonycorbacho]

Github user anthonycorbacho commented on the issue:

https://github.com/apache/zeppelin/pull/1583
  
#1595 will fix this 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 #1587: [ZEPPELIN-1609] using pyspark(python3) with livy inter...

[purechoc]

Github user purechoc commented on the issue:

https://github.com/apache/zeppelin/pull/1587
  
can't do that,
%livy.pyspark support python2 only.



---
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 #1596: ZEPPELIN-1616. Interpreter open happens in jobR...

[zjffdu]

GitHub user zjffdu opened a pull request:

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

ZEPPELIN-1616. Interpreter open happens in jobRun

### What is this PR for?
Not sure why we put interpreter open in jobRun, that means the thrift 
service method open is never used. I think open method in remote interpreter 
process should be called when RemoteInterpreter call open method in client 
side. 


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

### Todos
* [ ] - Task

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


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

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

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

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


commit 3c3542df3f7ae91c2aef55aa23745c3a1c0fd4d3
Author: Jeff Zhang 
Date:   2016-11-04T06:44:37Z

ZEPPELIN-1616. Interpreter open happens in jobRun




---
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-1616) Interpreter open happens in jobRun

[Jeff Zhang (JIRA)]

Jeff Zhang created ZEPPELIN-1616:


 Summary: Interpreter open happens in jobRun
 Key: ZEPPELIN-1616
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1616
 Project: Zeppelin
  Issue Type: Bug
Affects Versions: 0.7.0
Reporter: Jeff Zhang
Assignee: Jeff Zhang






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

[GitHub] zeppelin issue #1565: [ZEPPELIN-1564] Enable note deletion and paragraph out...

[tae-jun]

Github user tae-jun commented on the issue:

https://github.com/apache/zeppelin/pull/1565
  
@anthonycorbacho @khalidhuseynov Thanks for the comment! I agree with you 
guys.

This is a breaking change, so yeah we must be careful. So, if we proceed 
this, new API URL's prefix will be `v1/api/notebook`. And keep legacy API under 
`api/notebook` for backward compatibility. This will be the start of versioning.

I think we should design REST API together. I will create a proposal on 
JIRA soon, please review it when the time comes!

It will be harder to fix later. So, let's start 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 #1591: Fix latency on notebook save in ZeppelinHubNotebookRep...

[anthonycorbacho]

Github user anthonycorbacho commented on the issue:

https://github.com/apache/zeppelin/pull/1591
  
travis is super slow today

Amerika is working to hard today :)


---
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 #1591: [WIP] Fix latency on notebook save in ZeppelinHubNoteb...

[bzz]

Github user bzz commented on the issue:

https://github.com/apache/zeppelin/pull/1591
  
Looks great to me, thank you for fix and prompt response! 

Let's merge after CI is green, if there is no further discussions. 


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