[
https://issues.apache.org/jira/browse/LUCENE-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated LUCENE-1791:
-
Attachment: LUCENE-1791.patch
I figured out the problem with TestComplexExplanations ... the test uses a
Michael McCandless wrote:
I think eventually span queries should be absorbed into the normal
lucene queries. EG, if TermQuery creates a scorer that's able to
optionally enumerate matching spans, such that there's no performance
loss if you don't actuallly request the spans, then we don't need
Sp
[
https://issues.apache.org/jira/browse/LUCENE-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742683#action_12742683
]
Michael Busch commented on LUCENE-1801:
---
Patch looks good, Uwe!
When I change Token
[
https://issues.apache.org/jira/browse/LUCENE-1794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-1794:
Attachment: LUCENE-1794.patch
add reusable/reset impls for shingles, snowball, and memory/synonym.
[
https://issues.apache.org/jira/browse/LUCENE-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742649#action_12742649
]
Yonik Seeley commented on LUCENE-1801:
--
bq. As they are the source of tokens, they mu
[
https://issues.apache.org/jira/browse/LUCENE-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742644#action_12742644
]
Uwe Schindler commented on LUCENE-1796:
---
I opened LUCENE-1801 for that. A patch is a
[
https://issues.apache.org/jira/browse/LUCENE-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742646#action_12742646
]
Robert Muir commented on LUCENE-1801:
-
Uwe, get some rest.
I will double-check later
[
https://issues.apache.org/jira/browse/LUCENE-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-1801:
--
Attachment: (was: LUCENE-1801.patch)
> Tokenizers (which are the source of Tokens) should
[
https://issues.apache.org/jira/browse/LUCENE-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742643#action_12742643
]
Uwe Schindler commented on LUCENE-1801:
---
No problem, thanks for the patch. I was not
[
https://issues.apache.org/jira/browse/LUCENE-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-1801:
Attachment: LUCENE-1801.patch
sorry for the bad encoding issue!
> Tokenizers (which are the sourc
[
https://issues.apache.org/jira/browse/LUCENE-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742638#action_12742638
]
Robert Muir commented on LUCENE-1801:
-
uwe, sorry I see there is an encoding problem w
[
https://issues.apache.org/jira/browse/LUCENE-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-1801:
Attachment: LUCENE-1801.patch
with clearAttributes for the secret and super-secret tokenizer insid
[
https://issues.apache.org/jira/browse/LUCENE-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742634#action_12742634
]
Mark Miller commented on LUCENE-1791:
-
I only get the NAN issue showing up now.
I do
[
https://issues.apache.org/jira/browse/LUCENE-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742626#action_12742626
]
Robert Muir commented on LUCENE-1801:
-
Uwe, I can supply updated patch to yours if you
[
https://issues.apache.org/jira/browse/LUCENE-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742620#action_12742620
]
Uwe Schindler commented on LUCENE-1801:
---
Thanks Robert!
Can you look into this spec
[
https://issues.apache.org/jira/browse/LUCENE-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742618#action_12742618
]
Michael Busch commented on LUCENE-1801:
---
Sorry, Uwe. I'm in meetings.
I'll look int
[
https://issues.apache.org/jira/browse/LUCENE-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742616#action_12742616
]
Robert Muir commented on LUCENE-1801:
-
Uwe, there is also a tokenizer in contrib/memor
[
https://issues.apache.org/jira/browse/LUCENE-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742614#action_12742614
]
Hoss Man commented on LUCENE-1791:
--
FYI: with mark's updated path, we're back to just the
[
https://issues.apache.org/jira/browse/LUCENE-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-1801:
--
Attachment: LUCENE-1801.patch
Attached is a patch that implements clearAttributes() in all Tok
[
https://issues.apache.org/jira/browse/LUCENE-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742608#action_12742608
]
Mark Miller commented on LUCENE-1791:
-
Okay - so the first the original Parser issue:
[
https://issues.apache.org/jira/browse/LUCENE-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742606#action_12742606
]
Hoss Man commented on LUCENE-1791:
--
midair collision (x2) ... i think i see what you mean
[
https://issues.apache.org/jira/browse/LUCENE-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742603#action_12742603
]
Hoss Man commented on LUCENE-1791:
--
{quote}
Well that explains half the output anyway - e
[
https://issues.apache.org/jira/browse/LUCENE-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated LUCENE-1791:
Attachment: LUCENE-1791.patch
just fully rolling out to all of the subreaders makes the test pass
[
https://issues.apache.org/jira/browse/LUCENE-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742600#action_12742600
]
Hoss Man commented on LUCENE-1791:
--
bq. I'm guess the NAN failures are not a problem - lo
[
https://issues.apache.org/jira/browse/LUCENE-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742598#action_12742598
]
Mark Miller commented on LUCENE-1791:
-
{quote}I don't think the fieldcache insanity is
[
https://issues.apache.org/jira/browse/LUCENE-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742586#action_12742586
]
Mark Miller edited comment on LUCENE-1791 at 8/12/09 2:35 PM:
--
[
https://issues.apache.org/jira/browse/LUCENE-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742586#action_12742586
]
Mark Miller commented on LUCENE-1791:
-
I'm guess the NAN failures are not a problem -
[
https://issues.apache.org/jira/browse/LUCENE-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742574#action_12742574
]
Uwe Schindler commented on LUCENE-1801:
---
Any comments here? I will be unavailable un
[
https://issues.apache.org/jira/browse/LUCENE-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved LUCENE-1748.
-
Resolution: Fixed
thanks for taking a look Mike!
> getPayloadSpans on org.apache.lucene.search.
[
https://issues.apache.org/jira/browse/LUCENE-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742552#action_12742552
]
Hoss Man commented on LUCENE-1791:
--
bq. (grr it uses it's own random so no seed was l
[
https://issues.apache.org/jira/browse/LUCENE-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated LUCENE-1791:
-
Fix Version/s: 2.9
I just retried this patch against the trunk now that the
FieldCacheSanityChecker and
[
https://issues.apache.org/jira/browse/LUCENE-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved LUCENE-1749.
--
Resolution: Fixed
Assignee: Hoss Man
Committed revision 803676.
> FieldCache introspection API
[
https://issues.apache.org/jira/browse/LUCENE-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated LUCENE-1749:
-
Attachment: LUCENE-1749.patch
one last updated: the Locale.US asserts in TestRemoteSort had the same pro
[
https://issues.apache.org/jira/browse/LUCENE-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1802:
---
Attachment: LUCENE-1802.patch
Attached patch. I think it's ready to commit... I'll
[
https://issues.apache.org/jira/browse/LUCENE-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved LUCENE-1804.
--
Resolution: Fixed
Fix Version/s: 2.9
Committed.
I'm not sure it's worth adding constru
[
https://issues.apache.org/jira/browse/LUCENE-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved LUCENE-1800.
--
Resolution: Fixed
committed.
> QueryParser should use reusable token streams
> --
[
https://issues.apache.org/jira/browse/LUCENE-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-1802:
--
Assignee: Michael McCandless
> Un-deprecate QueryParser and remove documentati
[
https://issues.apache.org/jira/browse/LUCENE-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742514#action_12742514
]
Michael McCandless commented on LUCENE-1748:
Patch looks good... just need to
[
https://issues.apache.org/jira/browse/LUCENE-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742511#action_12742511
]
Michael McCandless commented on LUCENE-1800:
Patch looks good!
> QueryParser
[
https://issues.apache.org/jira/browse/LUCENE-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1789:
---
Attachment: LUCENE-1789.patch
Attached patch.
> getDocValues should provide a Multi
[
https://issues.apache.org/jira/browse/LUCENE-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated LUCENE-1749:
-
Attachment: LUCENE-1749.patch
updated patch to trunk (QueryWeight->Weight) and tweaked some FieldCacheIm
[
https://issues.apache.org/jira/browse/LUCENE-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-1789:
--
Assignee: Michael McCandless
> getDocValues should provide a MultiReader DocVa
[
https://issues.apache.org/jira/browse/LUCENE-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742467#action_12742467
]
Michael McCandless commented on LUCENE-1789:
OK, I'll take a crack at this!
>
[
https://issues.apache.org/jira/browse/LUCENE-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742458#action_12742458
]
Adriano Crestani commented on LUCENE-1768:
--
{quote}
I would propose to absorb the
[
https://issues.apache.org/jira/browse/LUCENE-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742460#action_12742460
]
Hoss Man commented on LUCENE-1789:
--
Cool... i don't suppose you have time to work on a pa
[
https://issues.apache.org/jira/browse/LUCENE-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742444#action_12742444
]
Michael McCandless commented on LUCENE-1458:
Thanks for modernizing the patch
[
https://issues.apache.org/jira/browse/LUCENE-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742441#action_12742441
]
Yonik Seeley commented on LUCENE-1804:
--
OO design principal of not removing functiona
[
https://issues.apache.org/jira/browse/LUCENE-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742439#action_12742439
]
Uwe Schindler commented on LUCENE-1804:
---
Normally it would be ok. E.g. in the reuse
[
https://issues.apache.org/jira/browse/LUCENE-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742388#action_12742388
]
Yonik Seeley commented on LUCENE-1804:
--
bq. But for completeness, this ctor should al
[
https://issues.apache.org/jira/browse/LUCENE-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742385#action_12742385
]
Uwe Schindler commented on LUCENE-1804:
---
OK, I was wondering, because TokenFilter is
On Aug 12, 2009, at 5:58 AM, Michael McCandless wrote:
I think being able to ask the Scorer for matching spans for the
current doc makes tons of sense.
I think eventually span queries should be absorbed into the normal
lucene queries. EG, if TermQuery creates a scorer that's able to
optionall
[
https://issues.apache.org/jira/browse/LUCENE-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742354#action_12742354
]
Yonik Seeley commented on LUCENE-1804:
--
It makes delegation possible. Say one wanted
[
https://issues.apache.org/jira/browse/LUCENE-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742352#action_12742352
]
Uwe Schindler commented on LUCENE-1804:
---
Why do you need this?
> Can't specify Attr
[
https://issues.apache.org/jira/browse/LUCENE-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated LUCENE-1748:
Attachment: LUCENE-1748.patch
makes Spans abstract
> getPayloadSpans on org.apache.lucene.search.
[
https://issues.apache.org/jira/browse/LUCENE-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated LUCENE-1804:
-
Attachment: LUCENE-1804.patch
> Can't specify AttributeSource for Tokenizer
> --
Can't specify AttributeSource for Tokenizer
---
Key: LUCENE-1804
URL: https://issues.apache.org/jira/browse/LUCENE-1804
Project: Lucene - Java
Issue Type: Bug
Reporter: Yonik Seeley
One c
[
https://issues.apache.org/jira/browse/LUCENE-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated LUCENE-1800:
-
Attachment: LUCENE-1800.patch
> QueryParser should use reusable token streams
>
[
https://issues.apache.org/jira/browse/LUCENE-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742308#action_12742308
]
Michael McCandless commented on LUCENE-1768:
bq. I would propose to absorb the
[
https://issues.apache.org/jira/browse/LUCENE-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller reopened LUCENE-1748:
-
> getPayloadSpans on org.apache.lucene.search.spans.SpanQuery should be abstract
> -
[
https://issues.apache.org/jira/browse/LUCENE-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742293#action_12742293
]
Yonik Seeley commented on LUCENE-1796:
--
bq. But in principle we could also change the
Hey Shai - I'm not saying if new syntax's come lets use it. Sorry if it
came off that way - I'm basically saying - lets see it get used - lets
see if the things that it offers are taken advantage of. A new syntax is
not a plus to me necessarily (though it is nice) - personally, I just
want a so
Michael Busch wrote:
We should also realize that - thanks to Luis and Adriano - we now have
actual code that can be the basis of discussions and that we can take
and improve. No matter if this new QP is going to replace the old one
or not, I'm very thankful that the two went through the effor
All Span*Query seem to rely on the SpanQuery.createWeight (which
returns SpanWeight/SpanScorer) to make their weight/scorer.
SpanScorer in turn simply enumerates all spans summing up their
"sloppy freq" and always scoring with that, regardless of the sub
queries.
So SpanNearQuery (or any composite
[
https://issues.apache.org/jira/browse/LUCENE-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Busch updated LUCENE-1458:
--
Attachment: LUCENE-1458.patch
I took Mike's latest patch and updated it to current trunk.
It a
I think being able to ask the Scorer for matching spans for the
current doc makes tons of sense.
I think eventually span queries should be absorbed into the normal
lucene queries. EG, if TermQuery creates a scorer that's able to
optionally enumerate matching spans, such that there's no performanc
[
https://issues.apache.org/jira/browse/LUCENE-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742270#action_12742270
]
Michael McCandless commented on LUCENE-1748:
bq. I'm tempted to make Spans abs
I think opaque terms is a good and useful feature and we have discussed
that several times and experimentally implemented in the past.
However I think that should be separate discussion/feature request. It
solves a different problem.
Michael
On 8/12/09 1:51 AM, Shai Erera wrote:
Is th
We can perhaps have one colon (:) and ' to surround the query and change the
field handling to recognize this is an opaque field (because of the '), but
I don't know if this breaks the current syntax/parser.
I think this way is cleaner :)
On Wed, Aug 12, 2009 at 1:51 AM, Shai Erera wrote:
> We
>
> Is there any example when you cannot use the processing phase for that?
>
I actually meant that w/ the old QP I can also do it, by extending
QueryParser and overriding "newWildcardQuery(Term)". I'm sure this can be
done w/ the new QP as well. I just gave an example to something the new QP
does
If I want to control how Wildcard clauses are handled, I can do it w/
today's QP as well, just extend it and override the appropriate getter
method.
The SyntaxParser can produce WildcardQueryNode object which can further be
processed on the processing phase. Is there any example when you cannot us
[
https://issues.apache.org/jira/browse/LUCENE-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler resolved LUCENE-1803.
---
Resolution: Fixed
Fix Version/s: 2.9
I just committed this. Thanks!
(revision: 803404
[
https://issues.apache.org/jira/browse/LUCENE-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler reassigned LUCENE-1803:
-
Assignee: Uwe Schindler
> Wrong javadoc on LowerCaseTokenizer.normalize
> --
Michael, I wrote the above reply before I noticed you already replied.
Thanks for the explanation.
I guess that the way I see it, being able to extend a SyntaxParser is more
important than building my final Query object. If I want to enhance the
query syntax by replacing [] {} w/ <= and >=. How do
Some comments in line:
The new QueryParser has not been used much at all yet. Its interfaces (which
will need to abide by back compat in core) have not been vetted enough.
Agreed, I still think some points must still be discussed about the API, and
to start discussing about it, the contributors m
>
> With the new QP we can build out a syntax that's compatible with
> GData and be able to embed location/spatial queries directly
> into the query string. (i.e. @+40.75-074.00 + 5mi)
>
What do you mean "with the new QP"? What prevents you from doing that w/o
the new QP, as in writing your own QP
[
https://issues.apache.org/jira/browse/LUCENE-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12742249#action_12742249
]
Paul Elschot commented on LUCENE-533:
-
I see I missed the introduction of payloads into
+1. We don't use Solr, but have quite a bunch of medium and
short-sized documents. Plus heaps of metadata fields.
I'm yet to read Uwe's example, but I feel I'm a bit misunderstood by
Did you read it yet? What do you think about it?
some of you. My gripe with new API is not that it bring
77 matches
Mail list logo
