[GitHub] zeppelin issue #2251: [ZEPPELIN-2403] added interpreter property types

[tinkoff-dwh]

Github user tinkoff-dwh commented on the issue:

https://github.com/apache/zeppelin/pull/2251
  
@1ambda 
widget is ok. About another widgets: angular-xeditable has no 
implementations for that (there are html5 inputs but old browsers not support 
html5)


---
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-2419) Interpreter Status in Notebook

[Vipul Modi (JIRA)]

Vipul Modi created ZEPPELIN-2419:


 Summary: Interpreter Status in Notebook
 Key: ZEPPELIN-2419
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2419
 Project: Zeppelin
  Issue Type: Task
Reporter: Vipul Modi
Assignee: Vipul Modi


It will be good to show interpreter status for interpreters bound to the 
notebook, details like interpreter is starting or running or stopped. Provide 
information on if the dependency download failed. Any other details. Details 
may vary for different interpreter group, not sure if a generic template makes 
sense.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (ZEPPELIN-2418) show dialog if user set to the empty owner permission

[Sora Lee (JIRA)]

Sora Lee created ZEPPELIN-2418:
--

 Summary: show dialog if user set to the empty owner permission
 Key: ZEPPELIN-2418
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2418
 Project: Zeppelin
  Issue Type: Bug
Reporter: Sora Lee
Assignee: Sora Lee


If user sets the empty {{Owners}} permission, the {{Owners}} is filled with  
current user. for example,  if user set only {{Readers}} permission, all field 
{{Wirters and Owers}} is full of current user.

It would be nice to show dialog if changing the empty {{Owners}} permission.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zeppelin issue #2133: [ZEPPELIN-1357,1892,1370][Umbrella] Text overlap in th...

[soralee]

Github user soralee commented on the issue:

https://github.com/apache/zeppelin/pull/2133
  
@Leemoonsoo Ready to merge!


---
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 #2256: [ZEPPELIN-2315] (bug) new note.json is overwritten by ...

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/2256
  
Ok make sense. 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.
---

[jira] [Created] (ZEPPELIN-2417) bump apache mahout to version 0.13.0

[Trevor Grant (JIRA)]

Trevor Grant created ZEPPELIN-2417:
--

 Summary: bump apache mahout to version 0.13.0
 Key: ZEPPELIN-2417
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2417
 Project: Zeppelin
  Issue Type: Improvement
Affects Versions: 0.8.0
Reporter: Trevor Grant
Assignee: Trevor Grant


Apache Mahout has released 0.13.0

Update to reflect version change
Drop dependency on spark-shell 
Include dependencies on ViennaCL and OMP (which will utilize GPUs if present 
and fall back to CPUs if not for BLAS ops)

Maintain 0.12.2 support for Flink(?) Flink bindings are no longer included in 
Mahout release



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (ZEPPELIN-2416) Make Spark Properties Optional in Spark Interperter

[Russell Spitzer (JIRA)]

Russell Spitzer created ZEPPELIN-2416:
-

 Summary: Make Spark Properties Optional in Spark Interperter
 Key: ZEPPELIN-2416
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2416
 Project: Zeppelin
  Issue Type: Improvement
  Components: Interpreters
Affects Versions: 0.7.1
Reporter: Russell Spitzer
Priority: Trivial


I was doing some experimentation connecting Zepplin to DataStax Enterprise and 
I noticed that the Spark Interperter requires the "master" interpreter 
parameter to be present in order to work. There are several locations which do  
null-unsafe operations against the return value of getProperty("master")

See
https://github.com/apache/zeppelin/blob/v0.7.1/spark/src/main/java/org/apache/zeppelin/spark/SparkInterpreter.java#L310

Then the value of this property is set in the SparkConf even if the value is 
already set there.
https://github.com/apache/zeppelin/blob/v0.7.1/spark/src/main/java/org/apache/zeppelin/spark/SparkInterpreter.java#L335
and
https://github.com/apache/zeppelin/blob/v0.7.1/spark/src/main/java/org/apache/zeppelin/spark/SparkInterpreter.java#L449

For this and other parameters it might make sense to allow values that are 
already set to be used and not overwritten. This would allow Zepplin to work 
better with "spark-defaults" and those vendors which preset these parameters in 
the environment.

I would propose that all interpreter properties be optional. Operationally this 
means that the "master" is allowed to be unset if it can be automatically 
inherited from the environment in the SparkConf. Other parameters would simply 
need a null check, where they would not be set if they are already null (unset).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zeppelin issue #2256: [ZEPPELIN-2315] (bug) new note.json is overwritten by ...

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2256
  
Old version zeppelins will not render converted note.json. On the other 
hand, if we keep 'result', they can render last version of old format. Is it ok?


---
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 #2251: [ZEPPELIN-2403] added interpreter property types

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2251
  
One suggestion. What about calling them as 'widget' or something instead of 
'type'? cause we might add actual type like 'number', 'string',... as 
@leemoonsu mentioned.


---
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-2415) Auto-suggestion of interpreter permissions should list roles as well

[Paul Brenner (JIRA)]

Paul Brenner created ZEPPELIN-2415:
--

 Summary: Auto-suggestion of interpreter permissions should list 
roles as well
 Key: ZEPPELIN-2415
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2415
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Paul Brenner


Auto-suggestion of interpreter permissions should list roles as well. This has 
already been implemented for notebook permissions in: 
https://issues.apache.org/jira/browse/ZEPPELIN-1237

If there is anywhere else that permissions are used similarly to how they are 
implemented in interpreter or notebook permissions we should probably identify 
those and implement groups there for consistency as well



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zeppelin issue #2257: [Branch-0.7] Support for Zeppelin Context redefinition...

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/2257
  
I'll merge it as hotfix into branch-0.7


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

[GitHub] zeppelin pull request #2257: [Branch-0.7] Fixes a build problem in Zeppelin ...

[cloverhearts]

GitHub user cloverhearts opened a pull request:

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

[Branch-0.7] Fixes a build problem in Zeppelin branch0.7.

Fixes a build problem in Zeppelin branch0.7.
Hotfix.

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

$ git pull https://github.com/cloverhearts/zeppelin 
fix/branch-0.7-build-hotfix

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

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


commit a3a615c3bf0be92089d03105b0fad96a05b66940
Author: CloverHearts 
Date:   2017-04-12T08:14:36Z

[Zeppelin-802] Support for Zeppelin Context redefinition on Python and 
Pyspark

If you override the reserved word ZeppelinContext such as `z` in the python 
language, the whole paragraph output problem occurred.
I have taken care to avoid this issue.

`z` == `_zc` == `zeppelin context`

Improvement

https://issues.apache.org/jira/browse/ZEPPELIN-802

The error should not occur in the following situations:
```
%python
z = 1
print("Hello Zeppelin")
```

```
%pyspark
z = 1
print("Hello Zeppelin")
```

![replace zeppelin 
context-err](https://cloud.githubusercontent.com/assets/10525473/24521772/319946be-15c8-11e7-96cf-7fdf41c70a66.png)

![replace zeppelin 
context](https://cloud.githubusercontent.com/assets/10525473/24521775/349fa7cc-15c8-11e7-8fe4-4f3f5597deff.png)

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

Author: CloverHearts 
Author: cloverhearts 

Closes #2207 from cloverhearts/ZEPPELIN-802-pyspark-zeppelin-context and 
squashes the following commits:

cc986010 [CloverHearts] added completion on namespace
14695cb8 [CloverHearts] Recovering a member name that is not associated 
with a namespace
31af92ab [CloverHearts] fix test case _zc to __zeppelin__
6697d677 [CloverHearts] apply to namespace and replace name _zc to 
__zeppelin__
ca795cff [cloverhearts] replace output
1d372df4 [cloverhearts] change name logger
4e8435ac [CloverHearts] added test case on python
b6b804ad [CloverHearts] replace name zeppelin context on python
9fbf70d6 [CloverHearts] fix pyspark test case
987e2118 [CloverHearts] added test code
5da3d6ed [CloverHearts] replace name zeppelin context on pyspark

(cherry picked from commit 8d03920b9bec86dd8e2fc343d32749a08f501362)
Signed-off-by: CloverHearts 

commit 2da0b423bb3075d6b960d2f8dbb5466f5f11b733
Author: CloverHearts 
Date:   2017-04-17T13:39:08Z

fix branch-0.7 build error




---
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 #2256: [ZEPPELIN-2315] (bug) new note.json is overwritten by ...

[jongyoul]

Github user jongyoul commented on the issue:

https://github.com/apache/zeppelin/pull/2256
  
How about to remove old result after merged to new one?


---
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-2414) Memory leak under scoped mode of SparkInterpreter caused by inapproprately setting Thread.contextClassLoader

[Mori[A]rty (JIRA)]

Mori[A]rty created ZEPPELIN-2414:


 Summary: Memory leak under scoped mode of SparkInterpreter caused 
by inapproprately setting Thread.contextClassLoader
 Key: ZEPPELIN-2414
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2414
 Project: Zeppelin
  Issue Type: Bug
  Components: Interpreters
Affects Versions: 0.6.2
 Environment: {quote}
jdk version: jdk1.7.0_67

spark interpreter env:
export MASTER=local\[4\]
export SPARK_SUBMIT_OPTIONS="--driver-memory 2G"
{quote}
Reporter: Mori[A]rty
 Fix For: 0.6.3


When using scoped mode of SparkInterpreter, after several repetitions of these 
three steps (create-notebook -> run a paragraph -> remove-notebook), the heap 
of RemoteInterpreterServer process will grow to 100% rapidly.

For example, in my local environment, RemoteInpreterServer's max heap size is 2 
GB. After I repeatedly run a simple paragrah
{quote}%spark 
sc{quote}
15 times (each time in a new notebook and delete the notebook after running), 
RemoteInpreterServer's heap has no more free space and the 15th execution of 
the paragrah was never finished.

heap occupation:
{quote}
  S0 S1 E  O  P YGC YGCTFGCFGCT GCT   
  0.00   0.00 100.00  99.98  49.38 192.304  1093  798.293  800.597
{quote}




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zeppelin issue #2256: [ZEPPELIN-2315] (bug) new note.json is overwritten by ...

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2256
  
Do we need 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 #2234: [ZEPPELIN-2374] sorting notes tree

[tinkoff-dwh]

Github user tinkoff-dwh commented on the issue:

https://github.com/apache/zeppelin/pull/2234
  
ready to 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 #2251: [ZEPPELIN-2403] added interpreter property types

[tinkoff-dwh]

Github user tinkoff-dwh commented on the issue:

https://github.com/apache/zeppelin/pull/2251
  
add

![n_add](https://cloud.githubusercontent.com/assets/25951039/25084422/c9f6aafe-2375-11e7-8952-36aee06d4637.png)

edit

![n_edit](https://cloud.githubusercontent.com/assets/25951039/25084424/c9f7d064-2375-11e7-85ae-b936b1c2c770.png)

view

![n_view](https://cloud.githubusercontent.com/assets/25951039/25084423/c9f735e6-2375-11e7-9a2d-27818781a32a.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.
---

[jira] [Created] (ZEPPELIN-2413) SparkInterpreter: Add parameter to chose default scheduler pool

[Fabian Boehnlein (JIRA)]

Fabian Boehnlein created ZEPPELIN-2413:
--

 Summary: SparkInterpreter: Add parameter to chose default 
scheduler pool
 Key: ZEPPELIN-2413
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2413
 Project: Zeppelin
  Issue Type: New Feature
  Components: Interpreters
Affects Versions: 0.7.1
Reporter: Fabian Boehnlein
Priority: Minor


Adding this issue after discussion in mailing list:
http://apache-zeppelin-users-incubating-mailing-list.75479.x6.nabble.com/Spark-Interpreter-Change-default-scheduler-pool-td5339.html#a5341

SparkSqlInterpreter submits to "fair" pool if "concurrent" option is set.

Add a parameter to SparkInterpreter that allows to set the default pool also 
for normal SparkInterpreter.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[GitHub] zeppelin issue #2252: [ZEPPELIN-1940] lint rule set is NOT applied at all.

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2252
  
rebased to resolve conflict with #2203, #2248


---
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 #2256: [ZEPPELIN-2315] (bug) new note.json is overwrit...

[1ambda]

GitHub user 1ambda opened a pull request:

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

[ZEPPELIN-2315] (bug) new note.json is overwritten by old note.json 
(master, branch-0.7)

### What is this PR for?

- `note.json` is converted every time
- as a result, changes in `note.json` is overwritten by old `note.json`

Occurs in **0.8.0-SNAPSHOT** and **branch-0.7**

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

### Todos

NONE

### What is the Jira issue?

[ZEPPELIN-2315](https://issues.apache.org/jira/browse/ZEPPELIN-2315)

### How should this be tested?

1. create a note in 0.6.0 which including graph
2. migrate it to 0.7.0+ (just copy dir)
3. open in Zeppelin
4. click other graph type rather than table (e.g `scatter chart`)
5. restart
7. should see the last change (graph) is persisted

### 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/1ambda/zeppelin 
ZEPPELIN-2315/should-convert-old-notebook-only-once

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

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






---
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 #2256: [ZEPPELIN-2315] (bug) new note.json is overwritten by ...

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2256
  
@jongyoul Please help review 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 #2233: [MINOR] Add paragraph to note

[AlexanderShoshin]

Github user AlexanderShoshin commented on the issue:

https://github.com/apache/zeppelin/pull/2233
  
This PR is ready 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 pull request #2255: [HOTFIX] Invalid method signature in GroovyInte...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #2255: [HOTFIX] Invalid method signature in GroovyInterpreter

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2255
  
Merge into master as a hotfix


---
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 #2133: [ZEPPELIN-1357,1892,1370][Umbrella] Text overlap in th...

[soralee]

Github user soralee commented on the issue:

https://github.com/apache/zeppelin/pull/2133
  
@Leemoonsoo Yeah, this CI problem is related in #2255 
if merging #2255, I'll rebase 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 issue #2133: [ZEPPELIN-1357,1892,1370][Umbrella] Text overlap in th...

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2133
  
Great improvement @soralee. Tested and LGTM.
Merge to master if 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.
---

[GitHub] zeppelin issue #2235: [ZEPPELIN-2375]: Avoid modification of CLASSPATH varia...

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2235
  
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 #2255: [HOTFIX] Invalid method signature in GroovyInterpreter

[tinkoff-dwh]

Github user tinkoff-dwh commented on the issue:

https://github.com/apache/zeppelin/pull/2255
  
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 #2236: [DOC] Improve documents related to Helium

[asfgit]

Github user asfgit closed the pull request at:

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


---
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 #2244: [MINOR] fix typo from 'interpeter' to 'interpreter'

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2244
  
Merge into master and branch-0.7 if there are no more comments 


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

[GitHub] zeppelin pull request #2255: [HOTFIX] Invalid method signature in GroovyInte...

[1ambda]

Github user 1ambda closed the pull request at:

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


---
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 #2255: [HOTFIX] Invalid method signature in GroovyInte...

[1ambda]

GitHub user 1ambda reopened a pull request:

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

[HOTFIX] Invalid method signature in GroovyInterpreter

### What is this PR for?

- https://github.com/apache/zeppelin/pull/2203 was merged
- but https://github.com/apache/zeppelin/pull/2203 was not rebased recently
- as a result, `GroovyInterperter` has invalid method signature.

```
[ERROR] COMPILATION ERROR : 
[ERROR] 
/home/travis/build/1ambda/zeppelin/groovy/src/main/java/org/apache/zeppelin/groovy/GroovyInterpreter.java:[123,3]
 method does not override or implement a method from a supertype
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on 
project zeppelin-groovy: Compilation failure
[ERROR] 
/home/travis/build/1ambda/zeppelin/groovy/src/main/java/org/apache/zeppelin/groovy/GroovyInterpreter.java:[123,3]
 method does not override or implement a method from a supertype
```

You can see CI failures in

- https://travis-ci.org/1ambda/zeppelin/jobs/222709988
- https://travis-ci.org/1ambda/zeppelin/jobs/222709989

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

### Todos

NONE

### What is the Jira issue?

Hotfix

### How should this be tested?

- CI should be green.
- Build this PR locally, `mvn clean package -DskipTests;`

### Screenshots (if appropriate)

NONE

### 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/1ambda/zeppelin 
HOTFIX/GroovyInterpreter-has-invalid-overrided-method

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

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


commit 29e840f8f41519f36f41c5f8288e27ca6df80afe
Author: 1ambda <1am...@gmail.com>
Date:   2017-04-17T06:24:20Z

fix: Method signature in GroovyInterpreter




---
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 #2255: [HOTFIX] Invalid method signature in GroovyInte...

[1ambda]

GitHub user 1ambda opened a pull request:

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

[HOTFIX] Invalid method signature in GroovyInterpreter

### What is this PR for?

- https://github.com/apache/zeppelin/pull/2203 was merged
- but https://github.com/apache/zeppelin/pull/2203 is not rebased recently.
- as a result, `GroovyInterperter` has invalid method signature.

```
[ERROR] COMPILATION ERROR : 
[ERROR] 
/home/travis/build/1ambda/zeppelin/groovy/src/main/java/org/apache/zeppelin/groovy/GroovyInterpreter.java:[123,3]
 method does not override or implement a method from a supertype
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on 
project zeppelin-groovy: Compilation failure
[ERROR] 
/home/travis/build/1ambda/zeppelin/groovy/src/main/java/org/apache/zeppelin/groovy/GroovyInterpreter.java:[123,3]
 method does not override or implement a method from a supertype
```

- https://travis-ci.org/1ambda/zeppelin/builds/222709985

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

### Todos

NONE

### What is the Jira issue?

Hotfix

### How should this be tested?

CI should be green.

### Screenshots (if appropriate)

NONE

### 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/1ambda/zeppelin 
HOTFIX/GroovyInterpreter-has-invalid-overrided-method

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

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


commit 29e840f8f41519f36f41c5f8288e27ca6df80afe
Author: 1ambda <1am...@gmail.com>
Date:   2017-04-17T06:24:20Z

fix: Method signature in GroovyInterpreter




---
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 #2239: Show dialog if owners field set to be empty on shiro

[soralee]

Github user soralee commented on the issue:

https://github.com/apache/zeppelin/pull/2239
  
@felixcheung Thanks for review! 
Yeah, you're right. It would be better if we also check on the REST API 
side stably.
So, let me create a JIRA ticket and revert code in `REST API`. 


---
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 #2252: [ZEPPELIN-1940] lint rule set is NOT applied at all.

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2252
  
rebased to resolve conflict with #2203, #2248


---
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 #2133: [ZEPPELIN-1357,1892,1370][Umbrella] Text overlap in th...

[soralee]

Github user soralee commented on the issue:

https://github.com/apache/zeppelin/pull/2133
  
@Leemoonsoo I added label and default variable furthermore, I changed from 
radio to button like this.
![peek 2017-04-17 
14-58](https://cloud.githubusercontent.com/assets/8110458/25080413/dea68ce0-237e-11e7-929d-d166a769bb9c.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.
---