I have http://svn.apache.org/repos/asf/lucene/java/trunk/ and
http://svn.apache.org/repos/asf/lucene/java/tags/ checked out.
I think having all this "back_compat" folders, under the "tags" can be very
confusing, especially for someone who looks in "tags" in search of a
released version and finds a
[
https://issues.apache.org/jira/browse/LUCENE-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796971#action_12796971
]
Grant Ingersoll commented on LUCENE-2127:
-
Very cool, Aaron! I've kicked around t
Yes, the goal is to be 1-to-1 in sync which is how it always has been and
why version number consistency is important.
A Lucene.Net assembly, has version number with 4 digits, like so:
"Lucene.Net 2.9.1.016" -- the last number "016" is used to both signify an
internal release, as the port is progr
[
https://issues.apache.org/jira/browse/LUCENE-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796910#action_12796910
]
Simon Willnauer commented on LUCENE-2188:
-
Uwe,
I'm not sure if I have a really g
[
https://issues.apache.org/jira/browse/LUCENE-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796898#action_12796898
]
Aaron McCurry commented on LUCENE-2127:
---
I have implemented a paging collector for 2
[
https://issues.apache.org/jira/browse/LUCENE-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer resolved LUCENE-2147.
-
Resolution: Fixed
Fix Version/s: 3.1
Committed in revision 896240
Thanks Chris
On Tue, 5 Jan 2010, Chris Hostetter wrote:
: https://issues.apache.org/jira/browse/LUCENENET-331). This begs the
: question, if Lucene.Net takes just this one patch, than Lucene.Net 2.9.1 is
: now 2.9.1.1 (which I personally don't like to see happening as I prefer to
: see a 1-to-1 release mat
: https://issues.apache.org/jira/browse/LUCENENET-331). This begs the
: question, if Lucene.Net takes just this one patch, than Lucene.Net 2.9.1 is
: now 2.9.1.1 (which I personally don't like to see happening as I prefer to
: see a 1-to-1 release match).
As a general comment on this topic: I wo
: Why do I see \java\tags\lucene_*_back_compat_tests_2009*\ directories (well
: over 100 so far) when I SVN update?
Are you saying you have "http://svn.apache.org/repos/asf/lucene/java/";
checked out in it's entirety?
That seems ... problematic. New tags/branches could be created at anytime
-
[
https://issues.apache.org/jira/browse/LUCENE-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796823#action_12796823
]
Jason Rutherglen commented on LUCENE-2127:
--
Grant,
This issue could be useful an
[
https://issues.apache.org/jira/browse/LUCENE-2189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Elschot updated LUCENE-2189:
-
Attachment: LUCENE-2189a.patch
2010, Jan 5: this patch has a good encoder, and includes a good n
[
https://issues.apache.org/jira/browse/LUCENE-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796804#action_12796804
]
Grant Ingersoll commented on LUCENE-2127:
-
I've started work on this by looking at
[
https://issues.apache.org/jira/browse/LUCENE-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796763#action_12796763
]
Jason Rutherglen commented on LUCENE-1313:
--
{quote}Lucene 3.0 is able to process
[
https://issues.apache.org/jira/browse/LUCENE-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jingkei Ly updated LUCENE-1313:
---
Attachment: TestLuceneNRT.java
Jason,
I've attached the benchmarking test I've based my observation
[
https://issues.apache.org/jira/browse/LUCENE-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796705#action_12796705
]
Jason Rutherglen commented on LUCENE-1313:
--
> the patch version seems to be about
[
https://issues.apache.org/jira/browse/LUCENE-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796677#action_12796677
]
Jingkei Ly commented on LUCENE-1313:
Thanks Jason, the patch applies cleanly now.
I'
[
https://issues.apache.org/jira/browse/LUCENE-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796674#action_12796674
]
Michael McCandless commented on LUCENE-2192:
OK thanks for bringing closure!
[
https://issues.apache.org/jira/browse/LUCENE-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramazan VARLIKLI closed LUCENE-2192.
Resolution: Invalid
Yes, The problem is not with Lucene but our application
> Memory Leak
[
https://issues.apache.org/jira/browse/LUCENE-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796661#action_12796661
]
Michael McCandless commented on LUCENE-2192:
So the problem isn't with Lucene
[
https://issues.apache.org/jira/browse/LUCENE-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796658#action_12796658
]
Ramazan VARLIKLI commented on LUCENE-2192:
--
I found the problem finally with you
https://issues.apache.org/jira/browse/SOLR-1657
i just struckthrough the things that are done.
> Mark, Robert: How far are we with progress in solr? Were there any
> additional problems with 3.0.0?
>
> Uwe
>
> -
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
>
Thanks Uwe.
Looks like we are only weeks away (maybe days). If so, then I see a good
reason for Lucene.Net to also release 2.9.2.
Btw, is the complete list of patches for 2.9.2 here:
https://issues.apache.org/jira/browse/LUCENE/fixforversion/12314342 If so,
I see 1 outstanding open issue: LUCEN
I wanted to mention: I wanted to wait a little bit to have progress with the
last transitions in solr to 3.0 (tokenstreams are almost finished), Version
support, and some segment based problems. E.g. in 3.0, we had some methods
accidentally removed with deprecations and so on. In my opinion, transi
My plan was to release it together with 3.0.1. Both version then will have
the same bug fix status.
I have the scripts here to build the artifacts (as I added fast vector
highlighter poms), so I could do it for both and start the release.
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
h
Lucene 2.9.2 hasn't been released yet, but I think we should release
it at some point soonish? It's accumulated some important bug fixes.
Mike
On Mon, Jan 4, 2010 at 10:59 PM, George Aroush wrote:
> Hi Folks,
>
> Over at Lucene.Net, we have 2.9.1 ready for official release. This is a
> port of
This is how we run our back-compat tests. Ie, when you run "ant
test-tag", it will checkout the current back-compat tag into tags/, and run those tests against current trunk. This catches us if
we accidentally break back-compat.
Sometimes changes to trunk require acceptable changes to back-compa
[
https://issues.apache.org/jira/browse/LUCENE-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796624#action_12796624
]
Michael McCandless commented on LUCENE-2192:
Given that you're creating a new
[
https://issues.apache.org/jira/browse/LUCENE-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796601#action_12796601
]
Ramazan VARLIKLI commented on LUCENE-2192:
--
Hi Michael ,
What I am doing is readi
28 matches
Mail list logo
