[
https://issues.apache.org/jira/browse/SOLR-7638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14579892#comment-14579892
]
ASF subversion and git services commented on SOLR-7638:
---
Commit
[
https://issues.apache.org/jira/browse/SOLR-7638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher resolved SOLR-7638.
Resolution: Fixed
Thanks [~upayavira]!
Angular UI cloud pane broken
laigood created SOLR-7657:
-
Summary: Mapreduce indexing not work on hadoop2.5.1
Key: SOLR-7657
URL: https://issues.apache.org/jira/browse/SOLR-7657
Project: Solr
Issue Type: Bug
I’ve gotten the two fixes (new admin Cloud UI and example/files
update-script.js) into 5_2 branch. Bring on the 5.2.1 RC!
—
Erik Hatcher, Senior Solutions Architect
http://www.lucidworks.com http://www.lucidworks.com/
On Jun 9, 2015, at 2:42 PM, Upayavira u...@odoko.co.uk wrote:
I'd
[
https://issues.apache.org/jira/browse/SOLR-7657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
laigood updated SOLR-7657:
--
Description:
In early solr5,mapreduce indexing work fine,but when i upgrade to solr5+,run
the same mr,it throw
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/13006/
Java: 32bit/jdk1.8.0_45 -client -XX:+UseParallelGC
1 tests failed.
FAILED: junit.framework.TestSuite.org.apache.solr.cloud.HttpPartitionTest
Error Message:
ObjectTracker found 1 object(s) that were not released!!!
Build: https://builds.apache.org/job/Lucene-Solr-Tests-trunk-Java8/58/
1 tests failed.
REGRESSION: org.apache.solr.handler.TestReplicationHandlerBackup.doTestBackup
Error Message:
Failed to create backup
Stack Trace:
java.lang.AssertionError: Failed to create backup
at
[
https://issues.apache.org/jira/browse/SOLR-7638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14579886#comment-14579886
]
ASF subversion and git services commented on SOLR-7638:
---
Commit
[
https://issues.apache.org/jira/browse/LUCENE-6537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14578906#comment-14578906
]
Robert Muir commented on LUCENE-6537:
-
Is it supposed to behave differently? I tried
On Jun 9, 2015, at 8:57 AM, Shalin Shekhar Mangar shalinman...@gmail.com
wrote:
Looks like there are several small fixes that need to be added. I'll cut an
RC tomorrow morning India time so that we have enough time to back port these
items.
I'll also setup a local Jenkins build for
[
https://issues.apache.org/jira/browse/LUCENE-6537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14578911#comment-14578911
]
Alan Woodward commented on LUCENE-6537:
---
It should return the same document
[
https://issues.apache.org/jira/browse/LUCENE-6277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14578913#comment-14578913
]
ASF subversion and git services commented on LUCENE-6277:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-6537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14578917#comment-14578917
]
Alan Woodward commented on LUCENE-6537:
---
It looks as though there's an extra hit in
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-MacOSX/2405/
Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC
1 tests failed.
FAILED: org.apache.solr.cloud.CollectionsAPIDistributedZkTest.test
Error Message:
Captured an uncaught exception in thread: Thread[id=10076,
Hi,
The version of the JAR files produced is still 5.2.0, should be 5.2.1!
In addition (that is causing failure here): The smoke tester for 5.2 complains:
The 5.2.0 index is missing for backwards compatibility testing. I think this
commit must be backported, too.
So I think the release update
madeeha ameer created SOLR-7658:
---
Summary: what happens when solr index limit exceeds
Key: SOLR-7658
URL: https://issues.apache.org/jira/browse/SOLR-7658
Project: Solr
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/LUCENE-6535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright updated LUCENE-6535:
Attachment: LUCENE-6535.patch
Fix; passes all tests for me.
Geo3D test failure, June 6th
Alan Woodward created LUCENE-6537:
-
Summary: Make NearSpansOrdered use lazy iteration
Key: LUCENE-6537
URL: https://issues.apache.org/jira/browse/LUCENE-6537
Project: Lucene - Core
Issue
[
https://issues.apache.org/jira/browse/LUCENE-6537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Woodward updated LUCENE-6537:
--
Attachment: LUCENE-6537.patch
Patch moving NearSpansOrdered to a lazy algorithm. This makes
[
https://issues.apache.org/jira/browse/LUCENE-6537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14578895#comment-14578895
]
Adrien Grand commented on LUCENE-6537:
--
+1
Make NearSpansOrdered use lazy
[
https://issues.apache.org/jira/browse/LUCENE-6537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14578870#comment-14578870
]
Alan Woodward commented on LUCENE-6537:
---
NearSpansOrdered uses an eager algorithm
[
https://issues.apache.org/jira/browse/LUCENE-6371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14578880#comment-14578880
]
Alan Woodward commented on LUCENE-6371:
---
I opened LUCENE-6537
Improve Spans
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/13008/
Java: 64bit/jdk1.8.0_60-ea-b12 -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC
1 tests failed.
FAILED: org.apache.solr.cloud.BasicDistributedZkTest.test
Error Message:
commitWithin did not work on node:
[
https://issues.apache.org/jira/browse/SOLR-7655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated SOLR-7655:
---
Attachment: SOLR-7655.patch
Here's a patch; a little better than the suggested fix: the Terms returned
Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Windows/4790/
Java: 64bit/jdk1.8.0_45 -XX:-UseCompressedOops -XX:+UseG1GC
2 tests failed.
FAILED:
junit.framework.TestSuite.org.apache.solr.cloud.LeaderInitiatedRecoveryOnCommitTest
Error Message:
Suite timeout exceeded (= 720 msec).
Hi Shawn,
That comment about commitReserveDuration is not accurate. It has nothing to
do with the size of the index. It is the time for which commits are
reserved even if no request has accessed them. A commit and its related
files will never be deleted as long as a request is fetching them. The
201 - 226 of 226 matches
Mail list logo