I ran smokeTestRelease.py on Windows+Cygwin. Several ***WARNING***: javadocs
want to fail! messages.
And also javadocs warnings that did trigger a failure under Solr:
unpack apache-solr-4.0.0-ALPHA.zip...
test solr example w/ Java 6...
File
Build: https://builds.apache.org/job/Lucene-Solr-tests-only-trunk/14655/
1 tests failed.
FAILED:
junit.framework.TestSuite.org.apache.solr.handler.TestReplicationHandler
Error Message:
ERROR: SolrIndexSearcher opens=74 closes=73
Stack Trace:
java.lang.AssertionError: ERROR: SolrIndexSearcher
[
https://issues.apache.org/jira/browse/LUCENE-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292486#comment-13292486
]
Uwe Schindler commented on LUCENE-3312:
---
I think as we have 2 interfaces, we should
[
https://issues.apache.org/jira/browse/LUCENE-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292488#comment-13292488
]
Chris Male commented on LUCENE-3312:
Yeah StoredDocument should only consist of
Because Java 6 is going EOL, we plan to upgrade to Java 7 at some point
in the next few months. In order to ensure that it goes smoothly, we
will only update one index at a time. This means that the SolrJ program
will be running on a different Java version than one of the indexes, and
the
Build: https://builds.apache.org/job/Solr-4.x/6/
1 tests failed.
REGRESSION: org.apache.solr.cloud.OverseerTest.testShardAssignmentBigger
Error Message:
could not find counter for shard:null
Stack Trace:
java.lang.AssertionError: could not find counter for shard:null
at
Found the bug -- it's a concurrency issue in DirTaxoWriter -- it now
supports addCategory being called concurrently, however not all code paths
support it well. I'll reopen LUCENE-4061 where these changes were made. The
solution shouldn't be too complicated.
Sorry for noise
Shai
On Sat, Jun 9,
[
https://issues.apache.org/jira/browse/LUCENE-4061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shai Erera reopened LUCENE-4061:
TestDirectoryTaxonomyWriter.testConcurrency sometimes fails on mismatch number
of categories.
This
Build: https://builds.apache.org/job/Solr-trunk/1881/
1 tests failed.
REGRESSION: org.apache.solr.cloud.BasicZkTest.testBasic
Error Message:
Cannot talk to ZooKeeper - Updates are disabled.
Stack Trace:
org.apache.solr.common.SolrException: Cannot talk to ZooKeeper - Updates are
disabled.
On Sun, Jun 10, 2012 at 2:04 AM, Steven A Rowe sar...@syr.edu wrote:
I ran smokeTestRelease.py on Windows+Cygwin. Several ***WARNING***:
javadocs want to fail! messages.
these are ok and expected, it means there exist some public/protected
classes without javadocs :)
we cant totally enforce
There is a text file explaining this: JRE_VERSION_MIGRATION.txt
here is a link to the one from the latest nightly build:
https://builds.apache.org/job/Lucene-trunk/javadoc/JRE_VERSION_MIGRATION.html
On Sun, Jun 10, 2012 at 6:36 AM, Shawn Heisey s...@elyograg.org wrote:
Because Java 6 is going
[
https://issues.apache.org/jira/browse/SOLR-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292507#comment-13292507
]
Mike Sokolov commented on SOLR-3284:
Another approach we have been using in a similar
[
https://issues.apache.org/jira/browse/SOLR-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292507#comment-13292507
]
Mike Sokolov edited comment on SOLR-3284 at 6/10/12 12:14 PM:
--
Robert Muir created LUCENE-4127:
---
Summary: negative offsets/deltas corrumption
Key: LUCENE-4127
URL: https://issues.apache.org/jira/browse/LUCENE-4127
Project: Lucene - Java
Issue Type: Bug
[
https://issues.apache.org/jira/browse/LUCENE-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-4127:
Attachment: LUCENE-4127_test.patch
Here are some dead-simple tests.
negative
[
https://issues.apache.org/jira/browse/LUCENE-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292510#comment-13292510
]
Robert Muir commented on LUCENE-4127:
-
just my opinion, I tend towards #1 here. I
[
https://issues.apache.org/jira/browse/LUCENE-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292512#comment-13292512
]
Michael McCandless commented on LUCENE-4101:
How about TYPE_NOT_STORED?
[
https://issues.apache.org/jira/browse/LUCENE-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292513#comment-13292513
]
Michael McCandless commented on LUCENE-4127:
+1 to strongly type offsets.
[
https://issues.apache.org/jira/browse/LUCENE-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292516#comment-13292516
]
Chris Male commented on LUCENE-4101:
I like that more. Another alternative instead
[
https://issues.apache.org/jira/browse/LUCENE-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292519#comment-13292519
]
Michael McCandless commented on LUCENE-4101:
Well ... both types are indexed;
Build: http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Linux-Java7-64/49/
2 tests failed.
FAILED:
junit.framework.TestSuite.org.apache.lucene.queryparser.flexible.standard.TestNumericQueryParser
Error Message:
Unparseable date: 1863.06.07 19時48分37秒 CST 37 -0600 1863
Stack Trace:
[
https://issues.apache.org/jira/browse/LUCENE-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292520#comment-13292520
]
Chris Male commented on LUCENE-4101:
bq. We could, alternatively, not make these
[
https://issues.apache.org/jira/browse/LUCENE-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292521#comment-13292521
]
Robert Muir commented on LUCENE-4101:
-
I like TYPE_UNSTORED better than
[
https://issues.apache.org/jira/browse/LUCENE-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292522#comment-13292522
]
Chris Male commented on LUCENE-4101:
The Type doesn't unstore anything though. That
[
https://issues.apache.org/jira/browse/LUCENE-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292523#comment-13292523
]
Steven Rowe commented on LUCENE-4101:
-
bq. I like TYPE_UNSTORED better than
[
https://issues.apache.org/jira/browse/LUCENE-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292526#comment-13292526
]
Robert Muir commented on LUCENE-4101:
-
yeah less words :)
but this matters much less
[
https://issues.apache.org/jira/browse/LUCENE-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-4127:
---
Attachment: LUCENE-4127.patch
I think we should also strongly check posIncr coming
[
https://issues.apache.org/jira/browse/LUCENE-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292528#comment-13292528
]
Robert Muir commented on LUCENE-4127:
-
+1! i feel like we should be able to
Build:
http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Windows-Java7-64/286/
1 tests failed.
REGRESSION: org.apache.solr.handler.TestReplicationHandler.test
Error Message:
expected:498 but was:0
Stack Trace:
java.lang.AssertionError: expected:498 but was:0
at
[
https://issues.apache.org/jira/browse/LUCENE-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-4127:
Attachment: LUCENE-4127_offsetAtt.patch
Here's a patch adding the stateless checks to
Is the intent that there be only one alpha and one beta, or could there be a
series of either if bugs and improvements are significant enough?
I reviewed the Solr 4.0 wiki, which sounds as if the intent is for a single
alpha and a single beta, but I am wondering if that makes sense given the
On Sun, Jun 10, 2012 at 11:22 AM, Jack Krupansky
j...@basetechnology.com wrote:
So, I would suggest that there be a series of alpha releases (and betas) as
significant bug fixes and improvements accumulate.
I won't do this. Someone else can if they want. Releasing is too
time-consuming, you
Build:
http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Linux-Java7-64/233/
3 tests failed.
REGRESSION:
org.apache.solr.handler.dataimport.TestSqlEntityProcessorDeltaPrefixedPk.testDeltaImport_replace_resolvesUnprefixedPk
Error Message:
Exception during query
Stack Trace:
[
https://issues.apache.org/jira/browse/LUCENE-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-4116:
Affects Version/s: 5.0
4.0
Fix Version/s: 5.0
[
https://issues.apache.org/jira/browse/LUCENE-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-4116:
Attachment: LUCENE-4116.patch
this is actually a test bug. I improved the test in this
[
https://issues.apache.org/jira/browse/LUCENE-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer resolved LUCENE-4116.
-
Resolution: Fixed
Lucene Fields: New,Patch Available (was: New)
committed to
[
https://issues.apache.org/jira/browse/LUCENE-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292540#comment-13292540
]
Uwe Schindler commented on LUCENE-4116:
---
Thanks!
Jenkins failure:
Maybe beta RC's would fit the same need as additional alpha releases. Maybe
a new beta RC every week or two as significant changes accumulate would
satisfy user needs.
Maybe the real value in having an alpha release is not the release itself
(since nightly builds are readily available) but to
[
https://issues.apache.org/jira/browse/LUCENE-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-4127:
Attachment: LUCENE-4127.patch
Here's a patch: I think its committable (e.g. so we can get alpha
[
https://issues.apache.org/jira/browse/LUCENE-4127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292543#comment-13292543
]
Michael McCandless commented on LUCENE-4127:
+1
negative
Synchonizer - Synchronizer?
D.
On Sun, Jun 10, 2012 at 6:42 PM, sim...@apache.org wrote:
Author: simonw
Date: Sun Jun 10 16:42:55 2012
New Revision: 1348623
URL: http://svn.apache.org/viewvc?rev=1348623view=rev
Log:
LUCENE-4116: fix concurrency test for DWPTStallControl
Modified:
[
https://issues.apache.org/jira/browse/LUCENE-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292545#comment-13292545
]
Dawid Weiss commented on LUCENE-4115:
-
Hmm... I don't think the use of ivy should
Robert Muir created LUCENE-4128:
---
Summary: add safety to preflex segmentinfo upgrade
Key: LUCENE-4128
URL: https://issues.apache.org/jira/browse/LUCENE-4128
Project: Lucene - Java
Issue Type:
[
https://issues.apache.org/jira/browse/LUCENE-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless reassigned LUCENE-4128:
--
Assignee: Michael McCandless
add safety to preflex segmentinfo upgrade
[
https://issues.apache.org/jira/browse/LUCENE-4101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-4101.
Resolution: Fixed
Remove XXXField.TYPE_STORED
---
On 6/10/2012 5:59 AM, Robert Muir wrote:
There is a text file explaining this: JRE_VERSION_MIGRATION.txt
here is a link to the one from the latest nightly build:
https://builds.apache.org/job/Lucene-trunk/javadoc/JRE_VERSION_MIGRATION.html
I've seen that already. That tells me that I should
[
https://issues.apache.org/jira/browse/SOLR-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292573#comment-13292573
]
Shawn Heisey commented on SOLR-3284:
Lance, if your idea (or your idea in combination
Hi Shawn,
It is correct, the JRE_VERSION_MIGRATION.txt / .html (in trunk/4.0) is about
Lucene and Indexing. In fact, the changes in Unicode versions affecting
analysis (as this guide describes). SolrJ does not do any analysis, is just
passes the String/native types down to solr uon the wire.
Build:
http://jenkins.sd-datasolutions.de/job/Lucene-Solr-trunk-Windows-Java6-64/499/
1 tests failed.
REGRESSION: org.apache.solr.spelling.suggest.SuggesterTSTTest.testSuggestions
Error Message:
Exception during query
Stack Trace:
java.lang.RuntimeException: Exception during query
at
Build:
http://jenkins.sd-datasolutions.de/job/Lucene-Solr-4.x-Windows-Java7-64/37/
1 tests failed.
REGRESSION: org.apache.solr.handler.TestReplicationHandler.test
Error Message:
expected:498 but was:0
Stack Trace:
java.lang.AssertionError: expected:498 but was:0
at
[
https://issues.apache.org/jira/browse/LUCENE-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292620#comment-13292620
]
John Berryman commented on LUCENE-2605:
---
subscribed - Current client has index full
[
https://issues.apache.org/jira/browse/SOLR-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292622#comment-13292622
]
Erik Hatcher commented on SOLR-3529:
Just some thoughts I have about the analysis page:
[
https://issues.apache.org/jira/browse/SOLR-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292623#comment-13292623
]
Erik Hatcher commented on SOLR-3529:
One thought about all those attributes... what
[
https://issues.apache.org/jira/browse/LUCENE-2605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13292620#comment-13292620
]
John Berryman edited comment on LUCENE-2605 at 6/11/12 2:53 AM:
According to https://issues.apache.org/jira/browse/LUCENE-2605, the Lucene
QueryParser tokenizes on white space before giving any text to the
Analyzer. This makes it impossible to use multi-term synonyms because the
SynonymFilter only receives one word at a time.
Resolution to this would really
55 matches
Mail list logo
