[GitHub] zeppelin issue #1394: rename r directory to 2BWJFTXKJ

2016-09-02 Thread Leemoonsoo
Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/1394
  
Ah I missed the change. 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 #1265: [ZEPPELIN-1210] Run interpreter per user

2016-09-02 Thread corneadoug
Github user corneadoug commented on the issue:

https://github.com/apache/zeppelin/pull/1265
  
Since I don't know much about how the interpreter part works, Its still 
quite confusing.
And I think that having both checkbox and a dropdown might not be helping.

First of all, is there a possibility that by setting 'Per User' or 'Per 
Note', some of the previous settings (isolated or scoped) become meaningless?

Otherwise, I think this could be a good improvement:
![screen shot 2016-09-03 at 1 24 19 
pm](https://cloud.githubusercontent.com/assets/710411/18222699/cd264bf6-71d9-11e6-8215-37b73f6a29f3.png)
First drop down (globally, per user, per note)
Second drop down (shared, scoped, isolated)

Would the 'Connect to existing process' option be part of that second 
dropdown? or is it not related?


---
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 #1400: [ZEPPELIN-1407] Fix Scala 2.11 build

2016-09-02 Thread lresende
Github user lresende commented on the issue:

https://github.com/apache/zeppelin/pull/1400
  
This should go for both master and 0.6x release.


---
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 #1400: [ZEPPELIN-1407] Fix Scala 2.11 build

2016-09-02 Thread lresende
Github user lresende commented on the issue:

https://github.com/apache/zeppelin/pull/1400
  
@bzz @Leemoonsoo Please review, this is more like a hotfix for the build.


---
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 #1400: [ZEPPELIN-1407] Fix Scala 2.11 build

2016-09-02 Thread lresende
GitHub user lresende opened a pull request:

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

[ZEPPELIN-1407] Fix Scala 2.11 build

### What is this PR for?
Avoid activating the Scala 2.10 profile when building for Scala 2.11

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

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

### How should this be tested?
Perform Scala 2.10 and 2.11 builds starting from a maven repository that 
does not have org.apache.zeppelin artifacts.


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

$ git pull https://github.com/lresende/incubator-zeppelin scala-profile

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

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


commit 68da065378764a1ce936bf632a26acd3e1209e55
Author: Luciano Resende 
Date:   2016-09-02T05:35:20Z

[ZEPPELIN-1407] Fix Scala 2.11 build




---
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 #1394: rename r directory to 2BWJFTXKJ

2016-09-02 Thread prabhjyotsingh
Github user prabhjyotsingh commented on the issue:

https://github.com/apache/zeppelin/pull/1394
  
Yes, I did both, rename the directory and 
https://github.com/prabhjyotsingh/zeppelin/blob/5993506b77be84d71ab730c2965572edd73e870e/notebook/2BWJFTXKJ/note.json#L1041


---
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 #1376: [ZEPPELIN-449] Enhance log messages when interpreter i...

2016-09-02 Thread lresende
Github user lresende commented on the issue:

https://github.com/apache/zeppelin/pull/1376
  
Now the issues seems to be related to build timeout ? 
No output has been received in the last 10 minutes, this potentially 
indicates a stalled build or something wrong with the build itself.


---
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 #1334: [ZEPPELIN-682] New interpreter for Apache Beam (incuba...

2016-09-02 Thread bzz
Github user bzz commented on the issue:

https://github.com/apache/zeppelin/pull/1334
  
I think having it as it is now sounds as a good start. It can be always 
enhanced it later on, based on user feedback.

Changes look great to me, thank you!

If that is ok - please let me test it more over the weekend and merge it 
early next week, if there is no further 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 #1265: [ZEPPELIN-1210] Run interpreter per user

2016-09-02 Thread jongyoul
Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/1265
  
Concerning those modes, AFAIK, before Zeppelin 0.6.0, Zeppelin has only 
`shared` mode, but most of users want to run a interpreter with their own, 
Zeppelin add two modes called `scoped` and `isolated`. The main difference 
between them is where that interpreter is launched. `scoped` mode launches an 
interpreter with same process and different thread with its own class loader. 
Otherwise, `isolated` launches different process. `per user` and `per note` are 
dimensions to support those modes.

@zjffdu I also agree we should try to reduce complexity, but we should try 
to keep user experience equally. Zeppelin's users are not only individuals but 
also enterprise. We should consider all of users' experience. And I already 
argued that issue with @Leemoonsoo, and we conclude that keeping current users' 
behaviour is more important than making them simple. I suggest we will start to 
discuss the breaking changes. As you mentioned the above, we should think of 
the relationship of those components.


---
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 #1333: [ZEPPELIN-1334] Environment variable defined in interp...

2016-09-02 Thread bzz
Github user bzz commented on the issue:

https://github.com/apache/zeppelin/pull/1333
  
Very similar test failure as we discussed above happened in un-related 
#1363 
[here](https://s3.amazonaws.com/archive.travis-ci.org/jobs/155836675/log.txt)

```

Failed tests: 
  InterpreterFactoryTest.testRemoteRepl:123 expected: but 
was:


Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.146 sec 
<<< FAILURE! - in org.apache.zeppelin.interpreter.InterpreterFactoryTest
testRemoteRepl(org.apache.zeppelin.interpreter.InterpreterFactoryTest)  
Time elapsed: 0.032 sec  <<< FAILURE!
java.lang.AssertionError: expected: but was:
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:743)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at 
org.apache.zeppelin.interpreter.InterpreterFactoryTest.testRemoteRepl(InterpreterFactoryTest.java:123)

```


---
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 #1389: [ZEPPELIN-1279] Spark on Mesos Docker.

2016-09-02 Thread asfgit
Github user asfgit closed the pull request at:

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


---
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 #1333: [ZEPPELIN-1334] Environment variable defined in interp...

2016-09-02 Thread bzz
Github user bzz commented on the issue:

https://github.com/apache/zeppelin/pull/1333
  
@zjffdu so there must be some state that persists between the runs. 

@Leemoonsoo do you have any idea what that state might be that affects 
`InterpreterFactoryTest `? There seems to be nothing like `@BeforeClass`, etc.

Shall we try re-triggering CI one more time?


---
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 #1376: [ZEPPELIN-449] Enhance log messages when interpreter i...

2016-09-02 Thread lresende
Github user lresende commented on the issue:

https://github.com/apache/zeppelin/pull/1376
  
@bzz Based on the jira, the exception is causing some confusion with users, 
so I would merge, but it's up to the community, I am fine if there are 
objections with this change.

And let me force a build.


---
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 #1371: [ZEPPELIN-1372]Automatically Detect the data type in t...

2016-09-02 Thread bzz
Github user bzz commented on the issue:

https://github.com/apache/zeppelin/pull/1371
  
Looks great to me, thank you @Peilin-Yang !

@corneadoug what do you think?  

Let's merge to master, if there is no further 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 #1376: [ZEPPELIN-449] Enhance log messages when interpreter i...

2016-09-02 Thread bzz
Github user bzz commented on the issue:

https://github.com/apache/zeppelin/pull/1376
  
@lresende shall we merge it or do you find @zjffdu suggestion to work and 
we can close it for now?

Thank you @doanduyhai ! Let's try to close\open it to trigger the CI and 
see if the failure presists


---
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 #1302: [ZEPPELIN-1306] Interpreter restarts on a note.

2016-09-02 Thread bzz
Github user bzz commented on the issue:

https://github.com/apache/zeppelin/pull/1302
  
Looks great to me, thank you @astroshim !

On @corneadoug point - it should be possible to animate the icon button \w 
arrows to be i.e rotating while "restart is in progress" so it stops spinning, 
as soon as restart is done. This might give user a nice visual feedback.

But @astroshim is righ, restart is pretty fast due to the nature of 
implementation - interpreter process just gets killed and then it's is 
lazy-started only on next time user runs the paragraph where it is binded.


---
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 #1378: [ZEPPELIN-1358] Add support to display Pandas DataFram...

2016-09-02 Thread bzz
Github user bzz commented on the issue:

https://github.com/apache/zeppelin/pull/1378
  
I see, indeed we could change the default to always show dataframe index, 
if you think it's more consistent with Python behavior, but let's add a flag 
anyway, so later, in case we decided to switch back - it would be a trivial 
change.

Other then that - looks great to me, 👍  for tests!


---
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-1407) Scala 2.11 build fails with empty maven repository

2016-09-02 Thread Luciano Resende (JIRA)
Luciano Resende created ZEPPELIN-1407:
-

 Summary: Scala 2.11 build fails with empty maven repository
 Key: ZEPPELIN-1407
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1407
 Project: Zeppelin
  Issue Type: Bug
  Components: build
Reporter: Luciano Resende
Assignee: Luciano Resende
Priority: Blocker


rm -rf ~/.m2/repository/org/apache/zeppelin
git clone g...@github.com:apache/zeppelin.git
cd zeppelin
dev/change_scala_version.sh 2.11
mvn -Pspark-2.0 -Pr -Phadoop-2.6 -Psparkr -Ppyspark -Pscalding -Pexamples 
-Pbuild-distr -DskipTests -Dscala-2.11 clean install

Zeppelin Display will fail, and it seems maven is resolving some scala 
libraries to 2.10 and causing compilation issues

[DEBUG] manageArtifactVersion: 
artifact=org.scala-lang:scala-library:jar:2.11.2:test, 
replacement=org.scala-lang:scala-library:jar:2.10.5
[DEBUG] testArtifact: artifact=org.scala-lang:scala-library:jar:2.10.5:test
[DEBUG] manageArtifactVersion: 
artifact=org.scala-lang:scala-library:jar:2.10.5:test, 
replacement=org.scala-lang:scala-library:jar:2.10.5
[DEBUG] omitForNearer: omitted=org.scala-lang:scala-library:jar:2.10.5:test 
kept=org.scala-lang:scala-library:jar:2.10.5:provided
[DEBUG] testArtifact: artifact=org.scala-lang:scala-reflect:jar:2.11.2:test
[DEBUG] includeArtifact: 
artifact=org.scala-lang:scala-reflect:jar:2.11.2:test
[DEBUG] startProcessChildren: 
artifact=org.scala-lang:scala-reflect:jar:2.11.2:test
[DEBUG]   manageArtifactVersion: 
artifact=org.scala-lang:scala-library:jar:2.11.2:test, 
replacement=org.scala-lang:scala-library:jar:2.10.5
[DEBUG]   testArtifact: 
artifact=org.scala-lang:scala-library:jar:2.10.5:test
[DEBUG]   manageArtifactVersion: 
artifact=org.scala-lang:scala-library:jar:2.10.5:test, 
replacement=org.scala-lang:scala-library:jar:2.10.5
[DEBUG]   omitForNearer: 
omitted=org.scala-lang:scala-library:jar:2.10.5:test 
kept=org.scala-lang:scala-library:jar:2.10.5:provided
[DEBUG] endProcessChildren: 
artifact=org.scala-lang:scala-reflect:jar:2.11.2:test
[DEBUG] testArtifact: 
artifact=org.scala-lang.modules:scala-xml_2.11:jar:1.0.2:test
[DEBUG] includeArtifact: 
artifact=org.scala-lang.modules:scala-xml_2.11:jar:1.0.2:test
[DEBUG] startProcessChildren: 
artifact=org.scala-lang.modules:scala-xml_2.11:jar:1.0.2:test
[DEBUG]   manageArtifactVersion: 
artifact=org.scala-lang:scala-library:jar:2.11.1:test, 
replacement=org.scala-lang:scala-library:jar:2.10.5
[DEBUG]   testArtifact: 
artifact=org.scala-lang:scala-library:jar:2.10.5:test
[DEBUG]   manageArtifactVersion: 
artifact=org.scala-lang:scala-library:jar:2.10.5:test, 
replacement=org.scala-lang:scala-library:jar:2.10.5
[DEBUG]   omitForNearer: 
omitted=org.scala-lang:scala-library:jar:2.10.5:test 
kept=org.scala-lang:scala-library:jar:2.10.5:provided

.

[INFO] --- maven-scala-plugin:2.15.2:testCompile (test-compile) @ 
zeppelin-display_2.11 ---
[INFO] Checking for multiple versions of scala
[INFO] includes = [**/*.java,**/*.scala,]
[INFO] excludes = []
[INFO] 
/Users/lresende/opensource/apache/zeppelin/zeppelin/zeppelin-display/src/test/scala:-1:
 info: compiling
[INFO] Compiling 6 source files to 
/Users/lresende/opensource/apache/zeppelin/zeppelin/zeppelin-display/target/test-classes
 at 1472853163836
[ERROR] error: bad symbolic reference. A signature in package.class refers to 
type compileTimeOnly
[INFO] in package scala.annotation which is not available.
[INFO] It may be completely missing from the current classpath, or the version 
on
[INFO] the classpath might be incompatible with the version used when compiling 
package.class.
[ERROR] 
/Users/lresende/opensource/apache/zeppelin/zeppelin/zeppelin-display/src/test/scala/org/apache/zeppelin/display/angular/AbstractAngularElemTest.scala:32:
 error: Reference to class FlatSpec in package scalatest should not have 
survived past type checking,
[INFO] it should have been processed and eliminated during expansion of an 
enclosing macro.
[INFO]   extends FlatSpec with BeforeAndAfter with BeforeAndAfterEach with 
Eventually with Matchers {
[INFO]   ^
[ERROR] 
/Users/lresende/opensource/apache/zeppelin/zeppelin/zeppelin-display/src/test/scala/org/apache/zeppelin/display/angular/AbstractAngularElemTest.scala:63:
 error: Reference to method onClick in class AbstractAngularElem should not 
have survived past type checking,
[INFO] it should have been processed and eliminated during expansion of an 
enclosing macro.
[INFO] val elem = angularElem().onClick(() => {
[INFO] ^

..









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


[GitHub] zeppelin issue #1394: rename r directory to 2BWJFTXKJ

2016-09-02 Thread Leemoonsoo
Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/1394
  
Shell we update 
https://github.com/apache/zeppelin/blob/master/notebook/r/note.json#L1011, too?


---
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 #1384: [ZEPPELIN-1387] Support table syntax in markdown inter...

2016-09-02 Thread 1ambda
Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/1384
  
I'v restored markdown4j parser and add `markdown.parser.type` property to 
`md` group. Pegdown parser will be used only if user specify `pegdown` property 
value.

https://cloud.githubusercontent.com/assets/4968473/18211602/66b9cf9c-7179-11e6-8506-9ae6fcfbfe3b.png;>

One more question. It seems that `description` does't show even if i 
already provide in `markdown/src/main/resources/interpreter-setting.json` like 

```json
[
  {
"group": "md",
"name": "md",
"className": "org.apache.zeppelin.markdown.MarkdownInterpreter",
"properties": {
  "markdown.parser.type": {
"envName": "MARKDOWN_PARSER_TYPE",
"propertyName": "markdown.parser.type",
"defaultValue": "markdown4j",
"description": "Markdown Parser Type. Available values: markdown4j, 
pegdown. Default = markdown4j"
  }
}
  }
]
```
 


---
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 #1384: [ZEPPELIN-1387] Support table syntax in markdown inter...

2016-09-02 Thread 1ambda
Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/1384
  
@Leemoonsoo 

I think **option 2** (Adding a property) is a better solution. because

1) Adding a new interpreter just for support another markdown parser might 
be confusing to users
2) Pegdown parser will be able to replace markdown4j parser soon if we 
implement YUML and Websequence. At that time, we can just modify the parser 
property of `md` interpreter instead of requesting for users to change their 
interpreter type


---
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 #1385: [ZEPPELIN-1395] Local or Remote Interpreter by Configu...

2016-09-02 Thread echarles
Github user echarles commented on the issue:

https://github.com/apache/zeppelin/pull/1385
  
@jongyoul `ZeppelinConfiguration.create()` is now used and method signature 
are now like 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 issue #1390: [WIP] [ZEPPELIN-1339] [ZEPPELIN-1000] [ZEPPELIN-1338] ...

2016-09-02 Thread echarles
Github user echarles commented on the issue:

https://github.com/apache/zeppelin/pull/1390
  
@zjffdu Correct, this PR also implements ZEPPELIN-1338 User level 
interpreter setting (I have updated the title and description on this PR).

@Leemoonsoo Will check and adapt if needed the behavior for multiple owners 
and will further digg into #1265 to assess any conflit/divergence. I'd like to 
second the comment made by @zjffdu in #1265 on the interpreter options 
complexity. Btw, at the time of the introduction of the current interpreter 
modes, I already raised my worries on the complexity of those and honestly I am 
not convinced that I understand them fully (at least at first sight without 
digging into the code) and I fear that #1265 will make the situation still more 
complex. Taking back @zjffdu statement: *Besides, I think we should think more 
deeply on the relationship between note, user and interpreter.*, and I would 
add also the relation with the SearchService, Helium... and any other services 
that Zeppelin uses (cc/ @jongyoul) - All these questions also binds to 
ZEPPELIN-1236 "Multi-user notebook with user controls support" created by 
@frosiere talking about shared dashboard... Having this discussion on the ma
 iling list independently of any PR would better define the efforst to be taken 
in each PR.

@khalidhuseynov I have the bad habit to build with `-Dcheckstyle.skip=true` 
- I commit a fix in the next hour.



---
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 #1394: rename r directory to 2BWJFTXKJ

2016-09-02 Thread echarles
Github user echarles commented on the issue:

https://github.com/apache/zeppelin/pull/1394
  
@prabhjyotsingh yes, assumption is correct. At the time of the R 
interpreter dev, I was used to manually rename the note folder and edit the 
json to set the id the same value.

This PR takes it back to the default layout (didn't test it, but checked 
that the id value in the json was also correct).

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 #1399: [ZEPPELIN-1182] Zeppelin should have Startup an...

2016-09-02 Thread rajarajan-g
GitHub user rajarajan-g opened a pull request:

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

[ZEPPELIN-1182] Zeppelin should have Startup and Shutdown message

### What is this PR for?
PR is for logging configuration details of Zeppelin server.

### What type of PR is it?
Improvement

### Todos
* [ ] - Task

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

### How should this be tested?
Please check the log if information on Server host, server path, context 
path, zeppelin version, class path is available in that file.

### Screenshots (if appropriate)

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

Note:
For configuration details such as  zeppelin version, server host, port 
& context path , these are available as part of zeppelin configuration. 

Logging information

```
 INFO [2016-09-02 14:35:25,218] ({main} 
ZeppelinConfiguration.java[create]:107) - Server Host: 0.0.0.0
 INFO [2016-09-02 14:35:25,218] ({main} 
ZeppelinConfiguration.java[create]:108) - Server Port: 8080
 INFO [2016-09-02 14:35:25,218] ({main} 
ZeppelinConfiguration.java[create]:109) - Context Path: /
 INFO [2016-09-02 14:35:25,224] ({main} 
ZeppelinConfiguration.java[create]:110) - Zeppelin Version: 0.7.0-SNAPSHOT
```

For Zeppelin class path and restart information,  I am logging it from 
Shell script to log file as in below paragraph, So the format of logging is 
different . I know this is not per standards, Please let me know if you have 
any suggestions
```
Zeppelin is restarted

ZEPPELIN_CLASSPATH: 
/home/rajarajang/Workspace/stsWorksapce/zeppelin/zeppelin-server/target/lib/*:/home/rajarajang/Workspace/stsWorksapce/zeppelin/zeppelin-zengine/target/lib/*:/home/rajarajang/Workspace/stsWorksapce/zeppelin/zeppelin-interpreter/target/lib/*:/home/rajarajang/Workspace/stsWorksapce/zeppelin/*::/home/rajarajang/Workspace/stsWorksapce/zeppelin/conf:/home/rajarajang/Workspace/stsWorksapce/zeppelin/zeppelin-interpreter/target/classes:/home/rajarajang/Workspace/stsWorksapce/zeppelin/zeppelin-zengine/target/classes:/home/rajarajang/Workspace/stsWorksapce/zeppelin/zeppelin-server/target/classes
```

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

$ git pull https://github.com/rajarajan-g/zeppelin ZEPPELIN-1182

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

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


commit da69b165dfdd7c3911405ff84d824c9698fe31b0
Author: rajarajan-g 
Date:   2016-09-02T09:21:03Z

Added log statements for configuration




---
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: How to start Zeppelin By IDE

2016-09-02 Thread Kavin Kumar K S
We can use the below commands to run the zeppelin server in IDE.

mvn antrun:run@start-zeppelin
mvn antrun:run@stop-zeppelin

Thanks,
Kavin



--
View this message in context: 
http://apache-zeppelin-dev-mailing-list.75694.x6.nabble.com/How-to-start-Zeppelin-By-IDE-tp14910p14959.html
Sent from the Apache Zeppelin dev mailing list mailing list archive at 
Nabble.com.


[GitHub] zeppelin issue #1393: [ZEPPELIN-1142] Zeppelin allows two users to simultane...

2016-09-02 Thread khalidhuseynov
Github user khalidhuseynov commented on the issue:

https://github.com/apache/zeppelin/pull/1393
  
@kavinkumarks thanks for improvement and it makes sense indeed to assign 
owner when creating note. just need to address above minor comments as well as 
restart CI, some profiles are failing.


---
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 #1365: ZEPPELIN-1374. Should prevent use dot in interp...

2016-09-02 Thread asfgit
Github user asfgit closed the pull request at:

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


---
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 #1398: [MINOR] Doc fix for spark interpreter

2016-09-02 Thread zjffdu
Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/1398
  
\cc @Leemoonsoo @AhyoungRyu 


---
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 #1398: [MINOR] Doc fix for spark interpreter

2016-09-02 Thread zjffdu
GitHub user zjffdu opened a pull request:

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

[MINOR] Doc fix for spark interpreter

### What is this PR for?
Several changes on doc of spark interpreter. 

* %spark, %sql, %pyspark only works when spark is the default interpreter 
group of note. So I update the doc to use the full interpreter name.
* Add SparkSession for 2.0
* Also add comments inline with other changes to explain the reason. 


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

### Todos
* [ ] - Task

### What is the Jira issue?
* No jira created. 

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

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

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


commit 40d4b11e29130fd8256af5c7848a1c7e7013c793
Author: Jeff Zhang 
Date:   2016-09-02T09:30:43Z

[MINOR] Doc fix for spark interpreter




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


[GitHub] zeppelin issue #1369: [ZEPPELIN-1376] Add proxy credentials for dependency r...

2016-09-02 Thread doanduyhai
Github user doanduyhai commented on the issue:

https://github.com/apache/zeppelin/pull/1369
  
@astroshim 

> BTW how come only spark interpreter shows error message bar?

The error popup applies to all interpreters, try to add a fictive 
dependency to `angular` or `shell` interpreter and you'll see also the error 
popup. The error message mentions clearly the `.` that has 
the dependency issue


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


[GitHub] zeppelin pull request #1397: [ZEPPELIN-1406] modify to load method artifact ...

2016-09-02 Thread cloverhearts
GitHub user cloverhearts opened a pull request:

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

[ZEPPELIN-1406] modify to load method artifact local path in Helium 
application json

### What is this PR for?
Currently contained in the Zeppelin Helium application does not work.
The relative value of the configuration file path does incurring call 
normally.
Therefore, it sets the Helium directory you specified in the application 
default directory.
An example of the application was to modify the path of helium.


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

### Todos
- [x] added setter method for artifact in Helium Packakge class
- [x] if not absolute path for artifact then replace to absolute path for 
helium artifact local path
- [x] replace helium example artifact path for json

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

### How should this be tested?
step 1. 
build
```
mvn clean package -DskipTests -Pbuild-distr -Pexamples -DskipTests
```

step 2.
go to web ui and someone notebook.
write paragraph.
here.
```
%spark 
import java.util.Date
new Date();
```

step 3.
choice. 
helium application clock.

working well.


### Screenshots (if appropriate)
 before
does not working.

![noshow](https://cloud.githubusercontent.com/assets/10525473/18199308/afbb3a3a-713a-11e6-926e-c4089874ae5b.png)

 after

![clock](https://cloud.githubusercontent.com/assets/10525473/18199270/83483df4-713a-11e6-9ced-de9b37974f19.png)



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



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

$ git pull https://github.com/cloverhearts/zeppelin 
dev/helium-json-relative-path

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

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


commit ad84e5b6f6945bc6e7209ba19d578fd7bf1c0e04
Author: CloverHearts 
Date:   2016-09-02T09:07:20Z

modification to artifact local path in Helium application json




---
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 #1396: [ZEPPELIN-1405] Remove propertyKeyUnusedConnectionList...

2016-09-02 Thread astroshim
Github user astroshim commented on the issue:

https://github.com/apache/zeppelin/pull/1396
  
\cc @jongyoul Please review this PR if i misunderstand.


---
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 #1396: [ZEPPELIN-1405] Remove propertyKeyUnusedConnect...

2016-09-02 Thread astroshim
GitHub user astroshim opened a pull request:

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

[ZEPPELIN-1405] Remove propertyKeyUnusedConnectionListMap variable in 
JDBCInterpreter

### What is this PR for?
This PR is for refactoring code for JDBCInterpreter.


### What type of PR is it?
Improvement 


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


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



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

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

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

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


commit 12dd7cb239cd22cb85d55221a18bbf157665a45a
Author: astroshim 
Date:   2016-09-02T09:05:50Z

remove propertyKeyUnusedConnectionListMap map




---
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-1405) Refactoring of JDBCInterpreter.

2016-09-02 Thread Shim HyungSung (JIRA)
Shim HyungSung created ZEPPELIN-1405:


 Summary: Refactoring of JDBCInterpreter.
 Key: ZEPPELIN-1405
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1405
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Shim HyungSung


It seems the propertyKeyUnusedConnectionListMap variable don't need in the 
JDBCInterpreter.java.



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


[GitHub] zeppelin issue #1330: [ZEPPELIN-1144]Zeppelin home page should only list not...

2016-09-02 Thread khalidhuseynov
Github user khalidhuseynov commented on the issue:

https://github.com/apache/zeppelin/pull/1330
  
@mwkang thanks for the contribution! actually this is related to multi-user 
note management and there's some work going on under #1392 or #1390 . 

In your case, i tested it, and there's a bit tricky moment with notes 
reloading and broadcasting. For example if you login as user1 with noteA and 
user2 with noteB and initially everything looks as expected, and then you 
reload your notes as shown below with refresh icon:
https://cloud.githubusercontent.com/assets/1642088/18198247/737174ee-7136-11e6-9d94-ba75f6882981.png;>
then if you refresh for user1 then noteA will appear in the list of all 
users, including user2 in our case. Same would happen if you reload for user2, 
meaning noteB will appear in the list of user1. 



---
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 #1388: [ZEPPELIN-1399] Refactor automatic interpreter name in...

2016-09-02 Thread corneadoug
Github user corneadoug commented on the issue:

https://github.com/apache/zeppelin/pull/1388
  
@minahlee Making a new line is a good improvement because some interpreters 
do not handle same line typing.

For removing the default interpreter, I don't have a strong opinion.
If we plan on having the backend provide the interpreter information in the 
paragraph and always show it outside of the text editor, we would remove this 
feature anyway.

However it could feel weird to have Release 0.6.1 have the default 
interpreter shown, 0.6.2 not showing it, then 0.6.3 or 0.7.0 have Interpreter 
always shown again but this time as part of the paragraph (not in text editor)


---
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 #1330: [ZEPPELIN-1144]Zeppelin home page should only list not...

2016-09-02 Thread bzz
Github user bzz commented on the issue:

https://github.com/apache/zeppelin/pull/1330
  
@mwkang could you please try close and then re-open this PR to trigger the 
CI and see if the same issue persists? Thanks!

\cc @khalidhuseynov for 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 issue #1390: [WIP] [ZEPPELIN-1339] [ZEPPELIN-1000] Note and service...

2016-09-02 Thread khalidhuseynov
Github user khalidhuseynov commented on the issue:

https://github.com/apache/zeppelin/pull/1390
  
since this also related to #1265 as well as 
[ZEPPELIN-1338](https://issues.apache.org/jira/browse/ZEPPELIN-1338) for 
interpreter multi user environment, maybe @jongyoul could take more detailed 
look here as well to see possible design, performance, resource utilisation 
issues


---
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 #1388: [ZEPPELIN-1399] Refactor automatic interpreter name in...

2016-09-02 Thread minahlee
Github user minahlee commented on the issue:

https://github.com/apache/zeppelin/pull/1388
  
@corneadoug actually I made it empty intentionally. please check out the 
discussion [here] 
(https://issues.apache.org/jira/browse/ZEPPELIN-707?focusedCommentId=15358493=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15358493)


---
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 #932: Replace CXF with Jersey2 [ZEPPELIN-903]

2016-09-02 Thread bzz
Github user bzz commented on the issue:

https://github.com/apache/zeppelin/pull/932
  
Thank you for addressing licensing issues! 

Let me look into that again and then merge to master, if there is no 
further 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 #1248: [ZEPPELIN-1069]Ignore implicit interpreter when user e...

2016-09-02 Thread bzz
Github user bzz commented on the issue:

https://github.com/apache/zeppelin/pull/1248
  
I'm sorry for delay, @mwkang - my plate was full last week.



---
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 #1395: [ZEPPELIN-1404] invalid html structure for boot...

2016-09-02 Thread cloverhearts
GitHub user cloverhearts opened a pull request:

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

[ZEPPELIN-1404] invalid html structure for bootstrap in interpreter setting 
page

### What is this PR for?
invalid html structure for bootstrap in interpreter setting page.
for example :
correct
```html




```

invalid now.
```html






```
There occurs a problem with the current designers, and shape.

Please, check to Screenshots in this pr.


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

### Todos
- [x] Fixed html structure
- [x] modification to margin for checkbox.

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

### How should this be tested?
click to interpreter menu in web ui.

### Screenshots (if appropriate)
 before wide screen.

![beforewide](https://cloud.githubusercontent.com/assets/10525473/18195922/60cee8ba-7129-11e6-8ec5-08aa2dd67ff1.png)

 after wide screen.

![afterwide](https://cloud.githubusercontent.com/assets/10525473/18195926/653d0756-7129-11e6-8c08-2ba150496e7c.png)
- active stripe table, and fixed margin, and other layout.

 before mobile size screen

![beforemobile](https://cloud.githubusercontent.com/assets/10525473/18195948/91598d5a-7129-11e6-9068-17f9a6b22717.png)

 after mobile size screen

![aftermobile](https://cloud.githubusercontent.com/assets/10525473/18195952/951c7664-7129-11e6-982b-0e5a494c228c.png)



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



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

$ git pull https://github.com/cloverhearts/zeppelin 
dev/interpreter-tag-fixed

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

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


commit 771c9014e8e7b2b759aedafc885d84e37f89283a
Author: CloverHearts 
Date:   2016-09-02T07:12:31Z

fixed to correct html(bootstrap) syntax for interpreter setting 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.
---


[jira] [Created] (ZEPPELIN-1404) invalid html structure for bootstrap in interpreter setting page

2016-09-02 Thread CloverHearts (JIRA)
CloverHearts created ZEPPELIN-1404:
--

 Summary: invalid html structure for bootstrap in interpreter 
setting page
 Key: ZEPPELIN-1404
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1404
 Project: Zeppelin
  Issue Type: Bug
Reporter: CloverHearts
Assignee: CloverHearts


invalid html structure for bootstrap in interpreter setting page.

for example :
# correct

   
   


# invalid now.








There occurs a problem with the current designers, and shape.



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


[GitHub] zeppelin issue #1369: [ZEPPELIN-1376] Add proxy credentials for dependency r...

2016-09-02 Thread astroshim
Github user astroshim commented on the issue:

https://github.com/apache/zeppelin/pull/1369
  
Proxy repo tested and it works properly. :+1: 


---
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 #1265: [ZEPPELIN-1210] Run interpreter per user

2016-09-02 Thread zjffdu
Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/1265
  
Thanks @jongyoul , change it to `isolated` works. 
Regarding the option complexity, I still have concern on that.  So now 
there's 2 dimensions for interpreter (user/note) IIUC. Before 0.6, zeppelin 
don't support shiro and it makes sense to take note as the dimension.  I guess 
the reason we introduce `shared`, `scopes`, `isolated` is because at that time 
we don't have shiro, but we want to control whether to share or isolate 
SparkContext between users. so we introduce `shared`, `scopes`, `isolated` to 
achieve that.  But after 0.6, zeppelin support shiro, I think it is more proper 
to take user as the first dimension (maybe remove note dimension later).

By default each user should run his own interpreter, I think this is the 
most often used scenarios.  For the scenario of `collaborative analysis`, I 
would suggest user to create a new interpreter with option `shared` and set 
permission on that interpreter to control who can share this interpreter across 
users.

Overall, my concern is to reduce complexity. Since zeppelin is a tool and 
bridge between user and spark(other interpreter). The goal of zeppelin is to 
make the life of analyst easier, we should add less complexity as possible on 
the user facing UI. I know break compatibility is bad for user, but complexity 
is also very bad to users,  we should balance them. 

**Besides, I think we should think more deeply on the relationship between 
note, user and interpreter.** 




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


[GitHub] zeppelin issue #1265: [ZEPPELIN-1210] Run interpreter per user

2016-09-02 Thread corneadoug
Github user corneadoug commented on the issue:

https://github.com/apache/zeppelin/pull/1265
  
@jongyoul Can you make a quick recap on the difference between all of those 
options?
(perUser, perNote, shared, scopes, isolated)


---
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 #1302: [ZEPPELIN-1306] Interpreter restarts on a note.

2016-09-02 Thread corneadoug
Github user corneadoug commented on the issue:

https://github.com/apache/zeppelin/pull/1302
  
My only feedback is that right now, it's hard to know if the interpreter 
has finished restarting or not.
My guess is that it takes some time, so you shouldn't be able to restart it 
again and you should be warned somehow when it's 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 issue #1265: [ZEPPELIN-1210] Run interpreter per user

2016-09-02 Thread jongyoul
Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/1265
  
About the first comment you should set `scoped` or `isolated`, not
`shared`. And growth of complexity is to remain backward compatibility. I
also agree that interpreter setting become too many. But if we may break
the current behaviour, we should discuss first and then change it. To make
that setting global is more easier than now, but we should try to reduce
the change when users upgrade Zeppelin.

On Friday, 2 September 2016, Jeff Zhang  wrote:

> Besides I have other 2 concerns.
>
>-
>
>I am a little confused about the combination of the interpreter
>options. There's so many combinations (2*2*3=12), I am not sure
>whether users are comfortable with that.
>
>[image: image]
>

>-
>
>Is it necessary to apply this feature globally ? For now it seems
>spark interpreter is the only one that needs it as we want each user 
has
>his own SparkContext. I don't see the necessary that other interpreter
>needs that. (At least it is not necessary for livy, as livy interpreter
>will create spark session per user)
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> , or 
mute
> the thread
> 

> .
>


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



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