[GitHub] zeppelin issue #1497: [ZEPPELIN-1233] Support Redis interpreter

2016-10-12 Thread darionyaphet
Github user darionyaphet commented on the issue:

https://github.com/apache/zeppelin/pull/1497
  
Hi @anthonycorbacho  thank you for you great help and I'm still working on 
it .

I have implement a lot of command include `GEO` ,`HASH`, `HYPERLOGLOG`,  
`LIST`, `KEYS`, `Sets` ,`SORTED SET` and `Strings` and have 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 pull request #1476: ZEPPELIN-335. Pig Interpreter

2016-10-12 Thread zjffdu
GitHub user zjffdu reopened a pull request:

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

ZEPPELIN-335. Pig Interpreter

### What is this PR for?
Based on #338 , I refactor most of pig interpreter. As I don't think the 
approach in #338 is the best approach. In #338, we use script `bin/pig` to 
launch pig script, it is different to control that job (hard to kill and get 
progress and stats info).  In this PR, I use pig api to launch pig script. 
Besides that I implement another interpreter type `%pig.query` to leverage the 
display system of zeppelin. For the details you can check `pig.md`


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

### Todos
* Syntax Highlight
* new interpreter type `%pig.udf`, so that user can write pig udf in 
zeppelin directly and don't need to build udf jar manually.


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

### How should this be tested?
Unit test is added and also manual test is done

### Screenshots (if appropriate)


![image](https://cloud.githubusercontent.com/assets/164491/18986649/54217b4c-8730-11e6-9e33-25f98a98a9b6.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/zjffdu/zeppelin ZEPPELIN-335

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

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


commit 7abad201a63df51d04326231cbf429122540e311
Author: Ali Bajwa 
Date:   2015-10-06T05:40:06Z

initial commit of pig interpreter

commit 2586336e44982ac3c92156c24a288c540792d0c5
Author: Ali Bajwa 
Date:   2015-10-06T06:25:47Z

exposed timeout and pig executable via interpreter and added comments

commit c28beb588922a5edbc9d5db3336bbdba9a22c3a1
Author: Ali Bajwa 
Date:   2015-10-07T05:02:18Z

Updated based on comments:
1. Documentation: added pig.md with interpreter documentation and added pig 
entry to index.md
2. Added test junit test based on passwd file parsing example here 
https://pig.apache.org/docs/r0.10.0/start.html#run
3. Removed author tag from comment (this was copied from shell interpreter 
https://github.com/apache/incubator-zeppelin/blob/master/shell/src/main/java/org/apache/zeppelin/shell/ShellInterpreter.java#L42)
4. Implemented cancel functionality
5. Display output stream in case of error

commit a09a7f78c6f72cf8bf5623a55c71cc06141671aa
Author: Jeff Zhang 
Date:   2016-09-28T11:41:24Z

refactor pig Interpreter

commit 05a3b9b0a76423660497dfb92cf773cec1687871
Author: Jeff Zhang 
Date:   2016-10-08T03:45:22Z

add pig.md

commit 39f161a36aad72c590a2feef4c8f7b4afefe72ec
Author: Jeff Zhang 
Date:   2016-10-08T08:09:33Z

address comments

commit 5e2e222555dabfb66a7981e5d7d0d0f659ca1144
Author: AhyoungRyu 
Date:   2016-10-09T12:35:07Z

Minor update for pig.md

commit df7a6db47ca2db5b8d3ed625000d6a25f035a8e5
Author: AhyoungRyu 
Date:   2016-10-09T12:35:25Z

Add pig.md to dropdown menu

commit fe014a72b445f6977d00356bfe780c40dade0167
Author: AhyoungRyu 
Date:   2016-10-09T12:39:41Z

Fix docs title in front matter

commit 1ae7db21a32f12ce139277a8dca4e61cd391bced
Author: Jeff Zhang 
Date:   2016-10-09T13:23:07Z

Merge pull request #2 from AhyoungRyu/ZEPPELIN-335/docs

[ZEPPELIN-335][DOCS] Minor update for pig.md

commit 58b4b2f26dd8f852d453854a37764a824903d9cd
Author: Jeff Zhang 
Date:   2016-10-09T13:28:41Z

minor update of docs

commit c85a09031a49add7f48114afe3ea43e4b572b0f2
Author: Jeff Zhang 
Date:   2016-10-09T23:45:03Z

add license

commit e858301bdfcac727fea8ef306f42ecd252ddfe94
Author: Jeff Zhang 
Date:   2016-10-10T00:27:08Z

address comments

commit a1b742bceeff34aad1196ce2de9235810b4ce961
Author: Jeff Zhang 
Date:   2016-10-10T07:42:30Z

minor update on doc




---
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 #1476: ZEPPELIN-335. Pig Interpreter

2016-10-12 Thread zjffdu
Github user zjffdu closed the pull request at:

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


---
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 #1505: [HOTFIX] Set default ZEPPELIN_INTP_MEM

2016-10-12 Thread asfgit
Github user asfgit closed the pull request at:

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


---
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 #1506: [BUILD][MINOR] Change build profile for distrib...

2016-10-12 Thread asfgit
Github user asfgit closed the pull request at:

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


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


[CANCEL][VOTE] Release Apache Zeppelin 0.6.2 (rc1)

2016-10-12 Thread Mina Lee
I am voting to -1 and canceling vote because of the issue that Zeppelin
cannot run Spark Interpreter with zero configuration.
Vote for rc2 will start shortly.
Thank you everyone who helped testing rc1 release. I encourage you to
verify for rc2 as well for the sake of stable release.

Cheers,
Mina

On Mon, Oct 10, 2016 at 9:34 PM Mina Lee  wrote:

> Hi folks,
>
> I propose the following RC to be released for the Apache Zeppelin
> 0.6.2 release.
>
> The commit id is 9a44590841d5d83da1a297d507f6e2e67784ba1f which is
> corresponds to the tag v0.6.2-rc1:
>
> https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=commit;h=9a44590841d5d83da1a297d507f6e2e67784ba1f
>
> The release archives (tgz), signature, and checksums are here
> https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.6.2-rc1/
>
> The release candidate consists of the following source distribution
> archive
> zeppelin-0.6.2.tgz
>
> In addition, the following supplementary binary distributions are provided
> for user convenience at the same location
> zeppelin-0.6.2-bin-all.tgz
> zeppelin-0.6.2-netinst-all.tgz
>
> The maven artifacts are here
> https://repository.apache.org/content/repositories/orgapachezeppelin-1019
>
> You can find the KEYS file here:
> https://people.apache.org/keys/committer/minalee.asc
>
> Release notes available at
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316221&version=12338135
>
> Vote will be open for next 72 hours (close at 6am 13/Oct PDT).
>
> [ ] +1 approve
> [ ] 0 no opinion
> [ ] -1 disapprove (and reason why)
>


Re: [VOTE] Release Apache Zeppelin 0.6.2 (rc1)

2016-10-12 Thread CloverHearts
+1

2016. 10. 11. 오후 4:38, "Victor Manuel Garcia"  작성:

+1

2016-10-11 3:36 GMT+02:00 Ahyoung Ryu :

> +1
>
>
>
> On Tue, Oct 11, 2016 at 10:24 AM, Jeff Zhang  wrote:
>
> > +1, teste with spark 2.0 with basic notes,  ZeppelinContext and UDF 
works
> > correctly.
> >
> > On Tue, Oct 11, 2016 at 8:41 AM, Anthony Corbacho <
> > corbacho.anth...@gmail.com> wrote:
> >
> > > +1
> > >
> > > I tested with my notebooks works as expected.
> > > Great job!
> > >
> > > On Mon, Oct 10, 2016 at 9:34 PM, Mina Lee  wrote:
> > >
> > > > Hi folks,
> > > >
> > > > I propose the following RC to be released for the Apache Zeppelin
> > > > 0.6.2 release.
> > > >
> > > > The commit id is 9a44590841d5d83da1a297d507f6e2e67784ba1f which is
> > > > corresponds to the tag v0.6.2-rc1:
> > > > https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=commit;h=
> > > > 9a44590841d5d83da1a297d507f6e2e67784ba1f
> > > >
> > > > The release archives (tgz), signature, and checksums are here
> > > > https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.6.2-rc1/
> > > >
> > > > The release candidate consists of the following source distribution
> > > archive
> > > > zeppelin-0.6.2.tgz
> > > >
> > > > In addition, the following supplementary binary distributions are
> > > provided
> > > > for user convenience at the same location
> > > > zeppelin-0.6.2-bin-all.tgz
> > > > zeppelin-0.6.2-netinst-all.tgz
> > > >
> > > > The maven artifacts are here
> > > > https://repository.apache.org/content/repositories/
> > > orgapachezeppelin-1019
> > > >
> > > > You can find the KEYS file here:
> > > > https://people.apache.org/keys/committer/minalee.asc
> > > >
> > > > Release notes available at
> > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > > projectId=12316221&version=12338135
> > > >
> > > > Vote will be open for next 72 hours (close at 6am 13/Oct PDT).
> > > >
> > > > [ ] +1 approve
> > > > [ ] 0 no opinion
> > > > [ ] -1 disapprove (and reason why)
> > > >
> > >
> >
> >
> >
> > --
> > Best Regards
> >
> > Jeff Zhang
> >
>



-- 
*Victor Manuel Garcia Martinez*
*Technical Architect*




*+34 672104297  | victor.gar...@beeva.com *
 *  | victormanuel.garcia.marti...@bbva.com
*







[VOTE] Release Apache Zeppelin 0.6.2 (RC2)

2016-10-12 Thread Mina Lee
Hi dev,

I propose the following RC to be released for the Apache Zeppelin 0.6.2
release.

The commit id is 091086de9400dd1c02ca02acf4180b1bf1e9ede7 which is corresponds
to the tag v0.6.2-rc2:
*https://git-wip-us.apache.org/repos/asf?p=zeppelin.git;a=commit;h=091086de9400dd1c02ca02acf4180b1bf1e9ede7
*

The release archives (tgz), signature, and checksums are here
https://dist.apache.org/repos/dist/dev/zeppelin/zeppelin-0.6.2-rc2/

The release candidate consists of the following source distribution archive
zeppelin-0.6.2.tgz

In addition, the following supplementary binary distributions are provided
for user convenience at the same location
zeppelin-0.6.2-bin-all.tgz
zeppelin-0.6.2-netinst-all.tgz

The maven artifacts are here
https://repository.apache
.org/content/repositories/orgapachezeppelin-1020/org/apache/zeppelin/

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=12336543&styleName=Html&projectId=12316221
*

Vote will be open for next 72 hours (close at 4am 15/Oct PDT).

[ ] +1 approve
[ ] 0 no opinion
[ ] -1 disapprove (and reason why)


[GitHub] zeppelin issue #1476: ZEPPELIN-335. Pig Interpreter

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

https://github.com/apache/zeppelin/pull/1476
  
@felixcheung Test is passed, I suspect the selenium test is flaky so failed 
last time. 


---
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 #1500: [ZEPPELIN-1371]add text/numeric conversion support to ...

2016-10-12 Thread Peilin-Yang
Github user Peilin-Yang commented on the issue:

https://github.com/apache/zeppelin/pull/1500
  
@corneadoug done


---
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-1536) Spark 2 SparkListenerBus has already stopped

2016-10-12 Thread darion yaphet (JIRA)
darion yaphet created ZEPPELIN-1536:
---

 Summary: Spark 2 SparkListenerBus has already stopped
 Key: ZEPPELIN-1536
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1536
 Project: Zeppelin
  Issue Type: Bug
  Components: Core
Affects Versions: 0.6.1
Reporter: darion yaphet


when I using zeppelin with spark 2.0.1 It's failed when startup spark job on 
yarn .

{noformat}

ERROR [2016-10-12 18:47:20,118] ({Yarn application state monitor} 
Logging.scala[logError]:70) - SparkListenerBus has already stopped! Dropping 
event SparkListenerStageCompleted(org.apache.spark.scheduler.StageInfo@7b1d3cb9)
ERROR [2016-10-12 18:47:20,119] ({pool-2-thread-2} Logging.scala[logError]:70) 
- SparkListenerBus has already stopped! Dropping event 
SparkListenerSQLExecutionEnd(0,1476269240118)
ERROR [2016-10-12 18:47:20,120] ({Yarn application state monitor} 
Logging.scala[logError]:70) - SparkListenerBus has already stopped! Dropping 
event 
SparkListenerJobEnd(0,1476269240119,JobFailed(org.apache.spark.SparkException: 
Job 0 cancelled because SparkContext was shut down))
ERROR [2016-10-12 18:47:20,123] ({pool-2-thread-2} Job.java[run]:189) - Job 
failed

org.apache.zeppelin.interpreter.InterpreterException: 
java.lang.reflect.InvocationTargetException
at 
org.apache.zeppelin.spark.ZeppelinContext.showDF(ZeppelinContext.java:218)
at 
org.apache.zeppelin.spark.SparkSqlInterpreter.interpret(SparkSqlInterpreter.java:129)
at 
org.apache.zeppelin.interpreter.LazyOpenInterpreter.interpret(LazyOpenInterpreter.java:94)
at 
org.apache.zeppelin.interpreter.remote.RemoteInterpreterServer$InterpretJob.jobRun(RemoteInterpreterServer.java:341)
at org.apache.zeppelin.scheduler.Job.run(Job.java:176)
at 
org.apache.zeppelin.scheduler.ParallelScheduler$JobRunner.run(ParallelScheduler.java:162)
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)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at 
org.apache.zeppelin.spark.ZeppelinContext.showDF(ZeppelinContext.java:214)
... 12 more
Caused by: org.apache.spark.SparkException: Job 0 cancelled because 
SparkContext was shut down
at 
org.apache.spark.scheduler.DAGScheduler$$anonfun$cleanUpAfterSchedulerStop$1.apply(DAGScheduler.scala:818)
at 
org.apache.spark.scheduler.DAGScheduler$$anonfun$cleanUpAfterSchedulerStop$1.apply(DAGScheduler.scala:816)
at scala.collection.mutable.HashSet.foreach(HashSet.scala:78)
at 
org.apache.spark.scheduler.DAGScheduler.cleanUpAfterSchedulerStop(DAGScheduler.scala:816)
at 
org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.onStop(DAGScheduler.scala:1685)
at org.apache.spark.util.EventLoop.stop(EventLoop.scala:83)
at org.apache.spark.scheduler.DAGScheduler.stop(DAGScheduler.scala:1604)
at 
org.apache.spark.SparkContext$$anonfun$stop$8.apply$mcV$sp(SparkContext.scala:1798)
at org.apache.spark.util.Utils$.tryLogNonFatalError(Utils.scala:1287)
at org.apache.spark.SparkContext.stop(SparkContext.scala:1797)
at 
org.apache.spark.scheduler.cluster.YarnClientSchedulerBackend$MonitorThread.run(YarnClientSchedulerBackend.scala:108)
at 
org.apache.spark.scheduler.DAGScheduler.runJob(DAGScheduler.scala:632)
at org.apache.spark.SparkContext.runJob(SparkContext.scala:1890)
at org.apache.spark.SparkContext.runJob(SparkContext.scala:1903)
at org.apache.spark.SparkContext.runJob(SparkContext.scala:1916)
at 
org.apache.spark.sql.execution.SparkPlan.executeTake(SparkPlan.scala:347)
at 
org.apache.spark.sql.execution.CollectLimitExec.executeCollect(limit.scala:39)

{noformat}



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


[GitHub] zeppelin issue #1464: [Zeppelin 796] [WIP] Duplicated notebook names should ...

2016-10-12 Thread rajarajan-g
Github user rajarajan-g commented on the issue:

https://github.com/apache/zeppelin/pull/1464
  
@jongyoul : Hey i was quite busy for sometime.

I was trying to resolve the commit issues that you have pointed out.

but while during rebase i am getting below error

```
git rebase master
First, rewinding head to replay your work on top of it...
Applying: Code changes for ZEPPELIN-796
Using index info to reconstruct a base tree...
M   
zeppelin-server/src/main/java/org/apache/zeppelin/socket/NotebookServer.java
M   zeppelin-web/src/components/noteName-create/notename.controller.js
M   zeppelin-web/src/components/noteName-import/note-import-dialog.html
M   zeppelin-web/src/components/noteName-import/notenameImport.controller.js
M   zeppelin-web/src/components/websocketEvents/websocketEvents.factory.js
:18: trailing whitespace.
 * @throws DuplicateNameException 
:40: trailing whitespace.
 * @throws DuplicateNameException 
:98: trailing whitespace.
   * @throws DuplicateNameException 
:175: trailing whitespace.

:187: trailing whitespace.
  conn.send(serializeMessage(new Message(OP.ERROR_DIALOG).put("info", 
warning: squelched 21 whitespace errors
warning: 26 lines add whitespace errors.
Falling back to patching base and 3-way merge...
Auto-merging 
zeppelin-web/src/components/websocketEvents/websocketEvents.factory.js
CONFLICT (content): Merge conflict in 
zeppelin-web/src/components/websocketEvents/websocketEvents.factory.js
Auto-merging 
zeppelin-web/src/components/noteName-import/notenameImport.controller.js
CONFLICT (content): Merge conflict in 
zeppelin-web/src/components/noteName-import/notenameImport.controller.js
Auto-merging 
zeppelin-web/src/components/noteName-import/note-import-dialog.html
Auto-merging 
zeppelin-web/src/components/noteName-create/notename.controller.js
CONFLICT (content): Merge conflict in 
zeppelin-web/src/components/noteName-create/notename.controller.js
Auto-merging 
zeppelin-server/src/main/java/org/apache/zeppelin/socket/NotebookServer.java
Failed to merge in the changes.
Patch failed at 0001 Code changes for ZEPPELIN-796
The copy of the patch that failed is found in:
   /home/rajarajang/Workspace/stsWorksapce/zeppelin/.git/rebase-apply/patch

When you have resolved this problem, run "git rebase --continue".
If you prefer to skip this patch, run "git rebase --skip" instead.
To check out the original branch and stop rebasing, run "git rebase 
--abort".
```
Even though after i resolve the conflicts, again it shows conflict again 
and not able to remove that unnecessary commit that you pointed out. Please 
help me out on resolving that issue

Please let me know if anyone has faced this issue and also please let me if 
there is a way to resolve this 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 #1464: [Zeppelin 796] [WIP] Duplicated notebook names should ...

2016-10-12 Thread rajarajan-g
Github user rajarajan-g commented on the issue:

https://github.com/apache/zeppelin/pull/1464
  
@corneadoug : If a user creates a note with same name, it would do no good 
to that user itself as it confuses him.

For resolving the scenario, we can pick one of the below ways
1. we should have one unique notebook name across the server.(Not quite a 
solution)
2. we can follow unique notebook name per user in server.
In case if a note is shared by the creator with other users, an extra 
information should be available to user like below in home page of notebook

**NoteName**  _**(created by user1)**_ 



---
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 #1476: ZEPPELIN-335. Pig Interpreter

2016-10-12 Thread abajwa-hw
Github user abajwa-hw commented on the issue:

https://github.com/apache/zeppelin/pull/1476
  
@zjffdu thanks for working on this interpreter! Looks great


---
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 #1471: Closes [ZEPPELIN-1505] Add Scio interpreter

2016-10-12 Thread ravwojdyla
Github user ravwojdyla commented on the issue:

https://github.com/apache/zeppelin/pull/1471
  
@zjffdu @AhyoungRyu are there any other 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 #1499: [ZEPPELIN-1528] Add progress information in addition t...

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

https://github.com/apache/zeppelin/pull/1499
  
Great! Thanks for your contribution. Looks like a big change and I'll take 
a look shortly.


---
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 #1476: ZEPPELIN-335. Pig Interpreter

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

https://github.com/apache/zeppelin/pull/1476
  
I think @AhyoungRyu has a comment?



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


Max text message size for Websocket connection

2016-10-12 Thread Sandeep More
Hello,

I am planning to add proxy support for Zeppelin in Knox and would like to
know what are the default values for the following properties:

1) Max text message size for Websocket connection
2) Max binary message size for Websocket connection

Also, are these properties configurable.

Thanks !
Sandeep


[jira] [Created] (ZEPPELIN-1537) Elasticsearch interpreter improvement for aggregations

2016-10-12 Thread Bruno Bonnin (JIRA)
Bruno Bonnin created ZEPPELIN-1537:
--

 Summary: Elasticsearch interpreter improvement for aggregations
 Key: ZEPPELIN-1537
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1537
 Project: Zeppelin
  Issue Type: Improvement
  Components: Interpreters
Affects Versions: 0.6.1, 0.6.0
Reporter: Bruno Bonnin
Assignee: Bruno Bonnin
 Fix For: 0.7.0


The result of an aggregation query returned by the interpreter contains only 
"key" and "doc_count" in case of a multi-buckets aggregations.
But the result returned by Elasticsearch can contain more data according to the 
query.
The result returned by the interpreter must return the same values as 
elasticsearch.



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


[GitHub] zeppelin pull request #1508: [ZEPPELIN-1537] Elasticsearch improvement for r...

2016-10-12 Thread bbonnin
GitHub user bbonnin opened a pull request:

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

[ZEPPELIN-1537] Elasticsearch improvement for results of aggregations

### What is this PR for?
The result of an aggregation query returned by the interpreter contains 
only "key" and "doc_count" in case of a multi-buckets aggregations.
But the result returned by Elasticsearch can contain more data according to 
the query.
This PR is an improvement of the result returned by the interpreter.

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

### Todos
* [X] - Dev of the improvement in the interpreter
* [X] - Add a test case 

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

### How should this be tested?
In a paragraph, enter a query with multiple aggregations:
search /logs { "aggs" : { 
"length" : { "terms": { "field": "status" }, 
"aggs" : { "sum_length" : { "sum" : { "field" : 
"content_length" } } } } }

### Screenshots (if appropriate)

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



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

$ git pull https://github.com/bbonnin/zeppelin master

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

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


commit a0a7bb9f3773340b9916f650fcbee5af8178fc21
Author: Bruno Bonnin 
Date:   2016-10-12T21:20:25Z

Elasticsearch improvement for results of aggregations




---
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-1538) Using Spark MulticlassMetrics throws NoSuchFieldException: MODULE$

2016-10-12 Thread nirav patel (JIRA)
nirav patel created ZEPPELIN-1538:
-

 Summary: Using Spark MulticlassMetrics throws 
NoSuchFieldException: MODULE$
 Key: ZEPPELIN-1538
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1538
 Project: Zeppelin
  Issue Type: Bug
  Components: Core
Affects Versions: 0.6.2
Reporter: nirav patel


I am using zeppeling 0.6.2 built for spark 2.0

I am frequently getting following error on call to ` 
multiclassMetrics.recall(labelId)`



Caused by: java.lang.NoSuchFieldException: MODULE$
at java.lang.Class.getField(Class.java:1703)
at scala.Enumeration.readResolve(Enumeration.scala:61)
at scala.Enumeration$Val.readResolve(Enumeration.scala:227)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
java.io.ObjectStreamClass.invokeReadResolve(ObjectStreamClass.java:1148)
... 336 more


Driver stacktrace:
  at 
org.apache.spark.scheduler.DAGScheduler.org$apache$spark$scheduler$DAGScheduler$$failJobAndIndependentStages(DAGScheduler.scala:1450)
  at 
org.apache.spark.scheduler.DAGScheduler$$anonfun$abortStage$1.apply(DAGScheduler.scala:1438)
  at 
org.apache.spark.scheduler.DAGScheduler$$anonfun$abortStage$1.apply(DAGScheduler.scala:1437)
  at 
scala.collection.mutable.ResizableArray$class.foreach(ResizableArray.scala:59)
  at scala.collection.mutable.ArrayBuffer.foreach(ArrayBuffer.scala:48)
  at org.apache.spark.scheduler.DAGScheduler.abortStage(DAGScheduler.scala:1437)
  at 
org.apache.spark.scheduler.DAGScheduler$$anonfun$handleTaskSetFailed$1.apply(DAGScheduler.scala:811)
  at 
org.apache.spark.scheduler.DAGScheduler$$anonfun$handleTaskSetFailed$1.apply(DAGScheduler.scala:811)
  at scala.Option.foreach(Option.scala:257)
  at 
org.apache.spark.scheduler.DAGScheduler.handleTaskSetFailed(DAGScheduler.scala:811)
  at 
org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.doOnReceive(DAGScheduler.scala:1659)
  at 
org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.onReceive(DAGScheduler.scala:1618)
  at 
org.apache.spark.scheduler.DAGSchedulerEventProcessLoop.onReceive(DAGScheduler.scala:1607)
  at org.apache.spark.util.EventLoop$$anon$1.run(EventLoop.scala:48)
  at org.apache.spark.scheduler.DAGScheduler.runJob(DAGScheduler.scala:632)
  at org.apache.spark.SparkContext.runJob(SparkContext.scala:1871)
  at org.apache.spark.SparkContext.runJob(SparkContext.scala:1884)
  at org.apache.spark.SparkContext.runJob(SparkContext.scala:1897)
  at org.apache.spark.SparkContext.runJob(SparkContext.scala:1911)
  at org.apache.spark.rdd.RDD$$anonfun$collect$1.apply(RDD.scala:893)
  at 
org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:151)
  at 
org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:112)
  at org.apache.spark.rdd.RDD.withScope(RDD.scala:358)
  at org.apache.spark.rdd.RDD.collect(RDD.scala:892)
  at 
org.apache.spark.rdd.PairRDDFunctions$$anonfun$countByKey$1.apply(PairRDDFunctions.scala:372)
  at 
org.apache.spark.rdd.PairRDDFunctions$$anonfun$countByKey$1.apply(PairRDDFunctions.scala:372)
  at 
org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:151)
  at 
org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:112)
  at org.apache.spark.rdd.RDD.withScope(RDD.scala:358)
  at 
org.apache.spark.rdd.PairRDDFunctions.countByKey(PairRDDFunctions.scala:371)
  at org.apache.spark.rdd.RDD$$anonfun$countByValue$1.apply(RDD.scala:1156)
  at org.apache.spark.rdd.RDD$$anonfun$countByValue$1.apply(RDD.scala:1156)
  at 
org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:151)
  at 
org.apache.spark.rdd.RDDOperationScope$.withScope(RDDOperationScope.scala:112)
  at org.apache.spark.rdd.RDD.withScope(RDD.scala:358)
  at org.apache.spark.rdd.RDD.countByValue(RDD.scala:1155)
  at 
org.apache.spark.mllib.evaluation.MulticlassMetrics.labelCountByClass$lzycompute(MulticlassMetrics.scala:42)
  at 
org.apache.spark.mllib.evaluation.MulticlassMetrics.labelCountByClass(MulticlassMetrics.scala:42)
  at 
org.apache.spark.mllib.evaluation.MulticlassMetrics.recall(MulticlassMetrics.scala:115)
  at cfae60361b5eed1a149235c6e9b59b24$anonfun$1.apply(:129)
  at cfae60361b5eed1a149235c6e9b59b24$anonfun$1.apply(:129)
  at 
scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:234)
  at 
scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:234)
  at 
scala.collection.IndexedSeqOptimized$class.foreach(IndexedSeqOptimized.scala:33)
  at scala.collection.mutable.ArrayOps$ofDouble.foreach(ArrayOps.scala:270)
  at scala.collection.TraversableLike$class.map(

[jira] [Created] (ZEPPELIN-1539) df.show and other calls to dataframes fails after adding new column to DF

2016-10-12 Thread nirav patel (JIRA)
nirav patel created ZEPPELIN-1539:
-

 Summary: df.show and other calls to dataframes fails after adding 
new column to DF
 Key: ZEPPELIN-1539
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1539
 Project: Zeppelin
  Issue Type: Bug
  Components: Core
Affects Versions: 0.6.2
Reporter: nirav patel


Tested with spark 2.0 build.

Once you add a new column to existing dataframe using withColumn() function 
everything start failing with following error.

Caused by: java.lang.NoSuchFieldException: MODULE$
at java.lang.Class.getField(Class.java:1703)
at scala.Enumeration.readResolve(Enumeration.scala:61)
at scala.Enumeration$Val.readResolve(Enumeration.scala:227)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
java.io.ObjectStreamClass.invokeReadResolve(ObjectStreamClass.java:1148)
... 333 more



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


Re: Max text message size for Websocket connection

2016-10-12 Thread moon soo Lee
Hi,

ZeppelinServer [1] sets Websocket text message size with default value
defined in ZeppelinConfiguration [2].

Hope this helps.

Thanks,
moon

[1]
https://github.com/apache/zeppelin/blob/master/zeppelin-server/src/main/java/org/apache/zeppelin/server/ZeppelinServer.java#L214
[2]
https://github.com/apache/zeppelin/blob/master/zeppelin-zengine/src/main/java/org/apache/zeppelin/conf/ZeppelinConfiguration.java#L576


On Thu, Oct 13, 2016 at 3:53 AM Sandeep More  wrote:

> Hello,
>
>
>
> I am planning to add proxy support for Zeppelin in Knox and would like to
>
> know what are the default values for the following properties:
>
>
>
> 1) Max text message size for Websocket connection
>
> 2) Max binary message size for Websocket connection
>
>
>
> Also, are these properties configurable.
>
>
>
> Thanks !
>
> Sandeep
>
>


Re: Max text message size for Websocket connection

2016-10-12 Thread Sandeep More
Perfect, this is exactly what I needed. Thanks Moon !

Best,
Sandeep

On Wed, Oct 12, 2016 at 8:57 PM, moon soo Lee  wrote:

> Hi,
>
> ZeppelinServer [1] sets Websocket text message size with default value
> defined in ZeppelinConfiguration [2].
>
> Hope this helps.
>
> Thanks,
> moon
>
> [1]
> https://github.com/apache/zeppelin/blob/master/zeppelin-
> server/src/main/java/org/apache/zeppelin/server/ZeppelinServer.java#L214
> [2]
> https://github.com/apache/zeppelin/blob/master/zeppelin-
> zengine/src/main/java/org/apache/zeppelin/conf/ZeppelinConfiguration.java#
> L576
>
>
> On Thu, Oct 13, 2016 at 3:53 AM Sandeep More 
> wrote:
>
> > Hello,
> >
> >
> >
> > I am planning to add proxy support for Zeppelin in Knox and would like to
> >
> > know what are the default values for the following properties:
> >
> >
> >
> > 1) Max text message size for Websocket connection
> >
> > 2) Max binary message size for Websocket connection
> >
> >
> >
> > Also, are these properties configurable.
> >
> >
> >
> > Thanks !
> >
> > Sandeep
> >
> >
>


[GitHub] zeppelin issue #1476: ZEPPELIN-335. Pig Interpreter

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

https://github.com/apache/zeppelin/pull/1476
  
@felixcheung @AhyoungRyu 's comment is addressed. 


---
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 #1500: [ZEPPELIN-1371]add text/numeric conversion support to ...

2016-10-12 Thread corneadoug
Github user corneadoug commented on the issue:

https://github.com/apache/zeppelin/pull/1500
  
@Peilin-Yang 
Have to fix a test, need to change the expected result in that test from 
`1,787` to `1787`
```
Failed tests: 
  SparkParagraphIT.testSqlSpark:188 Paragraph from SparkParagraphIT of 
testSqlSpark result: 
Expected: "age\njob\nmarital\neducation\nbalance\n30 unemployed married 
primary 1,787"
 but: was 
"age\nâ–¼\njob\nâ–¼\nmarital\nâ–¼\neducation\nâ–¼\nbalance\nâ–¼\n30
 unemployed married primary 1787"

Tests run: 15, Failures: 1, Errors: 0, Skipped: 0
```


---
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-1540) Misleading input form placeholder for note import url

2016-10-12 Thread Khalid Huseynov (JIRA)
Khalid Huseynov created ZEPPELIN-1540:
-

 Summary: Misleading input form placeholder for note import url
 Key: ZEPPELIN-1540
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1540
 Project: Zeppelin
  Issue Type: Improvement
Reporter: Khalid Huseynov
Priority: Minor


When trying to import note from some url, both input form placeholders contain 
"Note name" which is confusing. Second input form should contain "Note url"



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


[GitHub] zeppelin pull request #1509: [Zeppelin-1540] fix note url input placeholder

2016-10-12 Thread khalidhuseynov
GitHub user khalidhuseynov opened a pull request:

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

[Zeppelin-1540] fix note url input placeholder

### What is this PR for?
Fix input form placeholder for `note url`

### What type of PR is it?
Improvement

### Todos
* [x] - Task

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

### How should this be tested?
go to import note menu -> add from url -> see input forms

### Screenshots (if appropriate)
Before:
https://cloud.githubusercontent.com/assets/1642088/19337731/9ea41248-9152-11e6-859b-757f44b2866a.png";>


After:
https://cloud.githubusercontent.com/assets/1642088/19337716/7f90522c-9152-11e6-8ad2-cbfcdc241e10.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/khalidhuseynov/incubator-zeppelin 
fix/note-import-placeholder

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

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


commit c01b9828ffe1b628b7523c9671c59fe4fdfbcebe
Author: Khalid Huseynov 
Date:   2016-10-13T05:26:58Z

note name -> note url




---
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-1541) Spark isn't the default interpreter

2016-10-12 Thread Kavin Kumar (JIRA)
Kavin Kumar created ZEPPELIN-1541:
-

 Summary: Spark isn't the default interpreter
 Key: ZEPPELIN-1541
 URL: https://issues.apache.org/jira/browse/ZEPPELIN-1541
 Project: Zeppelin
  Issue Type: Bug
  Components: Interpreters
Reporter: Kavin Kumar
Priority: Minor


The default interpreter is currently set as "md" instead of spark due to the 
below property configuration in zeppelin-site.xml The double-quotes in front of 
spark below doesn't make it default.

{code}

  zeppelin.interpreter.group.order
"spark,md,angular,sh,livy,alluxio,file,psql,flink,python,ignite,lens,cassandra,geode,kylin,elasticsearch,scalding,jdbc,hbase
  

{code}



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


[GitHub] zeppelin issue #1509: [Zeppelin-1540] fix note url input placeholder

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

https://github.com/apache/zeppelin/pull/1509
  
@khalidhuseynov nice catch! yeah it's really confusing. 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.
---