To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project lucene-java has an issue affecting its community integration.
This issue affects
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project lucene-java has an issue affecting its community integration.
This issue affects
[
https://issues.apache.org/jira/browse/LUCENE-958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512902
]
Nicolas Lalevée commented on LUCENE-958:
I had the same feeling as you Ion because we both generate the filte
On Jul 16, 2007, at 1:06 AM, Chris Hostetter wrote:
: Do we have a best practice for going from, say a SpanQuery doc/
: position information and retrieving the actual range of positions of
: content from the Document? Is it just to reanalyze the Document
: using the appropriate Analyzer and s
RegexCapabilities is not Serializable
-
Key: LUCENE-961
URL: https://issues.apache.org/jira/browse/LUCENE-961
Project: Lucene - Java
Issue Type: Bug
Components: QueryParser
Affects Versions:
[
https://issues.apache.org/jira/browse/LUCENE-959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved LUCENE-959.
-
Resolution: Fixed
committed.
> Document Vector->ArrayList
> --
>
>
See http://lucene.zones.apache.org:8080/hudson/job/Lucene-Nightly/153/changes
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Chris Hostetter wrote:
> i guess i'm not following how exactly your pivoted norm calculation works
> ... it sounds like you are still rewarding 1 term long fields more then
True.
> any other length ... is the distinction between your approach and the
> default implementation just that the defaul
[
https://issues.apache.org/jira/browse/LUCENE-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513103
]
Doron Cohen commented on LUCENE-850:
> The function query capability works for many situations, as you
> can sto
Can someone add this site to the list? The address is
www.worksheetworks.com. To see the Lucene link, do any kind of search
(e.g. "math") in the search field at the top, and at the bottom of the
results list it says "Powered by [lucene logo]" with the logo being a
hyperlink to the Apache Lucene
: Basically it is
: (1 - Slope) * Pivot + (Slope) * Doclen
: Where Pivot reflects on the average doc length, and
: Smaller Slope reduces the amount by which short docs
: are preferred over long ones. In collection with very
isn't that just a flat line with a slope relative to teh specified "Slo
> : I think both are not good enough for large dynamic collections.
> : Both are good enough for experiments. But it should be more
> : efficient in a working dynamic large system.
>
> Hmmm... perhaps what we need is a generalization of the pyaload API to
> allow storing/reading payloads on a per d
On Jul 16, 2007, at 9:24 PM, Chris Hostetter wrote:
Hmmm... perhaps what we need is a generalization of the pyaload API to
allow storing/reading payloads on a per document, per field, or per
index
basis ... along with some sort of "PayloadMerger" that could be
used by
InexWriter when merg
Chris Hostetter wrote:
> isn't that just a flat line with a slope relative to teh
> specified "Slope"
> ? your pivot just seems to affect the y-intercept (which would be the
> lengthNorm for field containing 0 terms) but doesn't that cancel out of
> any scoring equation since the fieldNorm is mul
14 matches
Mail list logo
