[
https://issues.apache.org/jira/browse/SOLR-15080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17266614#comment-17266614
]
David Eric Pugh commented on SOLR-15080:
----------------------------------------
Thanks for the pointer, patch applied great! I played with this some, and was
pleasantly surprised by the state of both Zeppelin, and the Solr to Zeppelin
integration! I've worked with in the past and run into various hiccups.
Couple of notes from playing that I wanted to share...
1. It fired right up, awesome.
2. We drag in some extra interpreters like kotlin and influxdb, in a "perfect
world" we wouldn't worry about them. Just a nit pick.
3. I ran "help" in Zeppelin Solr notebook, and while I got an error message, I
did get help ;-) Unknown command: help. List of allowed commands: [use, search,
facet, stream, sql], somethign to fix in zeppelin-solr!
4. bin/solr zeppelin -a start, the use -a for "action" doesn't match other
commands like bin/solr zk upconfig
5. use collection worked
6. Wish there was a "fields" commmand to help me understand the solr schema ;-)
Maybe used to be?
7. search and facet commands worked great with my Solr 8.7 3 node cluster
ecommerce demo project Chorus that was separately running under a docker
compose set up, so nice to know this could
point to another external Solr!
8. The "sql" command gives this help message: Specify the streaming expression.
Example: stream {streaming expression}, which isn't really what you expect!
9. with the right query: sql select id,title from ecommerce limit 10 it worked
;-)
10. The solr interpreter template has reference to JDBC that is
jdbc.driver=org.apache.hive.jdbc.HiveDriver which is confusing! Do we even
need it? Should it be the Solr JDBC string?
11. The "stream" help message could be better, like the "search" one ;-)
Specify the streaming expression. Example: stream {streaming expression}
12. stream does work!
stream
search(
ecommerce,
q=laptop,
rows=8
)
This is pretty darn cool... I know some of these issues belong elsewhere.
This plus some example data loaded into Solr would be pretty cool to add.
There are powerful analytics capabilities in Solr, but folks only think of it
for more traditional full text/attribute search use cases. This could help
people understand this whole new set of capabilities.
bin/solr start -e nyc311 <-- loads the nyc311 dataset as an example.
bin/solr zeppelin -e nyc311 <-- Loads the nyc311 .zepl files (and others?)
or
bin/solr zeppelin bootstrap <-- loads the nyc311 .zepl files (and others?)
> Apache Zeppelin Sandbox Integration
> -------------------------------------
>
> Key: SOLR-15080
> URL: https://issues.apache.org/jira/browse/SOLR-15080
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Jason Gerlowski
> Assignee: Jason Gerlowski
> Priority: Major
> Attachments: SOLR-15080.patch
>
>
> With the steady expansion of Solr's "Math Expression" and "Streaming
> Expression" libraries, Solr has a lot of analytics and data exploration
> capabilities to show off in a "notebook" environment. Case in point - the
> "Visual Guide to Math Expressions" being worked on in SOLR-13105. These docs
> make heavy use of screenshots taken from Zeppelin, a popular notebook project
> run by the ASF. Interested readers are going to want to try their own hand
> at replicating the specific visualizations showed off in those docs, and in
> using Solr's analytics capabilities more broadly.
> Zeppelin isn't hard to set up and run, but there are a few steps that might
> deter or thwart unfamiliar users. I'd love to see Solr make this easier by
> offering some sort of integration point with Zeppelin to get users up and
> running.
> I'm still up in the air on what form would be best for such an integration.
> But as a strawman I've attached a patch that creates a "zeppelin" tool for
> "bin/solr".
> This tool is in the same spirit as our Solr "examples" in that it sets a user
> up to play with a particular use case without any fuss or configuration on
> their part. It will install Zeppelin, the Zeppelin "interpreter" needed to
> talk to Solr, and the Zeppelin configs necessary to talk to a local Solr. It
> contains other commands to start/stop Zeppelin and clean out the Zeppelin
> sandbox, but draws the line there in terms of exposing Zeppelin functionality
> more broadly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
