[
https://issues.apache.org/jira/browse/SOLR-15080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17268083#comment-17268083
]
Jason Gerlowski edited comment on SOLR-15080 at 1/19/21, 5:47 PM:
------------------------------------------------------------------
bq. I know some of these issues belong elsewhere
Yeah, the zeppelin-solr repo is the "proper" place, for anyone unfamiliar.
Stuff about the individual notebook commands belongs there. There hasn't been
a ton of movement in that code recently but I'm hoping to update and refresh
some things - both for the benefit of this ticket and to get it ready to
contribute to Zeppelin as one of their bundled interpreters. Anyways,
usability feedback very welcome over there.
I think we can address (3), (6), (8), and (11) in zeppelin-solr.
(2), (4), and (10) are related to the integration code, so the fix for those is
going to be in the "ZeppelinTool" class attached to this ticket.
To expand on (4) briefly...for the prototype I just did the quickest thing and
parsed arguments with the "Option" and "OptionBuilder" classes that SolrCLI
uses for other tools. Those sort of assume a particular syntax, so that's what
we got. I didn't want to spend much time working around that before figuring
out whether people objected to the feature in the first place. But since I'm
not hearing any objections I'm happy to spend time cleaning up the syntax.
was (Author: gerlowskija):
bq. I know some of these issues belong elsewhere
Yeah, the zeppelin-solr repo is the "proper" place, for anyone unfamiliar.
Stuff about the individual notebook commands belongs there. There hasn't been
a ton of movement in that code recently but I'm hoping to update and refresh
some things - both for the benefit of this ticket and to get it ready to
contribute to Zeppelin as one of their bundled interpreters. Anyways,
usability feedback very welcome over there.
I think we can address (3), (6), (8), and (11) in zeppelin-solr.
(2), (4), and (10) are related to the integration code, so the fix for those is
going to be in the "ZeppelinTool" class attached to this ticket..
To expand on (4) briefly...for the prototype I just did the quickest thing and
parsed arguments with the "Option" and "OptionBuilder" classes that SolrCLI
uses for other tools. Those sort of assume a particular syntax, so that's what
we got. I didn't want to spend much time working around that before figuring
out whether people objected to the feature in the first place. But since I'm
not hearing any objections I'm happy to spend time cleaning up the syntax.
> 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
