gerlowskija commented on pull request #74:
URL: https://github.com/apache/solr/pull/74#issuecomment-819722432


   Hey @HoustonPutman Thanks for chiming in. A few replies inline.
   
   > what does this provide over running Zeppelin locally yourself?
   
   It automates all of the needed setup behind a single command: `bin/solr 
zeppelin bootstrap`.  So in a word: convenience.  You're right that Solr 
doesn't "know" about Zeppelin the same way that it knows about ZK, though 
Zeppelin isn't a totally random tool either.  Our ["Math Expressions" 
docs](https://solr.apache.org/guide/8_8/math-expressions.html) make heavy use 
of Zeppelin screenshots, for instance.
   
   > I can see the use case for solr-bin add-ons, kind of like how kubectl does 
plugins.
   
   I tried making [making a proper Solr plugin out of 
this](https://github.com/gerlowskija/binsolr-zeppelin) a month or so back, but 
Solr's plugin framework isn't ready for this use case yet.  (Currently, the 
plugin infrastructure lives in CoreContainer so only running Solr nodes have 
access to plugin jars.  I was able to get my plugin installed, but SolrCLI 
couldn't see it to run ZeppelinTool).
   
   That's all to say - I'm only going the direct bin/solr route here because 
other attempts at a plugin setup failed.
   
   Can you expand on the kubectl-plugin-like approach you have in mind?  I'm 
not against it necessarily, but I'm not sure I understand the benefits yet.  
The large majority of the zeppelin integration logic lives in Java, with 
`bin/solr` really just being a passthrough call into Java-land. What does 
moving that passthrough over to `bin/plugins/zeppelin.sh` really get us?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org

Reply via email to