Hi All,
In order to create a 2.9.2 tag, I plan to wait
till LUCENENET-358 is fixed,
and
at least one of the other commiters post a +1
DIGY
From: Digy [mailto:digyd...@gmail.com]
Sent: Tuesday, May 04, 2010 10:17 PM
To: 'lucene-net-dev
[
https://issues.apache.org/jira/browse/LUCENENET-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy updated LUCENENET-357:
---
Attachment: Constants.patch
I am thinking of a different patch. With this patch(Constants.patch
[
https://issues.apache.org/jira/browse/LUCENENET-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy updated LUCENENET-357:
---
Summary: Lucene.Net in Medium Trust (Mostly won't work on shared hosts /
Mosso cloud etc due to 'Trust
[
https://issues.apache.org/jira/browse/LUCENENET-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy closed LUCENENET-358.
--
Resolution: Invalid
No response so far.
Closing this issue.
DIGY
CloseableThreadLocal memory leak
[
https://issues.apache.org/jira/browse/LUCENENET-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12864451#action_12864451
]
Digy commented on LUCENENET-357:
Another experience on topic Lucene.Net in Medium Trust
for the project, is possible to put this as improvement in
java version?
You should ask this to Lucene.Java community.
About sharing patch file, put it in other place is a good approach?
No, It would be better to open a JIRA issue.
DIGY
-Original Message-
From: Leonardo Azize Martins
[
https://issues.apache.org/jira/browse/LUCENENET-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12863432#action_12863432
]
Digy commented on LUCENENET-366:
Hi Ben,
Your patches start to divert from the original
[
https://issues.apache.org/jira/browse/LUCENENET-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy resolved LUCENENET-359.
Assignee: Digy
Resolution: Fixed
committed.
DIGY
Spellchecker accuracy gets overwritten
[
https://issues.apache.org/jira/browse/LUCENENET-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy resolved LUCENENET-364.
Assignee: Digy
Resolution: Fixed
We have made similar changes previously.
{quote}
CheckHits
Java
[
https://issues.apache.org/jira/browse/LUCENENET-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12863063#action_12863063
]
Digy commented on LUCENENET-365:
Hi Robert,
Thanks for the patch, but I am not sure
[
https://issues.apache.org/jira/browse/LUCENENET-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy resolved LUCENENET-360.
Assignee: Digy
Resolution: Fixed
Thanks Ben.
I changed it to SetAccuracy.
DIGY
Spellchecker
[
https://issues.apache.org/jira/browse/LUCENENET-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12861446#action_12861446
]
Digy commented on LUCENENET-358:
Hi Rezgar,
After applying your patch many NUnit test
[
https://issues.apache.org/jira/browse/LUCENENET-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12859967#action_12859967
]
Digy commented on LUCENENET-357:
Thanks Robert.
I committed the patch.
DIGY
Mostly
[
https://issues.apache.org/jira/browse/LUCENENET-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12859414#action_12859414
]
Digy commented on LUCENENET-357:
{quote}
Btw: Should I be using this version (2.9
[
https://issues.apache.org/jira/browse/LUCENENET-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12859521#action_12859521
]
Digy commented on LUCENENET-357:
Sorry Frank,
It is not that easy just to say use cache
[
https://issues.apache.org/jira/browse/LUCENENET-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy resolved LUCENENET-355.
Assignee: Digy
Resolution: Fixed
Patch committed.
DIGY
[LUCENE-2387] IndexWriter retains
[
https://issues.apache.org/jira/browse/LUCENENET-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy resolved LUCENENET-356.
Resolution: Won't Fix
Lucene 2.0.0.4 is too old to fix.
Please use a newer one. (I would recommend
Project: Lucene.Net
Issue Type: Bug
Reporter: Digy
Priority: Minor
See LUCENE-2387 .
DIGY
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure
[
https://issues.apache.org/jira/browse/LUCENENET-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy updated LUCENENET-355:
---
Attachment: LUCENE-2387.patch
A simple patch. All tests pass.
If no one objects I plan to commit in a day
[
https://issues.apache.org/jira/browse/LUCENENET-113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12857005#action_12857005
]
Digy commented on LUCENENET-113:
Hi Judah,
Have you tried a newer version of Lucene.Net
[
https://issues.apache.org/jira/browse/LUCENENET-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy closed LUCENENET-354.
--
Resolution: Won't Fix
The StandardAnalyzer tokenizer doesn't tokenize on all tokens when numbers
[
https://issues.apache.org/jira/browse/LUCENENET-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy closed LUCENENET-346.
--
Resolution: Won't Fix
If Lucene.Net is used under ASP.NET with impersonation enabled, accessing
[
https://issues.apache.org/jira/browse/LUCENENET-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy resolved LUCENENET-353.
Resolution: Fixed
Thanks Paulo for reporting this.
I committed the patch.
DIGY
[
https://issues.apache.org/jira/browse/LUCENENET-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy resolved LUCENENET-350.
Resolution: Fixed
Thanks Bianco.
I committed the LUCENENET-350.patch
DIGY
Performance enhancement
[
https://issues.apache.org/jira/browse/LUCENENET-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy closed LUCENENET-173.
--
Resolution: Won't Fix
As Robert previously mentioned, I don't think that Lucene.Net needs a custom
build
[
https://issues.apache.org/jira/browse/LUCENENET-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12847564#action_12847564
]
Digy commented on LUCENENET-346:
Hi Chris,
If you don't have any objections, I
[
https://issues.apache.org/jira/browse/LUCENENET-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy updated LUCENENET-353:
---
Attachment: FSDirectory.patch
FSDirectory.FileModified returns now milliseconds since the epoch (00:00:00
[
https://issues.apache.org/jira/browse/LUCENENET-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy resolved LUCENENET-351.
Resolution: Fixed
Thanks B.
( It is very hard to type your nick. Don't you have a shorter one
[
https://issues.apache.org/jira/browse/LUCENENET-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy updated LUCENENET-351:
---
Attachment: LuceneDictionary.patch
If no one objects, I will commit.
DIGY
spellcheck can fail
[
https://issues.apache.org/jira/browse/LUCENENET-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy resolved LUCENENET-349.
Resolution: Fixed
Thanks Bianco. I committed a small variation of your patch (as in
FVH.Java
[
https://issues.apache.org/jira/browse/LUCENE-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12843261#action_12843261
]
Digy commented on LUCENE-1889:
--
bq. One thing i noticed immediately is that many query types
Added to Contrib.Net.
DIGY
-Original Message-
From: Michael Garski [mailto:mgar...@myspace-inc.com]
Sent: Monday, March 08, 2010 7:38 PM
To: lucene-net-dev@lucene.apache.org
Subject: RE: [jira] Commented: (LUCENENET-345) [Contrib] Extensions
Committed. I'm open to any and all additions
[
https://issues.apache.org/jira/browse/LUCENENET-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy closed LUCENENET-289.
--
Resolution: Won't Fix
Just use
parser.SetMultiTermRewriteMethod
[
https://issues.apache.org/jira/browse/LUCENENET-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy closed LUCENENET-328.
--
Resolution: Not A Problem
trunk is the only place where all active work is done and where a new version
[
https://issues.apache.org/jira/browse/LUCENENET-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12841985#action_12841985
]
Digy commented on LUCENENET-347:
I committed LUCENENET-347-Terms-Boolean.patch
DIGY
[
https://issues.apache.org/jira/browse/LUCENENET-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12840899#action_12840899
]
Digy commented on LUCENENET-347:
With this issue, no need for Similarity.Net
see http
[
https://issues.apache.org/jira/browse/LUCENENET-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy resolved LUCENENET-23.
---
Resolution: Fixed
v2.9.2 is in contrib/Queries.Net now.
add c# version of FuzzyLikeThisQuery.java
I would store the min max in a location other than lucene index(file,db etc.)
and update them while indexing.
DIGY
-Original Message-
From: Ranga [mailto:ra...@capdigisoft.com]
Sent: Monday, March 01, 2010 4:08 PM
To: lucene-net-dev@lucene.apache.org
Subject: Finding minimum
[
https://issues.apache.org/jira/browse/LUCENENET-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12839797#action_12839797
]
Digy commented on LUCENENET-345:
bq. Great to see you are have a few items
[
https://issues.apache.org/jira/browse/LUCENENET-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy resolved LUCENENET-341.
Resolution: Fixed
Thanks Andy. All paches applied.
DIGY
Fix Compiler warnings to worry about
It's nearly time to get this as an official release and allow us to move
forward with 3.0. (or to maintain version parity with Java, 3.0.1)
3.0.1 and 2.9.2 are equal from the bugfix level, only deprecated methods are
removed. We should also consider jumping directly to 3.1.
DIGY
-Original
[
https://issues.apache.org/jira/browse/LUCENENET-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12835307#action_12835307
]
Digy commented on LUCENENET-340:
+1 for me too. But a new patch is needed for 2.9.2
DIGY
[
https://issues.apache.org/jira/browse/LUCENENET-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy updated LUCENENET-340:
---
Comment: was deleted
(was: +1 for me too. But a new patch is needed for 2.9.2
DIGY
[
https://issues.apache.org/jira/browse/LUCENENET-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12833598#action_12833598
]
Digy commented on LUCENENET-336:
The patch is getting bigger and bigger.
What about
svn up at /www/incubator.apache.org/lucene.net has never worked. Therefore
I changed only index.html.
DIGY
-Original Message-
From: George Aroush [mailto:geo...@aroush.net]
Sent: Tuesday, February 09, 2010 5:26 AM
To: lucene-net-dev@lucene.apache.org
Subject: RE: svn commit: r903444
[
https://issues.apache.org/jira/browse/LUCENENET-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy closed LUCENENET-334.
--
Resolution: Duplicate
see LUCENENET-336
DIGY
[LUCENE-2086] When resolving deletes, IW should resolve
[
https://issues.apache.org/jira/browse/LUCENENET-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy updated LUCENENET-338:
---
Attachment: Term.patch
Serialized queries function unreliably
[
https://issues.apache.org/jira/browse/LUCENENET-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy updated LUCENENET-338:
---
Attachment: TestSupportClass.patch
Test case.
DIGY
Serialized queries function unreliably
[
https://issues.apache.org/jira/browse/LUCENENET-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12800350#action_12800350
]
Digy commented on LUCENENET-336:
There is another update for 2.9.2
(https
[
https://issues.apache.org/jira/browse/LUCENENET-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy updated LUCENENET-336:
---
Attachment: Lucene.NET.2.9.2.patch
Shortcut for Lucene.NET 2.9.1 -- 2.9.2
[
https://issues.apache.org/jira/browse/LUCENENET-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy updated LUCENENET-332:
---
Description: https://issues.apache.org/jira/browse/LUCENE-2092
[LUCENE-2092] BooleanQuery.hashCode
Issue Type: Bug
Reporter: Digy
https://issues.apache.org/jira/browse/LUCENE-2095
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[
https://issues.apache.org/jira/browse/LUCENENET-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy updated LUCENENET-334:
---
Description: https://issues.apache.org/jira/browse/LUCENE-2092
[LUCENE-2086] When resolving deletes, IW
[
https://issues.apache.org/jira/browse/LUCENENET-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12797814#action_12797814
]
Digy commented on LUCENENET-334:
I translated TreeMap
[
https://issues.apache.org/jira/browse/LUCENE-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12784373#action_12784373
]
Digy commented on LUCENE-1581:
--
What about adding a new option to ASCIIFoldingFilter just
[
https://issues.apache.org/jira/browse/LUCENE-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12784405#action_12784405
]
Digy commented on LUCENE-1581:
--
OK. thanks.
DIGY
LowerCaseFilter should be able
[
https://issues.apache.org/jira/browse/LUCENE-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12693528#action_12693528
]
Digy commented on LUCENE-1581:
--
I believe also that Character.toLowerCase in Java works ok
[
https://issues.apache.org/jira/browse/LUCENE-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12693553#action_12693553
]
Digy commented on LUCENE-1581:
--
Although, it is not directly related to this issue
Issue Type: Bug
Reporter: Digy
Priority: Minor
Attachments: ISOLatin1AccentFilter.patch
Below mappings are missing
Ğ -- G
ğ -- g
İ -- I
ı -- i
Ş -- S
ş -- s
DIGY
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment
[
https://issues.apache.org/jira/browse/LUCENE-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Digy updated LUCENE-1580:
-
Attachment: ISOLatin1AccentFilter.patch
ISOLatin1AccentFilter does not handle Turkish (UTF-8) chars correctly
Issue Type: Improvement
Reporter: Digy
//Since I am a .Net programmer, Sample codes will be in c# but I don't think
that it would be a problem to understand them.
//
Assume an input text like İ and and analyzer like below
{code}
public class SomeAnalyzer : Analyzer
Or a home made md5 (without using
System.Security.Cryptography.MD5/java.security.MessageDigest) ?
DIGY
-Original Message-
From: Michael McCandless [mailto:luc...@mikemccandless.com]
Sent: Wednesday, March 11, 2009 11:08 PM
To: java-dev@lucene.apache.org
Subject: Re: FIPS compliance
Thanks Mike.
DIGY
-Original Message-
From: Michael McCandless [mailto:luc...@mikemccandless.com]
Sent: Tuesday, March 10, 2009 10:43 PM
To: java-dev@lucene.apache.org
Subject: Re: FIPS compliance?
Interesting... I wonder if in any java runtime there's ever a
rejection of a
known
in Lucene?
Thanks,
DIGY
SampleCode:
public class MainClass
{
DummyTokenStream DummyTokenStream1 = new DummyTokenStream();
DummyTokenStream DummyTokenStream2 = new DummyTokenStream();
//use the same documentfield instances for Indexing
[
https://issues.apache.org/jira/browse/LUCENE-1029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536510
]
Digy commented on LUCENE-1029:
--
I think , the phrase
+ * Please note that the replacements performed by this filter
301 - 365 of 365 matches
Mail list logo
