[jira] [Commented] (SOLR-13412) Make the Lucene Luke module available from a Solr distribution

["Erick Erickson (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-13412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17173135#comment-17173135 ] 

Erick Erickson commented on SOLR-13412:
---------------------------------------

Getting back to this. This isn't part of the Lucene Gradle build yet, see LUCENE-9488.

But apart from that, my original thought was "well, if Luke is easy to access, let's just make it available from Solr". Then I discovered that we don't actually package it all up, it's only accessible in the Ant world by executing an Ant target from the source tree.

It's unclear whether Gradle will be the same. It's also unclear whether, even if Luke is packaged, whether it'd be part of the Lucene distro, those are TBD.

So I have some of questions about what to do here:

1> First and foremost, how much effort is this worth? Would the universe of Solr users who would find access the stand-alone Luke app useful be OK with having to download the source code and execute a Gradle or Ant task? If the latter, I can just close this. I think it's arguable that the Luke Request Handler is sufficient for most Solr users, and those users who would find the standalone app useful can build it.

1.1> I also don't particularly want to answer a bunch of questions about "I started Luke on my laptop and I can't find the indexes for my collection that are on AWS" ;)

2> If we do include it, should we bloat the distro by adding Luke stand-alone or should it be a package?

My current thinking is that if the stand-alone Luke app is packaged with Lucene automagically, I'll continue with this JIRA. I don't think we should add it to the distro separately though, so if we can build the standalone app easily and add it as a package that makes sense. If neither of the above, just close this as "won't fix".


> Make the Lucene Luke module available from a Solr distribution
> --------------------------------------------------------------
>
>                 Key: SOLR-13412
>                 URL: https://issues.apache.org/jira/browse/SOLR-13412
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Erick Erickson
>            Assignee: Erick Erickson
>            Priority: Major
>         Attachments: SOLR-13412.patch
>
>
> Now that [~Tomoko Uchida] has put in a great effort to bring Luke into the project, I think it would be good to be able to access it from a Solr distro.
> I want to go to the right place under the Solr install directory and start Luke up to examine the local indexes. 
> This ticket is explicitly _not_ about accessing it from the admin UI, Luke is a stand-alone app that must be invoked on the node that has a Lucene index on the local filesystem
> We need to 
>  * have it included in Solr when running "ant package". 
>  * add some bits to the ref guide on how to invoke
>  ** Where to invoke it from
>  ** mention anything that has to be installed.
>  ** any other "gotchas" someone just installing Solr should be aware of.
>  * Ant should not be necessary.
>  * ????
>  
> I'll assign this to myself to keep track of, but would not be offended in the least if someone with more knowledge of "ant package" and the like wanted to take it over ;)
> If we can do it at all....



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org