Re: [ANNOUNCE] Apache Zeppelin 0.7.1 released

2017-03-31 Thread Hyung Sung Shim
Great job zeppelin communities!!
and Thank you mina~

2017년 4월 1일 (토) 오전 11:01, Mina Lee 님이 작성:

> The Apache Zeppelin community is pleased to announce the availability of
> the 0.7.1 release.
>
> Zeppelin is a collaborative data analytics and visualization tool for
> distributed, general-purpose data processing system such as Apache Spark,
> Apache Flink, etc.
>
> The community put significant effort into improving Apache Zeppelin since
> the last release, focusing on restart interpreter process stability, python
> interpreter
> improvement, table/chart rendering bug fix. 24 contributors provided 80+
> patches
> for improvements and bug fixes. More than 70+ issues have been resolved.
>
> We encourage you to download the latest release from
> http://zeppelin.apache.org/download.html
>
> Release note is available at
> http://zeppelin.apache.org/releases/zeppelin-release-0.7.1.html
>
> We welcome your help and feedback. For more information on the project and
> how to get involved, visit our website at http://zeppelin.apache.org/
>
> Thank you all users and contributors who have helped to improve Apache
> Zeppelin.
>
> Regards,
> The Apache Zeppelin community
>


[GitHub] zeppelin issue #2201: [ZEPPELIN-1965] Livy SQL Interpreter: Should use df.sh...

2017-03-31 Thread benoyantony
Github user benoyantony commented on the issue:

https://github.com/apache/zeppelin/pull/2201
  
It should not break anything as the property name remains same as before.
The documentation had a typo in it. It was missing 'sql' in it.

If it's confusing, I can do it as a separate fix.

On Mar 31, 2017 8:48 PM, "Felix Cheung"  wrote:

> *@felixcheung* commented on this pull request.
> --
>
> In docs/interpreter/livy.md
> :
>
> > @@ -56,14 +56,14 @@ Example: `spark.driver.memory` to 
`livy.spark.driver.memory`
>  URL where livy server is running
>
>
> -zeppelin.livy.spark.maxResult
> +zeppelin.livy.spark.sql.maxResult
>
> I love this, but it might break existing users. Perhaps we don't change
> this for now?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> ,
> or mute the thread
> 

> .
>



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


[ANNOUNCE] Apache Zeppelin 0.7.1 released

2017-03-31 Thread Mina Lee
The Apache Zeppelin community is pleased to announce the availability of
the 0.7.1 release.

Zeppelin is a collaborative data analytics and visualization tool for
distributed, general-purpose data processing system such as Apache Spark,
Apache Flink, etc.

The community put significant effort into improving Apache Zeppelin since
the last release, focusing on restart interpreter process stability, python
interpreter
improvement, table/chart rendering bug fix. 24 contributors provided 80+
patches
for improvements and bug fixes. More than 70+ issues have been resolved.

We encourage you to download the latest release from
http://zeppelin.apache.org/download.html

Release note is available at
http://zeppelin.apache.org/releases/zeppelin-release-0.7.1.html

We welcome your help and feedback. For more information on the project and
how to get involved, visit our website at http://zeppelin.apache.org/

Thank you all users and contributors who have helped to improve Apache
Zeppelin.

Regards,
The Apache Zeppelin community


[GitHub] zeppelin pull request #2209: [DOC] 0.7.1 release note

2017-03-31 Thread asfgit
Github user asfgit closed the pull request at:

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


---
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 #2203: [ZEPPELIN-2297] improvements to jdbc autocompleter

2017-03-31 Thread Leemoonsoo
Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2203
  
Great improvement! LGTM
\cc @cloverhearts @astroshim 


---
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 #2113: [ZEPPELIN-2190] Support custom web development ...

2017-03-31 Thread asfgit
Github user asfgit closed the pull request at:

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


---
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 #2034: [ZEPPELIN-2133] All interpreters sometimes thro...

2017-03-31 Thread prabhjyotsingh
Github user prabhjyotsingh closed the pull request at:

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


---
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 #2209: [DOC] 0.7.1 release note

2017-03-31 Thread Leemoonsoo
Github user Leemoonsoo commented on the issue:

https://github.com/apache/zeppelin/pull/2209
  
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 #2199: [ZEPPELIN-2326] - Updating Geode dependencies and impo...

2017-03-31 Thread 1ambda
Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2199
  
@markito I mean, this PR not the JIRA ticket :)


---
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 #2199: [ZEPPELIN-2326] - Updating Geode dependencies and impo...

2017-03-31 Thread markito
Github user markito commented on the issue:

https://github.com/apache/zeppelin/pull/2199
  
@1ambda can you please confirm if the reopened JIRA triggered Jenkins 
properly ?  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 pull request #2210: [ZEPPELIN-2088] Evaluate helium bundle one by o...

2017-03-31 Thread 1ambda
GitHub user 1ambda opened a pull request:

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

[ZEPPELIN-2088] Evaluate helium bundle one by one

### What is this PR for?

Evaluate helium bundle one by one. Because

- Bundling them in one file is not good idea because the whole bundling 
fails if only one fails
- Some node packages might not installed correctly. For example, 
`amchart/amcharts3` will be install 
`helium-bundles/node_modules/my-helium-vis/node_modules` but `amchart-export` 
will be install `helium-bundles/node_modules` so `my-helium-vis` can't import 
`amchart-export`. (This is real case)
- Additionally, I used yarn to install requires node_modules. Since 
separated bundling mean installing dependencies for each helium package and 
`npm` is too slow for that.
- Install Zeppelin framework modules using [local 
path](https://docs.npmjs.com/files/package.json#local-paths). It's more safe 
and correct way to install local modules.

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

### Todos

NONE

### What is the Jira issue?

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

### How should this be tested?

1. Install any local helium package
2. Install any online helium package
3. Use them
4. Disable
5. Test `npm run dev:helium`

### 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 
ZEPPELIN-2088/evaluate-helium-bundle-one-by-one

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

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


commit 0f8b6363ff30dc7dc8e028450d2af2ec7b96da6e
Author: 1ambda <1am...@gmail.com>
Date:   2017-03-30T14:30:47Z

feat: Build each bundle using yarn

commit f2576b78518190a331cb3dcf70ef10351e2e3e68
Author: 1ambda <1am...@gmail.com>
Date:   2017-03-30T20:50:41Z

feat: Build online packages

commit 2ea849298f8ee95bcfa29992857f85e28b3e2b0a
Author: 1ambda <1am...@gmail.com>
Date:   2017-03-31T04:53:06Z

feat: enable, disable

commit 9fa2a2c6c775c8158af8ee526d3bf971a04b95a7
Author: 1ambda <1am...@gmail.com>
Date:   2017-03-31T09:47:25Z

feat: Loading bundles

commit 94eaf3e19138fcd6b9e0cd0d7064bf21bc3a7a50
Author: 1ambda <1am...@gmail.com>
Date:   2017-03-31T10:31:28Z

test: Fix APIs

commit f85110311d8620449144509c74b4f3d86e3371b2
Author: 1ambda <1am...@gmail.com>
Date:   2017-03-31T10:40:52Z

fix: Log single bundle error to browser console

commit 80e52a8e487748783e368c9e532152fc4fdb2a02
Author: 1ambda <1am...@gmail.com>
Date:   2017-03-31T13:18:12Z

fix: HeliumBundleFactoryTest

commit 586e2fd7da2daca8afa30e6c259b745104acb6d3
Author: 1ambda <1am...@gmail.com>
Date:   2017-03-31T13:50:17Z

fix: Add nodeInstallationDir

commit bcd5bedf1df47308963532b664c04cc8b79be597
Author: 1ambda <1am...@gmail.com>
Date:   2017-03-31T14:00:36Z

feat: Apply #2178

commit 84c4b793178d823f6d28d84b070c1e0fc97b0dbf
Author: 1ambda <1am...@gmail.com>
Date:   2017-03-31T14:06:08Z

fix: Add error handling for failed bundle




---
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 #2209: [DOC] 0.7.1 release note

2017-03-31 Thread minahlee
Github user minahlee commented on the issue:

https://github.com/apache/zeppelin/pull/2209
  
Merge if there is no more discussion for new release publish


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


[RESULT][VOTE] Release Apache Zeppelin 0.7.1 (RC3)

2017-03-31 Thread Mina Lee
The vote passes with 6 binding +1 votes, 9 non-binding +1 votes, and no +0
or -1 votes. Thanks for everyone who verified rc and voted.

+1:

Jeff Zhang

DuyHai Doan

Hyung Sung Shim

Mina Lee*

Windy Qin

CloverHeartsDev

Jongyoul Lee*

Jun Kim

Anthony Corbacho*

Ahyoung Ryu

Khalid Huseynov

Felix Cheung*

Moon soo Lee*

Sora Lee

Prabhjyot Singh*

+0:

-1:

*binding

Vote thread:

https://lists.apache.org/thread.html/62e5c8c4bc10c3eb7c8037274ce596fee23d76f599073b06c84f48e0@%3Cdev.zeppelin.apache.org%3E


[jira] [Created] (ZEPPELIN-2338) If Notebook execution fails, Notbook API should return a 500 code with meaningful reason, such as the error message or stacktrace

2017-03-31 Thread Sofiane Cherchalli (JIRA)
Sofiane Cherchalli created ZEPPELIN-2338:


 Summary: If Notebook execution fails, Notbook API should return a 
500 code with meaningful reason, such as the error message or stacktrace
 Key: ZEPPELIN-2338
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2338
 Project: Zeppelin
  Issue Type: Bug
  Components: rest-api
Affects Versions: 0.7.0
Reporter: Sofiane Cherchalli
Priority: Critical


If Notebook execution fails, Notbook API should return a 500 code with 
meaningful reason, such as the error message or stacktrace. Otherwise, one has 
to open the notebook with GUI to find out the error or exception message.



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


[GitHub] zeppelin issue #2176: [ZEPPELIN-2300] SHOULD NOT update paragraph text when ...

2017-03-31 Thread FRosner
Github user FRosner commented on the issue:

https://github.com/apache/zeppelin/pull/2176
  
I get what you are saying and I agree. My only point was that you need to 
be aware that this change only does the following thing:

**Before**: Who persists the local changes earlier, wins the conflict. 
(User A wins in the example above)
**Now**: Who persists the local changes later, wins the conflict. (User B 
wins in the example above)

And I was wondering if this is a useful change or not. If this change is 
considered useful, the PR looks good to me :) If not, we should not merge it.

Again, thanks for your effort and time and I didn't mean to say that we 
cannot go step by step. I just wanted to challenge 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.
---


[jira] [Created] (ZEPPELIN-2337) java.lang.NoClassDefFoundError: org/glassfish/jersey/message/internal/HeaderUtils on lens query

2017-03-31 Thread Dhayanithi Subramanian (JIRA)
Dhayanithi Subramanian created ZEPPELIN-2337:


 Summary: java.lang.NoClassDefFoundError: 
org/glassfish/jersey/message/internal/HeaderUtils on lens query
 Key: ZEPPELIN-2337
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2337
 Project: Zeppelin
  Issue Type: Bug
 Environment: Ubuntu Linux 4.4.0-45-generic #66-Ubuntu 
java version: java version 1.8.0_111
Reporter: Dhayanithi Subramanian


I downloaded the 0.7 version binary package with all interpreters. 

I am getting 
java.lang.NoClassDefFoundError: 
org/glassfish/jersey/message/internal/HeaderUtils
when I try to run lens a query.

Please let me know if you need any other information.



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


[GitHub] zeppelin pull request #2178: [ZEPPELIN-2302] Add info level logs when instal...

2017-03-31 Thread asfgit
Github user asfgit closed the pull request at:

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


---
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 #2176: [ZEPPELIN-2300] SHOULD NOT update paragraph text when ...

2017-03-31 Thread 1ambda
Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2176
  
@FRosner Thanks for detailed reply.

We can't get the ultimate feature at once.

- locking
- realtime notification
- ...

IMO, This is just the first step. Then other people think about 
synchronization, and so on as we did. They might think auto save is not 
ultimate solution. If we want to resolve the whole things at once, we can't 
merge any of #2120 #2176 #2177.. 




---
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 #2207: [Zeppelin-802] Support for Zeppelin Context redefiniti...

2017-03-31 Thread zjffdu
Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/2207
  
I think a more thorough solution is to separate the namespace between 
python process and python repl. Only `ZeppelinContext` should be `available` in 
python repl namespace.  It would be better to specify a space in `exec`.  
e.g. 
```
exec(code, global=repl_namespace)
```


---
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 #2176: [ZEPPELIN-2300] SHOULD NOT update paragraph text when ...

2017-03-31 Thread FRosner
Github user FRosner commented on the issue:

https://github.com/apache/zeppelin/pull/2176
  
I am not sure if this change helps. We still have a race condition and 
conflict resolution is still "forceful overwrite and don't notify". If I see it 
correctly:

*Before*: Who persists the local changes earlier, wins the conflict. (User 
A wins in the 
[example](https://github.com/apache/zeppelin/pull/2176#issuecomment-290395313) 
above)
*Now*: Who persists the local changes later, wins the conflict.

If this is the expected behaviour and what you wanted to achieve, then LGTM 
:)

PS: If live editing like in Google docs can't be easily done, we could at 
least lock the paragraph for all but one user. A lock is granted when a 
paragraphs is focused. The lock gets released either when the focus is lost or 
someone else wants to acquire the lock. Changes get persisted before the lock 
gets released (i.e. either when losing focus or someone else also wants to 
edit). This way you cannot overwrite any remote changes as the paragraph will 
always get updated when you click into it and we don't have a race condition 
because of the lock.


---
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 #2208: [HOTFIX][gh-pages] Fix Maven web link for INTER...

2017-03-31 Thread asfgit
Github user asfgit closed the pull request at:

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


---
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 #2207: [Zeppelin-802] Support for Zeppelin Context redefiniti...

2017-03-31 Thread felixcheung
Github user felixcheung commented on the issue:

https://github.com/apache/zeppelin/pull/2207
  
right, I think it's everything that is called after calling `exec(code)`, 
might have been overwritten by the user code

```
or node in to_run_exec:
  mod = ast.Module([node])
  code = compile(mod, '', 'exec')
  exec(code)

for node in to_run_single:
  mod = ast.Interactive([node])
  code = compile(mod, '', 'single')
  exec(code)

for node in to_run_hooks:
  mod = ast.Module([node])
  code = compile(mod, '', 'exec')
  exec(code)
```

so I think: `intp`, `output`
and perhaps `to_run_exec`, `to_run_single`, `to_run_hooks`?



---
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 #2207: [Zeppelin-802] Support for Zeppelin Context redefiniti...

2017-03-31 Thread cloverhearts
Github user cloverhearts commented on the issue:

https://github.com/apache/zeppelin/pull/2207
  
@felixcheung Thank you for your good advice.
I will check your opinion.
and fix :)


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