[GitHub] zeppelin issue #2098: [ZEPPELIN-2217] AdvancedTransformation for Visualizati...

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2098
  
@AhyoungRyu 

Thanks for detailed review. 

1. It would be nice to have some popup or feedback when conf is updated.
2. Let me hide them when panel is minimized (e.g the chart panel, the 
parameter panel)

Regarding to `3. no-group field`, it's quite hard to say in just few lines. 
So let me describe more.

(A) Some charts require aggregation. (= groupBy in SQL)
(B) But some charts might not need aggregation. Assume that it's already 
grouped by SQL

In ultimate-line-chart, there are sub charts called `line`, `dashed`, 
`step` and `no-group`.

- `line`, `dashed`,` step` uses aggregation like zeppelin's existing 
charts. (similar to `PivotTransformation`)
- But `no-group` doesn't use aggregation. (similar to 
`ColumnTransformation`)




---
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 #2197: ZEPPELIN-2324. Add property zeppelin.spark.unSupported...

[zjffdu]

Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/2197
  
> perhaps it should be changed in 
sparkInterpreter.getSparkVersion().isSupportedVersion() instead

I thought about it, but feel it is not proper to create a new member field 
in class SparkVersion as this is a interpreter level property, even it is not 
proper to me to create a static field in SparkVersion. So in the new PR, I 
create a new method `isUnSupportedSparkVersion` in `SparkInterpreter` to wrap 
all the logic. 

> Can you add testcase for this conf?
I didn't find an easy way for this test. So just manually verified 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 #2177: [ZEPPELIN-2301] DON'T overwrite editor text when note ...

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2177
  
@AhyoungRyu Could you 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.
---

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

[1ambda]

Github user 1ambda commented on the issue:

https://github.com/apache/zeppelin/pull/2176
  
@AhyoungRyu Could you 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.
---

[GitHub] zeppelin issue #2151: [ZEPPELIN-465] Be able to run paragraph and the follow...

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2151
  
@Remilito Tested and it works as expected. 
Regarding docs, how about adding new section for this feature instead of 
`subsequent parameter (optional)` as a subsection under "Run a paragraph 
synchronously" & "Run a paragraph asynchronously" ? I saw many ppl have wanted 
this feature, so it'll be better to create new section for it. Below each "Run 
a paragraph synchronously" & "Run a paragraph asynchronously" section would be 
good place i think. 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 issue #2133: [ZEPPELIN-1357][Umbrella] Text overlap in the MultiBar...

[soralee]

Github user soralee commented on the issue:

https://github.com/apache/zeppelin/pull/2133
  
@Leemoonsoo Thanks for review and suggestions!
I think manual options depending on users seems great so far, because I 
didn't find automatic calculation about width of `xLabel`. Let me dig this part 
more and leave a comment after updating.


---
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 #2204: ZEPPELIN-2189. The order of dynamic forms should be th...

[zjffdu]

Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/2204
  
Thanks @AhyoungRyu for review, just fix a code style issue 


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

[GitHub] zeppelin issue #2204: ZEPPELIN-2189. The order of dynamic forms should be th...

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2204
  
Yeah I saw this as well. Let me take a look :) 


---
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 #2204: ZEPPELIN-2189. The order of dynamic forms shoul...

[zjffdu]

GitHub user zjffdu opened a pull request:

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

ZEPPELIN-2189. The order of dynamic forms should be the order that you 
create them


### What is this PR for?
The order of dynamic forms should be the order that you create them. So I 
made the following 2 changes for this:
* change the type of forms in GUI from TreeMap to LinkedHashMap
*  remove orderBy in paragraph-parameterizedQueryForm.html
Besides, I also did some code refactoring. 


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

### Todos
* [ ] - Task

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

### How should this be tested?
Tested manually.

### Screenshots (if appropriate)
Before

![2017-02-27_1310](https://cloud.githubusercontent.com/assets/164491/24486826/9ac3c1e4-153e-11e7-8280-8cf4f6ef7560.png)

After 

![2017-03-30_1109](https://cloud.githubusercontent.com/assets/164491/24486828/9b733ee4-153e-11e7-9a13-44ed71aa29d8.png)

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


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

$ git pull https://github.com/zjffdu/zeppelin ZEPPELIN-2189

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

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


commit 369900ec9fb2998004c13daf096b51680b11f2a1
Author: Jeff Zhang 
Date:   2017-03-30T01:05:34Z

ZEPPELIN-2189. The order of dynamic forms should be the order that you 
create them




---
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 #2135: Groovy Interpreter for Apazhe Zeppelin [ZEPPELIN-2176]

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2135
  
Thanks for addressing my comments! I left some minor comments again about 
"author name" in the source code and removing unnecessary `log.info`. Except 
these two things, 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.
---

Zeppelin Spark Streaming Twitter Stuck

[Chaoran Yu]

Hello,

Has anybody got Spark Streaming Twitter example to work in Zeppelin? When I 
started the streaming context with ssc.start(), the Zeppelin paragraph seemed 
to have started but it got stuck there. The top right corner of the paragraph 
says “RUNNING 0%” 

I think this is a problem with Spark Streaming + Zeppelin, rather than one with 
Twitter example in particular. Because I’ve tried my own simple streaming tests 
but got the same thing: Stuck in “RUNNING 0%” status forever. 

I also tried to stop the streaming context with ssc.stop() in a new paragraph 
but it won’t execute i.e. remain in “PENDING” status. In fact, any new code 
won’t execute in a new paragraph. I had to restart Zeppelin to get me out of 
this situation. Zeppelin logs didn’t reveal any errors either.

Could anyone help me here?

Thank you,
Chaoran Yu

[GitHub] zeppelin issue #2174: [ZEPELIN-2209] Add pagination to Helium menu

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2174
  
@felixcheung 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 #2189: [branch-0.7] Minor styling for Helium menu

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2189
  
@felixcheung Thanks! Merge into branch-0.7 if there are no further comments 
on 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 #2199: [ZEPPELIN-2326] - Updating Geode dependencies and impo...

[markito]

Github user markito commented on the issue:

https://github.com/apache/zeppelin/pull/2199
  
I'm sorry, skipped that part from the contribution guide. Will do and 
amend. 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 #2135: Groovy Interpreter for Apazhe Zeppelin [ZEPPELIN-2176]

[dlukyanov]

Github user dlukyanov commented on the issue:

https://github.com/apache/zeppelin/pull/2135
  
@AhyoungRyu, changes committed,waiting for travis


---
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 #2174: [ZEPELIN-2209] Add pagination to Helium menu

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2174
  
@1ambda I updated the pagination as you said and this is the current 
status. Will be appreciated if you can take a look again.

![hide_first_last_arrows](https://cloud.githubusercontent.com/assets/10060731/24462055/fbdfaf08-14dd-11e7-9808-79d901ea8220.gif)

@felixcheung I set the maximum pagination size as "5" and tested in the 
smallest mobile device size that Chrome dev tool provides (`320 x 568`) like 
below.

![small_device](https://cloud.githubusercontent.com/assets/10060731/24462153/3afcc824-14de-11e7-8145-d6b11cc797b2.gif)
The pagination is not broken when the screen is small. But `enable` btn and 
package type selection btn are broken instead 😅 Let me handle them in 
another PR. 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 issue #2134: [ZEPPELIN-2257] notification about incompleteness of d...

[sotnich]

Github user sotnich commented on the issue:

https://github.com/apache/zeppelin/pull/2134
  
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 #2203: [ZEPPELIN-2297] improvements to jdbc autocomple...

[tinkoff-dwh]

GitHub user tinkoff-dwh opened a pull request:

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

[ZEPPELIN-2297] improvements  to jdbc autocompleter

### What is this PR for?
PR contains some improvements for completion (JDBC Interpreter):
- types of completion
- display of long values
- refactoring of search of completions
- uniqness of completions with type `keyword`
- updating data in completer by pressing `Ctrl + .`
- setting the schema filter to generate completions
- fix highlighting code when used not default data source

### What type of PR is it?
Improvement

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

### How should this be tested?
try to work with new completer

### Screenshots (if appropriate)
1. Types of completion

![1](https://cloud.githubusercontent.com/assets/25951039/24449367/758eeeac-1490-11e7-863f-bf1b313a3f4d.png)
2. Display of long values
before

![2297_before_long_caption](https://cloud.githubusercontent.com/assets/25951039/24449397/8ecd3072-1490-11e7-8fd4-415424ef337e.gif)
after

![2297_after_long_caption](https://cloud.githubusercontent.com/assets/25951039/24449413/9c7a36b6-1490-11e7-9d7c-cbbdac71cbe7.gif)
3. Refactoring of search of completions. Updating data in completer by 
pressing `Ctrl + .`
before

![2297_before_refactoring_search](https://cloud.githubusercontent.com/assets/25951039/24449463/c1801214-1490-11e7-84a8-25c887b68d65.gif)
after

![2297_after_refactoring_search](https://cloud.githubusercontent.com/assets/25951039/24449567/1079bdc0-1491-11e7-8409-5187aeceb428.gif)
4. uniqness of completions with type keyword
before

![2297_before_uniq](https://cloud.githubusercontent.com/assets/25951039/24449615/4e20c8d0-1491-11e7-94cc-c86aab886c53.gif)
after

![2297_after_uniq](https://cloud.githubusercontent.com/assets/25951039/24449635/5cf59aca-1491-11e7-8ee1-31ea3cdacb3e.gif)
5. fix highlighting code when used not default data source
before

![2297_before_inrpret_name](https://cloud.githubusercontent.com/assets/25951039/24449730/b6c8d62a-1491-11e7-8dc3-39fa6975c8c3.gif)
after

![2297_after_inrpret_name](https://cloud.githubusercontent.com/assets/25951039/24449738/baf63e18-1491-11e7-8711-12557a674212.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/tinkoff-dwh/zeppelin ZEPPELIN-2297

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

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






---
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: Could not find or load main class run when using yarn run dev

[Jeff Zhang]

That's it, thanks.



Remy Gayet 于2017年3月29日周三 下午5:14写道：

> Is there any chance you are using hadoop-yarn instead of yarn pkg manager (
> https://yarnpkg.com/lang/en/)?
>
> On Wed, Mar 29, 2017 at 9:48 AM, Jeff Zhang  wrote:
>
> > Hi Folks,
> >
> > I follow the instruction here to debug zeppelin-web, but got the
> following
> > error,
> > Do I miss something ? Thanks
> >
> >jzhangMBPr:zeppelin-web jzhang$ yarn run dev
> >Error: Could not find or load main class run
> >
>
>
>
> --
> Remy GAYET,
> +33 6 798 798 62.
>

Re: Could not find or load main class run when using yarn run dev

[Remy Gayet]

Is there any chance you are using hadoop-yarn instead of yarn pkg manager (
https://yarnpkg.com/lang/en/)?

On Wed, Mar 29, 2017 at 9:48 AM, Jeff Zhang  wrote:

> Hi Folks,
>
> I follow the instruction here to debug zeppelin-web, but got the following
> error,
> Do I miss something ? Thanks
>
>jzhangMBPr:zeppelin-web jzhang$ yarn run dev
>Error: Could not find or load main class run
>



-- 
Remy GAYET,
+33 6 798 798 62.

[GitHub] zeppelin issue #2189: [branch-0.7] Minor styling for Helium menu

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2189
  
@felixcheung Is this good to go 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.
---

[jira] [Created] (ZEPPELIN-2329) Restart interpreter from error for non admin users

[Guillaume Van Delsen (JIRA)]

Guillaume Van Delsen created ZEPPELIN-2329:
--

 Summary: Restart interpreter from error for non admin users
 Key: ZEPPELIN-2329
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2329
 Project: Zeppelin
  Issue Type: Bug
Affects Versions: 0.8.0
Reporter: Guillaume Van Delsen


I have the following shiro.ini file with admin / non admin roles :

#/api/version = anon
/api/interpreter/** = authc, roles[admin]
/api/configurations/** = authc, roles[admin]
/api/credential/** = authc, roles[admin]
#/** = anon
/** = authc

Only admin users should have rights to edit interpreter config which works fine.

At some point, regular users should be able to restart their own interpreters 
(spark is this case) from the nb page but the pop-up just show an error 
(exactly :  (nothing is the log) and the process stay there.

I believe is due to the restriction on /api/interpreter uri as I get a 401.

Did the same with an admin user and works fine, the interpreter process is 
killed and lazily restarted when a cell is executed.

https://drive.google.com/file/d/0B4flaCIh3sQHdUIwR1Jfel9KWG8/view?usp=sharing





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

[GitHub] zeppelin pull request #2202: [Minor][ZEPPELIN-2328] Separate Helium related ...

[AhyoungRyu]

GitHub user AhyoungRyu opened a pull request:

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

[Minor][ZEPPELIN-2328] Separate Helium related docs from 'Contribution' 
section

### What is this PR for?
Actually writing "Visualization", "Spell" or "Application" type of Helium 
package is not a direct contribution to Zeppelin. So i created "Helium 
Framework" section and moved "Writing Zeppelin Visualization", "Writing 
Zeppelin Spell", and "Writing Zeppelin Application" under "Helium Framework" 
from "Contribution".

### What type of PR is it?
Documentation

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

### Screenshots (if appropriate)
 - Before 
https://cloud.githubusercontent.com/assets/10060731/2171/743d8c7e-14a0-11e7-8a10-ec02596d2a19.png;
 width="300px">

 - After 
https://cloud.githubusercontent.com/assets/10060731/2245/aecfe274-14a0-11e7-8488-99086b1db415.png;
 width="300px">

### 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/AhyoungRyu/zeppelin ZEPPELIN-2328

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

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


commit 6185fcd45c47ade3f0f36fd7918a56c80bd774eb
Author: AhyoungRyu 
Date:   2017-03-29T07:50:32Z

Separate Helium related docs from 'Contribution' section




---
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 #2198: [ZEPPELIN-2318] Fix proxy configuration for http clien...

[khalidhuseynov]

Github user khalidhuseynov commented on the issue:

https://github.com/apache/zeppelin/pull/2198
  
@felixcheung right `warning` level makes more sense in those cases, 
addressed in 8ea7d5d9652fa00d00cb6d749f0e1e718beb8c95


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

Could not find or load main class run when using yarn run dev

[Jeff Zhang]

Hi Folks,

I follow the instruction here to debug zeppelin-web, but got the following
error,
Do I miss something ? Thanks

   jzhangMBPr:zeppelin-web jzhang$ yarn run dev
   Error: Could not find or load main class run

Re: [VOTE] Release Apache Zeppelin 0.7.1 (RC3)

[Hyung Sung Shim]

+1
Tested tutorials of zeppelin-0.7.1-bin-all on CentOS7.
Thank you for your effort mina!

2017-03-29 16:04 GMT+09:00 DuyHai Doan :

> +1
> Le 29 mars 2017 07:06, "Jeff Zhang"  a écrit :
>
> > Thanks Jongyoul for explanation, let's improve it later.
> >
> > +1.
> >
> > * Build zeppelin from source successfully
> > * Run pig tutorial using tez mode successfully
> > * Run spark tutorial using livy interpreter successfully.
> > * Verify interpreter fail error can be propagated to frontend.
> > * Verify the restart button works in several scenarios. Works properly.
> >
> >
> >
> >
> > Jongyoul Lee 于2017年3月29日周三 上午11:37写道：
> >
> > > Jeff,
> > >
> > > Moon and I discuss the behaviors of clicking restart buttons from
> > notebook
> > > page and interpreter page. In your case, it's intended fully. For more
> > > detail, In case of "per user", we can do the same thing in note and
> > > interpreter pages, but in case of "per note", we cannot get the exact
> > note
> > > when users click restart button in interpreter tab. Thus Moon and I
> > decided
> > > not to change original behaviors of interpreter page. It would be
> changed
> > > when we add admin feature.
> > >
> > > Thanks for testing it.
> > >
> > > Regards,
> > > Jongyoul
> > >
> > > On Wed, Mar 29, 2017 at 11:47 AM, Jeff Zhang  wrote:
> > >
> > > > Might find another bug about restarting button. The restarting button
> > on
> > > > note page behaves differently from that of interpreter page.  This
> > might
> > > > confuse users.
> > > >
> > > > e.g. For livy interpreter, if I click the restart button in note
> page,
> > > then
> > > > only my livy session will be shutdown. But If I click the restart
> > button
> > > in
> > > > interpreter page, all the sessions will be shut down. This kind of
> > > > differences will confuse users IMO.
> > > >
> > > >
> > > >
> > > > Mina Lee 于2017年3月28日周二 下午6:53写道：
> > > >
> > > > > I propose the following RC to be released for the Apache Zeppelin
> > 0.7.1
> > > > > release.
> > > > >
> > > > > The commit id is 9eb77adfb3d9969f84d1657b78a95b58e44b5be8 which is
> > > > > corresponds to the tag v0.7.1-rc3:
> > > > >
> > > > > https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;h=
> > > > refs/tags/v0.7.1-rc3
> > > > >
> > > > > The release archives (tgz), signature, and checksums are here
> > > > > https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.
> 7.1-rc3/
> > > > >
> > > > > The release candidate consists of the following source distribution
> > > > archive
> > > > > zeppelin-0.7.1.tgz
> > > > >
> > > > > In addition, the following supplementary binary distributions are
> > > > provided
> > > > > for user convenience at the same location
> > > > > zeppelin-0.7.1-bin-all.tgz
> > > > > zeppelin-0.7.1-bin-netinst.tgz
> > > > >
> > > > > The maven artifacts are here
> > > > > https://repository.apache.org/content/repositories/
> > > > orgapachezeppelin-1035
> > > > >
> > > > > You can find the KEYS file here:
> > > > > https://dist.apache.org/repos/dist/release/zeppelin/KEYS
> > > > >
> > > > > Release notes available at
> > > > >
> > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > > version=12339166=12316221
> > > > >
> > > > > Vote will be open for next 72 hours (close at 04:00 31/Mar PDT).
> > > > >
> > > > > [ ] +1 approve
> > > > > [ ] 0 no opinion
> > > > > [ ] -1 disapprove (and reason why)
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > 이종열, Jongyoul Lee, 李宗烈
> > > http://madeng.net
> > >
> >
>

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

[zjffdu]

Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/2201
  
One minor thing left, could you add test case for 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 #2201: [ZEPPELIN-1965] Livy SQL Interpreter: Should use df.sh...

[zjffdu]

Github user zjffdu commented on the issue:

https://github.com/apache/zeppelin/pull/2201
  
Thanks @benoyantony for contribution, would you mind to add this 
configuration into livy.md as well ? 


---
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: [VOTE] Release Apache Zeppelin 0.7.1 (RC3)

[DuyHai Doan]

+1
Le 29 mars 2017 07:06, "Jeff Zhang"  a écrit :

> Thanks Jongyoul for explanation, let's improve it later.
>
> +1.
>
> * Build zeppelin from source successfully
> * Run pig tutorial using tez mode successfully
> * Run spark tutorial using livy interpreter successfully.
> * Verify interpreter fail error can be propagated to frontend.
> * Verify the restart button works in several scenarios. Works properly.
>
>
>
>
> Jongyoul Lee 于2017年3月29日周三 上午11:37写道：
>
> > Jeff,
> >
> > Moon and I discuss the behaviors of clicking restart buttons from
> notebook
> > page and interpreter page. In your case, it's intended fully. For more
> > detail, In case of "per user", we can do the same thing in note and
> > interpreter pages, but in case of "per note", we cannot get the exact
> note
> > when users click restart button in interpreter tab. Thus Moon and I
> decided
> > not to change original behaviors of interpreter page. It would be changed
> > when we add admin feature.
> >
> > Thanks for testing it.
> >
> > Regards,
> > Jongyoul
> >
> > On Wed, Mar 29, 2017 at 11:47 AM, Jeff Zhang  wrote:
> >
> > > Might find another bug about restarting button. The restarting button
> on
> > > note page behaves differently from that of interpreter page.  This
> might
> > > confuse users.
> > >
> > > e.g. For livy interpreter, if I click the restart button in note page,
> > then
> > > only my livy session will be shutdown. But If I click the restart
> button
> > in
> > > interpreter page, all the sessions will be shut down. This kind of
> > > differences will confuse users IMO.
> > >
> > >
> > >
> > > Mina Lee 于2017年3月28日周二 下午6:53写道：
> > >
> > > > I propose the following RC to be released for the Apache Zeppelin
> 0.7.1
> > > > release.
> > > >
> > > > The commit id is 9eb77adfb3d9969f84d1657b78a95b58e44b5be8 which is
> > > > corresponds to the tag v0.7.1-rc3:
> > > >
> > > > https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;h=
> > > refs/tags/v0.7.1-rc3
> > > >
> > > > The release archives (tgz), signature, and checksums are here
> > > > https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.7.1-rc3/
> > > >
> > > > The release candidate consists of the following source distribution
> > > archive
> > > > zeppelin-0.7.1.tgz
> > > >
> > > > In addition, the following supplementary binary distributions are
> > > provided
> > > > for user convenience at the same location
> > > > zeppelin-0.7.1-bin-all.tgz
> > > > zeppelin-0.7.1-bin-netinst.tgz
> > > >
> > > > The maven artifacts are here
> > > > https://repository.apache.org/content/repositories/
> > > orgapachezeppelin-1035
> > > >
> > > > You can find the KEYS file here:
> > > > https://dist.apache.org/repos/dist/release/zeppelin/KEYS
> > > >
> > > > Release notes available at
> > > >
> > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > version=12339166=12316221
> > > >
> > > > Vote will be open for next 72 hours (close at 04:00 31/Mar PDT).
> > > >
> > > > [ ] +1 approve
> > > > [ ] 0 no opinion
> > > > [ ] -1 disapprove (and reason why)
> > > >
> > >
> >
> >
> >
> > --
> > 이종열, Jongyoul Lee, 李宗烈
> > http://madeng.net
> >
>

[jira] [Created] (ZEPPELIN-2328) Need to separate Helium related docs pages from "Contribute" section

[Ahyoung Ryu (JIRA)]

Ahyoung Ryu created ZEPPELIN-2328:
-

 Summary: Need to separate Helium related docs pages from 
"Contribute" section
 Key: ZEPPELIN-2328
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-2328
 Project: Zeppelin
  Issue Type: Improvement
  Components: documentation
Reporter: Ahyoung Ryu
Assignee: Ahyoung Ryu
Priority: Minor
 Fix For: 0.8.0


Actually writing "Visualization", "Spell" or "Application" type of Helium 
package is not a direct contribution to Zeppelin. So i think [Writing Zeppelin 
Visualization|https://zeppelin.apache.org/docs/0.8.0-SNAPSHOT/development/writingzeppelinvisualization.html],
 [Writing Zeppelin Spell | 
https://zeppelin.apache.org/docs/0.8.0-SNAPSHOT/development/writingzeppelinspell.html],
 and [Writing Zeppelin Application | 
https://zeppelin.apache.org/docs/0.8.0-SNAPSHOT/development/writingzeppelinapplication.html]can
 be separated from "Contribute" section under dropdown menu. 



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

[GitHub] zeppelin issue #162: ZEPPELIN-179: Cassandra Interpreter

[liuyangandy]

Github user liuyangandy commented on the issue:

https://github.com/apache/zeppelin/pull/162
  
@doanduyhai My Zeppelin and Cassandra is running in DCOS, my 
```cassandra.hosts``` is my one of Cassandra cluster node IP, others properties 
are default. But when I try to test connectivity in Zeppelin notebook using the 
CQL, it always throws the following exception:

> java.lang.ClassNotFoundException: com.google.common.collect.ImmutableMap
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>   at 
com.datastax.driver.core.ProtocolVersion.(ProtocolVersion.java:78)
>   at 
org.apache.zeppelin.cassandra.JavaDriverConfig.getProtocolVersion(JavaDriverConfig.scala:209)
>   at 
org.apache.zeppelin.cassandra.CassandraInterpreter.open(CassandraInterpreter.java:273)
>   at 
org.apache.zeppelin.interpreter.ClassloaderInterpreter.open(ClassloaderInterpreter.java:74)
>   at 
org.apache.zeppelin.interpreter.LazyOpenInterpreter.open(LazyOpenInterpreter.java:68)
>   at 
org.apache.zeppelin.interpreter.LazyOpenInterpreter.interpret(LazyOpenInterpreter.java:92)
>   at 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:300)
>   at org.apache.zeppelin.scheduler.Job.run(Job.java:169)
>   at 
org.apache.zeppelin.scheduler.ParallelScheduler$JobRunner.run(ParallelScheduler.java:157)
>   at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
>   at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
>   at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)

Thanks for reading and helping.


---
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 #2201: [ZEPPELIN-1965] Livy SQL Interpreter: Should us...

[benoyantony]

GitHub user benoyantony opened a pull request:

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

[ZEPPELIN-1965] Livy SQL Interpreter: Should use df.show(1000, false)…

… to display results

### What is this PR for?
Livy SQL interpreter truncate result strings of size greater than 20. In 
some cases, we like to see the full string. We are adding an interpreter 
property zeppelin.livy.spark.sql.truncate to control whether to truncate 
strings or not. By default, zeppelin.livy.spark.sql.truncate is set to true.

### What type of PR is it?
Improvement

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

### How should this be tested?
Set zeppelin.livy.spark.sql.truncate to true or false 
Run a SQL query which produces string values of length greater than 20.
Depending on the value of zeppelin.livy.spark.sql.truncate, the strings 
will either get truncated or not.

### 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/benoyantony/zeppelin master

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

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


commit 3a3a4e9ce01f4dc184175e1f22b77d7a3bb6b46b
Author: Benoy Antony 
Date:   2017-03-29T06:24:31Z

[ZEPPELIN-1965] Livy SQL Interpreter: Should use df.show(1000, false) to 
display results




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

[AhyoungRyu]

Github user AhyoungRyu commented on the issue:

https://github.com/apache/zeppelin/pull/2199
  
Hi @markito Thanks for your contribution and taking care of Geode 
interpreter. 

 - Zeppelin build system relies on travis. So please setup your travis 
account and travis project for Zeppelin.
 - Please take a look 
https://zeppelin.apache.org/contribution/contributions.html#continuous-integration
 - The repository name must be Zeppelin (not incubator-zeppelin, ...)
 - It's not mandatory to pass all tests to be reviewed. But some reviewers 
might select passed PRs first

Trigger travis CI by pushing new commits or amend your last commit (git 
commit --amend and git push your-remote HEAD --force) after setup your travis.


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

[felixcheung]

Github user felixcheung commented on the issue:

https://github.com/apache/zeppelin/pull/2199
  
looks good, could you please setup CI as referenced here 
https://zeppelin.apache.org/contribution/contributions.html#continuous-integration


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