date:20111215

RE: Broken link in Lucene 3.5 JavaDoc?

2011-12-15 Thread Uwe Schindler

If you remove the useless CSS in the HTML it looks perfect in package.html!

-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de


> -Original Message-
> From: Shai Erera [mailto:ser...@gmail.com]
> Sent: Thursday, December 15, 2011 8:39 AM
> To: java-user@lucene.apache.org
> Subject: Re: Broken link in Lucene 3.5 JavaDoc?
> 
> If you access this URL:
> http://lucene.apache.org/java/3_5_0/api/contrib-facet/ then the link to the
> userguide points to the correct location.
> 
> I've tried to add it to package.html, but it doesn't look very good.
> 
> I will fix javadocs-all to copy the userguide to the correct location, as 
> facet-
> userguide.
> 
> Shai
> On Wed, Dec 14, 2011 at 3:21 PM, Robert Muir  wrote:
> 
> > Looks like a problem in the javadocs-all task that combines the core
> > and contribs.
> >
> > Maybe the build should inline the userguide directly into
> > package-summary.html so that you see it no matter how you get to the
> > o.a.l.facet package?
> >
> > On Wed, Dec 14, 2011 at 8:14 AM, Shai Erera  wrote:
> > > I will investigate it. In the meantime, this is the correct link:
> > > http://lucene.apache.org/java/3_5_0/api/contrib-facet/userguide.html
> > >
> > > Shai
> > >
> > > On Wed, Dec 14, 2011 at 3:08 PM, Lukáš Vlček 
> > wrote:
> > >
> > >> Hi,
> > >>
> > >> is there broken link in
> > >>
> > >>
> > http://lucene.apache.org/java/3_5_0/api/all/org/apache/lucene/facet/pa
> > ckage-summary.html
> > >>  ?
> > >> There is a link pointing to
> > >> http://lucene.apache.org/java/3_5_0/api/all/userguide.html
> > >> resulting
> > into
> > >> 404.
> > >>
> > >> Regards,
> > >> Lukas
> > >>
> >
> >
> >
> > --
> > lucidimagination.com
> >
> > -
> > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
> > For additional commands, e-mail: java-user-h...@lucene.apache.org
> >
> >


-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org

RE: Broken link in Lucene 3.5 JavaDoc?

2011-12-15 Thread Uwe Schindler

Alternatively in overview.html (which fits better).

There is only one limitation according to docs: The first sentence is copied 
over to the package description an if the first sentence is formatted as  
or whatever, it kills the whole Javascript formatting. So to make it perfect 
(and it looks really fine), leave an unformatted first sentence in the docs and 
then copy the plain HTML without CSS after it (removing the  from the 
first title)

Should I provide a patch?

Uwe

-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de


> -Original Message-
> From: Uwe Schindler [mailto:u...@thetaphi.de]
> Sent: Thursday, December 15, 2011 10:27 AM
> To: java-user@lucene.apache.org
> Subject: RE: Broken link in Lucene 3.5 JavaDoc?
> 
> If you remove the useless CSS in the HTML it looks perfect in package.html!
> 
> -
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: u...@thetaphi.de
> 
> 
> > -Original Message-
> > From: Shai Erera [mailto:ser...@gmail.com]
> > Sent: Thursday, December 15, 2011 8:39 AM
> > To: java-user@lucene.apache.org
> > Subject: Re: Broken link in Lucene 3.5 JavaDoc?
> >
> > If you access this URL:
> > http://lucene.apache.org/java/3_5_0/api/contrib-facet/ then the link
> > to the userguide points to the correct location.
> >
> > I've tried to add it to package.html, but it doesn't look very good.
> >
> > I will fix javadocs-all to copy the userguide to the correct location,
> > as facet- userguide.
> >
> > Shai
> > On Wed, Dec 14, 2011 at 3:21 PM, Robert Muir  wrote:
> >
> > > Looks like a problem in the javadocs-all task that combines the core
> > > and contribs.
> > >
> > > Maybe the build should inline the userguide directly into
> > > package-summary.html so that you see it no matter how you get to the
> > > o.a.l.facet package?
> > >
> > > On Wed, Dec 14, 2011 at 8:14 AM, Shai Erera  wrote:
> > > > I will investigate it. In the meantime, this is the correct link:
> > > > http://lucene.apache.org/java/3_5_0/api/contrib-facet/userguide.ht
> > > > ml
> > > >
> > > > Shai
> > > >
> > > > On Wed, Dec 14, 2011 at 3:08 PM, Lukáš Vlček
> > > > 
> > > wrote:
> > > >
> > > >> Hi,
> > > >>
> > > >> is there broken link in
> > > >>
> > > >>
> > > http://lucene.apache.org/java/3_5_0/api/all/org/apache/lucene/facet/
> > > pa
> > > ckage-summary.html
> > > >>  ?
> > > >> There is a link pointing to
> > > >> http://lucene.apache.org/java/3_5_0/api/all/userguide.html
> > > >> resulting
> > > into
> > > >> 404.
> > > >>
> > > >> Regards,
> > > >> Lukas
> > > >>
> > >
> > >
> > >
> > > --
> > > lucidimagination.com
> > >
> > > 
> > > - To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
> > > For additional commands, e-mail: java-user-h...@lucene.apache.org
> > >
> > >
> 
> 
> -
> To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
> For additional commands, e-mail: java-user-h...@lucene.apache.org


-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org

RE: Broken link in Lucene 3.5 JavaDoc?

2011-12-15 Thread Shai Erera

If you already did it, then a patch will be great. Perhaps we should open
an issue for other?

Shai
On Dec 15, 2011 11:44 AM, "Uwe Schindler"  wrote:

> Alternatively in overview.html (which fits better).
>
> There is only one limitation according to docs: The first sentence is
> copied over to the package description an if the first sentence is
> formatted as  or whatever, it kills the whole Javascript formatting. So
> to make it perfect (and it looks really fine), leave an unformatted first
> sentence in the docs and then copy the plain HTML without CSS after it
> (removing the  from the first title)
>
> Should I provide a patch?
>
> Uwe
>
> -
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: u...@thetaphi.de
>
>
> > -Original Message-
> > From: Uwe Schindler [mailto:u...@thetaphi.de]
> > Sent: Thursday, December 15, 2011 10:27 AM
> > To: java-user@lucene.apache.org
> > Subject: RE: Broken link in Lucene 3.5 JavaDoc?
> >
> > If you remove the useless CSS in the HTML it looks perfect in
> package.html!
> >
> > -
> > Uwe Schindler
> > H.-H.-Meier-Allee 63, D-28213 Bremen
> > http://www.thetaphi.de
> > eMail: u...@thetaphi.de
> >
> >
> > > -Original Message-
> > > From: Shai Erera [mailto:ser...@gmail.com]
> > > Sent: Thursday, December 15, 2011 8:39 AM
> > > To: java-user@lucene.apache.org
> > > Subject: Re: Broken link in Lucene 3.5 JavaDoc?
> > >
> > > If you access this URL:
> > > http://lucene.apache.org/java/3_5_0/api/contrib-facet/ then the link
> > > to the userguide points to the correct location.
> > >
> > > I've tried to add it to package.html, but it doesn't look very good.
> > >
> > > I will fix javadocs-all to copy the userguide to the correct location,
> > > as facet- userguide.
> > >
> > > Shai
> > > On Wed, Dec 14, 2011 at 3:21 PM, Robert Muir  wrote:
> > >
> > > > Looks like a problem in the javadocs-all task that combines the core
> > > > and contribs.
> > > >
> > > > Maybe the build should inline the userguide directly into
> > > > package-summary.html so that you see it no matter how you get to the
> > > > o.a.l.facet package?
> > > >
> > > > On Wed, Dec 14, 2011 at 8:14 AM, Shai Erera 
> wrote:
> > > > > I will investigate it. In the meantime, this is the correct link:
> > > > > http://lucene.apache.org/java/3_5_0/api/contrib-facet/userguide.ht
> > > > > ml
> > > > >
> > > > > Shai
> > > > >
> > > > > On Wed, Dec 14, 2011 at 3:08 PM, Lukáš Vlček
> > > > > 
> > > > wrote:
> > > > >
> > > > >> Hi,
> > > > >>
> > > > >> is there broken link in
> > > > >>
> > > > >>
> > > > http://lucene.apache.org/java/3_5_0/api/all/org/apache/lucene/facet/
> > > > pa
> > > > ckage-summary.html
> > > > >>  ?
> > > > >> There is a link pointing to
> > > > >> http://lucene.apache.org/java/3_5_0/api/all/userguide.html
> > > > >> resulting
> > > > into
> > > > >> 404.
> > > > >>
> > > > >> Regards,
> > > > >> Lukas
> > > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > lucidimagination.com
> > > >
> > > > 
> > > > - To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
> > > > For additional commands, e-mail: java-user-h...@lucene.apache.org
> > > >
> > > >
> >
> >
> > -
> > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
> > For additional commands, e-mail: java-user-h...@lucene.apache.org
>
>
> -
> To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
> For additional commands, e-mail: java-user-h...@lucene.apache.org
>
>

RE: Broken link in Lucene 3.5 JavaDoc?

2011-12-15 Thread Uwe Schindler

Yes, I could attach the patch there! Will you open it?

-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de

> -Original Message-
> From: Shai Erera [mailto:ser...@gmail.com]
> Sent: Thursday, December 15, 2011 1:47 PM
> To: java-user@lucene.apache.org
> Subject: RE: Broken link in Lucene 3.5 JavaDoc?
> 
> If you already did it, then a patch will be great. Perhaps we should open an
> issue for other?
> 
> Shai
> On Dec 15, 2011 11:44 AM, "Uwe Schindler"  wrote:
> 
> > Alternatively in overview.html (which fits better).
> >
> > There is only one limitation according to docs: The first sentence is
> > copied over to the package description an if the first sentence is
> > formatted as  or whatever, it kills the whole Javascript
> > formatting. So to make it perfect (and it looks really fine), leave an
> > unformatted first sentence in the docs and then copy the plain HTML
> > without CSS after it (removing the  from the first title)
> >
> > Should I provide a patch?
> >
> > Uwe
> >
> > -
> > Uwe Schindler
> > H.-H.-Meier-Allee 63, D-28213 Bremen
> > http://www.thetaphi.de
> > eMail: u...@thetaphi.de
> >
> >
> > > -Original Message-
> > > From: Uwe Schindler [mailto:u...@thetaphi.de]
> > > Sent: Thursday, December 15, 2011 10:27 AM
> > > To: java-user@lucene.apache.org
> > > Subject: RE: Broken link in Lucene 3.5 JavaDoc?
> > >
> > > If you remove the useless CSS in the HTML it looks perfect in
> > package.html!
> > >
> > > -
> > > Uwe Schindler
> > > H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de
> > > eMail: u...@thetaphi.de
> > >
> > >
> > > > -Original Message-
> > > > From: Shai Erera [mailto:ser...@gmail.com]
> > > > Sent: Thursday, December 15, 2011 8:39 AM
> > > > To: java-user@lucene.apache.org
> > > > Subject: Re: Broken link in Lucene 3.5 JavaDoc?
> > > >
> > > > If you access this URL:
> > > > http://lucene.apache.org/java/3_5_0/api/contrib-facet/ then the link
> > > > to the userguide points to the correct location.
> > > >
> > > > I've tried to add it to package.html, but it doesn't look very good.
> > > >
> > > > I will fix javadocs-all to copy the userguide to the correct location,
> > > > as facet- userguide.
> > > >
> > > > Shai
> > > > On Wed, Dec 14, 2011 at 3:21 PM, Robert Muir 
> wrote:
> > > >
> > > > > Looks like a problem in the javadocs-all task that combines the core
> > > > > and contribs.
> > > > >
> > > > > Maybe the build should inline the userguide directly into
> > > > > package-summary.html so that you see it no matter how you get to the
> > > > > o.a.l.facet package?
> > > > >
> > > > > On Wed, Dec 14, 2011 at 8:14 AM, Shai Erera 
> > wrote:
> > > > > > I will investigate it. In the meantime, this is the correct link:
> > > > > > http://lucene.apache.org/java/3_5_0/api/contrib-facet/userguide.ht
> > > > > > ml
> > > > > >
> > > > > > Shai
> > > > > >
> > > > > > On Wed, Dec 14, 2011 at 3:08 PM, Lukáš Vlček
> > > > > > 
> > > > > wrote:
> > > > > >
> > > > > >> Hi,
> > > > > >>
> > > > > >> is there broken link in
> > > > > >>
> > > > > >>
> > > > > http://lucene.apache.org/java/3_5_0/api/all/org/apache/lucene/facet/
> > > > > pa
> > > > > ckage-summary.html
> > > > > >>  ?
> > > > > >> There is a link pointing to
> > > > > >> http://lucene.apache.org/java/3_5_0/api/all/userguide.html
> > > > > >> resulting
> > > > > into
> > > > > >> 404.
> > > > > >>
> > > > > >> Regards,
> > > > > >> Lukas
> > > > > >>
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > lucidimagination.com
> > > > >
> > > > > 
> > > > > - To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
> > > > > For additional commands, e-mail: java-user-h...@lucene.apache.org
> > > > >
> > > > >
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
> > > For additional commands, e-mail: java-user-h...@lucene.apache.org
> >
> >
> > -
> > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
> > For additional commands, e-mail: java-user-h...@lucene.apache.org
> >
> >


-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org

RE: Broken link in Lucene 3.5 JavaDoc?

2011-12-15 Thread Shai Erera

... issue for *it*, not 'other' :)

Shai
On Dec 15, 2011 2:47 PM, "Shai Erera"  wrote:

> If you already did it, then a patch will be great. Perhaps we should open
> an issue for other?
>
> Shai
> On Dec 15, 2011 11:44 AM, "Uwe Schindler"  wrote:
>
>> Alternatively in overview.html (which fits better).
>>
>> There is only one limitation according to docs: The first sentence is
>> copied over to the package description an if the first sentence is
>> formatted as  or whatever, it kills the whole Javascript formatting. So
>> to make it perfect (and it looks really fine), leave an unformatted first
>> sentence in the docs and then copy the plain HTML without CSS after it
>> (removing the  from the first title)
>>
>> Should I provide a patch?
>>
>> Uwe
>>
>> -
>> Uwe Schindler
>> H.-H.-Meier-Allee 63, D-28213 Bremen
>> http://www.thetaphi.de
>> eMail: u...@thetaphi.de
>>
>>
>> > -Original Message-
>> > From: Uwe Schindler [mailto:u...@thetaphi.de]
>> > Sent: Thursday, December 15, 2011 10:27 AM
>> > To: java-user@lucene.apache.org
>> > Subject: RE: Broken link in Lucene 3.5 JavaDoc?
>> >
>> > If you remove the useless CSS in the HTML it looks perfect in
>> package.html!
>> >
>> > -
>> > Uwe Schindler
>> > H.-H.-Meier-Allee 63, D-28213 Bremen
>> > http://www.thetaphi.de
>> > eMail: u...@thetaphi.de
>> >
>> >
>> > > -Original Message-
>> > > From: Shai Erera [mailto:ser...@gmail.com]
>> > > Sent: Thursday, December 15, 2011 8:39 AM
>> > > To: java-user@lucene.apache.org
>> > > Subject: Re: Broken link in Lucene 3.5 JavaDoc?
>> > >
>> > > If you access this URL:
>> > > http://lucene.apache.org/java/3_5_0/api/contrib-facet/ then the link
>> > > to the userguide points to the correct location.
>> > >
>> > > I've tried to add it to package.html, but it doesn't look very good.
>> > >
>> > > I will fix javadocs-all to copy the userguide to the correct location,
>> > > as facet- userguide.
>> > >
>> > > Shai
>> > > On Wed, Dec 14, 2011 at 3:21 PM, Robert Muir 
>> wrote:
>> > >
>> > > > Looks like a problem in the javadocs-all task that combines the core
>> > > > and contribs.
>> > > >
>> > > > Maybe the build should inline the userguide directly into
>> > > > package-summary.html so that you see it no matter how you get to the
>> > > > o.a.l.facet package?
>> > > >
>> > > > On Wed, Dec 14, 2011 at 8:14 AM, Shai Erera 
>> wrote:
>> > > > > I will investigate it. In the meantime, this is the correct link:
>> > > > >
>> http://lucene.apache.org/java/3_5_0/api/contrib-facet/userguide.ht
>> > > > > ml
>> > > > >
>> > > > > Shai
>> > > > >
>> > > > > On Wed, Dec 14, 2011 at 3:08 PM, Lukáš Vlček
>> > > > > 
>> > > > wrote:
>> > > > >
>> > > > >> Hi,
>> > > > >>
>> > > > >> is there broken link in
>> > > > >>
>> > > > >>
>> > > >
>> http://lucene.apache.org/java/3_5_0/api/all/org/apache/lucene/facet/
>> > > > pa
>> > > > ckage-summary.html
>> > > > >>  ?
>> > > > >> There is a link pointing to
>> > > > >> http://lucene.apache.org/java/3_5_0/api/all/userguide.html
>> > > > >> resulting
>> > > > into
>> > > > >> 404.
>> > > > >>
>> > > > >> Regards,
>> > > > >> Lukas
>> > > > >>
>> > > >
>> > > >
>> > > >
>> > > > --
>> > > > lucidimagination.com
>> > > >
>> > > > 
>> > > > - To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
>> > > > For additional commands, e-mail: java-user-h...@lucene.apache.org
>> > > >
>> > > >
>> >
>> >
>> > -
>> > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
>> > For additional commands, e-mail: java-user-h...@lucene.apache.org
>>
>>
>> -
>> To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
>> For additional commands, e-mail: java-user-h...@lucene.apache.org
>>
>>

RE: Broken link in Lucene 3.5 JavaDoc?

2011-12-15 Thread Shai Erera

Sure, as soon as I'll be in front of a computer.

Shai
On Dec 15, 2011 2:48 PM, "Uwe Schindler"  wrote:

> Yes, I could attach the patch there! Will you open it?
>
> -
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: u...@thetaphi.de
>
> > -Original Message-
> > From: Shai Erera [mailto:ser...@gmail.com]
> > Sent: Thursday, December 15, 2011 1:47 PM
> > To: java-user@lucene.apache.org
> > Subject: RE: Broken link in Lucene 3.5 JavaDoc?
> >
> > If you already did it, then a patch will be great. Perhaps we should
> open an
> > issue for other?
> >
> > Shai
> > On Dec 15, 2011 11:44 AM, "Uwe Schindler"  wrote:
> >
> > > Alternatively in overview.html (which fits better).
> > >
> > > There is only one limitation according to docs: The first sentence is
> > > copied over to the package description an if the first sentence is
> > > formatted as  or whatever, it kills the whole Javascript
> > > formatting. So to make it perfect (and it looks really fine), leave an
> > > unformatted first sentence in the docs and then copy the plain HTML
> > > without CSS after it (removing the  from the first title)
> > >
> > > Should I provide a patch?
> > >
> > > Uwe
> > >
> > > -
> > > Uwe Schindler
> > > H.-H.-Meier-Allee 63, D-28213 Bremen
> > > http://www.thetaphi.de
> > > eMail: u...@thetaphi.de
> > >
> > >
> > > > -Original Message-
> > > > From: Uwe Schindler [mailto:u...@thetaphi.de]
> > > > Sent: Thursday, December 15, 2011 10:27 AM
> > > > To: java-user@lucene.apache.org
> > > > Subject: RE: Broken link in Lucene 3.5 JavaDoc?
> > > >
> > > > If you remove the useless CSS in the HTML it looks perfect in
> > > package.html!
> > > >
> > > > -
> > > > Uwe Schindler
> > > > H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de
> > > > eMail: u...@thetaphi.de
> > > >
> > > >
> > > > > -Original Message-
> > > > > From: Shai Erera [mailto:ser...@gmail.com]
> > > > > Sent: Thursday, December 15, 2011 8:39 AM
> > > > > To: java-user@lucene.apache.org
> > > > > Subject: Re: Broken link in Lucene 3.5 JavaDoc?
> > > > >
> > > > > If you access this URL:
> > > > > http://lucene.apache.org/java/3_5_0/api/contrib-facet/ then the
> link
> > > > > to the userguide points to the correct location.
> > > > >
> > > > > I've tried to add it to package.html, but it doesn't look very
> good.
> > > > >
> > > > > I will fix javadocs-all to copy the userguide to the correct
> location,
> > > > > as facet- userguide.
> > > > >
> > > > > Shai
> > > > > On Wed, Dec 14, 2011 at 3:21 PM, Robert Muir 
> > wrote:
> > > > >
> > > > > > Looks like a problem in the javadocs-all task that combines the
> core
> > > > > > and contribs.
> > > > > >
> > > > > > Maybe the build should inline the userguide directly into
> > > > > > package-summary.html so that you see it no matter how you get to
> the
> > > > > > o.a.l.facet package?
> > > > > >
> > > > > > On Wed, Dec 14, 2011 at 8:14 AM, Shai Erera 
> > > wrote:
> > > > > > > I will investigate it. In the meantime, this is the correct
> link:
> > > > > > >
> http://lucene.apache.org/java/3_5_0/api/contrib-facet/userguide.ht
> > > > > > > ml
> > > > > > >
> > > > > > > Shai
> > > > > > >
> > > > > > > On Wed, Dec 14, 2011 at 3:08 PM, Lukáš Vlček
> > > > > > > 
> > > > > > wrote:
> > > > > > >
> > > > > > >> Hi,
> > > > > > >>
> > > > > > >> is there broken link in
> > > > > > >>
> > > > > > >>
> > > > > >
> http://lucene.apache.org/java/3_5_0/api/all/org/apache/lucene/facet/
> > > > > > pa
> > > > > > ckage-summary.html
> > > > > > >>  ?
> > > > > > >> There is a link pointing to
> > > > > > >> http://lucene.apache.org/java/3_5_0/api/all/userguide.html
> > > > > > >> resulting
> > > > > > into
> > > > > > >> 404.
> > > > > > >>
> > > > > > >> Regards,
> > > > > > >> Lukas
> > > > > > >>
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > lucidimagination.com
> > > > > >
> > > > > >
> 
> > > > > > - To unsubscribe, e-mail:
> java-user-unsubscr...@lucene.apache.org
> > > > > > For additional commands, e-mail:
> java-user-h...@lucene.apache.org
> > > > > >
> > > > > >
> > > >
> > > >
> > > > -
> > > > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
> > > > For additional commands, e-mail: java-user-h...@lucene.apache.org
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
> > > For additional commands, e-mail: java-user-h...@lucene.apache.org
> > >
> > >
>
>
> -
> To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
> For additional commands, e-mail: java-user-h...@lucene.apache.org
>
>

Re: Broken link in Lucene 3.5 JavaDoc?

2011-12-15 Thread Shai Erera

I opened LUCENE-3649.

Shai

On Thu, Dec 15, 2011 at 2:50 PM, Shai Erera  wrote:

> Sure, as soon as I'll be in front of a computer.
>
> Shai
> On Dec 15, 2011 2:48 PM, "Uwe Schindler"  wrote:
>
>> Yes, I could attach the patch there! Will you open it?
>>
>> -
>> Uwe Schindler
>> H.-H.-Meier-Allee 63, D-28213 Bremen
>> http://www.thetaphi.de
>> eMail: u...@thetaphi.de
>>
>> > -Original Message-
>> > From: Shai Erera [mailto:ser...@gmail.com]
>> > Sent: Thursday, December 15, 2011 1:47 PM
>> > To: java-user@lucene.apache.org
>> > Subject: RE: Broken link in Lucene 3.5 JavaDoc?
>> >
>> > If you already did it, then a patch will be great. Perhaps we should
>> open an
>> > issue for other?
>> >
>> > Shai
>> > On Dec 15, 2011 11:44 AM, "Uwe Schindler"  wrote:
>> >
>> > > Alternatively in overview.html (which fits better).
>> > >
>> > > There is only one limitation according to docs: The first sentence is
>> > > copied over to the package description an if the first sentence is
>> > > formatted as  or whatever, it kills the whole Javascript
>> > > formatting. So to make it perfect (and it looks really fine), leave an
>> > > unformatted first sentence in the docs and then copy the plain HTML
>> > > without CSS after it (removing the  from the first title)
>> > >
>> > > Should I provide a patch?
>> > >
>> > > Uwe
>> > >
>> > > -
>> > > Uwe Schindler
>> > > H.-H.-Meier-Allee 63, D-28213 Bremen
>> > > http://www.thetaphi.de
>> > > eMail: u...@thetaphi.de
>> > >
>> > >
>> > > > -Original Message-
>> > > > From: Uwe Schindler [mailto:u...@thetaphi.de]
>> > > > Sent: Thursday, December 15, 2011 10:27 AM
>> > > > To: java-user@lucene.apache.org
>> > > > Subject: RE: Broken link in Lucene 3.5 JavaDoc?
>> > > >
>> > > > If you remove the useless CSS in the HTML it looks perfect in
>> > > package.html!
>> > > >
>> > > > -
>> > > > Uwe Schindler
>> > > > H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de
>> > > > eMail: u...@thetaphi.de
>> > > >
>> > > >
>> > > > > -Original Message-
>> > > > > From: Shai Erera [mailto:ser...@gmail.com]
>> > > > > Sent: Thursday, December 15, 2011 8:39 AM
>> > > > > To: java-user@lucene.apache.org
>> > > > > Subject: Re: Broken link in Lucene 3.5 JavaDoc?
>> > > > >
>> > > > > If you access this URL:
>> > > > > http://lucene.apache.org/java/3_5_0/api/contrib-facet/ then the
>> link
>> > > > > to the userguide points to the correct location.
>> > > > >
>> > > > > I've tried to add it to package.html, but it doesn't look very
>> good.
>> > > > >
>> > > > > I will fix javadocs-all to copy the userguide to the correct
>> location,
>> > > > > as facet- userguide.
>> > > > >
>> > > > > Shai
>> > > > > On Wed, Dec 14, 2011 at 3:21 PM, Robert Muir 
>> > wrote:
>> > > > >
>> > > > > > Looks like a problem in the javadocs-all task that combines the
>> core
>> > > > > > and contribs.
>> > > > > >
>> > > > > > Maybe the build should inline the userguide directly into
>> > > > > > package-summary.html so that you see it no matter how you get
>> to the
>> > > > > > o.a.l.facet package?
>> > > > > >
>> > > > > > On Wed, Dec 14, 2011 at 8:14 AM, Shai Erera 
>> > > wrote:
>> > > > > > > I will investigate it. In the meantime, this is the correct
>> link:
>> > > > > > >
>> http://lucene.apache.org/java/3_5_0/api/contrib-facet/userguide.ht
>> > > > > > > ml
>> > > > > > >
>> > > > > > > Shai
>> > > > > > >
>> > > > > > > On Wed, Dec 14, 2011 at 3:08 PM, Lukáš Vlček
>> > > > > > > 
>> > > > > > wrote:
>> > > > > > >
>> > > > > > >> Hi,
>> > > > > > >>
>> > > > > > >> is there broken link in
>> > > > > > >>
>> > > > > > >>
>> > > > > >
>> http://lucene.apache.org/java/3_5_0/api/all/org/apache/lucene/facet/
>> > > > > > pa
>> > > > > > ckage-summary.html
>> > > > > > >>  ?
>> > > > > > >> There is a link pointing to
>> > > > > > >> http://lucene.apache.org/java/3_5_0/api/all/userguide.html
>> > > > > > >> resulting
>> > > > > > into
>> > > > > > >> 404.
>> > > > > > >>
>> > > > > > >> Regards,
>> > > > > > >> Lukas
>> > > > > > >>
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > --
>> > > > > > lucidimagination.com
>> > > > > >
>> > > > > >
>> 
>> > > > > > - To unsubscribe, e-mail:
>> java-user-unsubscr...@lucene.apache.org
>> > > > > > For additional commands, e-mail:
>> java-user-h...@lucene.apache.org
>> > > > > >
>> > > > > >
>> > > >
>> > > >
>> > > >
>> -
>> > > > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
>> > > > For additional commands, e-mail: java-user-h...@lucene.apache.org
>> > >
>> > >
>> > > -
>> > > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
>> > > For additional commands, e-mail: java-user-h...@lucene.apache.org
>> > >
>> > >
>>
>>
>> -
>>

Trying to generate a list of DISTINCT field names from all documents in an index

2011-12-15 Thread todd.hunt

Hi,
 
I have come across a problem with our code that is not scaling well and I'm
hoping there is a way I can tweak our existing code to run faster.
 
We are indexing on a Java object called "Node".  A "Node" can have one or
more "Attributes".  The "Attributes" consist of a key / value pair and the
index value of the Node they are associated with.  The Attributes are
basically meta data about the Node.  We are using a FieldBridge to add the
Attribute keys and values to the Node "document" in Lucene.
 
Our current logic uses a Collector to find all of the "Attributes"
associated with a Node document and put them into a Set.  That Set then is
returned to the UI so that the user can have a drop down list of choices to
search on.
 
Here is part of the Collector code:
 
searcher.search(query, new Collector() {
private int docBase;
 
@Override
public void setScorer(Scorer scorer) throws IOException
{
//No Op
}
 
@Override
public void collect(int docId) {
int doc = docId + docBase;
try {
Document document = searcher.doc(doc);
List fieldList = document.getFields();
for (Object fieldObj : fieldList) {
if (fieldObj instanceof Fieldable) {
Fieldable field = (Fieldable) fieldObj;
String fieldName = field.name();
if
(!excludedFieldNameSet.contains(fieldName)) {
results.add(fieldName);
}
}
}
} catch (IOException e) {
throw JavaUtils.asRuntimeException(e);
}
}
 
@Override
public void setNextReader(IndexReader indexReader, int
docBase) throws IOException {
this.docBase = docBase;
}
 
@Override
public boolean acceptsDocsOutOfOrder() {
return true;
}
});
} catch (IOException e) {
throw JavaUtils.asRuntimeException(e);
}
}

This logic was very fast with our customers who had ten's of thousands of
Nodes with 2 or more Attributes per node.  But now we have a customer with
over a million nodes and at least 5 attributes per node.  So it is taking 10
to 20 seconds to generate this list, which is way too slow.
 
My "Plan B" is to cache the list of unique attribute fields either in
another Lucene index, EHCache, or in memory on the server.
 
The reason we started down this path is because the attributes that can be
added to a node are dynamic.  So initially, going through all the documents
looking for unique attributes seemed like a good solution.  
 
I've read through the Lucene In Action book and various postings online. 
Maybe I'm not looking for the correct terms, but I can't find anything that
will return and cache a list of unique field names.  If anyone can help
point me towards a better solution, please let me know.  Like I stated
before, I'd like to be able to keep most of what we have now, but if I need
to scrap this code and do something different, I'm all for it.  I'd even
change the way our Node document is stored in Lucene if that would make a
difference.
 
Thank you,
 
Todd

--
View this message in context: 
http://lucene.472066.n3.nabble.com/Trying-to-generate-a-list-of-DISTINCT-field-names-from-all-documents-in-an-index-tp3588729p3588729.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org

NGramTokenFilter filters out small tokens?

2011-12-15 Thread Rob Hasselbaum

Hi. I'm trying to configure an analyzer to be somewhat forgiving of
spelling mistakes in longer words of a search query. So, for example, if a
word in the query matches at least five characters of an indexed word
(token), I want that to be a hit. NGramTokenFilter with a minimum gram size
of 5 seems perfect for this. However, I just discovered that any tokens
less than 5 characters are being completely filtered out. So queries
containing words of < 5 characters are not matching anything at all. At
first I thought this was a bug, but then I found LUCENE-1491, which
indicates this is actually the intended behavior. Hmmm... How then should I
configure my analyzer to support exact matches on words <= 5 characters and
partial matches on words > 5? I guess I could develop my own token filter
based on NGramTokenFilter, but my requirements seem so basic that I'm
probably missing a simpler answer, Any help greatly appreciated!

Obtaining IDF values for the terms in a document set

2011-12-15 Thread Mike O'Leary

We have a large set of documents that we would like to index with a customized 
stopword list. We have run tests by indexing a random set of about 10% of the 
documents, and we'd like to generate a list of the terms in that smaller set 
and their IDF values as a way to create a starter set of stopwords for the 
larger document set by selecting the terms that have the lowest IDF values. 
First of all, is this the best way to create a stopword list? Second, is there 
a straightforward way to generate a list of terms and their IDF values from a 
Lucene index?
Thanks,
Mike

Re: Obtaining IDF values for the terms in a document set

2011-12-15 Thread Simon Willnauer

On Thu, Dec 15, 2011 at 6:33 PM, Mike O'Leary  wrote:
> We have a large set of documents that we would like to index with a 
> customized stopword list. We have run tests by indexing a random set of about 
> 10% of the documents, and we'd like to generate a list of the terms in that 
> smaller set and their IDF values as a way to create a starter set of 
> stopwords for the larger document set by selecting the terms that have the 
> lowest IDF values. First of all, is this the best way to create a stopword 
> list? Second, is there a straightforward way to generate a list of terms and 
> their IDF values from a Lucene index?
> Thanks,
> Mike

hey mike,

I can certainly help you with generating the list of your top N terms,
if that is the best or right way to generate the stopwords list I am
not sure but maybe somebody else will step up.

to get the top N terms out of your index you can simply iterate the
terms in a field and put the top N terms based on the docFreq() on a
heap. something like this:

 static class TermAndDF {
   String term;
   int df;
 }
 int queueSize = N;
 PriorityQueue queue = ...

 final TermEnum termEnum = reader.terms(new Term(field));
  try {
do {
  final Term term = termEnum.term();
  if (term == null || term.field() != field) break;
  int docFreq = termEnum.docFreq();
  if (queue.size() < queueSize) {
 queue.add(new TermAndDF(term.text(), docFreq);
  } else if (queue.top().df < docFreq) {
 TermAndFreq tnFrq = queue.top();
 tnFrq.term = term.text();
 tnFrq.df = docFreq;
  }
} while (termEnum.next());
  } finally {
termEnum.close();
  }

another way of doing it is to use index pruning and drop terms with
docFreq above a threshold after you have indexed your doc set.

simon

-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org

RE: Obtaining IDF values for the terms in a document set

2011-12-15 Thread Mike O'Leary

Hi Simon,
I guess in a sense we are interested in obtaining a list of the top N terms, 
but they would be the top terms in the sense that they have the lowest IDF 
values. These would be the terms that appear in all or almost all documents in 
the document set. This is not a count of the number of term occurrences in 
documents, it is a count of documents that contain at least one occurrence of a 
given term. Lucene must be storing IDF values for the terms of a document set 
somewhere in order to compute TF/IDF values when searching. I am wondering if 
there is an easy way to iterate through all of the terms that occur in the 
document set and obtain their IDF values.
Thanks,
Mike

-Original Message-
From: Simon Willnauer [mailto:simon.willna...@googlemail.com] 
Sent: Thursday, December 15, 2011 11:44 AM
To: java-user@lucene.apache.org
Subject: Re: Obtaining IDF values for the terms in a document set

On Thu, Dec 15, 2011 at 6:33 PM, Mike O'Leary  wrote:
> We have a large set of documents that we would like to index with a 
> customized stopword list. We have run tests by indexing a random set of about 
> 10% of the documents, and we'd like to generate a list of the terms in that 
> smaller set and their IDF values as a way to create a starter set of 
> stopwords for the larger document set by selecting the terms that have the 
> lowest IDF values. First of all, is this the best way to create a stopword 
> list? Second, is there a straightforward way to generate a list of terms and 
> their IDF values from a Lucene index?
> Thanks,
> Mike

hey mike,

I can certainly help you with generating the list of your top N terms, if that 
is the best or right way to generate the stopwords list I am not sure but maybe 
somebody else will step up.

to get the top N terms out of your index you can simply iterate the terms in a 
field and put the top N terms based on the docFreq() on a heap. something like 
this:

 static class TermAndDF {
   String term;
   int df;
 }
 int queueSize = N;
 PriorityQueue queue = ...

 final TermEnum termEnum = reader.terms(new Term(field));
  try {
do {
  final Term term = termEnum.term();
  if (term == null || term.field() != field) break;
  int docFreq = termEnum.docFreq();
  if (queue.size() < queueSize) {
 queue.add(new TermAndDF(term.text(), docFreq);
  } else if (queue.top().df < docFreq) {
 TermAndFreq tnFrq = queue.top();
 tnFrq.term = term.text();
 tnFrq.df = docFreq;
  }
} while (termEnum.next());
  } finally {
termEnum.close();
  }

another way of doing it is to use index pruning and drop terms with docFreq 
above a threshold after you have indexed your doc set.

simon

-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org

RE: Obtaining IDF values for the terms in a document set

2011-12-15 Thread Burton-West, Tom

Hi Mike,

If you just need the IDF you can run HighFreqTerm.java in contrib against 
either your sample index or your index to get the N terms with the highest DF 
values (i.e. lowest IDF.) If you have a large index, giving it lots of memory 
seems to help.

Depending on your use case, you may instead want to run it with the "-t" flag 
which will get the terms with the highest total occurrences (total tf), which 
is a good measure of the size of the positions list for those terms.  The size 
of the positions list only matters if you allow phrase or proximity queries.

See:
http://svn.apache.org/viewvc/lucene/dev/branches/branch_3x/lucene/contrib/misc/src/java/org/apache/lucene/misc/HighFreqTerms.java?view=markup

Regarding the positions list and slow phrase queries see:
http://www.hathitrust.org/blogs/large-scale-search/tuning-search-performance
http://www.hathitrust.org/blogs/large-scale-search/slow-queries-and-common-words-part-2

You can also look at the standard stop word sets at
http://snowball.tartarus.org/  (look under the entries for each stemmer)
or http://search.cpan.org/~creamyg/Lingua-StopWords-0.09/
or http://members.unine.ch/jacques.savoy/clef/index.html

Tom Burton-West
http://www.hathitrust.org/blogs/large-scale-search

-Original Message-
From: Mike O'Leary [mailto:tmole...@uw.edu] 
Sent: Thursday, December 15, 2011 12:34 PM
To: java-user@lucene.apache.org
Subject: Obtaining IDF values for the terms in a document set

We have a large set of documents that we would like to index with a customized 
stopword list. We have run tests by indexing a random set of about 10% of the 
documents, and we'd like to generate a list of the terms in that smaller set 
and their IDF values as a way to create a starter set of stopwords for the 
larger document set by selecting the terms that have the lowest IDF values. 
First of all, is this the best way to create a stopword list? Second, is there 
a straightforward way to generate a list of terms and their IDF values from a 
Lucene index?
Thanks,
Mike

-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org

Re: Trying to generate a list of DISTINCT field names from all documents in an index

2011-12-15 Thread todd.hunt

Thank you, Trejkaz.

I was just about to post the fact that I /finally/ found that method by
looking at the source code for LUKE.

There is a night and day difference in performance.

--
View this message in context: 
http://lucene.472066.n3.nabble.com/Trying-to-generate-a-list-of-DISTINCT-field-names-from-all-documents-in-an-index-tp3588729p3589959.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org

Using Lucene to match document sets to each other

2011-12-15 Thread Josh Stone

I have a use case for which I'm trying to figure out the best way to use
Lucene and could use some guidance.

I have a set of documents representing products in a catalog (name,
description, etc.). I then pull down data from different sources such as
Ebay and Amazon and need to determine if the items retrieved from those
sources match any of the products in the catalog. So I'm essentially
attempting to take many items and many products and determine where I have
matches.

I'm not sure the best way to go about this, but one questionable approach
is to index the items as I pull them in (to RAM) and do one search for
every product in my catalog, looking for matching names or descriptions.
This means an almost exponential number of queries though. Is there a
better approach? Any help is appreciated.

Thanks,
Josh

RE: Broken link in Lucene 3.5 JavaDoc?

RE: Broken link in Lucene 3.5 JavaDoc?

RE: Broken link in Lucene 3.5 JavaDoc?

RE: Broken link in Lucene 3.5 JavaDoc?

RE: Broken link in Lucene 3.5 JavaDoc?

RE: Broken link in Lucene 3.5 JavaDoc?

Re: Broken link in Lucene 3.5 JavaDoc?

Trying to generate a list of DISTINCT field names from all documents in an index

NGramTokenFilter filters out small tokens?

Obtaining IDF values for the terms in a document set

Re: Obtaining IDF values for the terms in a document set

RE: Obtaining IDF values for the terms in a document set

RE: Obtaining IDF values for the terms in a document set

Re: Trying to generate a list of DISTINCT field names from all documents in an index

Using Lucene to match document sets to each other

15 matches

Site Navigation

Mail list logo

Footer information