[
https://issues.apache.org/jira/browse/LUCENE-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850644#action_12850644
]
Shai Erera commented on LUCENE-2353:
I don't have an account yet, so I cannot commit t
Convert NumericUtils and NumericTokenStream to use BytesRef instead of
Strings/char[]
-
Key: LUCENE-2354
URL: https://issues.apache.org/jira/browse/LUCENE-2354
Projec
[
https://issues.apache.org/jira/browse/LUCENE-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler resolved LUCENE-2352.
---
Resolution: Fixed
Committed revision: 928295
> Add a new TestBackwardsCompatibility index f
[
https://issues.apache.org/jira/browse/LUCENE-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-2352:
--
Attachment: LUCENE-2352.patch
Add a range for all docs to check if lower-prec terms are also o
[
https://issues.apache.org/jira/browse/LUCENE-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-2352:
--
Attachment: index.30.nocfs.zip
index.30.cfs.zip
LUCENE-2352.pat
[
https://issues.apache.org/jira/browse/LUCENE-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera updated LUCENE-2353:
---
Attachment: LUCENE-2353.patch
The fix is only relevant to get(String, String) and not to all other
Config incorrectly handles Windows absolute pathnames
-
Key: LUCENE-2353
URL: https://issues.apache.org/jira/browse/LUCENE-2353
Project: Lucene - Java
Issue Type: Bug
Components:
Right.
But now that public copyTo takes list-of-files I think "expert" apps
can do the right thing here. Worst case is they .listAll but then
filter out the files they know they add to index dir.
Mike
On Sat, Mar 27, 2010 at 4:56 PM, Earwin Burrfoot wrote:
> Well, it was a back-compat break fr
Well, it was a back-compat break from before copyTo.
But nothing can be done here, unless you want to teach Directory how to parse
the index inside : }
> Ugh, actually, it is still a back-compat break :(
>
> Because Directory.copy just forwards to copyTo.
>
> I'll advertise in CHANGES for flex.
Ugh, actually, it is still a back-compat break :(
Because Directory.copy just forwards to copyTo.
I'll advertise in CHANGES for flex.
Mike
On Sat, Mar 27, 2010 at 4:41 PM, Michael McCandless
wrote:
> Right... in fact as long as we land flex before 3.1 releases then this
> is not a back-compat
Right... in fact as long as we land flex before 3.1 releases then this
is not a back-compat break (but we should heavily advertise the change
in semantics) ;)
Ie Directory.copy used to filter for only index files, but
Directory.copyTo copies everything so you must provide your own list
if this mat
I'm merging the conflicts now... it turned out to cause a number of
conflicts because in flex I changed how DW stores the terms in RAM, to
first prefix-code each term's length as vInt (most often 1 byte, but
in messed up cases 2 bytes), and then then the term's characters as
UTF8 bytes. This cause
I think original Directory.copy() just copied everything in flex, without
nocommits?
Unlike before, now you can specify which files do you want to have copied, so
people can query Codecs and whatnot themselves.
>> Author: uschindler
>> Date: Sat Mar 27 19:12:08 2010
>> New Revision: 928246
>>
>
Hey Uwe, I can update the flex branch to use parallel arrays after the
weekend.
Michael
On Mar 27, 2010, at 12:12 PM, uschind...@apache.org wrote:
Author: uschindler
Date: Sat Mar 27 19:12:08 2010
New Revision: 928246
URL: http://svn.apache.org/viewvc?rev=928246&view=rev
Log:
Merge upto tr
[
https://issues.apache.org/jira/browse/LUCENE-2351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-2351:
Attachment: LUCENE-2351_infinite.patch
attached is a patch to optimize "infinite transitions"
its
Add a new TestBackwardsCompatibility index for flex backwards (a 3.0 one with
also numeric fields)
--
Key: LUCENE-2352
URL: https://issues.apache.org/jira/browse/LUCEN
[
https://issues.apache.org/jira/browse/LUCENE-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850550#action_12850550
]
Robert Muir commented on LUCENE-1990:
-
By the way Toke, we have lately been benchmarki
[
https://issues.apache.org/jira/browse/LUCENE-2351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850546#action_12850546
]
Uwe Schindler commented on LUCENE-2351:
---
This one should be final:
{code}
+ public
[
https://issues.apache.org/jira/browse/LUCENE-2351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850545#action_12850545
]
Michael McCandless commented on LUCENE-2351:
The attached patch improves sneak
[
https://issues.apache.org/jira/browse/LUCENE-2351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-2351:
---
Attachment: LUCENE-2351.patch
Patch to adress some of the optos:
* Adds optional
optimize automatonquery
---
Key: LUCENE-2351
URL: https://issues.apache.org/jira/browse/LUCENE-2351
Project: Lucene - Java
Issue Type: Improvement
Components: Search
Affects Versions: Flex Branch
Of course introducing the idea of updates also introduces the notion of a
primary key and there's probably an entirely separate discussion to be had
around user-supplied vs Lucene-generated keys.
That aside, the biggest concern for me here is the impact that this is likely
to have on search -
First off, this is something I've had in my head for a long time, but don't
have any code.
As many of you know, one of the main things that vexes any search engine based
on an inverted index is how to do fast updates of just one field w/o having to
delete and re-add the whole document like we d
[
https://issues.apache.org/jira/browse/LUCENE-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850505#action_12850505
]
Grant Ingersoll commented on LUCENE-1879:
-
Thanks, Shai, I had indeed misread the
[
https://issues.apache.org/jira/browse/LUCENE-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850500#action_12850500
]
Michael McCandless commented on LUCENE-2324:
I don't think we should delete in
[
https://issues.apache.org/jira/browse/LUCENE-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-2111:
---
Attachment: flexBench.py
benchUtil.py
I'm benchmarking flex vs trunk
[
https://issues.apache.org/jira/browse/LUCENE-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850497#action_12850497
]
Mark Harwood commented on LUCENE-2306:
--
FYI, re changes to defaults. I try to keep th
[
https://issues.apache.org/jira/browse/LUCENE-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-2306:
--
Summary: contrib/xml-query-parser: NumericRangeQuery and -Filter support
(was: contrib/xml-qu
[
https://issues.apache.org/jira/browse/LUCENE-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850495#action_12850495
]
Uwe Schindler commented on LUCENE-2306:
---
Committed package and test fixes in revisio
[
https://issues.apache.org/jira/browse/LUCENE-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850494#action_12850494
]
Mark Harwood commented on LUCENE-2306:
--
bq. Should I commit?
Yes, thanks, Uwe. Miss
[
https://issues.apache.org/jira/browse/LUCENE-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler reopened LUCENE-2306:
---
I will commit my changes to the package names and a missing super.tearDown()
soon.
But I found
31 matches
Mail list logo
