[jira] [Created] (ZEPPELIN-2365) Button to create new note into folder

[Tinkoff DWH (JIRA)]

Tinkoff DWH created ZEPPELIN-2365:
-

 Summary: Button to create new note into folder
 Key: ZEPPELIN-2365
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2365
 Project: Zeppelin
  Issue Type: New Feature
Reporter: Tinkoff DWH
Assignee: Tinkoff DWH
Priority: Minor


On the home page in the tree of notes add button to create a note in a specific 
folder



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

[GitHub] zeppelin issue #2225: [ZEPPELIN-2357] fix: tooltip doesn't work in btn-group

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2225
  
@1ambda Yeah I also knew it when I was adding the pagination to Helium menu 
for both zeppelin.apache.org and Zeppelin :)
Tested again and it works well. 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 #2225: [ZEPPELIN-2357] fix: tooltip doesn't work in btn-group

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2225
  
@AhyoungRyu thanks for review. didn't know that! 
Just updated.


---
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 #2225: [ZEPPELIN-2357] fix: tooltip doesn't work in btn-group

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2225
  
@1ambda If we update angular-bootstrap version, the pagination in Helium 
page won't work since they change the pagination lib name (`pagination` ->`ul 
uib-pagination`)
So you might need to change [this 
part](https://github.com/apache/zeppelin/blob/master/zeppelin-web/src/app/helium/helium.html#L189)
from 
```

```

to
```

```


---
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 #2224: [ZEPPELIN-2304] Fix vis Icon sizes in helium page (bra...

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2224
  
LGTM
Merge into 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 issue #2215: [ZEPPELIN-2341] Remove -Psparkr build profile

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2215
  
@Leemoonsoo Thanks!
Merge into master 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.
---

[jira] [Created] (ZEPPELIN-2364) Add GUI for import/export to Zeppelin webapp

[Ahyoung Ryu (JIRA)]

Ahyoung Ryu created ZEPPELIN-2364:
-

 Summary: Add GUI for import/export to Zeppelin webapp
 Key: ZEPPELIN-2364
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2364
 Project: Zeppelin
  Issue Type: Sub-task
Reporter: Ahyoung Ryu






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

[jira] [Created] (ZEPPELIN-2362) implement an ".ipnb -<-> note.json" converter

[Ahyoung Ryu (JIRA)]

Ahyoung Ryu created ZEPPELIN-2362:
-

 Summary: implement an ".ipnb -<-> note.json" converter
 Key: ZEPPELIN-2362
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2362
 Project: Zeppelin
  Issue Type: Sub-task
Reporter: Ahyoung Ryu


Will be nice to implement {{.ipnb -<-> note.json}} converter with unit tests 
for this. 



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

[jira] [Created] (ZEPPELIN-2363) Implement REST API for import\export notebooks in Zeppelin

[Ahyoung Ryu (JIRA)]

Ahyoung Ryu created ZEPPELIN-2363:
-

 Summary: Implement REST API for import\export notebooks in Zeppelin
 Key: ZEPPELIN-2363
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2363
 Project: Zeppelin
  Issue Type: Sub-task
Reporter: Ahyoung Ryu






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

[GitHub] zeppelin pull request #2134: [ZEPPELIN-2257] notification about incompletene...

[asfgit]

Github user asfgit closed the pull request at:

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


---
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-2361) Flaky test: ParagraphActionsIT.testRunOnSelectionChange

[Lee moon soo (JIRA)]

Lee moon soo created ZEPPELIN-2361:
--

 Summary: Flaky test: ParagraphActionsIT.testRunOnSelectionChange
 Key: ZEPPELIN-2361
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2361
 Project: Zeppelin
  Issue Type: Bug
Reporter: Lee moon soo


Selenium test profile sometimes fails with

{code}
Results :

Failed tests: 
  ParagraphActionsIT.testRunOnSelectionChange:306 Even if 
'RunOnSelectionChange' is set as false, still can run the paragraph by pressing 
ENTER 
Expected: "My selection is 1"
 but: was "My selection is 2"

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

https://travis-ci.org/apache/zeppelin/jobs/218608853

or 

{code}

Results :

Tests in error: 
  ParagraphActionsIT.testRunOnSelectionChange:306 » StaleElementReference 
Elemen...

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

https://travis-ci.org/apache/zeppelin/jobs/218598988



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

Re: Roadmap for 0.8.0

[Ruslan Dautkhanov]

Hi Jeff,

I looked at the PR for ZEPPELIN-1595


It does not look it covers %sh interpreter.

%sh and %sql interpters are somewhat unique as they don't have access to
Zeppelin API (please correct me if I'm wrong)

So what https://issues.apache.org/jira/browse/ZEPPELIN-1967 is suggesting,
is to introduce syntax
that is used in Jupyter notebooks, i.e. {*var1*} will be implied as
z.get('var1'), for example:

%sh
/path/to/script --param8={*var1*} --param9={*var2*}

where var1 and var2 would be implied to be fetched as z.get('var1')
and z.get('var2') respectively.


Or similarly for %sql :

%sql
create table dwh.table_{*year*} stores as parquet
as
select * from spark_df1 where year = {*year*}

We miss a lot global variables for %sql and %sh so that a Zeppelin note can
be used as a single parametrized
orchestration for a whole workflow.


Thank you,
Ruslan Dautkhanov

On Wed, Apr 5, 2017 at 12:01 AM, Jeff Zhang  wrote:

>
> Hi Ruslan,
>
> Regarding 'make zeppelinContext available in shell interpreter', you may
> want to check https://issues.apache.org/jira/browse/ZEPPELIN-1595
>
>
> Ruslan Dautkhanov 于2017年4月3日周一 下午12:05写道：
>
>> That's exciting to see plans for 0.8.0 on the horizon.
>>
>> Here's my top list for 0.8 :
>>
>> - https://issues.apache.org/jira/browse/ZEPPELIN-2197 "Interpreter Idle
>> timeout"
>>  This is a most-wanted feature by our Zeppelin admins. It was mentioned
>> at least once on this email chain.
>>
>> - https://issues.apache.org/jira/browse/ZEPPELIN-1967 "Passing Z
>> variables to Shell Interpreter"
>>  We had several of our users asking about this functionality. %sh and
>> some other interpreters can't be
>>  parametrized by global variables. ZEPPELIN-1967 is one way of how this
>> can be solved.
>>
>> - https://issues.apache.org/jira/browse/ZEPPELIN-1660 "Home directory
>> references (i.e. ~/zeppelin/) in zeppelin-env.sh don't work as expected"
>>   Less of a critical compared to the above two, but it could complement
>> the multi-tenancy feature very well.
>>
>>
>> Best regards,
>> Ruslan Dautkhanov
>>
>> On Wed, Mar 22, 2017 at 11:29 AM, Felix Cheung > > wrote:
>>
>> +1 with latest/stable.
>>
>>
>>
>>
>> --
>> *From:* moon soo Lee 
>> *Sent:* Tuesday, March 21, 2017 8:41:58 AM
>> *To:* us...@zeppelin.apache.org
>> *Cc:* dev@zeppelin.apache.org
>>
>> *Subject:* Re: Roadmap for 0.8.0
>>
>>
>> And if i suggest simplest way for us to set quality expectation to user,
>> which will be labeling release in download page.
>>
>> Currently releases are divided into 2 categories in download page.
>> 'Latest release' and 'Old releases'. I think we can treat 'Latest' as
>> unstable and add one more category 'Stable release'.
>>
>> For example, once 0.8.0 is released,
>>
>> Latest release : 0.8.0
>> Stable release : 0.7.1
>> Old release : 0.6.2, 0.6.1 
>>
>> Once we feel confident about the stability of latest release, we can just
>> change label from latest to stable in the download page. (and previous
>> stable goes to old releases)
>> We can even include formal vote for moving release from 'latest' to
>> 'stable' in our release process, if it is necessary.
>>
>> Thanks,
>> moon
>>
>> On Tue, Mar 21, 2017 at 6:59 AM moon soo Lee  wrote:
>>
>> Yes, having longer RC period will help.
>>
>> But if i recall 0.7.0 release, although 21 people participated verifying
>> through 4 RC for 15days, it wasn't enough to catch all critical problems
>> during the release process. After the release, we've got much more number
>> of bug reports, in next few days.
>>
>> Basically, verifying RC is limited to people who subscribe mailing list +
>> willing to contribute time to verify RC, which is much smaller number of
>> people who download release from download page. So having longer RC period
>> will definitely help and i think we should do, but I think it's still not
>> enough to make sure the quality, considering past history.
>>
>> AFAIK, releasing 0.8.0-preview, calling it unstable is up to the project.
>> ASF release process defines how to release source code, but it does not
>> really restrict what kind of 'version' the project should have releases.
>> For example, spark released spark-2.0.0-preview[1] before spark-2.0.0.
>>
>> Thanks,
>> moon
>>
>> [1] http://spark.apache.org/news/spark-2.0.0-preview.html
>>
>> On Mon, Mar 20, 2017 at 11:31 PM Jongyoul Lee  wrote:
>>
>> I agree that it will help prolong RC period and use it actually. And also
>> we need code freeze for the new features and spend time to stabilize RC.
>>
>> On Tue, Mar 21, 2017 at 1:25 PM, Felix Cheung 
>> wrote:
>>
>> +1 on quality and stabilization.
>>
>> I'm not sure if releasing as preview or calling it unstable fits with the
>> ASF release process though.
>>
>> Other projects have code freeze, RC (and longer 

[GitHub] zeppelin issue #2225: [ZEPPELIN-2357] fix: tooltip doesn't work in btn-group

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2225
  
I was very annoying problem. Thanks @1ambda for the fix.
Tested and LGTM.

Merge to master and branch-0.7 if no further 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 issue #2215: [ZEPPELIN-2341] Remove -Psparkr build profile

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2215
  
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 #2219: [ZEPPELIN-2348] Line chart setting is not rende...

[1ambda]

Github user 1ambda closed the pull request at:

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


---
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 #2210: [ZEPPELIN-2088] Bundle helium packages one by one

[Leemoonsoo]

Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2210
  
Tested and 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 #2227: [ZEPPELIN-2359] Support Spell as Display

[echarles]

GitHub user echarles opened a pull request:

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

[ZEPPELIN-2359] Support Spell as Display

### What is this PR for?

SPELL should be considered as another display type, just like TEXT, HTML, 
TABLE...

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

### Todos
* [ ] - Task

### What is the Jira issue?

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

### How should this be tested?

Run in a paragraph

```
val json = 
"""{"array":[1,2,3],"boolean":true,"null":null,"number":123,"object":{"a":"b","c":"d","e":"f"},"string":"Hello
 World"}"""
println(s"""%spell %json
$json""")
```

or

```
val hello = "hello all"
println(s"""%spell %echo
$hello""")
```

### Screenshots

NA

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


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

$ git pull https://github.com/datalayer/zeppelin ZEPPELIN-2359

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

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


commit ebe7ebb336f182581df5e2c5d7df01308f88b367
Author: Eric Charles 
Date:   2017-03-18T11:23:13Z

Automatic message for commit of samedi 18 mars 2017, 11:23:13 (UTC+)

commit 39543dec69555ec9968175ad6f8a36dcb7a28ae0
Author: Eric Charles 
Date:   2017-03-25T13:03:02Z

Merge branch 'master' of https://github.com/apache/zeppelin

commit e89fd7098c11a821bbb78498f627eada0700992d
Author: Eric Charles 
Date:   2017-03-29T04:00:14Z

Merge branch 'master' of https://github.com/apache/zeppelin

commit 2fb48c0a8db6e5bd154861133724e0d0947bf792
Author: Eric Charles 
Date:   2017-04-05T13:16:40Z

Merge branch 'master' of https://github.com/apache/zeppelin

commit 78d0ff2d92de4cb0027c7ea78be8db1d6cc4cf8e
Author: Eric Charles 
Date:   2017-04-05T16:15:55Z

revert to scala 2.10

commit 4c1d5b0f8b7d8ce61eacf56aedefcc877539f5e3
Author: Eric Charles 
Date:   2017-04-05T17:40:43Z

Support Spell as Display




---
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-2360) [Umbrella] Improve Note editing experience

[Lee moon soo (JIRA)]

Lee moon soo created ZEPPELIN-2360:
--

 Summary: [Umbrella] Improve Note editing experience
 Key: ZEPPELIN-2360
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2360
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Lee moon soo


This is umbrella issue for improving Note editing experience.



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

[jira] [Created] (ZEPPELIN-2359) Support Spell as Display

[Eric Charles (JIRA)]

Eric Charles created ZEPPELIN-2359:
--

 Summary: Support Spell as Display
 Key: ZEPPELIN-2359
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2359
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Eric Charles






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

[GitHub] zeppelin pull request #2226: [ZEPPELIN-2235] Helium load.js should reside in...

[echarles]

GitHub user echarles opened a pull request:

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

[ZEPPELIN-2235] Helium load.js should reside in subfolder + update babel 
and webpack versions

### What is this PR for?
Changes are needed to make zeppelin-sigma-spell work. 
The solution that worked for me was to update HeliumBundleFactory.java and 
webpack.config.js so the load.js now resided in a subfolder 
(local-repo/helium-bundle/src/).

The positive side-effect for me is also that the generation of the webpack 
is faster (maybe because the node_modules are not more scanned?).

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

### Todos
* [ ] - Task

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

### How should this be tested?
Start and enable the zeppelin-sigma-spell
Test in a paragraph with 

```
%sigma

{
  "nodes":[

{"label":"n-1","x":-100,"y":"0","id":"1","attributes":{},"color":"red","size":10},

{"label":"n-2","x":0,"y":0,"id":"2","attributes":{},"color":"yellow","size":10},

{"label":"n-3","x":0,"y":-100,"id":"3","attributes":{},"color":"green","size":10.0},

{"label":"n-4","x":-100,"y":-100,"id":"4","attributes":{},"color":"green","size":10.0}
  ],
  "edges":[
{"source":"1","target":"2","id":"1-2","color":"red","size":10.0},
{"source":"1","target":"3","id":"1-3","color":"green","size":10.0},
{"source":"4","target":"3","id":"4-1","color":"green","size":10.0}
  ]
}
![screenshot from 2017-04-05 
17-42-37](https://cloud.githubusercontent.com/assets/226720/24713939/58744ec4-1a27-11e7-9d13-db29c6e8fe72.png)

```

### Screenshots (if appropriate)

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


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

$ git pull https://github.com/datalayer/zeppelin ZEPPELIN-2235

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

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


commit ebe7ebb336f182581df5e2c5d7df01308f88b367
Author: Eric Charles 
Date:   2017-03-18T11:23:13Z

Automatic message for commit of samedi 18 mars 2017, 11:23:13 (UTC+)

commit 39543dec69555ec9968175ad6f8a36dcb7a28ae0
Author: Eric Charles 
Date:   2017-03-25T13:03:02Z

Merge branch 'master' of https://github.com/apache/zeppelin

commit e89fd7098c11a821bbb78498f627eada0700992d
Author: Eric Charles 
Date:   2017-03-29T04:00:14Z

Merge branch 'master' of https://github.com/apache/zeppelin

commit 2fb48c0a8db6e5bd154861133724e0d0947bf792
Author: Eric Charles 
Date:   2017-04-05T13:16:40Z

Merge branch 'master' of https://github.com/apache/zeppelin

commit 38fe62869bf98ec6c77934c03befb0924ffa58bf
Author: Eric Charles 
Date:   2017-04-05T15:34:46Z

more load js in subfolder and update package.json + webpack.config.js to 
ensure zeppelin-sigma-spell works fine




---
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-2358) zeppelin throw PermGen out of memory after a long time running

[poseidon (JIRA)]

poseidon created ZEPPELIN-2358:
--

 Summary: zeppelin throw PermGen out of memory after a long time 
running
 Key: ZEPPELIN-2358
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2358
 Project: Zeppelin
  Issue Type: Bug
  Components: Interpreters
Affects Versions: 0.6.2
 Environment: HDP  zeppelin 0.6.2 
HDP spark 1.6.2 
HDP HADOOP 2.6 


``` zeppelin-evn

export MASTER=yarn-client
export SPARK_YARN_JAR={{spark_jar}}

export ZEPPELIN_LOG_DIR={{zeppelin_log_dir}}
export ZEPPELIN_PID_DIR={{zeppelin_pid_dir}}


export JAVA_HOME={{java64_home}}

export ZEPPELIN_JAVA_OPTS="-Dspark.executor.memory={{executor_mem}} 
-Dspark.executor.instances={{executor_instances}} 
-Dspark.yarn.queue={{spark_queue}}"

export ZEPPELIN_INTP_MEM="-XX:MaxPermSize=1024m"

export ZEPPELIN_INTP_JAVA_OPTS="-Dhdp.version=2.4.2.0-258 
-XX:+CMSClassUnloadingEnabled -XX:+UseConcMarkSweepGC 
-XX:+CMSPermGenSweepingEnabled  -XX:MaxPermSize=1024m"  

export SPARK_HOME=/usr/hdp/2.4.2.0-258/spark

export SPARK_SUBMIT_OPTIONS="--driver-memory 7G --executor-memory 16G 
--jars=/usr/hdp/2.4.2.0-258/zeppelin/interpreter/spark/hanlp-portable-1.3.1.jar"

HADOOP_CONF_DIR.
export HADOOP_CONF_DIR=/etc/hadoop/conf

export 
PYTHONPATH="${SPARK_HOME}/python:${SPARK_HOME}/python/lib/py4j-0.8.2.1-src.zip"
export SPARK_YARN_USER_ENV="PYTHONPATH=${PYTHONPATH}"

```


Reporter: poseidon


1、setup zeppelin with ambari 
2、config interpreter with a greate mount of PermGen Memory
3、create a notebook in zeppelin 
4、run spark code 

for some reason I need to use one notebook again and again. 

after running like 1000 lines code in notebook.
zeppelin  throw like PermGen Space Out of Memory Exception.

and notebook won't return from running any more.





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

[GitHub] zeppelin pull request #2224: [ZEPPELIN-2304] Fix vis Icon sizes in helium pa...

[1ambda]

GitHub user 1ambda reopened a pull request:

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

[ZEPPELIN-2304] Fix vis Icon sizes in helium page (branch-0.7)

### What is this PR for?

Icon size of helium vis packages doesn't fit into the container button. I 
attached a image.

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

### Todos

NONE

### What is the Jira issue?

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

### How should this be tested?

1. Install 2+ vis packages.
2. Open the `#helium` page

### Screenshots (if appropriate)

 Before

https://cloud.githubusercontent.com/assets/4968473/24238569/17b7dbaa-0fee-11e7-9994-39fd7700c70c.png;>

 After

https://cloud.githubusercontent.com/assets/4968473/24238572/1aac7b72-0fee-11e7-934d-da4c2d864b54.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/1ambda/zeppelin 
ZEPPELIN-2304/fix-vis-icon-size-in-helium-page-for-072

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

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


commit 9853730387d1d529f3b8ecad79801400c2303eb0
Author: 1ambda <1am...@gmail.com>
Date:   2017-04-05T07:38:41Z

fix: Vis icon size in helium.html




---
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 #2225: [ZEPPELIN-2357] fix: tooltip doesnt work with b...

[1ambda]

GitHub user 1ambda opened a pull request:

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

[ZEPPELIN-2357] fix: tooltip doesnt work with btngroup

### What is this PR for?

tooltip provided by [angular-ui: 
bootstrap](https://github.com/angular-ui/bootstrap) doesn't work with 
`btn-group` class. 

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

### Todos
* [x] - fixed tooltip issue by bumping version of angular-bootstrap
* [x] - added tooltip to charts as like before 

### What is the Jira issue?

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

### How should this be tested?

1. Open spark tutorial
2. Test tooltips in notebook controller and in paragraphs.

### Screenshots (if appropriate)

 Before


![tooltip_before](https://cloud.githubusercontent.com/assets/4968473/24699102/dc76be40-1a2d-11e7-9ae3-b550a1739ca8.gif)


 After


![tooltip_after1](https://cloud.githubusercontent.com/assets/4968473/24699105/dfaa5716-1a2d-11e7-8d8a-0576fb307200.gif)


![tooltip_after2](https://cloud.githubusercontent.com/assets/4968473/24699111/e429454a-1a2d-11e7-97cc-09bd77dcc4ca.gif)

### Questions:
* Does the licenses files need update? - YES, updated
* 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-2357/tooltip-doesnt-work-with-btngroup

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

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


commit 62784c81dfbe7958585cd69c0ef68060d88db991
Author: 1ambda <1am...@gmail.com>
Date:   2017-04-05T08:25:29Z

fix: Bump up angular-bootstrap version

commit 1e2db4ebdc9072c35cc7d70cee44576e2438cf94
Author: 1ambda <1am...@gmail.com>
Date:   2017-04-05T08:27:02Z

fix: Use uib-tooltip instead

commit 0b6ad26843b9f5114a7eae0f7da4ee4d47031217
Author: 1ambda <1am...@gmail.com>
Date:   2017-04-05T09:25:18Z

feat: Tooltip for charts

commit d03a70e3b35511ae283a4ea430940095967eaf95
Author: 1ambda <1am...@gmail.com>
Date:   2017-04-05T09:29:00Z

fix: bin license




---
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 #2224: [ZEPPELIN-2304] Fix vis Icon sizes in helium page (bra...

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2224
  
CI failure is irrelevant with this change. Looks good :)


---
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 #2222: add a configuration zeppelin.jdbc.auth.kerberos.proxy ...

[prabhjyotsingh]

Github user prabhjyotsingh commented on the issue:

https://github.com/apache/zeppelin/pull/
  
Tested locally, 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-2357) Tooltip doesn't work with btn-group

[Hoon Park (JIRA)]

Hoon Park created ZEPPELIN-2357:
---

 Summary: Tooltip doesn't work with btn-group
 Key: ZEPPELIN-2357
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2357
 Project: Zeppelin
  Issue Type: Bug
  Components: front-end
Reporter: Hoon Park
 Fix For: 0.8.0
 Attachments: tooltip_before.gif

Tooltip doesn't work with {{btn-group}}



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

[GitHub] zeppelin issue #2224: [ZEPPELIN-2304] Fix vis Icon sizes in helium page (bra...

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2224
  
@AhyoungRyu Could you 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 pull request #2224: [ZEPPELIN-2304] Fix vis Icon sizes in helium pa...

[1ambda]

GitHub user 1ambda opened a pull request:

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

[ZEPPELIN-2304] Fix vis Icon sizes in helium page (branch-0.7)

### What is this PR for?

Icon size of helium vis packages doesn't fit into the container button. I 
attached a image.

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

### Todos

NONE

### What is the Jira issue?

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

### How should this be tested?

1. Install 2+ vis packages.
2. Open the `#helium` page

### Screenshots (if appropriate)

 Before

https://cloud.githubusercontent.com/assets/4968473/24238569/17b7dbaa-0fee-11e7-9994-39fd7700c70c.png;>

 After

https://cloud.githubusercontent.com/assets/4968473/24238572/1aac7b72-0fee-11e7-934d-da4c2d864b54.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/1ambda/zeppelin 
ZEPPELIN-2304/fix-vis-icon-size-in-helium-page-for-072

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

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


commit 9853730387d1d529f3b8ecad79801400c2303eb0
Author: 1ambda <1am...@gmail.com>
Date:   2017-04-05T07:38:41Z

fix: Vis icon size in helium.html




---
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: Roadmap for 0.8.0

[Jeff Zhang]

Hi Ruslan,

Regarding 'make zeppelinContext available in shell interpreter', you may
want to check https://issues.apache.org/jira/browse/ZEPPELIN-1595


Ruslan Dautkhanov 于2017年4月3日周一 下午12:05写道：

> That's exciting to see plans for 0.8.0 on the horizon.
>
> Here's my top list for 0.8 :
>
> - https://issues.apache.org/jira/browse/ZEPPELIN-2197 "Interpreter Idle
> timeout"
>  This is a most-wanted feature by our Zeppelin admins. It was mentioned at
> least once on this email chain.
>
> - https://issues.apache.org/jira/browse/ZEPPELIN-1967 "Passing Z
> variables to Shell Interpreter"
>  We had several of our users asking about this functionality. %sh and some
> other interpreters can't be
>  parametrized by global variables. ZEPPELIN-1967 is one way of how this
> can be solved.
>
> - https://issues.apache.org/jira/browse/ZEPPELIN-1660 "Home directory
> references (i.e. ~/zeppelin/) in zeppelin-env.sh don't work as expected"
>   Less of a critical compared to the above two, but it could complement
> the multi-tenancy feature very well.
>
>
> Best regards,
> Ruslan Dautkhanov
>
> On Wed, Mar 22, 2017 at 11:29 AM, Felix Cheung 
> wrote:
>
> +1 with latest/stable.
>
>
>
>
> --
> *From:* moon soo Lee 
> *Sent:* Tuesday, March 21, 2017 8:41:58 AM
> *To:* us...@zeppelin.apache.org
> *Cc:* dev@zeppelin.apache.org
>
> *Subject:* Re: Roadmap for 0.8.0
>
>
> And if i suggest simplest way for us to set quality expectation to user,
> which will be labeling release in download page.
>
> Currently releases are divided into 2 categories in download page. 'Latest
> release' and 'Old releases'. I think we can treat 'Latest' as unstable and
> add one more category 'Stable release'.
>
> For example, once 0.8.0 is released,
>
> Latest release : 0.8.0
> Stable release : 0.7.1
> Old release : 0.6.2, 0.6.1 
>
> Once we feel confident about the stability of latest release, we can just
> change label from latest to stable in the download page. (and previous
> stable goes to old releases)
> We can even include formal vote for moving release from 'latest' to
> 'stable' in our release process, if it is necessary.
>
> Thanks,
> moon
>
> On Tue, Mar 21, 2017 at 6:59 AM moon soo Lee  wrote:
>
> Yes, having longer RC period will help.
>
> But if i recall 0.7.0 release, although 21 people participated verifying
> through 4 RC for 15days, it wasn't enough to catch all critical problems
> during the release process. After the release, we've got much more number
> of bug reports, in next few days.
>
> Basically, verifying RC is limited to people who subscribe mailing list +
> willing to contribute time to verify RC, which is much smaller number of
> people who download release from download page. So having longer RC period
> will definitely help and i think we should do, but I think it's still not
> enough to make sure the quality, considering past history.
>
> AFAIK, releasing 0.8.0-preview, calling it unstable is up to the project.
> ASF release process defines how to release source code, but it does not
> really restrict what kind of 'version' the project should have releases.
> For example, spark released spark-2.0.0-preview[1] before spark-2.0.0.
>
> Thanks,
> moon
>
> [1] http://spark.apache.org/news/spark-2.0.0-preview.html
>
> On Mon, Mar 20, 2017 at 11:31 PM Jongyoul Lee  wrote:
>
> I agree that it will help prolong RC period and use it actually. And also
> we need code freeze for the new features and spend time to stabilize RC.
>
> On Tue, Mar 21, 2017 at 1:25 PM, Felix Cheung 
> wrote:
>
> +1 on quality and stabilization.
>
> I'm not sure if releasing as preview or calling it unstable fits with the
> ASF release process though.
>
> Other projects have code freeze, RC (and longer RC iteration time) etc. -
> do we think those will help improve quality when the release is finally cut?
>
>
> _
> From: Jianfeng (Jeff) Zhang 
> Sent: Monday, March 20, 2017 6:13 PM
> Subject: Re: Roadmap for 0.8.0
>
> To: , dev 
>
>
>
>
>
> Strongly +1 for adding system test for different interpreter modes and
> focus on bug fixing than new features. I do heard from some users complain
> about the bugs of zeppelin major release. A stabilized release is very
> necessary for community.
>
>
>
>
> Best Regard,
> Jeff Zhang
>
>
> From: moon soo Lee  >>
>
> Reply-To: "us...@zeppelin.apache.org >"  mailto:us...@zeppelin.apache.org >>
>
>
> Date: Tuesday, March 21, 2017 at 4:10 AM
>
> To: "us...@zeppelin.apache.org >"