You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by Andrzej Bialecki <ab...@getopt.org> on 2003/08/11 13:10:38 UTC

Luke v 0.2 - Lucene Index Browser

Dear Lucene Users,

I'm glad to announce that a new version of Luke is available for 
download, and as a Java WebStart application.

Luke is a diagnostic tool for Lucene (http://jakarta.apache.org/lucene) 
indexes. It enables you to browse documents in existing indexes, perform 
queries, navigate through terms, optimize indexes and more.

Please go to http://www.getopt.org/luke and give it a try. You can 
either use the Java WebStart version, or just download the JAR file with 
binaries. Full source code is available, under Apache license.

Changes in v0.2:

* Add Java WebStart version.
* Add Read-Only mode.
* Fix spinbox bug (really a bug in the Thinlet toolkit - fixed there).
* Allow to browse hidden directories.
* Add a combobox to choose the default field for searching.
* Other minor code cleanups.

Thanks to all who provided their comments and suggestions!

-- 
Best regards,
Andrzej Bialecki

-------------------------------------------------
Software Architect, System Integration Specialist
CEN/ISSS EC Workshop, ECIMF project chair
EU FP6 E-Commerce Expert/Evaluator
-------------------------------------------------
FreeBSD developer (http://www.freebsd.org)




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


Re: Luke v 0.2 - Lucene Index Browser

Posted by Julien Nioche <Ju...@lingway.com>.
Hello,

> > - Remove the empty field (see mailing list Lucene dev 4/16/2003 message
from
> > Otis)
>
> Well... I thought it was just reported as a bug. I don't see any
> responses to this, so I guess this is still a bug, and Luke is not the
> one to be fixed. :-)

Sure - I meant HIDE this field in the summary as a temporary solution
but it would be better to solve the problem in Lucene of course.


> > - Information about the # of segments
>
> Need to check this, but shouldn't be any problem. I'm not sure whether
> it's useful, though... ?

It 's an indication of whether or not an index has to be optimized.



----- Original Message -----
From: "Andrzej Bialecki" <ab...@getopt.org>
To: "Lucene Users List" <lu...@jakarta.apache.org>
Sent: Monday, August 11, 2003 7:55 PM
Subject: Re: Luke v 0.2 - Lucene Index Browser


> Julien Nioche wrote:
>
> > Hello,
> >
> > Thanks to Andrzej for this new version! Luke is really useful.
> >
>
> You're welcome. It was fun to code.
>
> >
> >>open the original Dokuments with the platform dependant mimetype viewer
>
> Someone else already explained the problems with this... What is a
> document in Lucene? It's a set of fields and their String values (or
> their terms), so it's not possible to open the original document from
> which the values were extracted, because there is no original...
>
> >
> > ???
> >
> > My suggestions by order of importance would be :
> >
> > - History of the 5 last indexes used : under the File Menu item ?
>
> No problem. I mean, technically it's no problem, it's just a problem of
> getting to it on my so called "free time" ...
>
> > - Remove the empty field (see mailing list Lucene dev 4/16/2003 message
from
> > Otis)
>
> Well... I thought it was just reported as a bug. I don't see any
> responses to this, so I guess this is still a bug, and Luke is not the
> one to be fixed. :-)
>
> > - Possibility to merge different indexes
>
> No problem.
>
> > - Information about the # of segments
>
> Need to check this, but shouldn't be any problem. I'm not sure whether
> it's useful, though... ?
>
> > [- and almost impossible : recompose the unstored fields of a document]
>
> It's not impossible, just time-consuming - all information (except the
> parts removed by analyzer) is already there. This functionality has a
> high "cool-ness" factor, which makes it very tempting... :-)
>
> Thanks for these suggestions! I can't promise any timeline, but
> eventually I'd like to include this functionality in Luke. Patches are
> always welcome... :-)
>
> --
> Best regards,
> Andrzej Bialecki
>
> -------------------------------------------------
> Software Architect, System Integration Specialist
> CEN/ISSS EC Workshop, ECIMF project chair
> EU FP6 E-Commerce Expert/Evaluator
> -------------------------------------------------
> FreeBSD developer (http://www.freebsd.org)
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>
>


Re: Luke v 0.2 - Lucene Index Browser

Posted by Peter Becker <pb...@dstc.edu.au>.
Andrzej Bialecki wrote:

[...Luke feature requests...]

>>
>>> open the original Dokuments with the platform dependant mimetype viewer
>>
>
> Someone else already explained the problems with this... What is a 
> document in Lucene? It's a set of fields and their String values (or 
> their terms), so it's not possible to open the original document from 
> which the values were extracted, because there is no original...

We store the paths to the documents in the index, partly for exactly 
this reason, partly to get an identifier for the documents. The thing I 
could see Luke doing would be guessing that a field contains a path or 
URL and then offering to give it to BrowserLauncher, which you use anyway.

Personally I'd like to see this feature, too. It would be interesting to 
analyse an index by looking at unusual terms and then being able to see 
the full document somewhere. But I think it is hard to generalize the 
approach and it might actually break for our indexes sooner or later 
since we are thinking about storing the location relative to the indexed 
directories -- which allows us to use one index with different file 
system mappings, e.g. to index a directory locally on a Linux box which 
is then used on a Windows client via SMB. If we go down this road the 
index wouldn't contain the complete information for opening files anymore.

Just my 2c,
   Peter


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


Re: TermVector again (Re: Luke v 0.2 - Lucene Index Browser)

Posted by Otis Gospodnetic <ot...@yahoo.com>.
--- Andrzej Bialecki <ab...@getopt.org> wrote:
> Andrzej Bialecki wrote:
> > Julien Nioche wrote:
> >  
> 
> >> [- and almost impossible : recompose the unstored fields of a
> document]
> > 
> > 
> > It's not impossible, just time-consuming - all information (except
> the 
> > parts removed by analyzer) is already there. This functionality has
> a 
> > high "cool-ness" factor, which makes it very tempting... :-)
> 
> I had a look at the current Lucene API, and I realized that this is a
> 
> very costly operation now. Now, if we had a TermVector support that
> was 
> mentioned several times on this list, things would be very
> different...
> 
> Does anyone know what is the status / plans regarding this?

As far as I know it is not on the to-do list of any of the more active
Lucene developers.  In other words, it is waiting for some external
contributor with more time and with required knowledge.

Code that worked with one of the 1.2 versions was posted to the list a
looong time ago by Dmitry.

Otis


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

TermVector again (Re: Luke v 0.2 - Lucene Index Browser)

Posted by Andrzej Bialecki <ab...@getopt.org>.
Andrzej Bialecki wrote:
> Julien Nioche wrote:
>  

>> [- and almost impossible : recompose the unstored fields of a document]
> 
> 
> It's not impossible, just time-consuming - all information (except the 
> parts removed by analyzer) is already there. This functionality has a 
> high "cool-ness" factor, which makes it very tempting... :-)

I had a look at the current Lucene API, and I realized that this is a 
very costly operation now. Now, if we had a TermVector support that was 
mentioned several times on this list, things would be very different...

Does anyone know what is the status / plans regarding this?

-- 
Best regards,
Andrzej Bialecki

-------------------------------------------------
Software Architect, System Integration Specialist
CEN/ISSS EC Workshop, ECIMF project chair
EU FP6 E-Commerce Expert/Evaluator
-------------------------------------------------
FreeBSD developer (http://www.freebsd.org)




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


TermVector again (Re: Luke v 0.2 - Lucene Index Browser)

Posted by Andrzej Bialecki <ab...@getopt.org>.
Andrzej Bialecki wrote:
> Julien Nioche wrote:
>  

>> [- and almost impossible : recompose the unstored fields of a document]
> 
> 
> It's not impossible, just time-consuming - all information (except the 
> parts removed by analyzer) is already there. This functionality has a 
> high "cool-ness" factor, which makes it very tempting... :-)

I had a look at the current Lucene API, and I realized that this is a 
very costly operation now. Now, if we had a TermVector support that was 
mentioned several times on this list, things would be very different...

Does anyone know what is the status / plans regarding this?

-- 
Best regards,
Andrzej Bialecki

-------------------------------------------------
Software Architect, System Integration Specialist
CEN/ISSS EC Workshop, ECIMF project chair
EU FP6 E-Commerce Expert/Evaluator
-------------------------------------------------
FreeBSD developer (http://www.freebsd.org)




Re: Luke v 0.2 - Lucene Index Browser

Posted by Julien Nioche <Ju...@lingway.com>.
Hello,

> > - Remove the empty field (see mailing list Lucene dev 4/16/2003 message
from
> > Otis)
>
> Well... I thought it was just reported as a bug. I don't see any
> responses to this, so I guess this is still a bug, and Luke is not the
> one to be fixed. :-)

Sure - I meant HIDE this field in the summary as a temporary solution
but it would be better to solve the problem in Lucene of course.


> > - Information about the # of segments
>
> Need to check this, but shouldn't be any problem. I'm not sure whether
> it's useful, though... ?

It 's an indication of whether or not an index has to be optimized.



----- Original Message -----
From: "Andrzej Bialecki" <ab...@getopt.org>
To: "Lucene Users List" <lu...@jakarta.apache.org>
Sent: Monday, August 11, 2003 7:55 PM
Subject: Re: Luke v 0.2 - Lucene Index Browser


> Julien Nioche wrote:
>
> > Hello,
> >
> > Thanks to Andrzej for this new version! Luke is really useful.
> >
>
> You're welcome. It was fun to code.
>
> >
> >>open the original Dokuments with the platform dependant mimetype viewer
>
> Someone else already explained the problems with this... What is a
> document in Lucene? It's a set of fields and their String values (or
> their terms), so it's not possible to open the original document from
> which the values were extracted, because there is no original...
>
> >
> > ???
> >
> > My suggestions by order of importance would be :
> >
> > - History of the 5 last indexes used : under the File Menu item ?
>
> No problem. I mean, technically it's no problem, it's just a problem of
> getting to it on my so called "free time" ...
>
> > - Remove the empty field (see mailing list Lucene dev 4/16/2003 message
from
> > Otis)
>
> Well... I thought it was just reported as a bug. I don't see any
> responses to this, so I guess this is still a bug, and Luke is not the
> one to be fixed. :-)
>
> > - Possibility to merge different indexes
>
> No problem.
>
> > - Information about the # of segments
>
> Need to check this, but shouldn't be any problem. I'm not sure whether
> it's useful, though... ?
>
> > [- and almost impossible : recompose the unstored fields of a document]
>
> It's not impossible, just time-consuming - all information (except the
> parts removed by analyzer) is already there. This functionality has a
> high "cool-ness" factor, which makes it very tempting... :-)
>
> Thanks for these suggestions! I can't promise any timeline, but
> eventually I'd like to include this functionality in Luke. Patches are
> always welcome... :-)
>
> --
> Best regards,
> Andrzej Bialecki
>
> -------------------------------------------------
> Software Architect, System Integration Specialist
> CEN/ISSS EC Workshop, ECIMF project chair
> EU FP6 E-Commerce Expert/Evaluator
> -------------------------------------------------
> FreeBSD developer (http://www.freebsd.org)
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>
>


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


Re: Luke v 0.2 - Lucene Index Browser

Posted by Peter Becker <pb...@dstc.edu.au>.
Andrzej Bialecki wrote:

[...Luke feature requests...]

>>
>>> open the original Dokuments with the platform dependant mimetype viewer
>>
>
> Someone else already explained the problems with this... What is a 
> document in Lucene? It's a set of fields and their String values (or 
> their terms), so it's not possible to open the original document from 
> which the values were extracted, because there is no original...

We store the paths to the documents in the index, partly for exactly 
this reason, partly to get an identifier for the documents. The thing I 
could see Luke doing would be guessing that a field contains a path or 
URL and then offering to give it to BrowserLauncher, which you use anyway.

Personally I'd like to see this feature, too. It would be interesting to 
analyse an index by looking at unusual terms and then being able to see 
the full document somewhere. But I think it is hard to generalize the 
approach and it might actually break for our indexes sooner or later 
since we are thinking about storing the location relative to the indexed 
directories -- which allows us to use one index with different file 
system mappings, e.g. to index a directory locally on a Linux box which 
is then used on a Windows client via SMB. If we go down this road the 
index wouldn't contain the complete information for opening files anymore.

Just my 2c,
   Peter


Re: Luke v 0.2 - Lucene Index Browser

Posted by Andrzej Bialecki <ab...@getopt.org>.
Julien Nioche wrote:

> Hello,
> 
> Thanks to Andrzej for this new version! Luke is really useful.
> 

You're welcome. It was fun to code.

> 
>>open the original Dokuments with the platform dependant mimetype viewer

Someone else already explained the problems with this... What is a 
document in Lucene? It's a set of fields and their String values (or 
their terms), so it's not possible to open the original document from 
which the values were extracted, because there is no original...

> 
> ???
> 
> My suggestions by order of importance would be :
> 
> - History of the 5 last indexes used : under the File Menu item ?

No problem. I mean, technically it's no problem, it's just a problem of 
getting to it on my so called "free time" ...

> - Remove the empty field (see mailing list Lucene dev 4/16/2003 message from
> Otis)

Well... I thought it was just reported as a bug. I don't see any 
responses to this, so I guess this is still a bug, and Luke is not the 
one to be fixed. :-)

> - Possibility to merge different indexes

No problem.

> - Information about the # of segments

Need to check this, but shouldn't be any problem. I'm not sure whether 
it's useful, though... ?

> [- and almost impossible : recompose the unstored fields of a document]

It's not impossible, just time-consuming - all information (except the 
parts removed by analyzer) is already there. This functionality has a 
high "cool-ness" factor, which makes it very tempting... :-)

Thanks for these suggestions! I can't promise any timeline, but 
eventually I'd like to include this functionality in Luke. Patches are 
always welcome... :-)

-- 
Best regards,
Andrzej Bialecki

-------------------------------------------------
Software Architect, System Integration Specialist
CEN/ISSS EC Workshop, ECIMF project chair
EU FP6 E-Commerce Expert/Evaluator
-------------------------------------------------
FreeBSD developer (http://www.freebsd.org)




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


Re: Luke v 0.2 - Lucene Index Browser

Posted by Andrzej Bialecki <ab...@getopt.org>.
Julien Nioche wrote:

> Hello,
> 
> Thanks to Andrzej for this new version! Luke is really useful.
> 

You're welcome. It was fun to code.

> 
>>open the original Dokuments with the platform dependant mimetype viewer

Someone else already explained the problems with this... What is a 
document in Lucene? It's a set of fields and their String values (or 
their terms), so it's not possible to open the original document from 
which the values were extracted, because there is no original...

> 
> ???
> 
> My suggestions by order of importance would be :
> 
> - History of the 5 last indexes used : under the File Menu item ?

No problem. I mean, technically it's no problem, it's just a problem of 
getting to it on my so called "free time" ...

> - Remove the empty field (see mailing list Lucene dev 4/16/2003 message from
> Otis)

Well... I thought it was just reported as a bug. I don't see any 
responses to this, so I guess this is still a bug, and Luke is not the 
one to be fixed. :-)

> - Possibility to merge different indexes

No problem.

> - Information about the # of segments

Need to check this, but shouldn't be any problem. I'm not sure whether 
it's useful, though... ?

> [- and almost impossible : recompose the unstored fields of a document]

It's not impossible, just time-consuming - all information (except the 
parts removed by analyzer) is already there. This functionality has a 
high "cool-ness" factor, which makes it very tempting... :-)

Thanks for these suggestions! I can't promise any timeline, but 
eventually I'd like to include this functionality in Luke. Patches are 
always welcome... :-)

-- 
Best regards,
Andrzej Bialecki

-------------------------------------------------
Software Architect, System Integration Specialist
CEN/ISSS EC Workshop, ECIMF project chair
EU FP6 E-Commerce Expert/Evaluator
-------------------------------------------------
FreeBSD developer (http://www.freebsd.org)




Re: Luke v 0.2 - Lucene Index Browser

Posted by Julien Nioche <Ju...@lingway.com>.
Hello,

Thanks to Andrzej for this new version! Luke is really useful.

> open the original Dokuments with the platform dependant mimetype viewer
???

My suggestions by order of importance would be :

- History of the 5 last indexes used : under the File Menu item ?
- Remove the empty field (see mailing list Lucene dev 4/16/2003 message from
Otis)
- Possibility to merge different indexes
- Information about the # of segments
[- and almost impossible : recompose the unstored fields of a document]

Best regards

Julien


----- Original Message -----
From: "Günter Kukies" <gu...@heuft.com>
To: "Lucene Users List" <lu...@jakarta.apache.org>
Sent: Monday, August 11, 2003 5:12 PM
Subject: Re: Luke v 0.2 - Lucene Index Browser


> Hi,
>
> nice Tool.
>
> Here some points for further developments:
> show the contents of a Reader-valued Field
> open the original Dokuments with the platform dependant mimetype viewer
>
> regards,
> Günter
>
>
> ----- Original Message -----
> From: "Andrzej Bialecki" <ab...@getopt.org>
> To: "Lucene Users List" <lu...@jakarta.apache.org>
> Cc: "Lucene Developers List" <lu...@jakarta.apache.org>
> Sent: Monday, August 11, 2003 1:10 PM
> Subject: Luke v 0.2 - Lucene Index Browser
>
>
> > Dear Lucene Users,
> >
> > I'm glad to announce that a new version of Luke is available for
> > download, and as a Java WebStart application.
> >
> > Luke is a diagnostic tool for Lucene (http://jakarta.apache.org/lucene)
> > indexes. It enables you to browse documents in existing indexes, perform
> > queries, navigate through terms, optimize indexes and more.
> >
> > Please go to http://www.getopt.org/luke and give it a try. You can
> > either use the Java WebStart version, or just download the JAR file with
> > binaries. Full source code is available, under Apache license.
> >
> > Changes in v0.2:
> >
> > * Add Java WebStart version.
> > * Add Read-Only mode.
> > * Fix spinbox bug (really a bug in the Thinlet toolkit - fixed there).
> > * Allow to browse hidden directories.
> > * Add a combobox to choose the default field for searching.
> > * Other minor code cleanups.
> >
> > Thanks to all who provided their comments and suggestions!
> >
> > --
> > Best regards,
> > Andrzej Bialecki
> >
> > -------------------------------------------------
> > Software Architect, System Integration Specialist
> > CEN/ISSS EC Workshop, ECIMF project chair
> > EU FP6 E-Commerce Expert/Evaluator
> > -------------------------------------------------
> > FreeBSD developer (http://www.freebsd.org)
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: lucene-user-help@jakarta.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>
>


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


Re: Luke v 0.2 - Lucene Index Browser

Posted by Julien Nioche <Ju...@lingway.com>.
Hello,

Thanks to Andrzej for this new version! Luke is really useful.

> open the original Dokuments with the platform dependant mimetype viewer
???

My suggestions by order of importance would be :

- History of the 5 last indexes used : under the File Menu item ?
- Remove the empty field (see mailing list Lucene dev 4/16/2003 message from
Otis)
- Possibility to merge different indexes
- Information about the # of segments
[- and almost impossible : recompose the unstored fields of a document]

Best regards

Julien


----- Original Message -----
From: "Günter Kukies" <gu...@heuft.com>
To: "Lucene Users List" <lu...@jakarta.apache.org>
Sent: Monday, August 11, 2003 5:12 PM
Subject: Re: Luke v 0.2 - Lucene Index Browser


> Hi,
>
> nice Tool.
>
> Here some points for further developments:
> show the contents of a Reader-valued Field
> open the original Dokuments with the platform dependant mimetype viewer
>
> regards,
> Günter
>
>
> ----- Original Message -----
> From: "Andrzej Bialecki" <ab...@getopt.org>
> To: "Lucene Users List" <lu...@jakarta.apache.org>
> Cc: "Lucene Developers List" <lu...@jakarta.apache.org>
> Sent: Monday, August 11, 2003 1:10 PM
> Subject: Luke v 0.2 - Lucene Index Browser
>
>
> > Dear Lucene Users,
> >
> > I'm glad to announce that a new version of Luke is available for
> > download, and as a Java WebStart application.
> >
> > Luke is a diagnostic tool for Lucene (http://jakarta.apache.org/lucene)
> > indexes. It enables you to browse documents in existing indexes, perform
> > queries, navigate through terms, optimize indexes and more.
> >
> > Please go to http://www.getopt.org/luke and give it a try. You can
> > either use the Java WebStart version, or just download the JAR file with
> > binaries. Full source code is available, under Apache license.
> >
> > Changes in v0.2:
> >
> > * Add Java WebStart version.
> > * Add Read-Only mode.
> > * Fix spinbox bug (really a bug in the Thinlet toolkit - fixed there).
> > * Allow to browse hidden directories.
> > * Add a combobox to choose the default field for searching.
> > * Other minor code cleanups.
> >
> > Thanks to all who provided their comments and suggestions!
> >
> > --
> > Best regards,
> > Andrzej Bialecki
> >
> > -------------------------------------------------
> > Software Architect, System Integration Specialist
> > CEN/ISSS EC Workshop, ECIMF project chair
> > EU FP6 E-Commerce Expert/Evaluator
> > -------------------------------------------------
> > FreeBSD developer (http://www.freebsd.org)
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: lucene-user-help@jakarta.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>
>


Re: How do you pronounce 'Lucene'?

Posted by "Kevin A. Burton" <bu...@newsmonster.org>.
Doug Cutting wrote:

> Loo-seen.
>
> Danny Sofer wrote:
>
>> ...and where does the name come from?
>
>
> It's my wife's middle name, and her maternal grandmother's first name.
>
At one point in time (before it became an Apache project) Jetspeed was 
named Christina but then we broke up so I named it Jetspeed (the amount 
of time it took for our relationship to end)

:)

Kevin

-- 
Help Support NewsMonster Development!  Purchase NewsMonster PRO!

    http://www.newsmonster.org/download-pro.html

Kevin A. Burton, Location - San Francisco, CA, Cell - 415.595.9965
       AIM - sfburtonator,  Web - http://www.peerfear.org/
GPG fingerprint: 4D20 40A0 C734 307E C7B4  DCAA 0303 3AC5 BD9D 7C4D
  IRC - freenode.net #infoanarchy | #p2p-hackers | #newsmonster



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


Re: How do you pronounce 'Lucene'?

Posted by "Kevin A. Burton" <bu...@newsmonster.org>.
Doug Cutting wrote:

> Loo-seen.
>
> Danny Sofer wrote:
>
>> ...and where does the name come from?
>
>
> It's my wife's middle name, and her maternal grandmother's first name.
>
At one point in time (before it became an Apache project) Jetspeed was 
named Christina but then we broke up so I named it Jetspeed (the amount 
of time it took for our relationship to end)

:)

Kevin

-- 
Help Support NewsMonster Development!  Purchase NewsMonster PRO!

    http://www.newsmonster.org/download-pro.html

Kevin A. Burton, Location - San Francisco, CA, Cell - 415.595.9965
       AIM - sfburtonator,  Web - http://www.peerfear.org/
GPG fingerprint: 4D20 40A0 C734 307E C7B4  DCAA 0303 3AC5 BD9D 7C4D
  IRC - freenode.net #infoanarchy | #p2p-hackers | #newsmonster



Re: How do you pronounce 'Lucene'?

Posted by Doug Cutting <cu...@lucene.com>.
Loo-seen.

Danny Sofer wrote:
> ...and where does the name come from?

It's my wife's middle name, and her maternal grandmother's first name.

Doug


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


Re: How do you pronounce 'Lucene'?

Posted by Doug Cutting <cu...@lucene.com>.
Loo-seen.

Danny Sofer wrote:
> ...and where does the name come from?

It's my wife's middle name, and her maternal grandmother's first name.

Doug


Re: How do you pronounce 'Lucene'?

Posted by Joseph Ottinger <jo...@enigmastation.com>.
I pronounce it "lieu'-seen" or "loo'-seen", usually the latter because I'm
lazy.

On Mon, 11 Aug 2003, Danny Sofer wrote:

> ...and where does the name come from?
>
> we've already developed three way to say 'lucene' and we can't agree on
> which one we like best.
>
> somebody please help!
>
> many thanks,
>
> danny.
> ===================================
> danny sofer   t. 020 7378 6655   m. 0795 722 1632
> www.kitsite.com - content management for websites
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>

-------------------------------------------------------------------
Joseph B. Ottinger                         http://enigmastation.com
IT Consultant                                joeo@enigmastation.com
J2EE Editor - Java Developer's Journal   josephottinger@sys-con.com


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


Re: How do you pronounce 'Lucene'?

Posted by Joseph Ottinger <jo...@enigmastation.com>.
I pronounce it "lieu'-seen" or "loo'-seen", usually the latter because I'm
lazy.

On Mon, 11 Aug 2003, Danny Sofer wrote:

> ...and where does the name come from?
>
> we've already developed three way to say 'lucene' and we can't agree on
> which one we like best.
>
> somebody please help!
>
> many thanks,
>
> danny.
> ===================================
> danny sofer   t. 020 7378 6655   m. 0795 722 1632
> www.kitsite.com - content management for websites
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>

-------------------------------------------------------------------
Joseph B. Ottinger                         http://enigmastation.com
IT Consultant                                joeo@enigmastation.com
J2EE Editor - Java Developer's Journal   josephottinger@sys-con.com


How do you pronounce 'Lucene'?

Posted by Danny Sofer <da...@kitsite.com>.
...and where does the name come from?

we've already developed three way to say 'lucene' and we can't agree on
which one we like best.

somebody please help!

many thanks,

danny.
===================================
danny sofer   t. 020 7378 6655   m. 0795 722 1632
www.kitsite.com - content management for websites


How do you pronounce 'Lucene'?

Posted by Danny Sofer <da...@kitsite.com>.
...and where does the name come from?

we've already developed three way to say 'lucene' and we can't agree on
which one we like best.

somebody please help!

many thanks,

danny.
===================================
danny sofer   t. 020 7378 6655   m. 0795 722 1632
www.kitsite.com - content management for websites


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


Re: Luke v 0.2 - Lucene Index Browser

Posted by Erik Hatcher <li...@ehatchersolutions.com>.
On Monday, August 11, 2003, at 11:12  AM, Günter Kukies wrote:
> Hi,
>
> nice Tool.
>
> Here some points for further developments:
> show the contents of a Reader-valued Field

But Reader-valued fields are not "stored" in the index 
(Field.Text(name, Reader), that is).  The only thing it could show is 
the terms from that field for each document.

	Erik


Re: Luke v 0.2 - Lucene Index Browser

Posted by Erik Hatcher <li...@ehatchersolutions.com>.
On Monday, August 11, 2003, at 11:12  AM, Günter Kukies wrote:
> Hi,
>
> nice Tool.
>
> Here some points for further developments:
> show the contents of a Reader-valued Field

But Reader-valued fields are not "stored" in the index 
(Field.Text(name, Reader), that is).  The only thing it could show is 
the terms from that field for each document.

	Erik


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


Re: Luke v 0.2 - Lucene Index Browser

Posted by Günter Kukies <gu...@heuft.com>.
Hi,

nice Tool.

Here some points for further developments:
show the contents of a Reader-valued Field
open the original Dokuments with the platform dependant mimetype viewer

regards,
Günter


----- Original Message -----
From: "Andrzej Bialecki" <ab...@getopt.org>
To: "Lucene Users List" <lu...@jakarta.apache.org>
Cc: "Lucene Developers List" <lu...@jakarta.apache.org>
Sent: Monday, August 11, 2003 1:10 PM
Subject: Luke v 0.2 - Lucene Index Browser


> Dear Lucene Users,
>
> I'm glad to announce that a new version of Luke is available for
> download, and as a Java WebStart application.
>
> Luke is a diagnostic tool for Lucene (http://jakarta.apache.org/lucene)
> indexes. It enables you to browse documents in existing indexes, perform
> queries, navigate through terms, optimize indexes and more.
>
> Please go to http://www.getopt.org/luke and give it a try. You can
> either use the Java WebStart version, or just download the JAR file with
> binaries. Full source code is available, under Apache license.
>
> Changes in v0.2:
>
> * Add Java WebStart version.
> * Add Read-Only mode.
> * Fix spinbox bug (really a bug in the Thinlet toolkit - fixed there).
> * Allow to browse hidden directories.
> * Add a combobox to choose the default field for searching.
> * Other minor code cleanups.
>
> Thanks to all who provided their comments and suggestions!
>
> --
> Best regards,
> Andrzej Bialecki
>
> -------------------------------------------------
> Software Architect, System Integration Specialist
> CEN/ISSS EC Workshop, ECIMF project chair
> EU FP6 E-Commerce Expert/Evaluator
> -------------------------------------------------
> FreeBSD developer (http://www.freebsd.org)
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>
>


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


Re: Luke v 0.2 - Lucene Index Browser

Posted by Günter Kukies <gu...@heuft.com>.
Hi,

nice Tool.

Here some points for further developments:
show the contents of a Reader-valued Field
open the original Dokuments with the platform dependant mimetype viewer

regards,
Günter


----- Original Message -----
From: "Andrzej Bialecki" <ab...@getopt.org>
To: "Lucene Users List" <lu...@jakarta.apache.org>
Cc: "Lucene Developers List" <lu...@jakarta.apache.org>
Sent: Monday, August 11, 2003 1:10 PM
Subject: Luke v 0.2 - Lucene Index Browser


> Dear Lucene Users,
>
> I'm glad to announce that a new version of Luke is available for
> download, and as a Java WebStart application.
>
> Luke is a diagnostic tool for Lucene (http://jakarta.apache.org/lucene)
> indexes. It enables you to browse documents in existing indexes, perform
> queries, navigate through terms, optimize indexes and more.
>
> Please go to http://www.getopt.org/luke and give it a try. You can
> either use the Java WebStart version, or just download the JAR file with
> binaries. Full source code is available, under Apache license.
>
> Changes in v0.2:
>
> * Add Java WebStart version.
> * Add Read-Only mode.
> * Fix spinbox bug (really a bug in the Thinlet toolkit - fixed there).
> * Allow to browse hidden directories.
> * Add a combobox to choose the default field for searching.
> * Other minor code cleanups.
>
> Thanks to all who provided their comments and suggestions!
>
> --
> Best regards,
> Andrzej Bialecki
>
> -------------------------------------------------
> Software Architect, System Integration Specialist
> CEN/ISSS EC Workshop, ECIMF project chair
> EU FP6 E-Commerce Expert/Evaluator
> -------------------------------------------------
> FreeBSD developer (http://www.freebsd.org)
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>
>