[
https://issues.apache.org/jira/browse/LUCENENET-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779810#action_12779810
]
Michael Garski commented on LUCENENET-288:
--
Getting closer...
The issue is cau
Hi Everyone,
Just a small nit-picking here.
Patches should be to fix issues, and nothing more. There is no need to bring
in additional comments or code that don't exists in the Java Lucene world
_unless_ if the comment and code is to explain behavior difference between the
two languages, or e
[
https://issues.apache.org/jira/browse/LUCENENET-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779781#action_12779781
]
Michael Garski commented on LUCENENET-288:
--
A little more digging into this...
Function.TestCustomScoreQuery
-
Key: LUCENENET-288
URL: https://issues.apache.org/jira/browse/LUCENENET-288
Project: Lucene.Net
Issue Type: Bug
Reporter: Michael Garski
Three of the tests in TestCust
[
https://issues.apache.org/jira/browse/LUCENENET-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Iliev updated LUCENENET-287:
---
Description:
SegmentInfos is derived from ArrayList. So Equals and GetHashCode should
be
[
https://issues.apache.org/jira/browse/LUCENENET-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Garski updated LUCENENET-286:
-
Attachment: LUCENENET-286.patch
Just a few changes to the test itself:
1) Mark MakeLo
TestIndexWriterReader.TestUpdateDocument
--
Key: LUCENENET-287
URL: https://issues.apache.org/jira/browse/LUCENENET-287
Project: Lucene.Net
Issue Type: Bug
Reporter: Andrei Iliev
[
https://issues.apache.org/jira/browse/LUCENENET-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Iliev updated LUCENENET-287:
---
Attachment: SegmentInfos.patch
> TestIndexWriterReader.TestUpdateDocument
>
IndexWrtier Tests
-
Key: LUCENENET-286
URL: https://issues.apache.org/jira/browse/LUCENENET-286
Project: Lucene.Net
Issue Type: Bug
Reporter: Michael Garski
There are a two tests still failing in TestIndexWriter
[
https://issues.apache.org/jira/browse/LUCENENET-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779664#action_12779664
]
Nicholas Paldino commented on LUCENENET-285:
The ToString equivalents in Jav
[
https://issues.apache.org/jira/browse/LUCENENET-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779663#action_12779663
]
Andrei Iliev commented on LUCENENET-284:
Thanks Nicholas for comments.
My comme
[
https://issues.apache.org/jira/browse/LUCENENET-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy resolved LUCENENET-275.
Resolution: Fixed
patch committed.
> TestTokenStreamBWComp issue with 2.9.1
> -
Problem with "CurrentCulture"
-
Key: LUCENENET-285
URL: https://issues.apache.org/jira/browse/LUCENENET-285
Project: Lucene.Net
Issue Type: Bug
Reporter: Digy
Hi Folks,
There is a bug in utilizing T
Hmmm...
I am uncomfortable changing the query under the covers inside the
QueryParser as it diverges from the behavior in the Java version for
what amounts to the same query expressed in a different manner. When
Lucene.Net 'diverges' from the Java version to be made more '.net-like',
I see that a
[
https://issues.apache.org/jira/browse/LUCENENET-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779599#action_12779599
]
Nicholas Paldino commented on LUCENENET-284:
A few things here.
- Collectio
Michael,
Thanks for the response. It's somewhat of a moot point now, as the
error in the test was something else entirely, but it seems that Lucene.NET
(as it stands now), when doing filtering on date fields, if using the
inclusive date, will internally generate the value up to the last
m
[
https://issues.apache.org/jira/browse/LUCENENET-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Garski updated LUCENENET-275:
-
Attachment: LUCENENET-275.patch
Here it is. All tests in Analysis are passing now.
>
[
https://issues.apache.org/jira/browse/LUCENENET-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779584#action_12779584
]
Nicholas Paldino commented on LUCENENET-283:
Note, this patch relies on the
[
https://issues.apache.org/jira/browse/LUCENENET-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Garski reopened LUCENENET-275:
--
Just running through the full test suite and I noticed this one was failing
again. The
[
https://issues.apache.org/jira/browse/LUCENENET-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicholas Paldino updated LUCENENET-283:
---
Attachment: TestQueryParser.DateRangeTests.patch
The tests themselves are wrong.
[
https://issues.apache.org/jira/browse/LUCENENET-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy resolved LUCENENET-278.
Resolution: Fixed
Thanks Nicholas,
I replaced 36's with SupportClass.Character.MAX_RADIX.
patch committe
java vs .Net GetHashCode and Equals for ArrayList
--
Key: LUCENENET-284
URL: https://issues.apache.org/jira/browse/LUCENENET-284
Project: Lucene.Net
Issue Type: Bug
Reporter: Andre
[
https://issues.apache.org/jira/browse/LUCENENET-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Iliev updated LUCENENET-284:
---
Attachment: ArrayList.patch
> java vs .Net GetHashCode and Equals for ArrayList
> ---
TestDateRange and TestLegacyDateRange fail.
---
Key: LUCENENET-283
URL: https://issues.apache.org/jira/browse/LUCENENET-283
Project: Lucene.Net
Issue Type: Bug
Reporter: Nicholas Paldino
No. Lucene.NET's default behavior should not depend on an external library.
DIGY
-Original Message-
From: Michael Garski [mailto:mgar...@myspace-inc.com]
Sent: Wednesday, November 18, 2009 8:01 PM
To: lucene-net-dev@incubator.apache.org
Subject: RE: [jira] Resolved: (LUCENENET-274) ClassD
[
https://issues.apache.org/jira/browse/LUCENENET-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy resolved LUCENENET-256.
Resolution: Fixed
Thanks Andrei,
I changed Version.ToString(2) to Version.ToString(3) and cleaned the c
Digy,
Looks like you accidentally dropped the SHARP_ZIP_LIB define from
Lucene.Net.csproj
-DEBUG;TRACE;SHARP_ZIP_LIB
+TRACE;DEBUG
Michael
-Original Message-
From: Digy (JIRA) [mailto:j...@apache.org]
Sent: Wednesday, November 18, 2009 9:59 AM
To: lucene-net-dev@incubator.apach
[
https://issues.apache.org/jira/browse/LUCENENET-274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy resolved LUCENENET-274.
Resolution: Fixed
Resolved.
DIGY
> ClassDiagram1.cd included in Lucene.Net.csproj without actual Class
Great points Nick. I wanted to think about this overnight and take a
fresh look at it in the morning, and here's my take on it.
TestLegacyDateRange tests the now-deprecated way of expressing date &
time information in documents. The DateField type goes away in 3.0 in
favor of DateTools
T
[
https://issues.apache.org/jira/browse/LUCENENET-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779552#action_12779552
]
Nicholas Paldino commented on LUCENENET-278:
Changed to call ToString on nes
[
https://issues.apache.org/jira/browse/LUCENENET-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicholas Paldino updated LUCENENET-278:
---
Attachment: DateField.patch
> Instances of DateField class cannot be created.
> --
[
https://issues.apache.org/jira/browse/LUCENENET-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicholas Paldino updated LUCENENET-278:
---
Attachment: (was: DateField.patch)
> Instances of DateField class cannot be cr
[
https://issues.apache.org/jira/browse/LUCENENET-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicholas Paldino updated LUCENENET-278:
---
Attachment: (was: SupportClass.patch)
> Instances of DateField class cannot be
[
https://issues.apache.org/jira/browse/LUCENENET-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy resolved LUCENENET-281.
Resolution: Fixed
Thanks Nicholas & Google :-)
patch committed.
DIGY
> TestCJK on TestQueryP
[
https://issues.apache.org/jira/browse/LUCENENET-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy resolved LUCENENET-282.
Resolution: Fixed
Patch committed.
DIGY
> Handle potential overflow in LogByteSizeMergePolicy.SetMaxMer
[
https://issues.apache.org/jira/browse/LUCENENET-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779539#action_12779539
]
Digy commented on LUCENENET-278:
Hi Nicholas,
There are two classes in Lucene.NET. Supp
[
https://issues.apache.org/jira/browse/LUCENENET-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Garski updated LUCENENET-282:
-
Attachment: LUCENENET-282.patch
Patch will allow for a graceful overflow. Thanks to A
Handle potential overflow in LogByteSizeMergePolicy.SetMaxMergeMB
-
Key: LUCENENET-282
URL: https://issues.apache.org/jira/browse/LUCENENET-282
Project: Lucene.Net
Issue Type: B
My bad :( That's what I get when I start responding to things before drinking
coffee in the morning.
I'll open another issue on the setter and post a patch for it so any overflow
is handled gracefully.
Michael
-Original Message-
From: Digy (JIRA) [mailto:j...@apache.org]
Sent: Wednes
[
https://issues.apache.org/jira/browse/LUCENENET-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy resolved LUCENENET-280.
Resolution: Fixed
Thanks Nicholas,
Patch commited.
DIGY
> TestProtectedCtors test on TestQueryParser fa
[
https://issues.apache.org/jira/browse/LUCENENET-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779524#action_12779524
]
Digy commented on LUCENENET-257:
Oh, I forgot to say "very good catch". Thanks Michael
D
[
https://issues.apache.org/jira/browse/LUCENENET-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779523#action_12779523
]
Digy commented on LUCENENET-257:
Some may want to set 1.5 MB merge size :-)
Anyway, I ap
[
https://issues.apache.org/jira/browse/LUCENENET-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy resolved LUCENENET-257.
Resolution: Fixed
> TestCheckIndex.TestDeletedDocs
> ---
>
>
[
https://issues.apache.org/jira/browse/LUCENENET-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy resolved LUCENENET-279.
Resolution: Fixed
Thanks Michael, good catch.
patch applied.
> TestIndexWriter.TestExceptionOnMergeInit
[
https://issues.apache.org/jira/browse/LUCENENET-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779515#action_12779515
]
Digy commented on LUCENENET-279:
mergingSegments is declared as "HashSet" in java and ad
[
https://issues.apache.org/jira/browse/LUCENENET-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779507#action_12779507
]
Michael Garski commented on LUCENENET-257:
--
Good catch! I had not noticed that
[
https://issues.apache.org/jira/browse/LUCENENET-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779498#action_12779498
]
Michael Garski commented on LUCENENET-279:
--
It doesn't fail in Java as the argu
[
https://issues.apache.org/jira/browse/LUCENENET-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779435#action_12779435
]
Andrei Iliev commented on LUCENENET-279:
Thanks Michael,
I did it in same way in
[
https://issues.apache.org/jira/browse/LUCENENET-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779428#action_12779428
]
Andrei Iliev commented on LUCENENET-257:
Thanks Michael,
Something still bother
49 matches
Mail list logo
