[
https://issues.apache.org/jira/browse/LUCENE-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doron Cohen reassigned LUCENE-1213:
---
Assignee: Doron Cohen
MultiFieldQueryParser ignores slop parameter
[
https://issues.apache.org/jira/browse/LUCENE-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doron Cohen updated LUCENE-1213:
Attachment: multifield-fix.patch
Trekaj thanks for the patch.
Attached a slightly compacted fix
[
https://issues.apache.org/jira/browse/LUCENE-1210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576927#action_12576927
]
Michael McCandless commented on LUCENE-1210:
Yes, I agree. At some point soon
[
https://issues.apache.org/jira/browse/LUCENE-1208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576941#action_12576941
]
Michael McCandless commented on LUCENE-1208:
Agreed. I'm thinking these
[
https://issues.apache.org/jira/browse/LUCENE-1210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576924#action_12576924
]
Michele Bini commented on LUCENE-1210:
--
Uhm, shouldn't the patch be committed in the
[
https://issues.apache.org/jira/browse/LUCENE-1208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576933#action_12576933
]
Michele Bini commented on LUCENE-1208:
--
As with LUCENE-1210, shouldn't the patch be
You make a good point. I think I will prob make this change.
Asgeir Frimannsson (JIRA) wrote:
[
https://issues.apache.org/jira/browse/LUCENE-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576858#action_12576858
]
Asgeir Frimannsson commented
[
https://issues.apache.org/jira/browse/LUCENE-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated LUCENE-794:
---
Attachment: SpanHighlighter-02-10-2008.patch
Another attempt at putting this to bed.
Added the
Possible hidden exception on SegmentInfos commit
Key: LUCENE-1214
URL: https://issues.apache.org/jira/browse/LUCENE-1214
Project: Lucene - Java
Issue Type: Bug
Components: Index
[
https://issues.apache.org/jira/browse/LUCENE-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-1214:
--
Assignee: Michael McCandless
Possible hidden exception on SegmentInfos
[
https://issues.apache.org/jira/browse/LUCENE-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576970#action_12576970
]
Michael McCandless commented on LUCENE-1214:
Good catch Mark. It seems like
On Thu, Jan 17, 2008 at 4:01 PM, DM Smith [EMAIL PROTECTED] wrote:
On Jan 17, 2008, at 1:38 AM, Chris Hostetter wrote:
: I'd like to recommend that 3.0 contain the new Java 5 API changes
and what it
: replaces be marked deprecated. 3.0 would also remove what was
deprecated in
: 2.9.
[
https://issues.apache.org/jira/browse/LUCENE-1208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12577073#action_12577073
]
Michael Busch commented on LUCENE-1208:
---
We had seen this deadlock problem in our
Michael McCandless (JIRA) wrote:
[
https://issues.apache.org/jira/browse/LUCENE-1208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576941#action_12576941
]
Michael McCandless commented on LUCENE-1208:
OK I'll backport.
Mike
Michael Busch wrote:
Michael McCandless (JIRA) wrote:
[ https://issues.apache.org/jira/browse/LUCENE-1208?
page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
tabpanelfocusedCommentId=12576941#action_12576941 ]
Michael McCandless commented on
We voted to make 3.0 Java 1.5, full well knowing that it will break
the back compat. requirements. I don't see the point of postponing it
or dragging it out.
On Mar 10, 2008, at 12:02 PM, Doron Cohen wrote:
On Thu, Jan 17, 2008 at 4:01 PM, DM Smith [EMAIL PROTECTED]
wrote:
On Jan
Grant Ingersoll wrote:
We voted to make 3.0 Java 1.5, full well knowing that it will break
the back compat. requirements. I don't see the point of postponing it
or dragging it out.
I thought his suggestion was to skip 3.0 as a designator and instead use
4.0. If so, the schedule would not
Hi all,
perhaps this is a simple question, but I don't know how to do it.
I'm developing on a new contrib subfolder. My development needs to use
classes in another contrib subfolder. How do I add the corresponding JAR
to the build.xml file?
thanks in advance.
--
Felipe
On Mon, Mar 10, 2008 at 9:21 PM, DM Smith [EMAIL PROTECTED] wrote:
Grant Ingersoll wrote:
We voted to make 3.0 Java 1.5, full well knowing that it will break
the back compat. requirements. I don't see the point of postponing it
or dragging it out.
I thought his suggestion was to skip
Here is how the span highlighter I have been working on uses the Memory
contrib (I think I copied this from another contrib that has a dependency):
?xml version=1.0?
project name=highlighter default=buildHighlighter
description
Hits highlighter
/description
import
All it takes is one line in the announcement saying Version 3.0 uses
Java 1.5 I don't think the significance will be lost on anyone.
Everyone knows what Java 1.5 is. I'm -1 on calling it 4.0. People
will then ask where is 3.0. I am +1 for sticking w/ the plan we voted
for as described
Grant Ingersoll wrote:
All it takes is one line in the announcement saying Version 3.0 uses
Java 1.5 I don't think the significance will be lost on anyone.
Everyone knows what Java 1.5 is. I'm -1 on calling it 4.0. People
will then ask where is 3.0. I am +1 for sticking w/ the plan we
[
https://issues.apache.org/jira/browse/LUCENE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12577207#action_12577207
]
Mark Miller commented on LUCENE-584:
I think there is still an issue here. The code
[
https://issues.apache.org/jira/browse/LUCENE-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12577207#action_12577207
]
[EMAIL PROTECTED] edited comment on LUCENE-584 at 3/10/08 2:48 PM:
[
https://issues.apache.org/jira/browse/LUCENE-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12577220#action_12577220
]
Mark Miller commented on LUCENE-1214:
-
I am still trying to work that out...some
: I'm fine with the plan as far as I understand it, but can you clarify
: something for me?
:
: While 3.0 won't be backward compatible in that it requires Java 5.0, will it
: be otherwise backward compatible? That is, if I compile with 2.9, eliminate
: all deprecations and use Java 5, can I drop
Support of Unicode Collation
Key: LUCENE-1215
URL: https://issues.apache.org/jira/browse/LUCENE-1215
Project: Lucene - Java
Issue Type: New Feature
Components: Analysis
Reporter: Hiroaki
[
https://issues.apache.org/jira/browse/LUCENE-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiroaki Kawai updated LUCENE-1215:
--
Attachment: NormalizerTokenFilter.java
Support of Unicode Collation
[
https://issues.apache.org/jira/browse/LUCENE-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12577309#action_12577309
]
Hiroaki Kawai commented on LUCENE-1032:
---
I think this feature should merged to
[
https://issues.apache.org/jira/browse/LUCENE-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12577312#action_12577312
]
Andrew Lynch commented on LUCENE-1215:
--
This will be quite useful. I used the
30 matches
Mail list logo
