[
https://issues.apache.org/jira/browse/LUCENE-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292006#comment-13292006
]
Dawid Weiss commented on LUCENE-4115:
-
I know why the jars are locked - it's because
[
https://issues.apache.org/jira/browse/LUCENE-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dawid Weiss updated LUCENE-4115:
Attachment: LUCENE-4115.patch
Corrected patch, checked the build on windows, didn't fail for me.
[
https://issues.apache.org/jira/browse/LUCENE-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292016#comment-13292016
]
Dawid Weiss commented on LUCENE-4115:
-
Hoss -- I've been doing some experiments with
[
https://issues.apache.org/jira/browse/LUCENE-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292020#comment-13292020
]
Dawid Weiss commented on LUCENE-4115:
-
One thing I didn't know how to work around
[
https://issues.apache.org/jira/browse/LUCENE-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292022#comment-13292022
]
Simon Willnauer commented on LUCENE-4101:
-
do we really need to block 4.0 for
Hoss Man created SOLR-3529:
--
Summary: clarify distnction between index query tables on
analysis debug pages
Key: SOLR-3529
URL: https://issues.apache.org/jira/browse/SOLR-3529
Project: Solr
Issue
[
https://issues.apache.org/jira/browse/SOLR-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-3529:
---
Attachment: med-side-by-side.png
med-side-by-side-below-fold.png
[
https://issues.apache.org/jira/browse/SOLR-3528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292059#comment-13292059
]
Hoss Man commented on SOLR-3528:
* given that we now display all of the token attributes,
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-4.x/33/
1 tests failed.
REGRESSION: org.apache.lucene.index.TestNorms.testIllegalCustomEncoder
Error Message:
Codec only supports single byte norm values. Type give: FLOAT_32
Stack Trace:
java.lang.UnsupportedOperationException: Codec
I'll take care of this
On Fri, Jun 8, 2012 at 6:55 PM, Apache Jenkins Server
jenk...@builds.apache.org wrote:
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-4.x/33/
1 tests failed.
REGRESSION: org.apache.lucene.index.TestNorms.testIllegalCustomEncoder
Error Message:
Codec
[
https://issues.apache.org/jira/browse/LUCENE-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292079#comment-13292079
]
Hoss Man commented on LUCENE-4115:
--
bq. I agree with you 100% that we shouldn't be doing
[
https://issues.apache.org/jira/browse/SOLR-3526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292082#comment-13292082
]
Hoss Man commented on SOLR-3526:
I'll defer on the large topic to miller/yonik/sami, but as
Robert Muir created LUCENE-4125:
---
Summary: AvoidCodecs (and maybe similar nearby logic) still runs
BeforeClass
Key: LUCENE-4125
URL: https://issues.apache.org/jira/browse/LUCENE-4125
Project: Lucene -
[
https://issues.apache.org/jira/browse/SOLR-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292097#comment-13292097
]
Hoss Man commented on SOLR-3497:
I don't understand this request.
I don't see any way that
Wait a minute ... why do we still have all of these
solr/contrib/*/CHANGES.txt files? ... i thought we decided a long time
ago to consolidate everything into ./lucene/CHANGES.txt and
./solr/CHANGES.txt ?
: $ find . -name CHANGES.txt
: ./lucene/CHANGES.txt
: ./solr/CHANGES.txt
:
[
https://issues.apache.org/jira/browse/LUCENE-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated LUCENE-2073:
-
Fix Version/s: (was: 4.1)
4.0
Assignee: Robert Muir
rmuir already wrote
Hoss Man created SOLR-3530:
--
Summary: better error messages / Content-Type validation in solrJ
Key: SOLR-3530
URL: https://issues.apache.org/jira/browse/SOLR-3530
Project: Solr
Issue Type:
[
https://issues.apache.org/jira/browse/LUCENE-3949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated LUCENE-3949:
-
Attachment: LUCENE-3949.patch
fix-license-jdoc.pl
Here's a script to mass fix
[
https://issues.apache.org/jira/browse/LUCENE-3949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man reassigned LUCENE-3949:
Assignee: Hoss Man
Fix license headers in all Java files to not be in Javadocs /** format
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/14643/
1 tests failed.
REGRESSION: org.apache.solr.cloud.OverseerTest.testShardLeaderChange
Error Message:
Unexpected shard leader coll:collection1 shard:shard1 expected:core[1] but
was:core[4]
Stack Trace:
Build:
http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Windows-Java6-64/27/
1 tests failed.
REGRESSION: org.apache.solr.handler.TestReplicationHandler.test
Error Message:
expected:494 but was:0
Stack Trace:
java.lang.AssertionError: expected:494 but was:0
at
[
https://issues.apache.org/jira/browse/LUCENE-2899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lance Norskog updated LUCENE-2899:
--
Attachment: LUCENE-2899.patch
License-ready.
Ivy-ready.
OpenNLP libraries available through
I am not sure what the issue is.
This is working for me...
On Fri, Jun 8, 2012 at 8:35 AM, Jason Rutherglen (JIRA) j...@apache.org wrote:
[
Does this mean there are no more index format change plans in the
pipeline for 4.0?
On Fri, Jun 8, 2012 at 7:54 PM, Robert Muir rcm...@gmail.com wrote:
Please vote to release these artifacts: http://s.apache.org/lusolr40arc0
--
lucidimagination.com
It only means there is a vote for 4.0 alpha. if it succeeds, we will
support the index format (with the caveat if there is a huge blocker
bug, we will fix it correctly, but I think this caveat generally
always applies to any release really).
If the vote fails, we might need to change the format.
If we don't want to add IEnumerable (though it seems that IEnumerable could
be added in parallel with the existing pattern) could we add a bunch of
extension methods?
Something like the following...
{noformat}
public static class LuceneExtensions
{
public static IEnumerableTerm GetEnumerable(this
Hi,
We could add IEnumerableT to TermEnum without affecting the current
api. It would allow things like foreach(var t in reader.Terms()).
Dispose _will_ be called by a foreach statement if the IEnumeratorT
implements IDisposable (not the IEnumerableT). However, the linq
extension methods are
Hi Andy,
I have used similar extension methods for a long time. What I like
especially in extension methods is that they don't require changes in
Lucene.Net kernel and make further ports of Lucene.java independent from
.Net structures.
+1 for a Lucene.Net extensions in contrib. Even a +1 for a
101 - 128 of 128 matches
Mail list logo
