[GitHub] zeppelin pull request #1549: ZEPPELIN-1547. Paragraph text should be trimmed

2016-10-21 Thread zjffdu
GitHub user zjffdu opened a pull request:

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

ZEPPELIN-1547. Paragraph text should be trimmed

### What is this PR for?
The paragraph text should be trimmed, otherwise repl name can not be 
correctly recognized. 


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

### Todos
* [ ] - Task

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

### How should this be tested?
Unit test is added

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

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

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


commit 40194e7bcaa6d69ee1ab94e28506319edba84935
Author: Jeff Zhang 
Date:   2016-10-22T05:31:08Z

ZEPPELIN-1547. Paragraph text should be trimmed




---
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-1574) Paragraph text should be trimmed

2016-10-21 Thread Jeff Zhang (JIRA)
Jeff Zhang created ZEPPELIN-1574:


 Summary: Paragraph text should be trimmed
 Key: ZEPPELIN-1574
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1574
 Project: Zeppelin
  Issue Type: Bug
Affects Versions: 0.6.2
Reporter: Jeff Zhang
Assignee: Jeff Zhang






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


[GitHub] zeppelin issue #1548: Commented the properties in interpreter file and added...

2016-10-21 Thread jongyoul
Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/1548
  
Can you change the title of this PR including jira issue number and title?


---
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 #1514: ZEPPELIN-1516. NPE LivySparkSQLInterpreter thrown with...

2016-10-21 Thread zjffdu
Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/1514
  
I plan to do it after #1462, could you also take a look at #1462 ?


---
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 #1548: Commented the properties in interpreter file and added...

2016-10-21 Thread jongyoul
Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/1548
  
Thanks for the contribution. I left a comment and please check 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 #1538: [ZEPPELIN-1386] Docker images for running Apache Zeppe...

2016-10-21 Thread mfelgamal
Github user mfelgamal commented on the issue:

https://github.com/apache/zeppelin/pull/1538
  
@bzz Thank you for your feedback. A MD documentation page is added to the 
install section of Zeppelin documentation.


---
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 #1514: ZEPPELIN-1516. NPE LivySparkSQLInterpreter thrown with...

2016-10-21 Thread felixcheung
Github user felixcheung commented on the issue:

https://github.com/apache/zeppelin/pull/1514
  
looks good. is it possible to have a test for this?


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


[GitHub] zeppelin issue #1302: [ZEPPELIN-1306] Interpreter restarts on a note.

2016-10-21 Thread astroshim
Github user astroshim commented on the issue:

https://github.com/apache/zeppelin/pull/1302
  
re-trigger CI


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

2016-10-21 Thread astroshim
Github user astroshim closed the pull request at:

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


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

2016-10-21 Thread astroshim
GitHub user astroshim reopened a pull request:

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

[ZEPPELIN-1306] Interpreter restarts on a note.

### What is this PR for?
This PR is for usability of restarting interpreter. 


### What type of PR is it?
Improvement


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


### How should this be tested?
You can restart interpreter on the interpreter binding page on a note.
and can only restart ```scoped``` and ```isolated``` interpreter.
Please refer to screen shot.


### Screenshots (if appropriate)

![restartintp](https://cloud.githubusercontent.com/assets/3348133/17474018/b2739462-5d8e-11e6-81bb-da15544547a5.gif)



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



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

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

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

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


commit 5ad4503951e252b5a8be52f66a271e1ac913
Author: astroshim 
Date:   2016-08-08T07:26:32Z

Interpreter restarts on a note.

commit 439b3613d9ee6bcbf2b60499c6c1d72bb6a9b9d1
Author: astroshim 
Date:   2016-08-08T08:50:38Z

fix js code style.

commit 4dbe05ae1c811fed5db0b7bb1575bcdb4c08e8b4
Author: astroshim 
Date:   2016-08-14T16:01:36Z

change argument string to boolean

commit 03bdd05cb4d8cec5057c29a1dbe7f14dbf2d3c09
Author: astroshim 
Date:   2016-08-17T02:16:21Z

Merge branch 'master' into ZEPPELIN-1306

commit e698e6f91c6acf16605cdc5239096df0e9bfa98e
Author: astroshim 
Date:   2016-08-22T02:13:26Z

change method name

commit 322d427f26cf0cbe0108e363126e4ecef14c15d4
Author: astroshim 
Date:   2016-08-26T01:22:07Z

Merge branch 'master' into ZEPPELIN-1306

commit 29966a0194df23f67e95450f7fd1b05cd66bb0cb
Author: astroshim 
Date:   2016-08-26T16:38:28Z

change UI and restart interpreter process

commit 50c6acf9c796f2908f70845dd4d1c447a0d68863
Author: astroshim 
Date:   2016-08-26T16:41:11Z

delete unnecessary code

commit 2cea65bff322f0372d2c1df48ffe1b17823b7aba
Author: astroshim 
Date:   2016-08-26T16:56:34Z

change method name

commit f9ea386453e1db6ff8b910bcccdb0bb246445a6e
Author: astroshim 
Date:   2016-08-27T15:17:24Z

fix code style

commit a980500f68e6b49c34d7c44342b81bc8a3ff6e22
Author: astroshim 
Date:   2016-08-28T11:39:48Z

update html

commit 123882df7dc546539bc4e430ab596ad665d064b6
Author: astroshim 
Date:   2016-08-28T13:50:39Z

change button to icon

commit aa30b3966e16fb0da61a963a6ac382190413f720
Author: astroshim 
Date:   2016-08-31T15:59:08Z

inactive link when interpreter is not selected.

commit 78fdd74ba8124493086332f5905695db6244004a
Author: astroshim 
Date:   2016-09-06T05:05:42Z

update alert message.

commit ecfa7fbccb56bec87b2f2cb6e8fbe6d8736f35f6
Author: astroshim 
Date:   2016-09-07T07:47:53Z

remove dud code.

commit 0453402769ab34bc744610f8f9404ff11033ed42
Author: astroshim 
Date:   2016-09-09T06:23:56Z

Merge branch 'master' into ZEPPELIN-1306

commit 3127154ef5560bd86f3407d32edc9dd53fa15f71
Author: astroshim 
Date:   2016-09-16T13:18:35Z

Merge branch 'master' into ZEPPELIN-1306

commit 72a2259522b6975df069b507d7c8b58ca007d0af
Author: astroshim 
Date:   2016-09-16T14:55:42Z

add testcase and fix the doc.

commit 4c4339f513f365aecf55bce466b20a92e4166678
Author: astroshim 
Date:   2016-09-21T12:52:34Z

Merge branch 'master' into ZEPPELIN-1306

commit 5c4b32a4646da0e14123e14685e0d58b2b087d02
Author: astroshim 
Date:   2016-09-27T02:51:05Z

Merge branch 'master' into ZEPPELIN-1306

commit fa45bb55b2f8311e30cd8ceb7e24c73cb14505a8
Author: astroshim 
Date:   2016-09-27T13:05:51Z

remove debug log

commit 36f564273e2eaeeec97453151e315469d8026c90
Author: astroshim 
Date:   2016-10-04T14:53:09Z

add InterpreterForNote testcase

commit e8e0c179b11efb9f16deb9a657ea81455e3093eb
Author: astroshim 
Date:   2016-10-11T00:05:39Z

rebase

commit 499aa6bf3439b9e2524de59067f6d88eb6aec9bf
Author: astroshim 
Date:   2016-10-19T23:31:04Z

add PySparkInterpreter testcase

commit 

[GitHub] zeppelin pull request #1548: Commented the properties in interpreter file an...

2016-10-21 Thread meenakshisekar
GitHub user meenakshisekar opened a pull request:

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

Commented the properties in interpreter file and added setting file.

### What is this PR for?
This handles replacing the registration of interpreter with static block by 
the interpreter-setting.json file



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

### Todos
Sub-Task

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

### How should this be tested?
here shouldn't be any warning like below on starting the server
INFO [2016-09-29 00:25:46,247] ({main} LensInterpreter.java[]:155) 
- Bootstrapping Cassandra Interpreter WARN [2016-09-29 00:25:46,250] ({main} 
Interpreter.java[register]:347) - Static initialization is deprecated for 
interpreter lens, You should change it to use interpreter-setting.json in your 
jar or interpreter/{interpreter}/interpreter-setting.json INFO [2016-09-29 
00:25:46,250] ({main} InterpreterFactory.java[init]:204) - 
Inclass=org.apache.zeppelin.lens.LensInterpreter

And ensure that the lens related paragraphs run without any error

### 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/meenakshisekar/zeppelin ZEPPELIN-917

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

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


commit db2827f867199cdd5e3fe2bc05f614dd88e013f5
Author: meenakshisekar 
Date:   2016-10-21T09:59:38Z

Commented the properties in interpreter file and added setting file.

commit f94c8a3d44d441174fff2e89708e9ec62c1f5d22
Author: meenakshisekar 
Date:   2016-10-21T11:41:58Z

Commented the properties in interpreter file and added setting file.




---
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 #1547: responce => response

2016-10-21 Thread jongyoul
Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/1547
  
I think you'd better push another commit in #1544. I think that would be 
better process to handle issue. Can you do that?


---
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-1573) ClassNotFoundException: org.apache.zeppelin.spark.ZeppelinContext when using Zeppelin's input value inside spark DataFrame filter method running on Spark Standalone Cl

2016-10-21 Thread Thiago Siqueira (JIRA)
Thiago Siqueira created ZEPPELIN-1573:
-

 Summary: ClassNotFoundException: 
org.apache.zeppelin.spark.ZeppelinContext when using Zeppelin's input value 
inside spark DataFrame filter method running on Spark Standalone Cluster
 Key: ZEPPELIN-1573
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1573
 Project: Zeppelin
  Issue Type: Bug
  Components: Interpreters
Affects Versions: 0.6.2
 Environment: Red Hat Enterprise Linux Server release 7.2 (Maipo), 
Java HotSpot(TM) 64-Bit Server VM (build 25.101-b13, mixed mode)
Reporter: Thiago Siqueira
Priority: Minor


ClassNotFoundException: org.apache.zeppelin.spark.ZeppelinContext when using 
Zeppelin's input value inside spark DataFrame filter method running on Spark 
Standalone Cluster

val city = z.select("City",cities).toString
oDF.select("city").filter(r => city.equals(r.getAs[String]("city"))).count()
I even tried copying the input value to another val with

new String(bytes[])
but still get the same error.

The same code work seamlessly if instead of getting the value from z.select I 
declare as a String literal

city: String = "NY"
org.apache.spark.SparkException: Job aborted due to stage failure: Task 0
in stage 49.0 failed 4 times, most recent failure: Lost task 0.3 in stage
49.0 (TID 277, 10.6.60.217): java.lang.NoClassDefFoundError:
Lorg/apache/zeppelin/spark/ZeppelinContext;

org.apache.spark.SparkException: Job aborted due to stage failure: Task 0 in 
stage 88.0 failed 4 times, most recent failure: Lost task 0.3 in stage 88.0 
(TID 5675, 10.6.60.219): ExecutorLostFailure (executor 27 exited caused by one 
of the running tasks) Reason: Remote RPC client disassociated. Likely due to 
containers exceeding thresholds, or network issues. Check driver logs for WARN 
messages.
Driver stacktrace:
  at 
org.apache.spark.scheduler.DAGScheduler.org$apache$spark$scheduler$DAGScheduler$$failJobAndIndependentStages(DAGScheduler.scala:1450)
  at 
org.apache.spark.scheduler.DAGScheduler$$anonfun$abortStage$1.apply(DAGScheduler.scala:1438)
  at 
org.apache.spark.scheduler.DAGScheduler$$anonfun$abortStage$1.apply(DAGScheduler.scala:1437)
  at 
scala.collection.mutable.ResizableArray$class.foreach(ResizableArray.scala:59)
  at scala.collection.mutable.ArrayBuffer.foreach(ArrayBuffer.scala:48)
  at org.apache.spark.scheduler.DAGScheduler.abortStage(DAGScheduler.scala:1437)
  at 
org.apache.spark.scheduler.DAGScheduler$$anonfun$handleTaskSetFailed$1.apply(DAGScheduler.scala:811)
  at 
org.apache.spark.scheduler.DAGScheduler$$anonfun$handleTaskSetFailed$1.apply(DAGScheduler.scala:811)
  at scala.Option.foreach(Option.scala:257)
  at 
org.apache.spark.scheduler.DAGScheduler.handleTaskSetFailed(DAGScheduler.scala:811)
  at 
org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.doOnReceive(DAGScheduler.scala:1659)
  at 
org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.onReceive(DAGScheduler.scala:1618)
  at 
org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.onReceive(DAGScheduler.scala:1607)
  at org.apache.spark.util.EventLoop$$anon$1.run(EventLoop.scala:48)
  at org.apache.spark.scheduler.DAGScheduler.runJob(DAGScheduler.scala:632)
  at org.apache.spark.SparkContext.runJob(SparkContext.scala:1871)
  at org.apache.spark.SparkContext.runJob(SparkContext.scala:1884)
  at org.apache.spark.SparkContext.runJob(SparkContext.scala:1897)
  at org.apache.spark.SparkContext.runJob(SparkContext.scala:1911)
  at org.apache.spark.rdd.RDD$$anonfun$collect$1.apply(RDD.scala:893)
  at 
org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:151)
  at 
org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:112)
  at org.apache.spark.rdd.RDD.withScope(RDD.scala:358)
  at org.apache.spark.rdd.RDD.collect(RDD.scala:892)
  at 
org.apache.spark.sql.execution.SparkPlan.executeCollect(SparkPlan.scala:290)
  at 
org.apache.spark.sql.Dataset$$anonfun$org$apache$spark$sql$Dataset$$execute$1$1.apply(Dataset.scala:2183)
  at 
org.apache.spark.sql.execution.SQLExecution$.withNewExecutionId(SQLExecution.scala:57)
  at org.apache.spark.sql.Dataset.withNewExecutionId(Dataset.scala:2532)
  at 
org.apache.spark.sql.Dataset.org$apache$spark$sql$Dataset$$execute$1(Dataset.scala:2182)
  at 
org.apache.spark.sql.Dataset.org$apache$spark$sql$Dataset$$collect(Dataset.scala:2189)
  at org.apache.spark.sql.Dataset$$anonfun$count$1.apply(Dataset.scala:2217)
  at org.apache.spark.sql.Dataset$$anonfun$count$1.apply(Dataset.scala:2216)
  at org.apache.spark.sql.Dataset.withCallback(Dataset.scala:2545)
  at org.apache.spark.sql.Dataset.count(Dataset.scala:2216)
  ... 47 elided



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


[jira] [Created] (ZEPPELIN-1572) Let SparkInterpreter use Credentials

2016-10-21 Thread Jongyoul Lee (JIRA)
Jongyoul Lee created ZEPPELIN-1572:
--

 Summary: Let SparkInterpreter use Credentials
 Key: ZEPPELIN-1572
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1572
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Jongyoul Lee






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


[GitHub] zeppelin issue #1520: [ZEPPELIN-1061] Select default interpreter while creat...

2016-10-21 Thread AhyoungRyu
Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/1520
  
@kavinkumarks Thanks for your contribution. Tested and it works well! 

Can we reset the selected interpreter in the note creation page? Currently 
the dialog keeps the previously selected one.

![interpreter_selection](https://cloud.githubusercontent.com/assets/10060731/19592458/d504e33e-97b6-11e6-9589-8a97399a8470.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 #1545: ZEPPELIN-1571. Support pig udf interpreter

2016-10-21 Thread zjffdu
Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/1545
  
Thanks @minahlee It works 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 #1540: [WIP][ZEPPELIN-1566] Make paragraph editable with doub...

2016-10-21 Thread minahlee
Github user minahlee commented on the issue:

https://github.com/apache/zeppelin/pull/1540
  
@jongyoul Thank you for suggestion!
As you might see I set `editOnDblClick` to be `true` for angular, markdown.

I think make markdown paragraph editable with double click is quite common 
behavior. Jupyter notebook and databricks cloud would be the example. Also in 
ux point of view, I think it would be rare to show both editor and output at 
the same time for markdown paragraph.

But not sure what would be better for angular paragraph.

What do you think?



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


[GitHub] zeppelin pull request #1547: responce => response

2016-10-21 Thread hunylee
GitHub user hunylee opened a pull request:

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

responce => response

### What is this PR for?
A few sentences describing the overall goals of the pull request's commits.
First time? Check out the contributing guide - 
https://zeppelin.apache.org/contribution/contributions.html


### What type of PR is it?
[Bug Fix | Improvement | Feature | Documentation | Hot Fix | Refactoring]

### Todos
* [ ] - Task

### What is the Jira issue?
* Open an issue on Jira https://issues.apache.org/jira/browse/ZEPPELIN/
* Put link here, and add [ZEPPELIN-*Jira number*] in PR title, eg. 
[ZEPPELIN-533]

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

### Screenshots (if appropriate)

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

responce => response

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

$ git pull https://github.com/hunylee/zeppelin patch-2

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

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


commit 3afa78c3198eb017dff6e7bf8dc00f916eb4a873
Author: terrylee 
Date:   2016-10-21T07:22:04Z

responce => response

responce => response




---
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 #1547: responce => response

2016-10-21 Thread hunylee
Github user hunylee commented on the issue:

https://github.com/apache/zeppelin/pull/1547
  
responce is error.
response is correct


---
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 #1546: [ Hotfix ] Incorrect (per user) setup ui for "create n...

2016-10-21 Thread cloverhearts
Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/1546
  
@jongyoul
could you please review for this pr?


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


[GitHub] zeppelin pull request #1546: [ Hotfix ] Incorrect (per user) setup ui for "c...

2016-10-21 Thread cloverhearts
Github user cloverhearts closed the pull request at:

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


---
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 #1546: [ Hotfix ] Incorrect (per user) setup ui for "c...

2016-10-21 Thread cloverhearts
GitHub user cloverhearts reopened a pull request:

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

[ Hotfix ] Incorrect (per user) setup ui for "create new interpreter 
component"

### What is this PR for?
A few sentences describing the overall goals of the pull request's commits.
First time? Check out the contributing guide - 
https://zeppelin.apache.org/contribution/contributions.html


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

### Todos
- [x] fix to text margin top
- [x] implement to (per note / per user) setup feature of create new 
insterpreter 

### How should this be tested?
1. on click interpreter menu.
2. on click interpreter menu.
3. check per user and per note setting. (`per user` setting must be shiro 
is activated)
4. save and check to result.

### Screenshots (if appropriate)
 - Create new Interpreter  - before

![pernotebefore](https://cloud.githubusercontent.com/assets/10525473/19588103/6d1236a4-979e-11e6-972b-bb6d35f83ac5.png)

 - Create new Interpreter  - after
![new create 
interpreter](https://cloud.githubusercontent.com/assets/10525473/19588118/87ad23ca-979e-11e6-9a2b-4ec8be27c74f.png)

 - fix margin for interpreter settings  - before

![pernotebefore](https://cloud.githubusercontent.com/assets/10525473/19588140/a8b701ee-979e-11e6-804b-4e39c063281d.png)

 - fix margin for interpreter settings  - after

![margin](https://cloud.githubusercontent.com/assets/10525473/19588145/b13ca8f0-979e-11e6-9a02-186b92a0dad1.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 
hotfix-inerpreterRunningModeUIFix

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

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


commit ebf1d811c7e6b34cf5af85ef5a2a2f6d1b9b2910
Author: CloverHearts 
Date:   2016-10-21T05:40:01Z

hotfix - change setup ui for interpreter setting 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 #1545: ZEPPELIN-1571. Support pig udf interpreter

2016-10-21 Thread minahlee
Github user minahlee commented on the issue:

https://github.com/apache/zeppelin/pull/1545
  
js file for java syntax highlight(`mode-java.js`) is never used before so 
you will need to import it first.
Here are the files where `mode-java.js` should be added:

https://github.com/apache/zeppelin/blob/master/zeppelin-web/src/index.html#L123
https://github.com/apache/zeppelin/blob/master/zeppelin-web/bower.json#L51


---
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 #1545: ZEPPELIN-1571. Support pig udf interpreter

2016-10-21 Thread zjffdu
Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/1545
  
@minahlee The syntax highlight for java doesn't work, could you help to 
check what's I missing here ? 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 #1545: ZEPPELIN-1571. Support pig udf interpreter

2016-10-21 Thread zjffdu
Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/1545
  
@felixcheung @AhyoungRyu  Please help 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.
---