[
https://issues.apache.org/jira/browse/LUCENE-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12796601#action_12796601
]
Ramazan VARLIKLI commented on LUCENE-2192:
--
Hi Michael ,
What I am doing is
[
https://issues.apache.org/jira/browse/LUCENE-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12796624#action_12796624
]
Michael McCandless commented on LUCENE-2192:
Given that you're creating a new
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/tag
name, and run those tests against current trunk. This catches us if
we accidentally break back-compat.
Sometimes changes to trunk require acceptable changes to
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 geo...@aroush.net wrote:
Hi Folks,
Over at Lucene.Net, we have 2.9.1 ready for official release. This
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
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,
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
eMail:
[
https://issues.apache.org/jira/browse/LUCENE-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12796658#action_12796658
]
Ramazan VARLIKLI commented on LUCENE-2192:
--
I found the problem finally with
[
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-tabpanelfocusedCommentId=12796674#action_12796674
]
Michael McCandless commented on LUCENE-2192:
OK thanks for bringing closure!
[
https://issues.apache.org/jira/browse/LUCENE-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12796677#action_12796677
]
Jingkei Ly commented on LUCENE-1313:
Thanks Jason, the patch applies cleanly now.
[
https://issues.apache.org/jira/browse/LUCENE-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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:all-tabpanel
]
Jingkei Ly updated LUCENE-1313:
---
Attachment: TestLuceneNRT.java
Jason,
I've attached the benchmarking test I've based my
[
https://issues.apache.org/jira/browse/LUCENE-1313?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12796763#action_12796763
]
Jason Rutherglen commented on LUCENE-1313:
--
{quote}Lucene 3.0 is able to process
[
https://issues.apache.org/jira/browse/LUCENE-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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-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
[
https://issues.apache.org/jira/browse/LUCENE-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12796823#action_12796823
]
Jason Rutherglen commented on LUCENE-2127:
--
Grant,
This issue could be useful
: 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/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
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
[
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
[
https://issues.apache.org/jira/browse/LUCENE-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12796898#action_12796898
]
Aaron McCurry commented on LUCENE-2127:
---
I have implemented a paging collector for
[
https://issues.apache.org/jira/browse/LUCENE-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12796910#action_12796910
]
Simon Willnauer commented on LUCENE-2188:
-
Uwe,
I'm not sure if I have a really
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
[
https://issues.apache.org/jira/browse/LUCENE-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12796971#action_12796971
]
Grant Ingersoll commented on LUCENE-2127:
-
Very cool, Aaron! I've kicked around
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 all
26 matches
Mail list logo
