You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by Ajay Bhat <a....@gmail.com> on 2013/07/12 07:13:12 UTC
Request for Mentor for LUCENE-2562 : Make Luke a Lucene/Solr Module
Hi all,
I had attended the ASF-ICFOSS Mentoring Programme [1], 2013 in India
conducted by Luciano Resende[2] and I've developed an interest in open
source. I'd like to work on the JIRA Lucene 2562 - Make Luke a Lucene/Solr
Module [3] as a project.
I've checked out the Lucene trunk and taken a look at the work Mark Miller
has done on it. If no one has taken it up, I'm willing to work on it after
submitting a formal project proposal after I get a mentor. I'd like some
technical guidance on Lucene from the community as well.
[1] http://community.apache.org/mentoringprogramme-icfoss-pilot.html
[2] http://people.apache.org/~lresende
[3] https://issues.apache.org/jira/browse/LUCENE-2562
Thanks and regards,
Ajay
Re: Request for Mentor for LUCENE-2562 : Make Luke a Lucene/Solr Module
Posted by Mark Miller <ma...@gmail.com>.
On Jul 13, 2013, at 2:04 AM, Ajay Bhat <a....@gmail.com> wrote:
> Thanks Mark.
>
> I've got to make a project proposal at this page. https://cwiki.apache.org/confluence/display/COMDEV/ASF-ICFOSS+Pilot+Mentoring+Programme
>
> Shall I include you as a mentor? Would anyone else like to be a mentor to this project alongwith Mark?
>
> I've also got some preliminary questions about the issue
>
> 1. You mention that the UI, currently using Java (Swing I presume?) needs to be ported to another toolkit. May I ask why?
>
The license of the current UI framework.
> 2. For porting, is there a preferred toolkit you'd like it to be ported to or any you, like the PyGTK?
>
I think a Java UI framework is the way to go - I've already done a lot of the work on that issue using Apache Pivot. http://pivot.apache.org/
> 3. Has the work on Pivot been completed? If not, what else is to be done?
>
A lot of work has been completed. A lot of the basic UI tabs were already working - mostly it probably needs to be updated to the latest Lucene API's and the remaining features need to be ported over. A lot of work has already been done and a lot of the work remains - if you look at the attachments on that JIRA you will see some early screen shots of the current work - more was done after those shots were taken.
https://issues.apache.org/jira/secure/attachment/12450420/luke1.jpg
https://issues.apache.org/jira/secure/attachment/12450421/luke2.jpg
https://issues.apache.org/jira/secure/attachment/12450422/luke3.jpg
> 4. Can I run Luke by itself or should it be built alongwith Lucene as it refers some classes of Lucene?
>
The idea of that JIRA issue is to put Luke in as a Lucene module. This way, as the Lucene API's are changed, Luke will get updated at the same time since it will be part of the Lucene project.
> Also, it would be great if you could link me to some slides or posts about Luke (the first two links on the issue page don't seem to work)
>
https://code.google.com/p/luke/
- Mark
> Regards,
>
> Ajay
>
>
>
> On Jul 12, 2013 11:28 PM, "Mark Miller" <ma...@gmail.com> wrote:
>
> Great! I'd be glad to help get you going!
>
> I think that issue would have a very large affect if we could get it up to speed - it's a very popular tool and having it released with Lucene and always up to date with trunk would really help a lot of people I think.
>
> - Mark
>
>
> On Fri, Jul 12, 2013 at 1:13 AM, Ajay Bhat <a....@gmail.com> wrote:
> Hi all,
>
> I had attended the ASF-ICFOSS Mentoring Programme [1], 2013 in India conducted by Luciano Resende[2] and I've developed an interest in open source. I'd like to work on the JIRA Lucene 2562 - Make Luke a Lucene/Solr Module [3] as a project.
>
> I've checked out the Lucene trunk and taken a look at the work Mark Miller has done on it. If no one has taken it up, I'm willing to work on it after submitting a formal project proposal after I get a mentor. I'd like some technical guidance on Lucene from the community as well.
>
> [1] http://community.apache.org/mentoringprogramme-icfoss-pilot.html
>
> [2] http://people.apache.org/~lresende
>
> [3] http
> LUCENE-2562
>
> s://issues.apache.org/jira/browse/Thanks and regards,
> Ajay
>
>
>
> --
> - Mark
Re: Request for Mentor for LUCENE-2562 : Make Luke a Lucene/Solr Module
Posted by Ajay Bhat <a....@gmail.com>.
Two more questions :
1. How much of the original Luke.java has yet to be modularised?
2. What are the new APIs in Lucene 4.1 and 4.2 that need immediate
attention to be updated?
On Tue, Jul 16, 2013 at 12:15 AM, Ajay Bhat <a....@gmail.com> wrote:
> Hi all,
>
> The most pressing issue is that I need a mentor for this project by
> Wednesday, 17th July 2013 if I'm to do it for the ASF-ICFOSS program [1].
> Currently I've not found any mentors. Would anyone here please consent to
> be a mentor for this project so I can include you in my proposal?
>
> For the project I've decided to use Apache Pivot and familiarize myself
> with it, going throught the tutorials ASAP
>
> There's some more questions I have:
>
> 1. The original version by Andrzej [2] I have checked out in Eclipse but I
> can't run it. It's all under mainly a huge Luke.java file. Just want to
> check that the UI is same as that in the sandboxed version in Lucene.
>
> 2. There are various plugins that require Luke.java to be imported. But
> there's also a Shell.java plugin [3] that doesn't need any import needed.
> Does this mean it can be ported directly or is it kept for future
> improvement? If its the latter I guess a CMD Interface suggested by Jack
> Krupansky could be implemented using this class.
>
>
> [1] http://community.apache.org/mentoringprogramme-icfoss-pilot.html
>
> [2] https://code.google.com/p/luke/
>
> [3] org.getopt.luke.plugins.Shell
>
>
> On Mon, Jul 15, 2013 at 9:03 PM, Shawn Heisey <so...@elyograg.org> wrote:
>
>> On 7/15/2013 9:15 AM, Robert Muir wrote:
>> > I disagree with this completely. Solr is last priority
>>
>> I'm on the Solr side of things, with only the tiniest knowledge or
>> interest in hacking on Lucene. Despite that, I have to agree with
>> Robert here.
>>
>> Let's make sure the Luke module is very solid and prove that we can keep
>> it operational through 2-3 full minor release cycles before we try to
>> integrate it into Solr.
>>
>> We already have luke functionality in the Solr UI. Compared to the real
>> thing it might be a band-aid, but it works.
>>
>> Thanks,
>> Shawn
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>>
>
Re: Request for Mentor for LUCENE-2562 : Make Luke a Lucene/Solr Module
Posted by Ajay Bhat <a....@gmail.com>.
Hi all,
The most pressing issue is that I need a mentor for this project by
Wednesday, 17th July 2013 if I'm to do it for the ASF-ICFOSS program [1].
Currently I've not found any mentors. Would anyone here please consent to
be a mentor for this project so I can include you in my proposal?
For the project I've decided to use Apache Pivot and familiarize myself
with it, going throught the tutorials ASAP
There's some more questions I have:
1. The original version by Andrzej [2] I have checked out in Eclipse but I
can't run it. It's all under mainly a huge Luke.java file. Just want to
check that the UI is same as that in the sandboxed version in Lucene.
2. There are various plugins that require Luke.java to be imported. But
there's also a Shell.java plugin [3] that doesn't need any import needed.
Does this mean it can be ported directly or is it kept for future
improvement? If its the latter I guess a CMD Interface suggested by Jack
Krupansky could be implemented using this class.
[1] http://community.apache.org/mentoringprogramme-icfoss-pilot.html
[2] https://code.google.com/p/luke/
[3] org.getopt.luke.plugins.Shell
On Mon, Jul 15, 2013 at 9:03 PM, Shawn Heisey <so...@elyograg.org> wrote:
> On 7/15/2013 9:15 AM, Robert Muir wrote:
> > I disagree with this completely. Solr is last priority
>
> I'm on the Solr side of things, with only the tiniest knowledge or
> interest in hacking on Lucene. Despite that, I have to agree with
> Robert here.
>
> Let's make sure the Luke module is very solid and prove that we can keep
> it operational through 2-3 full minor release cycles before we try to
> integrate it into Solr.
>
> We already have luke functionality in the Solr UI. Compared to the real
> thing it might be a band-aid, but it works.
>
> Thanks,
> Shawn
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
Re: Request for Mentor for LUCENE-2562 : Make Luke a Lucene/Solr
Module
Posted by Shawn Heisey <so...@elyograg.org>.
On 7/15/2013 9:15 AM, Robert Muir wrote:
> I disagree with this completely. Solr is last priority
I'm on the Solr side of things, with only the tiniest knowledge or
interest in hacking on Lucene. Despite that, I have to agree with
Robert here.
Let's make sure the Luke module is very solid and prove that we can keep
it operational through 2-3 full minor release cycles before we try to
integrate it into Solr.
We already have luke functionality in the Solr UI. Compared to the real
thing it might be a band-aid, but it works.
Thanks,
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Request for Mentor for LUCENE-2562 : Make Luke a Lucene/Solr Module
Posted by Yonik Seeley <yo...@lucidworks.com>.
On Mon, Jul 15, 2013 at 11:15 AM, Robert Muir <rc...@gmail.com> wrote:
> I disagree with this completely. Solr is last priority
I guess that would be up to those doing the work. Solr is a higher
priority for some people.
-Yonik
http://lucidworks.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Request for Mentor for LUCENE-2562 : Make Luke a Lucene/Solr Module
Posted by Mark Miller <ma...@gmail.com>.
Yes, it's in the public repo - see my recent comment on
https://issues.apache.org/jira/browse/LUCENE-2562 - it's really simple to
check it out and run it.
On Tue, Jul 16, 2013 at 2:07 AM, Ashish <pa...@gmail.com> wrote:
> @Mark - Do you have it in public repo?
>
>
>
>
> On Tue, Jul 16, 2013 at 12:02 AM, Mark Miller <ma...@gmail.com>wrote:
>
>> 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 <rc...@gmail.com> wrote:
>>
>> I disagree with this completely. Solr is last priority
>> On Jul 15, 2013 6:14 AM, "Jack Krupansky" <ja...@basetechnology.com>
>> 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 <dm...@gmail.com>
>>> *Sent:* Monday, July 15, 2013 8:54 AM
>>> *To:* dev@lucene.apache.org
>>> *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 <ab...@getopt.org> 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" <ab@getopt.org
>>>>> <ma...@getopt.org>> 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>
>>>>>
>>>>> <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>
>>>>>
>>>>> <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: dev-unsubscribe@lucene.apache.**__org
>>>>> <ma...@lucene.apache.org>>
>>>>>
>>>>>
>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>> <mailto:dev-help@lucene.**apache.org <de...@lucene.apache.org>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> 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: dev-unsubscribe@lucene.apache.**org<de...@lucene.apache.org>
>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>
>>>>
>>>
>>
>>
>
>
> --
> thanks
> ashish
>
> Blog: http://www.ashishpaliwal.com/blog
> My Photo Galleries: http://www.pbase.com/ashishpaliwal
>
--
- Mark
Re: Request for Mentor for LUCENE-2562 : Make Luke a Lucene/Solr Module
Posted by Ajay Bhat <a....@gmail.com>.
I've started writing up a proposal. As soon as I get a mentor, I'll post it
on this thread.
I've got one more question : There are plugins like HadoopPlugin.java [1]
and [2] in the source code [3] but I can't find them or any other plugins
in the version that uses Thinlet API [4]. How do I run these classes from
Eclipse IDE?
[1]
http://luke.googlecode.com/svn/trunk/src/org/getopt/luke/plugins/HadoopPlugin.java
[2]
http://luke.googlecode.com/svn/trunk/src/org/getopt/luke/plugins/ZipfAnalysisPlugin.java
[3] http://luke.googlecode.com/svn/trunk/src/org/getopt/luke/
[4] Attachment
On Tue, Jul 16, 2013 at 11:37 AM, Ashish <pa...@gmail.com> wrote:
> @Mark - Do you have it in public repo?
>
>
>
>
> On Tue, Jul 16, 2013 at 12:02 AM, Mark Miller <ma...@gmail.com>wrote:
>
>> 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 <rc...@gmail.com> wrote:
>>
>> I disagree with this completely. Solr is last priority
>> On Jul 15, 2013 6:14 AM, "Jack Krupansky" <ja...@basetechnology.com>
>> 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 <dm...@gmail.com>
>>> *Sent:* Monday, July 15, 2013 8:54 AM
>>> *To:* dev@lucene.apache.org
>>> *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 <ab...@getopt.org> 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" <ab@getopt.org
>>>>> <ma...@getopt.org>> 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>
>>>>>
>>>>> <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>
>>>>>
>>>>> <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: dev-unsubscribe@lucene.apache.**__org
>>>>> <ma...@lucene.apache.org>>
>>>>>
>>>>>
>>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>> <mailto:dev-help@lucene.**apache.org <de...@lucene.apache.org>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> 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: dev-unsubscribe@lucene.apache.**org<de...@lucene.apache.org>
>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>>
>>>>
>>>
>>
>>
>
>
> --
> thanks
> ashish
>
> Blog: http://www.ashishpaliwal.com/blog
> My Photo Galleries: http://www.pbase.com/ashishpaliwal
>
Re: Request for Mentor for LUCENE-2562 : Make Luke a Lucene/Solr Module
Posted by Ashish <pa...@gmail.com>.
@Mark - Do you have it in public repo?
On Tue, Jul 16, 2013 at 12:02 AM, Mark Miller <ma...@gmail.com> wrote:
> 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 <rc...@gmail.com> wrote:
>
> I disagree with this completely. Solr is last priority
> On Jul 15, 2013 6:14 AM, "Jack Krupansky" <ja...@basetechnology.com> 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 <dm...@gmail.com>
>> *Sent:* Monday, July 15, 2013 8:54 AM
>> *To:* dev@lucene.apache.org
>> *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 <ab...@getopt.org> 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" <ab@getopt.org
>>>> <ma...@getopt.org>> 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>
>>>>
>>>> <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>
>>>>
>>>> <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: dev-unsubscribe@lucene.apache.**__org
>>>> <ma...@lucene.apache.org>>
>>>>
>>>>
>>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>> <mailto:dev-help@lucene.**apache.org <de...@lucene.apache.org>>
>>>>
>>>>
>>>
>>>
>>> --
>>> 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: dev-unsubscribe@lucene.apache.**org<de...@lucene.apache.org>
>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>
>>>
>>
>
>
--
thanks
ashish
Blog: http://www.ashishpaliwal.com/blog
My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: Request for Mentor for LUCENE-2562 : Make Luke a Lucene/Solr Module
Posted by Mark Miller <ma...@gmail.com>.
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 <rc...@gmail.com> wrote:
> I disagree with this completely. Solr is last priority
>
> On Jul 15, 2013 6:14 AM, "Jack Krupansky" <ja...@basetechnology.com> 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: dev@lucene.apache.org
> 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 <ab...@getopt.org> 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" <ab@getopt.org
> <ma...@getopt.org>> 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: dev-unsubscribe@lucene.apache.__org
> <ma...@lucene.apache.org>
>
> For additional commands, e-mail: dev-help@lucene.apache.org
> <ma...@lucene.apache.org>
>
>
>
>
> --
> 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: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
Re: Request for Mentor for LUCENE-2562 : Make Luke a Lucene/Solr Module
Posted by Robert Muir <rc...@gmail.com>.
I disagree with this completely. Solr is last priority
On Jul 15, 2013 6:14 AM, "Jack Krupansky" <ja...@basetechnology.com> 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 <dm...@gmail.com>
> *Sent:* Monday, July 15, 2013 8:54 AM
> *To:* dev@lucene.apache.org
> *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 <ab...@getopt.org> 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" <ab@getopt.org
>>> <ma...@getopt.org>> 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>
>>>
>>> <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>
>>>
>>> <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: dev-unsubscribe@lucene.apache.**__org
>>> <ma...@lucene.apache.org>>
>>>
>>>
>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>> <mailto:dev-help@lucene.**apache.org <de...@lucene.apache.org>>
>>>
>>>
>>
>>
>> --
>> 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: dev-unsubscribe@lucene.apache.**org<de...@lucene.apache.org>
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>>
>
Re: Request for Mentor for LUCENE-2562 : Make Luke a Lucene/Solr Module
Posted by Jack Krupansky <ja...@basetechnology.com>.
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: dev@lucene.apache.org
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 <ab...@getopt.org> 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" <ab@getopt.org
<ma...@getopt.org>> 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: dev-unsubscribe@lucene.apache.__org
<ma...@lucene.apache.org>
For additional commands, e-mail: dev-help@lucene.apache.org
<ma...@lucene.apache.org>
--
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Request for Mentor for LUCENE-2562 : Make Luke a Lucene/Solr Module
Posted by Dmitry Kan <dm...@gmail.com>.
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 <ab...@getopt.org> 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" <ab@getopt.org
>> <ma...@getopt.org>> 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>
>>
>> <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>
>>
>> <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: dev-unsubscribe@lucene.apache.**__org
>> <ma...@lucene.apache.org>
>> >
>>
>> For additional commands, e-mail: dev-help@lucene.apache.org
>> <mailto:dev-help@lucene.**apache.org <de...@lucene.apache.org>>
>>
>>
>
>
> --
> 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: dev-unsubscribe@lucene.apache.**org<de...@lucene.apache.org>
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
Re: Request for Mentor for LUCENE-2562 : Make Luke a Lucene/Solr
Module
Posted by Andrzej Bialecki <ab...@getopt.org>.
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" <ab@getopt.org
> <ma...@getopt.org>> 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: dev-unsubscribe@lucene.apache.__org
> <ma...@lucene.apache.org>
> For additional commands, e-mail: dev-help@lucene.apache.org
> <ma...@lucene.apache.org>
>
--
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Request for Mentor for LUCENE-2562 : Make Luke a Lucene/Solr Module
Posted by Ajay Bhat <a....@gmail.com>.
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.
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" <ab...@getopt.org> 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: dev-unsubscribe@lucene.apache.**org<de...@lucene.apache.org>
> For additional commands, e-mail: dev-help@lucene.apache.org
>
>
Re: Request for Mentor for LUCENE-2562 : Make Luke a Lucene/Solr
Module
Posted by Andrzej Bialecki <ab...@getopt.org>.
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
>
> 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
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Request for Mentor for LUCENE-2562 : Make Luke a Lucene/Solr
Module
Posted by Shawn Heisey <so...@elyograg.org>.
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
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.
Thanks,
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Request for Mentor for LUCENE-2562 : Make Luke a Lucene/Solr Module
Posted by Ajay Bhat <a....@gmail.com>.
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.
Ajay Bhat, TKMCE
On Jul 13, 2013 11:34 AM, "Ajay Bhat" <a....@gmail.com> wrote:
> Thanks Mark.
>
> I've got to make a project proposal at this page.
> https://cwiki.apache.org/confluence/display/COMDEV/ASF-ICFOSS+Pilot+Mentoring+Programme
>
> Shall I include you as a mentor? Would anyone else like to be a mentor to
> this project alongwith Mark?
>
> I've also got some preliminary questions about the issue
>
> 1. You mention that the UI, currently using Java (Swing I presume?) needs
> to be ported to another toolkit. May I ask why?
> 2. For porting, is there a preferred toolkit you'd like it to be ported to
> or any you, like the PyGTK?
> 3. Has the work on Pivot been completed? If not, what else is to be done?
> 4. Can I run Luke by itself or should it be built alongwith Lucene as it
> refers some classes of Lucene?
>
> Also, it would be great if you could link me to some slides or posts about
> Luke (the first two links on the issue page don't seem to work)
>
> Regards,
>
> Ajay
>
>
> On Jul 12, 2013 11:28 PM, "Mark Miller" <ma...@gmail.com> wrote:
>
>> Great! I'd be glad to help get you going!
>>
>> I think that issue would have a very large affect if we could get it up
>> to speed - it's a very popular tool and having it released with Lucene and
>> always up to date with trunk would really help a lot of people I think.
>>
>> - Mark
>>
>>
>> On Fri, Jul 12, 2013 at 1:13 AM, Ajay Bhat <a....@gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> I had attended the ASF-ICFOSS Mentoring Programme [1], 2013 in India
>>> conducted by Luciano Resende[2] and I've developed an interest in open
>>> source. I'd like to work on the JIRA Lucene 2562 - Make Luke a Lucene/Solr
>>> Module [3] as a project.
>>>
>>> I've checked out the Lucene trunk and taken a look at the work Mark
>>> Miller has done on it. If no one has taken it up, I'm willing to work on it
>>> after submitting a formal project proposal after I get a mentor. I'd like
>>> some technical guidance on Lucene from the community as well.
>>>
>>> [1] http://community.apache.org/mentoringprogramme-icfoss-pilot.html
>>>
>>> [2] http://people.apache.org/~lresende
>>>
>>> [3] https://issues.apache.org/jira/browse/LUCENE-2562
>>>
>>> Thanks and regards,
>>> Ajay
>>>
>>
>>
>>
>> --
>> - Mark
>>
>
Re: Request for Mentor for LUCENE-2562 : Make Luke a Lucene/Solr Module
Posted by Ajay Bhat <a....@gmail.com>.
Thanks Mark.
I've got to make a project proposal at this page.
https://cwiki.apache.org/confluence/display/COMDEV/ASF-ICFOSS+Pilot+Mentoring+Programme
Shall I include you as a mentor? Would anyone else like to be a mentor to
this project alongwith Mark?
I've also got some preliminary questions about the issue
1. You mention that the UI, currently using Java (Swing I presume?) needs
to be ported to another toolkit. May I ask why?
2. For porting, is there a preferred toolkit you'd like it to be ported to
or any you, like the PyGTK?
3. Has the work on Pivot been completed? If not, what else is to be done?
4. Can I run Luke by itself or should it be built alongwith Lucene as it
refers some classes of Lucene?
Also, it would be great if you could link me to some slides or posts about
Luke (the first two links on the issue page don't seem to work)
Regards,
Ajay
On Jul 12, 2013 11:28 PM, "Mark Miller" <ma...@gmail.com> wrote:
> Great! I'd be glad to help get you going!
>
> I think that issue would have a very large affect if we could get it up to
> speed - it's a very popular tool and having it released with Lucene and
> always up to date with trunk would really help a lot of people I think.
>
> - Mark
>
>
> On Fri, Jul 12, 2013 at 1:13 AM, Ajay Bhat <a....@gmail.com> wrote:
>
>> Hi all,
>>
>> I had attended the ASF-ICFOSS Mentoring Programme [1], 2013 in India
>> conducted by Luciano Resende[2] and I've developed an interest in open
>> source. I'd like to work on the JIRA Lucene 2562 - Make Luke a Lucene/Solr
>> Module [3] as a project.
>>
>> I've checked out the Lucene trunk and taken a look at the work Mark
>> Miller has done on it. If no one has taken it up, I'm willing to work on it
>> after submitting a formal project proposal after I get a mentor. I'd like
>> some technical guidance on Lucene from the community as well.
>>
>> [1] http://community.apache.org/mentoringprogramme-icfoss-pilot.html
>>
>> [2] http://people.apache.org/~lresende
>>
>> [3] https://issues.apache.org/jira/browse/LUCENE-2562
>>
>> Thanks and regards,
>> Ajay
>>
>
>
>
> --
> - Mark
>
Re: Request for Mentor for LUCENE-2562 : Make Luke a Lucene/Solr Module
Posted by Mark Miller <ma...@gmail.com>.
Great! I'd be glad to help get you going!
I think that issue would have a very large affect if we could get it up to
speed - it's a very popular tool and having it released with Lucene and
always up to date with trunk would really help a lot of people I think.
- Mark
On Fri, Jul 12, 2013 at 1:13 AM, Ajay Bhat <a....@gmail.com> wrote:
> Hi all,
>
> I had attended the ASF-ICFOSS Mentoring Programme [1], 2013 in India
> conducted by Luciano Resende[2] and I've developed an interest in open
> source. I'd like to work on the JIRA Lucene 2562 - Make Luke a Lucene/Solr
> Module [3] as a project.
>
> I've checked out the Lucene trunk and taken a look at the work Mark Miller
> has done on it. If no one has taken it up, I'm willing to work on it after
> submitting a formal project proposal after I get a mentor. I'd like some
> technical guidance on Lucene from the community as well.
>
> [1] http://community.apache.org/mentoringprogramme-icfoss-pilot.html
>
> [2] http://people.apache.org/~lresende
>
> [3] https://issues.apache.org/jira/browse/LUCENE-2562
>
> Thanks and regards,
> Ajay
>
--
- Mark
Re: Request for Mentor for LUCENE-2562 : Make Luke a Lucene/Solr Module
Posted by Ajay Bhat <a....@gmail.com>.
Guys, I really do need a mentor urgently for this project so I can post my
proposal to the ASF ICFOSS page [1], since as part of the programme we have
to be allotted a mentor.
I understand if people are too busy with other commitments to
development. In that case, I wouldn't bug the mentor too much if
they're on their busy
schedule. I just need some general guidance and for the mentor to point out
if I'm going in the wrong direction for this project.
Thanks,
Ajay
[1]
https://cwiki.apache.org/confluence/display/COMDEV/ASF-ICFOSS+Pilot+Mentoring+Programme
On Fri, Jul 12, 2013 at 10:43 AM, Ajay Bhat <a....@gmail.com> wrote:
> Hi all,
>
> I had attended the ASF-ICFOSS Mentoring Programme [1], 2013 in India
> conducted by Luciano Resende[2] and I've developed an interest in open
> source. I'd like to work on the JIRA Lucene 2562 - Make Luke a Lucene/Solr
> Module [3] as a project.
>
> I've checked out the Lucene trunk and taken a look at the work Mark Miller
> has done on it. If no one has taken it up, I'm willing to work on it after
> submitting a formal project proposal after I get a mentor. I'd like some
> technical guidance on Lucene from the community as well.
>
> [1] http://community.apache.org/mentoringprogramme-icfoss-pilot.html
>
> [2] http://people.apache.org/~lresende
>
> [3] https://issues.apache.org/jira/browse/LUCENE-2562
>
> Thanks and regards,
> Ajay
>