Github user randerzander commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/765#issuecomment-197093663
@corneadoug @prabhjyotsingh any additional comments? Several people waiting
to use and build on top of this PR once it merges.
---
If your project
Github user randerzander commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/765#issuecomment-195813797
How to specify which columns should be used for lat/long/description?
Should there be a settings option we can use like other charts have?
---
If your
Github user randerzander commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/728#issuecomment-193081840
@corneadoug not sure about status of #152 , but this PR adds significant
additional functionality (heatmaps). since this PR is based on @Madhuka's work
Github user randerzander commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/728#issuecomment-192782294
this looks awesome. maps/heatmaps are one of the most asked for features
whenever I demo Zeppelin.
With this as a base, how difficult would
Github user randerzander commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/611#issuecomment-170285411
I wonder if this can be used in combination with #152/Zeppelin-157 ? I'm
thinking a streaming job emits GPS points which are dynamically populated
Github user randerzander commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/152#issuecomment-163108454
@Madhuka @bzz what's holding this one up? Is there something someone else
can do to get this across the goal line?
---
If your project is set up
GitHub user randerzander opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/327
ZEPPELIN-324: Zeppelin-web builds fail on OSX due to PhantomJS port
conflicts on port 8080
You can merge this pull request into a Git repository by running:
$ git pull https
Github user randerzander commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/152#issuecomment-141191419
anything we can do to figure out the failing CI build issue? This feature
is incredibly useful- will stop quite a lot of HTML and JS hacking for users
Github user randerzander commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/270#issuecomment-137828701
@Leemoonsoo how does z.load work with spark-submit? Seems those dependency
jars should be added automatically to spark-submit's --jars argument
Github user randerzander commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/167#issuecomment-132454645
Oops, good catch 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
Github user randerzander commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/167#issuecomment-131630155
Thanks for your help @tzolov and @Leemoonsoo I think I've got it this time!
---
If your project is set up for it, you can reply to this email and have
Github user randerzander commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/167#issuecomment-131468731
@tzolov @Leemoonsoo incorporated all feedbacks. Added ability to use upsert
and DDL statements by switching to execute instead of executeQuery
Github user randerzander commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/167#issuecomment-130886576
First two feedbacks incorporated.
@tzolov Having looked closer at your Mockito example, I think it may work.
I'll follow up here ASAP
Github user randerzander commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/167#issuecomment-129597424
First, thanks for the review and feedback, @Leemoonsoo and @tzolov -
I agree with the first 3, and will follow up with those changes
Github user randerzander commented on the pull request:
https://github.com/apache/incubator-zeppelin/pull/167#issuecomment-129567811
I suggest separating the Generic JDBC interpreter into its own feature as a
separate effort, then picking which of the existing interpreters can
GitHub user randerzander opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/167
Zeppelin-186: Apache Phoenix interpreter
Include an interpreter for Apache Phoenix
Almost identical to Hive interpreter. Could/should generic JDBC
interpreters be combined
GitHub user randerzander opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/166
README typo, build profile addition and version bump
Added interpreter/ folder to .gitignore
README.md
Fixed a typo in README.md
Updated mvn build command
17 matches
Mail list logo
