[
https://issues.apache.org/jira/browse/LUCENE-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754615#action_12754615
]
Mark Miller commented on LUCENE-1908:
-
bq. In that work we got best results from Lucen
[
https://issues.apache.org/jira/browse/LUCENE-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754610#action_12754610
]
Doron Cohen commented on LUCENE-1908:
-
{quote}
I'm still a little confused I guess
{q
[
https://issues.apache.org/jira/browse/LUCENE-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doron Cohen updated LUCENE-1908:
Attachment: LUCENE-1908.patch
Attached fixes according to comments by Shai and Mark:
* spell/typos
[
https://issues.apache.org/jira/browse/LUCENE-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754577#action_12754577
]
Mark Miller edited comment on LUCENE-1908 at 9/12/09 12:12 PM:
-
[
https://issues.apache.org/jira/browse/LUCENE-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754577#action_12754577
]
Mark Miller commented on LUCENE-1908:
-
bq. Is it really better? It seems to "punish" t
So to modify the rules a bit to account for the ordered case (again, I
am sure of nothing):
1. Only one span can start from a term.
2. Start matching from the left and work right.
3. If the Span is ordered, upon finding a match, shrink the
start position to the same term closest to the end term
[
https://issues.apache.org/jira/browse/LUCENE-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754571#action_12754571
]
Doron Cohen commented on LUCENE-1908:
-
Mark and Shai Thanks for reviewing!
Mark, I th
[
https://issues.apache.org/jira/browse/LUCENE-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1458:
---
Attachment: LUCENE-1458-back-compat.patch
LUCENE-1458.tar.bz2
Attach
Paul Elschot wrote:
> On Saturday 12 September 2009 14:40:28 Mark Miller wrote:
> > Michael McCandless wrote:
> > > OK thanks for the responses. This is indeed tricky stuff!
> > >
> > > On Sat, Sep 12, 2009 at 12:28 AM, Mark Miller
> wrote:
> > >
> > >
> > >> They start at the left and march right
On Saturday 12 September 2009 14:40:28 Mark Miller wrote:
> Michael McCandless wrote:
> > OK thanks for the responses. This is indeed tricky stuff!
> >
> > On Sat, Sep 12, 2009 at 12:28 AM, Mark Miller wrote:
> >
> >
> >> They start at the left and march right - each Span always starting
> >>
On Sat, Sep 12, 2009 at 8:40 AM, Mark Miller wrote:
>>> They start at the left and march right - each Span always starting
>>> after the last started,
>>
>> That's not quite always true -- eg I got span 1-8, twice, once I
>> added "b" as a clause to the SNQ.
>
> Mmm - right - depends on how you l
[
https://issues.apache.org/jira/browse/LUCENE-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated LUCENE-1897:
Fix Version/s: (was: 2.9)
we will likely just close this, but for now I'm just taking off 2.9
Mark Miller wrote:
>
>> Yeah I think you do, except each payload is only returned once. So
>> it's only the first span that hits a payload that will return it.
>>
>> So it sounds like SNQ just isn't guaranteed to be exhaustive in how it
>> enumerates the spans, eg I'll never see that 2nd occurrenc
Sorry for the spam - type of '8' instead of 'a' - hard enough to follow
without that - read this one below instead:
Mark Miller wrote:
> Mark Miller wrote:
>
>>> Yeah I think you do, except each payload is only returned once. So
>>> it's only the first span that hits a payload that will return
In other words, Spans is guaranteed to find a document *if* a set of
terms match the positional constraints - if bush is within 20 of george,
its guaranteed to find that - but it doesn't give any concern to finding
every george within 20 of bush (though it may find multiple, or even
all of them dep
Michael McCandless wrote:
> OK thanks for the responses. This is indeed tricky stuff!
>
> On Sat, Sep 12, 2009 at 12:28 AM, Mark Miller wrote:
>
>
>> They start at the left and march right - each Span always starting
>> after the last started,
>>
>
> That's not quite always true -- eg I g
Make IndexReader.DEFAULT_TERMS_INDEX_DIVISOR public
---
Key: LUCENE-1909
URL: https://issues.apache.org/jira/browse/LUCENE-1909
Project: Lucene - Java
Issue Type: Improvement
Report
On Sep 12, 2009, at 5:12 AM, Michael McCandless wrote:
OK thanks for the responses. This is indeed tricky stuff!
On Sat, Sep 12, 2009 at 12:28 AM, Mark Miller
wrote:
They start at the left and march right - each Span always starting
after the last started,
That's not quite always true
OK thanks for the responses. This is indeed tricky stuff!
On Sat, Sep 12, 2009 at 12:28 AM, Mark Miller wrote:
> They start at the left and march right - each Span always starting
> after the last started,
That's not quite always true -- eg I got span 1-8, twice, once I added
"b" as a clause t
> On Fri, Sep 11, 2009 at 4:45 PM, Uwe Schindler wrote:
> > By the way: This is documented:
> > http://hudson.zones.apache.org/hudson/job/Lucene-
> trunk/javadoc/core/org/apac
> > he/lucene/document/NumericField.html
> >
> > NOTE: This class is only used during indexing. When retrieving the
> stor
20 matches
Mail list logo
