Github user rawkintrevo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/418#issuecomment-209982506
I'm basing my tutorial at ApacheCon loosely off of this. Let me go back
through and edit/update as appropriate. Hopefully next week or so.
---
If
Github user rawkintrevo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/794#issuecomment-202599734
After reviewing the other InterpreterTest files, I find that none utilize a
test where the output '.contains' a specific string. That specif
Github user rawkintrevo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/794#issuecomment-202538580
I moved the test to the end on a hunch that max fix the build issue.
@Leemoonsoo can you run again on your machine? I think the code is solid- it
just
GitHub user rawkintrevo reopened a pull request:
https://github.com/apache/incubator-zeppelin/pull/794
[ZEPPELIN-760] Companion object bug fix for Flink Interpretter
### What is this PR for?
This implements the solution presented for the Spark interpreter in PR-780
for the
Github user rawkintrevo closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/794
---
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
Github user rawkintrevo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/794#issuecomment-202463668
I really don't. I don't know much of anything about Ignite. I really was
only doing this for Flink, but Felix asked that I apply the fix to
Github user rawkintrevo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/794#issuecomment-201485432
Failed at:
Zeppelin: Server and Display system apis this time? Run it again?
---
If your project is set up for it, you can reply to this email and
Github user rawkintrevo closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/794
---
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
GitHub user rawkintrevo reopened a pull request:
https://github.com/apache/incubator-zeppelin/pull/794
[ZEPPELIN-760] Companion object bug fix for Flink Interpretter
### What is this PR for?
This implements the solution presented for the Spark interpreter in PR-780
for the
Github user rawkintrevo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/794#issuecomment-201433744
3622.1 Failed on
assertTrue(result.message().contains(sizeVal + ": Int = " +
ignite.cluster().nodes().size()));
Which I di
Github user rawkintrevo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/794#issuecomment-201269846
I was getting test errors earlier because I copy/pasted to fast and didn't
change the name of the interpreter context variable as I went (or chang
Github user rawkintrevo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/794#issuecomment-201109499
once again failing on npm install.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user rawkintrevo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/794#issuecomment-200554562
this has failed twice on npm install... ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
GitHub user rawkintrevo opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/794
[ZEPPELIN-658] Companion object bug fix for Flink Interpretter
### What is this PR for?
This implements the solution presented for the Spark interpreter in PR-780
for the Flink
Github user rawkintrevo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/418#issuecomment-173008525
Bump? These edits were taken care of some time ago.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user rawkintrevo closed the pull request at:
https://github.com/apache/incubator-zeppelin/pull/610
---
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
GitHub user rawkintrevo opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/610
[Doc] Fixed image links in displaysystem docs
These were broken and it annoyed me.
You can merge this pull request into a Git repository by running:
$ git pull https
Github user rawkintrevo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/418#issuecomment-169520079
That was sloppy copy-paste from my gist. My bad...
It's supposed to be
counts.collect().foreach(println(_)) // execute the script and
Github user rawkintrevo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/418#issuecomment-169518501
Spell check yes.
On note 2: I agree in spirit, however I'd really like to keep accessible
very novice users. Going forward I'm g
Github user rawkintrevo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/418#issuecomment-169333476
Yea, this is my first merge so once again- I have no idea what I'm doing.
Let me know if I need to do something.
Thanks!
---
If your pr
Github user rawkintrevo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/418#issuecomment-167327613
good idea- I am out for the holiday- I'll hit this Sunday night.
---
If your project is set up for it, you can reply to this email and have your
Github user rawkintrevo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/418#issuecomment-166157081
I only added pages to the website, and didn't realize those need headers.
Updating now.
---
If your project is set up for it, you can reply to
Github user rawkintrevo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/418#issuecomment-165940218
this is failing on missing dependencies
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
Github user rawkintrevo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/418#issuecomment-165902673
@jongyoul @bzz Sorry, I got busy with school and work stuff. Also, weird
my gmail didn't flag these as important. Anyway, the only thing left to
Github user rawkintrevo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/418#issuecomment-156277418
After carefully reviewing
https://github.com/rawkintrevo/incubator-zeppelin/blob/master/docs/docs/install/yarn_install.md
I don't thi
Github user rawkintrevo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/418#issuecomment-155795364
Ahh, yes the blog version runs against a branch of Zeppelin that covers the
most up to date Flink. That seemed inappropriate here so these directions
Github user rawkintrevo commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/418#issuecomment-155604728
No. Just the Flink 0.9 release that Zeppelin runs on internally.
---
If your project is set up for it, you can reply to this email and have your
reply
GitHub user rawkintrevo opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/418
Zeppelin Flink Spark tutorial
Moon recommended I migrate a How To tutorial I wrote into the website.
http://mail-archives.apache.org/mod_mbox/incubator-zeppelin-users
28 matches
Mail list logo
