Hi
We are going to submit a PR for livy support for Spark - run the Spark
Driver in YARN rather than on the client. I heard that Hortonworks had a
proposal for such a PR. Does anybody have a link to it?
--
-
Dr. Jim Dowling
Associate Prof, KTH - Royal Institute of Technology
Github user mwkang commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/806#issuecomment-208182170
@corneadoug
Could you review this?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If you
Hello Malshan.
Thank you for your comment.
I thought this functionality need for users before but it doesn't now.
and The process you mentioned is right.
Thank you.
2016-04-11 4:48 GMT+09:00 Minudika Malshan :
> Hello,
>
> I am trying to implement the requested feature on Interpreter Rest API.
>
Github user johnnyws commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/796#issuecomment-208135091
Thanks, @felizbear ! I've made changes based on your comments. Passed karma
& jshint. Waiting green light from Travis and ready to merge.
---
If your proje
Github user felizbear commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/796#issuecomment-208119840
@johnnyws looks good. a few minor comments
+ creating en empty object and assigning props to it is unconventional in
JS; normally, you would create
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/804
---
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 fea
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/823#issuecomment-208085418
Merging it into master
---
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 doe
Github user Leemoonsoo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/745#issuecomment-208084967
Merge into master if there're no more discussions.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Hello,
I am trying to implement the requested feature on Interpreter Rest API.
As far as I understood, in order to get the interpreter id via REST API, we
have to send the name of interpreter, of which we need to get the id with
the rest call. Am I correct?
I would like to know your opinions on t
Github user doanduyhai commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/745#issuecomment-208034624
@Leemoonsoo Merge if ok ? Next 2 PR will concentrate on keeping same
paragraph Id when re-importing node from JSON and add comprehensive
documentation for
Thank you DuyHai :)
On Sun, Apr 10, 2016 at 2:48 AM, DuyHai Doan wrote:
> @Override
> public InterpreterResult interpret(String st, InterpreterContext context) {
> String paragraphId = context.getParagraphId();
> ...
> }
>
>
> On Sat, Apr 9, 2016 at 10:24 PM, Minudika Malshan
> wrote:
>
> >
11 matches
Mail list logo