[
https://issues.apache.org/jira/browse/LUCENE-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Helleringer updated LUCENE-1777:
Attachment: LUCENE-1777.patch
This should solve your problem.
Could you check ple
[
https://issues.apache.org/jira/browse/LUCENE-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738249#action_12738249
]
Michael McCandless commented on LUCENE-1777:
Indeed, this is the exception I s
[
https://issues.apache.org/jira/browse/LUCENE-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1504:
---
Attachment: LUCENE-1504.patch
New patch:
* Also switched over CartesianShapeFilte
[
https://issues.apache.org/jira/browse/LUCENE-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738256#action_12738256
]
Michael McCandless commented on LUCENE-1777:
I've included the "floor miles at
[
https://issues.apache.org/jira/browse/LUCENE-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738266#action_12738266
]
Michael McCandless commented on LUCENE-1777:
I do like upgrading int -> double
[
https://issues.apache.org/jira/browse/LUCENE-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-1504:
--
Description: Contrib-Spatial should be rewritten to use the new DocIdSet
Filter API with OpenB
[
https://issues.apache.org/jira/browse/LUCENE-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738271#action_12738271
]
Nicolas Helleringer commented on LUCENE-1777:
-
Actually there is already a flo
[
https://issues.apache.org/jira/browse/LUCENE-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738280#action_12738280
]
Robert Muir commented on LUCENE-1702:
-
related to this issue, Steven has added support
[
https://issues.apache.org/jira/browse/LUCENE-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738298#action_12738298
]
Michael McCandless commented on LUCENE-1777:
bq. Actually there is already a f
[
https://issues.apache.org/jira/browse/LUCENE-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738299#action_12738299
]
Nicolas Helleringer commented on LUCENE-1777:
-
1°) is done by the patch i atta
[
https://issues.apache.org/jira/browse/LUCENE-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-1504:
--
Assignee: Michael McCandless (was: Uwe Schindler)
> Contrib-Spatial should us
[
https://issues.apache.org/jira/browse/LUCENE-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738304#action_12738304
]
Nicolas Helleringer commented on LUCENE-1777:
-
Sounds great !
Thx
> Error on
[
https://issues.apache.org/jira/browse/LUCENE-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738302#action_12738302
]
Michael McCandless commented on LUCENE-1504:
I'll take it.
> Contrib-Spatial
[
https://issues.apache.org/jira/browse/LUCENE-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738301#action_12738301
]
Michael McCandless commented on LUCENE-1777:
{quote}
I do not agree with 2°) a
[
https://issues.apache.org/jira/browse/LUCENE-1504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-1504:
---
Attachment: LUCENE-1504.patch
OK new patch:
* Improved TestCartesian to test 6.0,
[
https://issues.apache.org/jira/browse/LUCENE-1689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738312#action_12738312
]
Robert Muir commented on LUCENE-1689:
-
I think instead of the way I prototyped in the
> The biggest win for NRT was switching to per-segment Collector because
> that meant we could re-use FieldCache entries for all segments that
> hadn't changed.
In my opinion, this switch was enough to get as NRT-ey, as you want.
Fusing IR/IW together makes Lucene a great deal more complicated and
I don't think that's the problem -- mergeMiddle shouldn't need any
sync'ing, because getNextMerge (which is sync'd) will have already
advanced the merge into runningMerges.
Ie, finishMerges(false) tells all runningMerges to abort, and then
waits for them to do so. During this time, because stopMe
> I'm curious if anyone has thought about (or even tried) caching the low-level
> index data in Java, rather than
> in the OS. For example, at the IndexInput level there could be an LRU cache
> of byte[] blocks, similar to
> how a RDBMS caches index pages. (Conveniently, BufferedIndexInput alre
[
https://issues.apache.org/jira/browse/LUCENE-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738325#action_12738325
]
Robert Muir commented on LUCENE-1775:
-
Michael, I looked at your patch, really glad yo
[
https://issues.apache.org/jira/browse/LUCENE-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738331#action_12738331
]
Michael McCandless commented on LUCENE-1773:
Patch looks good Koji! I plan to
[
https://issues.apache.org/jira/browse/LUCENE-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738332#action_12738332
]
Mark Miller commented on LUCENE-1774:
-
Good idea!
I'm not so keen on adding it as a p
[
https://issues.apache.org/jira/browse/LUCENE-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated LUCENE-1776:
Attachment: LUCENE-1776.patch
> NearSpansOrdered does not lazy load payloads as the PayloadSpans j
[
https://issues.apache.org/jira/browse/LUCENE-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738346#action_12738346
]
Shai Erera commented on LUCENE-1774:
I like that idea. DeleteDocTask today defines a "
[
https://issues.apache.org/jira/browse/LUCENE-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738346#action_12738346
]
Shai Erera edited comment on LUCENE-1774 at 8/3/09 6:55 AM:
I
[
https://issues.apache.org/jira/browse/LUCENE-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738349#action_12738349
]
Mark Miller commented on LUCENE-1774:
-
bq. What do you think? Shall I open an issue fo
[
https://issues.apache.org/jira/browse/LUCENE-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller resolved LUCENE-1776.
-
Resolution: Fixed
Lucene Fields: [New, Patch Available] (was: [New])
> NearSpansOrdered
On 08/03/2009 08:21 AM, Earwin Burrfoot wrote:
The biggest win for NRT was switching to per-segment Collector because
that meant we could re-use FieldCache entries for all segments that
hadn't changed.
In my opinion, this switch was enough to get as NRT-ey, as you want.
Fusing IR/IW togeth
[
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
Too trunk - removes the lazy load payload issue which has been resol
Add log.step support per task
-
Key: LUCENE-1778
URL: https://issues.apache.org/jira/browse/LUCENE-1778
Project: Lucene - Java
Issue Type: Improvement
Components: contrib/benchmark
Reporter:
[
https://issues.apache.org/jira/browse/LUCENE-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera updated LUCENE-1778:
---
Attachment: LUCENE-1778.patch
PerfTask changes + a test case. All benchmark tests pass.
> Add log.s
[
https://issues.apache.org/jira/browse/LUCENE-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated LUCENE-1778:
Priority: Minor (was: Major)
Assignee: Mark Miller
> Add log.step support per task
>
[
https://issues.apache.org/jira/browse/LUCENE-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated LUCENE-1778:
Attachment: LUCENE-1778.patch
I changed the delete log step in the existing algs to match the new
[
https://issues.apache.org/jira/browse/LUCENE-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738447#action_12738447
]
Shai Erera commented on LUCENE-1778:
Thanks Mark, updating the existing .alg files sli
I'm trying to get started with the new (flexible) QueryParser, in
contrib.
I see the "original" package, and the useful OriginalQueryParserHelper
within there, that are meant to ease the transition off of the old
QueryParser to the new one.
First question: is the original package also intended to
[
https://issues.apache.org/jira/browse/LUCENE-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Busch reopened LUCENE-1775:
---
> Change org.apache.lucene.analysis.shingle to use new TokenStream API
> ---
[
https://issues.apache.org/jira/browse/LUCENE-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Busch updated LUCENE-1775:
--
Summary: Change remaining contrib streams/filters to use new TokenStream
API (was: Change org
[
https://issues.apache.org/jira/browse/LUCENE-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Busch updated LUCENE-1775:
--
Attachment: lucene-contrib-sinks.patch
{quote}
One last question, we didnt do anything with an
[
https://issues.apache.org/jira/browse/LUCENE-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Busch updated LUCENE-1775:
--
Attachment: (was: lucene-contrib-sinks.patch)
> Change remaining contrib streams/filters t
[
https://issues.apache.org/jira/browse/LUCENE-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Busch updated LUCENE-1775:
--
Attachment: lucene-contrib-sinks.patch
> Change remaining contrib streams/filters to use new T
[
https://issues.apache.org/jira/browse/LUCENE-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-1775:
Attachment: lucene-contrib-sinks.patch
same patch as Michael's, just removed a stray import
org.a
The Lucene PMC is pleased to announce that Robert Muir has accepted an
invitation to join the Lucene community as a contrib committer.
Robert has contributed a number of advances related to foreign
language analysis and other capabilities in the Lucene contrib.
Robert, tradition has it tha
+1, welcome aboard!
Note to whom it may concern:
Someone please give Robert his super JIRA karma so that I can properly
assign him LUCENE-1628.
- Mark
Grant Ingersoll wrote:
The Lucene PMC is pleased to announce that Robert Muir has accepted an
invitation to join the Lucene community as a co
Grant, thanks for the nice introduction.
I will give a try at this introduction thing: I have a computer
science background, but the last few years I have been meddling with
languages more than developing software. Maybe this has caused my
software skills to be a little rusty! Currently, I work fo
[
https://issues.apache.org/jira/browse/LUCENE-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738543#action_12738543
]
Michael Busch commented on LUCENE-1775:
---
Thanks, Robert. I'll commit this later toda
Welcome Robert! Good to have you in the team!
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Robert Muir [mailto:rcm...@gmail.com]
> Sent: Monday, August 03, 2009 9:51 PM
> To: java-dev@lucene.apache.org
Michael McCandless wrote:
On the impact of search performance for large vs small mergeFactors, I
think the jury is still out. People should keep testing that (and
report back!). Certainly, for the fastest reopen time you never want
any merging to be done :)
Here is the original exchange I r
I see the "original" package, and the useful OriginalQueryParserHelper
within there, that are meant to ease the transition off of the old
QueryParser to the new one.
First question: is the original package also intended to be Lucene's
"default" QueryParser, going forward? Ie, most users will simp
Thanks for this howto; maybe I can try to do this for LUCENE-1768 as some
exercise at the end of the week :-) - I was not able to look into the new
framework in detail (I only looked into the Powerpoints on Michael B's
Linkedin profile page), but it would be good to have a howto like this mail
some
If I read it correctly, the parsing of the query string is decoupled from
this. So somebody could also create another query syntax and reuse all
processors and builders?
Yes, as far as the processors know how to process the node your text parser
creates. The QP framework was really designed to hav
Welcome Robert!
I'll now go reassign LUCENE-1758 to you ;)
Mike
On Mon, Aug 3, 2009 at 3:51 PM, Robert Muir wrote:
> Grant, thanks for the nice introduction.
>
> I will give a try at this introduction thing: I have a computer
> science background, but the last few years I have been meddling with
[
https://issues.apache.org/jira/browse/LUCENE-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738560#action_12738560
]
Mark Miller commented on LUCENE-1685:
-
I'll commit this within a few days
> Make the
On Mon, Aug 3, 2009 at 3:59 PM, Adriano
Crestani wrote:
> Yes, it's the Lucene's "default" query parser implemented using the new QP
> framework.
OK.
> Now, about moving it to oal.queryParser, I think it's a subjective decision.
> I like it inside oal.queryParser.original, because
> we can easil
[
https://issues.apache.org/jira/browse/LUCENE-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Busch resolved LUCENE-1775.
---
Resolution: Fixed
Committed revision 800606.
> Change remaining contrib streams/filters to
[
https://issues.apache.org/jira/browse/LUCENE-1758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-1758:
--
Assignee: Robert Muir (was: Michael McCandless)
Welcome aboard Robert!
> imp
[
https://issues.apache.org/jira/browse/LUCENE-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller reassigned LUCENE-1628:
---
Assignee: Robert Muir (was: Mark Miller)
> Persian Analyzer
>
>
>
Michael McCandless wrote:
OK thanks for the clarification... that makes sense. So the builder
should really be a "rote" translation of a query node into the
corresponding Query. All "interesting" work should instead be done by
the processors (or maybe the parser).
Hi Mike,
Only the Proce
[
https://issues.apache.org/jira/browse/LUCENE-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738692#action_12738692
]
Mark Miller commented on LUCENE-1763:
-
bq. I think subclassing LMP is also extremely a
[
https://issues.apache.org/jira/browse/LUCENE-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738698#action_12738698
]
Mark Miller commented on LUCENE-1749:
-
I've got one more draft here with the smallest
[
https://issues.apache.org/jira/browse/LUCENE-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738714#action_12738714
]
Mark Miller commented on LUCENE-1748:
-
Has something like this come up in the past? Ho
[
https://issues.apache.org/jira/browse/LUCENE-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738721#action_12738721
]
Chris Hostetter commented on LUCENE-1749:
-
: I've got one more draft here with t
[
https://issues.apache.org/jira/browse/LUCENE-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738754#action_12738754
]
Hoss Man commented on LUCENE-1769:
--
bq. I only want to remove the call to the (I call it
Why is "reversed" passed into SortField.getComparator(), and what does it mean?
Should it always be passed as sortField.getReversed() (and if so, why
does the param exist at all)?
Also, FieldComparator has no javadoc for most of it's methods. For example:
public void setNextReader(IndexReader
Mike - isn't "fast forwarding 3 years" means that the current QP will be
removed, together w/ the OriginalQPHelper and we'll have just one QP? And
I'd think we'll want to call it Default or something, so users can
distinguish between it (which parses the Lucene query syntax) and another
custom pars
[
https://issues.apache.org/jira/browse/LUCENE-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera updated LUCENE-1778:
---
Attachment: LUCENE-1778.patch
Updated package.html to describe the latest ContentSource/DocMaker cha
The "original" and "helper" aren't that descriptive to users.
It's named "helper" because it extends QueryParserHelper, that's the only
reason. I think it's ok to rename "original" to something else. . I also
share Mike's opinion, I prefer "default" over "original".
Mike - isn't "fast forwarding
[
https://issues.apache.org/jira/browse/LUCENE-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738840#action_12738840
]
Nick Pellow commented on LUCENE-1769:
-
Hi Hoss,
{quote}
Nick: if i'm understanding t
What a terrible timing! A week earlier and I could have assigned
LUCENE-1460 to you, Robert... :)
Just kidding, very happy that you're aboard!
Michael
On 8/3/09 12:32 PM, Grant Ingersoll wrote:
The Lucene PMC is pleased to announce that Robert Muir has accepted an
invitation to join the Luce
68 matches
Mail list logo
