My feeling is that what we need most is what I've been working on (surprise, surprise :) )
We need a simple Java app, very similar to the std Luke app. We need it to be Apache licensed all the way through. We need it to be fully integrated as a module. We need it to be straightforward enough that any of the Lucene/Solr committers can easily work on it and update it as API's change. GWT is probably a stretch for that goal - Apache Pivot is pretty straight forward though - for any reasonable Java developer. I picked it up in absolutely no time to build the thing from scratch - modifying it is 10 times easier. The backend code is all java, the layout and widgets all XML. I've been pushing towards that goal (over the years now) with Luke ALE (Apache Lucene Edition). It's not a straight port of Luke with thinlet to Luke with Apache Pivot - Luke has 90% of it's code in one huge class - I've already been working on modularizing that code as I've moved it over - not too heavily because that would have made it difficult to keep porting code, but a good start. Now that the majority of features have been moved over, it's probably easier to keep refactoring - which is needed, because another very important missing piece is unit tests - and good units tests will require even more refactoring of the code. I also think a GWT version - something that could probably run nicely with Solr - would be awesome. But way down the line in priority for me. We need something very close to Lucene that the committers will push up the hill as they push Lucene. - Mark On Jul 15, 2013, at 11:15 AM, Robert Muir <[email protected]> wrote: > I disagree with this completely. Solr is last priority > > On Jul 15, 2013 6:14 AM, "Jack Krupansky" <[email protected]> wrote: > My personal thoughts/preferences/suggestions for Luke: > > 1. Need a clean Luke Java library – heavily unit-tested. As integrated with > Lucene as possible. > 2. A simple command line interface – always useful. > 3. A Solr plugin handler – based on #1. Good for apps as well as Admin UI. > Nice to be able to curl a request to look at a specific doc, for example. > 4. GUI fully integrated with the new Solr Web Admin UI. A separate UI... > sucks. > 5. Any additional, un-untegrated GUI is icing on the cake and not really > desirable for Solr. May be great for Elasticsearch and other Lucene-based > apps, but Solr should be the #1 priority – after #1 and #2 above. > > -- Jack Krupansky > > From: Dmitry Kan > Sent: Monday, July 15, 2013 8:54 AM > To: [email protected] > Subject: Re: Request for Mentor for LUCENE-2562 : Make Luke a Lucene/Solr > Module > > Hello guys, > > Indeed, the GWT port is work in progress and far from done. The driving > factor here was to be able to later integrate luke into the solr admin as > well as have the standalone webapp for non-solr users. > There is (was?) a luke stats handler in the solr ui, that printed some stats > on the index. That could be substituted with the GWT app. > > The code isn't yet ready to see the light. So if it makes more sense for Ajay > to work on the existing jira with the Apache Pivot implementation, I would > say go ahead. > > In the current port effort (the aforementioned github's fork) the UI is the > original one, developed by Andrzej. Beside the UI rework there is plenty > things to port / verify (like e.g. Hadoop plugin) against the latest lucene > versions. > > See the readme.md: https://github.com/dmitrykey/luke > > > Whichever way's taken, hopefully we end up having stable releases of luke :) > > Dmitry Kan > > > On 14 July 2013 22:38, Andrzej Bialecki <[email protected]> wrote: > On 7/14/13 5:04 AM, Ajay Bhat wrote: > Shawn and Andrzej, > > Thanks for answering my questions. I've looked over the code done by > Dmitry and I'll look into what I can do to help with the UI porting in > future. > > I was actually thinking of doing this JIRA as a project by myself with > some assistance from the community after getting a mentor for the ASF > ICFOSS program, which I haven't found yet. It would be great if I could > get one of you guys as a mentor. > > As the UI work has been mostly done by others like Dmitry Kan, I don't > think I need to work on that majorly for now. > > It's far from done - he just started the process. > > > What other work is there to be done that I can do as a project? Any new > features or improvements? > > Regards, > Ajay > > On Jul 14, 2013 1:54 AM, "Andrzej Bialecki" <[email protected] > <mailto:[email protected]>> wrote: > > On 7/13/13 8:56 PM, Shawn Heisey wrote: > > On 7/13/2013 3:15 AM, Ajay Bhat wrote: > > One more question : What version of Lucene does Luke > currently support > right now? I saw a comment on the issue page that it doesn't > support the > Lucene 4.1 and 4.2 trunk. > > > The official Luke project only has versions up through 4.0.0-ALPHA. > > http://code.google.com/p/luke/ > > There is a forked project that has produced Luke for newer > Lucene versions. > > https://java.net/projects/__opengrok/downloads > > <https://java.net/projects/opengrok/downloads> > > I can't seem to locate any information about how they have > licensed the > newer versions, and I'm not really sure where the source code is > living. > > Regarding a question you asked earlier, Luke is a standalone > program. > It does include Lucene classes in the "lukeall" version of the > executable jar. > > Luke may have some uses as a library, but I think that most > people run > it separately. There is partial Luke functionality embedded in > the Solr > admin UI, but I don't know whether that is something cooked up > by Solr > devs or if it shares actual code with Luke. > > > Ajay, > > Luke is a standalone GUI application, not a library. It uses a > custom version of Thinlet GUI toolkit, which is no longer > maintained, and it's LGPL licensed, so Luke can't be contributed to > the Lucene project as is. > > Recently several people expressed interest in porting Luke to some > other GUI toolkit that is Apache-friendly. See the discussion here: > > http://groups.google.com/d/__msg/luke-discuss/S_Whwg2jwmA/__9JgqKIe5aiwJ > > <http://groups.google.com/d/msg/luke-discuss/S_Whwg2jwmA/9JgqKIe5aiwJ> > > In particular, there's a fork by Dmitry Kan - he plans to integrate > other patches and forks, and to port Luke from Thinlet to GWT and > sync it with the latest version of Lucene. I think you should > coordinate your efforts with him and other contributors that work on > that code base. This fork is Apache-licensed and the long-term plan > is to contribute it back to Lucene once the porting is done. > > The Pivot-based port of Luke that is in the Lucene sandbox is in an > early stage. I'm not sure Mark Miller has time to work on it due to > his involvement in SolrCloud development. > > The Luke handler in Solr is a completely different code base, and it > shares only the name with the Luke application. > > -- > Best regards, > Andrzej Bialecki > http://www.sigram.com, blog http://www.sigram.com/blog > ___.,___,___,___,_._. __________________<><______________________ > > [___||.__|__/|__||\/|: Information Retrieval, System Integration > ___|||__||..\|..||..|: Contact: info at sigram dot com > > > ------------------------------__------------------------------__--------- > To unsubscribe, e-mail: [email protected].__org > <mailto:[email protected]> > > For additional commands, e-mail: [email protected] > <mailto:[email protected]> > > > > > -- > Best regards, > Andrzej Bialecki > http://www.sigram.com, blog http://www.sigram.com/blog > ___.,___,___,___,_._. __________________<><____________________ > [___||.__|__/|__||\/|: Information Retrieval, System Integration > ___|||__||..\|..||..|: Contact: info at sigram dot com > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
