i think we can make some reasonable defaults (based on Version) for fuzzy so
that its fast.
i'm trying to figure out a way to use TREC's confusion data (
http://trec.nist.gov/data/t5_confusion.html, OCR-damaged test collection),
to help determine some defaults so Hoss won't be after me... yes i kn
[
https://issues.apache.org/jira/browse/LUCENE-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833496#action_12833496
]
Robert Muir edited comment on LUCENE-2262 at 2/14/10 3:50 AM:
--
Nah, let's just make fuzzy not work in the qp by default :) And make
that back compat while your at it - while not abusing Version so that
it's used for something subjective :) wouldn't want to rile up Hoss.
I'm like 3/4 serious.
- Mark
http://www.lucidimagination.com (mobile)
On Feb 13, 2
[
https://issues.apache.org/jira/browse/LUCENE-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833496#action_12833496
]
Robert Muir commented on LUCENE-2262:
-
bq. in my opinion disallowing these queries wit
[
https://issues.apache.org/jira/browse/LUCENE-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-2262:
Description:
QueryParser currently throws an exception if a wildcard term begins with the
'?' ope
[
https://issues.apache.org/jira/browse/LUCENE-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833493#action_12833493
]
Yonik Seeley commented on LUCENE-2262:
--
bq. yonik, that's not what this issue is abou
[
https://issues.apache.org/jira/browse/LUCENE-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833488#action_12833488
]
Robert Muir commented on LUCENE-2262:
-
btw Yonik, in my opinion disallowing these quer
[
https://issues.apache.org/jira/browse/LUCENE-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833485#action_12833485
]
Robert Muir commented on LUCENE-2262:
-
bq. It doesn't seem like this type of bug is no
[
https://issues.apache.org/jira/browse/LUCENE-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833481#action_12833481
]
Yonik Seeley commented on LUCENE-2262:
--
It doesn't seem like this type of bug is not
Hi,
I have a few questions regarding more like this:
1. In MoreLikeThis, it seems like the check for fieldNames being null and
fetching them from the reader is not done for all the like methods. For
example, it does not look like it is done at all for like(Reader r), and on
the other hand, it i
On Fri, Nov 27, 2009 at 1:27 PM, Michael McCandless <
luc...@mikemccandless.com> wrote:
>
> Also one thing I'd love to try is NOT forking the JVM for each test
> (fork="no" in the junit task). I wonder how much time that'd buy...
>
>
it shaves off a good deal of time on my machine.
'ant test-cor
[
https://issues.apache.org/jira/browse/LUCENE-2263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonio Martinez updated LUCENE-2263:
-
Priority: Blocker (was: Critical)
Environment:
bash-3.00$ cat /etc/release
Deadlock with FSIndexInput and SegmentReader
-
Key: LUCENE-2263
URL: https://issues.apache.org/jira/browse/LUCENE-2263
Project: Lucene - Java
Issue Type: Bug
Affects Versions: 2.2
Env
Hi
IndexWriter.init() checks a couple of times whether infoStream != null in
order to print informative messages ... init() is called only from the
ctors, which means infoStream will always be null at this point, no?
Therefore I think those checks can be removed? Not for performance reasons,
but f
[
https://issues.apache.org/jira/browse/LUCENE-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-2262:
Attachment: LUCENE-2262_backwards.patch
patch for the backwards tests (not the best I admit, but u
[
https://issues.apache.org/jira/browse/LUCENE-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-2262:
Attachment: LUCENE-2262.patch
initial patch:
* doesnt throw the exception for leading ? when match
QueryParser should now allow leading '?' wildcards
--
Key: LUCENE-2262
URL: https://issues.apache.org/jira/browse/LUCENE-2262
Project: Lucene - Java
Issue Type: Improvement
Components
[
https://issues.apache.org/jira/browse/LUCENE-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833415#action_12833415
]
Robert Muir commented on LUCENE-2261:
-
will commit this in a day or two if no one obje
[
https://issues.apache.org/jira/browse/LUCENE-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-2261:
Attachment: LUCENE-2261.patch
bq. There is only one thing unrelated to that issue: It makes no sen
> Please do not commit anything to the branches and trunk, if it is fix-
> for 2.9.x or 3.0.x. All other changes can be committed.
Of course only changes in *trunk* may be committed that are not also fix-for
2.9 and 3.0. :-)
-
Hi all,
the release of 2.9.2 and 3.0.1 is in progress. I merged all CHANGES.txt
entries, merged remaining bugfixes and prepared the version number in both
branches. The only missing fix is
https://issues.apache.org/jira/browse/LUCENE-1941, which is in progress, I will
backport and commit when
[
https://issues.apache.org/jira/browse/LUCENE-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler reassigned LUCENE-1941:
-
Assignee: Uwe Schindler
> MinPayloadFunction returns 0 when only one payload is present
[
https://issues.apache.org/jira/browse/LUCENE-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-2165:
--
Fix Version/s: 2.9.2
backport
> SnowballAnalyzer lacks a constructor that takes a Set of Stop
[
https://issues.apache.org/jira/browse/LUCENE-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-2144:
--
Fix Version/s: 2.9.2
merge back also to 2.9.2
> InstantiatedIndexReader does not handle #term
24 matches
Mail list logo