Lucene Benchmark

Hi guys: Can you guys point me to some details on the Lucene Benchmark module? Specifically the grammar/syntax for the Algorithm files? Thanks -John

[JENKINS] Lucene-Solr-5.x-Windows (32bit/jdk1.7.0_67) - Build # 4231 - Still Failing!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Windows/4231/ Java: 32bit/jdk1.7.0_67 -client -XX:+UseG1GC 1 tests failed. FAILED: org.apache.solr.cloud.DeleteReplicaTest.testDistribSearch Error Message: No live SolrServers available to handle this request:[https://127.0.0.1:63512,

[jira] [Updated] (SOLR-6476) Create a bulk mode for schema API

[ https://issues.apache.org/jira/browse/SOLR-6476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul updated SOLR-6476: - Attachment: SOLR-6476.patch Create a bulk mode for schema API -

[JENKINS] Lucene-Solr-Tests-trunk-Java7 - Build # 4879 - Failure

Build: https://builds.apache.org/job/Lucene-Solr-Tests-trunk-Java7/4879/ 1 tests failed. REGRESSION: org.apache.solr.client.solrj.TestLBHttpSolrServer.testReliability Error Message: No live SolrServers available to handle this request Stack Trace:

[jira] [Updated] (SOLR-6453) Stop throwing an error message from Overseer on Solr exit

[ https://issues.apache.org/jira/browse/SOLR-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul updated SOLR-6453: - Attachment: SOLR-6453.patch I guess this is the right fix Stop throwing an error message from Overseer

Re: Lucene Benchmark

Hi John, It's obvious http://lucene.apache.org/core/4_8_0/benchmark/org/apache/lucene/benchmark/byTask/package-summary.html It's also described in LUA. I just get into it and understand how to use it. Feel free to ask if you face any difficulties. Beware that Lucene devs use

[jira] [Created] (SOLR-6556) User from trusted kerberos realm can't access admin console

Andrejs Dubovskis created SOLR-6556: --- Summary: User from trusted kerberos realm can't access admin console Key: SOLR-6556 URL: https://issues.apache.org/jira/browse/SOLR-6556 Project: Solr

[jira] [Commented] (LUCENE-5975) Lucene can't read 3.0-3.3 deleted documents

[ https://issues.apache.org/jira/browse/LUCENE-5975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14146049#comment-14146049 ] Uwe Schindler commented on LUCENE-5975: --- Thanks for figuring that out! Nice test!

[jira] [Commented] (LUCENE-5569) Rename AtomicReader to LeafReader

[ https://issues.apache.org/jira/browse/LUCENE-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14146075#comment-14146075 ] ASF subversion and git services commented on LUCENE-5569: - Commit

[JENKINS] Lucene-Solr-SmokeRelease-5.x - Build # 196 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-SmokeRelease-5.x/196/ No tests ran. Build Log: [...truncated 51701 lines...] prepare-release-no-sign: [mkdir] Created dir: /usr/home/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-5.x/lucene/build/smokeTestRelease/dist [copy]

[jira] [Commented] (SOLR-6453) Stop throwing an error message from Overseer on Solr exit

[ https://issues.apache.org/jira/browse/SOLR-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14146085#comment-14146085 ] Ramkumar Aiyengar commented on SOLR-6453: - Thanks for picking this up, Noble! Just

[jira] [Commented] (SOLR-6453) Stop throwing an error message from Overseer on Solr exit

[ https://issues.apache.org/jira/browse/SOLR-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14146101#comment-14146101 ] Noble Paul commented on SOLR-6453: -- The objective of that method is to handle the overseer

[jira] [Commented] (SOLR-6453) Stop throwing an error message from Overseer on Solr exit

[ https://issues.apache.org/jira/browse/SOLR-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14146112#comment-14146112 ] Ramkumar Aiyengar commented on SOLR-6453: - Ah, okay, makes sense.. Could you add

[jira] [Comment Edited] (SOLR-6453) Stop throwing an error message from Overseer on Solr exit

[ https://issues.apache.org/jira/browse/SOLR-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14146112#comment-14146112 ] Ramkumar Aiyengar edited comment on SOLR-6453 at 9/24/14 9:19 AM:

[jira] [Commented] (LUCENE-5569) Rename AtomicReader to LeafReader

[ https://issues.apache.org/jira/browse/LUCENE-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14146123#comment-14146123 ] ASF subversion and git services commented on LUCENE-5569: - Commit

[jira] [Resolved] (LUCENE-5569) Rename AtomicReader to LeafReader

[ https://issues.apache.org/jira/browse/LUCENE-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan Ernst resolved LUCENE-5569. Resolution: Fixed Fix Version/s: (was: Trunk) 5.0 Assignee:

[jira] [Commented] (SOLR-6453) Stop throwing an error message from Overseer on Solr exit

[ https://issues.apache.org/jira/browse/SOLR-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14146125#comment-14146125 ] Noble Paul commented on SOLR-6453: -- bq.Also, OverseerTest passed for me with this change,

[jira] [Created] (SOLR-6557) bandwidth cap for large file replication

Kenji Kikuchi created SOLR-6557: --- Summary: bandwidth cap for large file replication Key: SOLR-6557 URL: https://issues.apache.org/jira/browse/SOLR-6557 Project: Solr Issue Type: Improvement

[jira] [Commented] (SOLR-6557) bandwidth cap for large file replication

[ https://issues.apache.org/jira/browse/SOLR-6557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14146131#comment-14146131 ] Ramkumar Aiyengar commented on SOLR-6557: - Does SOLR-6485 do what you are looking

[jira] [Updated] (SOLR-6557) bandwidth cap for large file replication

[ https://issues.apache.org/jira/browse/SOLR-6557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kenji Kikuchi updated SOLR-6557: Attachment: SOLR-replication_bandwidth.patch Please review the patch attached. If there are any

[jira] [Resolved] (LUCENE-5863) Generate backwards compatibility indexes for all 4.x releases

[ https://issues.apache.org/jira/browse/LUCENE-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-5863. Resolution: Fixed This is done right? We now have smoke tester checking this...

Re: [JENKINS] Lucene-Solr-SmokeRelease-5.x - Build # 196 - Still Failing

I am extremely close from disabling this analytics module, as i mentioned last week. Guys the solr build is still fucking broken. On Wed, Sep 24, 2014 at 4:46 AM, Apache Jenkins Server jenk...@builds.apache.org wrote: Build: https://builds.apache.org/job/Lucene-Solr-SmokeRelease-5.x/196/ No

[jira] [Commented] (SOLR-6460) Keep transaction logs around longer

[ https://issues.apache.org/jira/browse/SOLR-6460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14146174#comment-14146174 ] Renaud Delbru commented on SOLR-6460: - Hi, here is an initial analysis and proposal

Re: How to traverse automaton with new api?

Thanks a lot, Mike! I should have checked it first thing! On 23 September 2014 17:47, Michael McCandless luc...@mikemccandless.com wrote: Try looking at the sources for Automaton.toDot? It does a similar traversal... Mike McCandless http://blog.mikemccandless.com On Tue, Sep 23, 2014

[jira] [Commented] (SOLR-6557) bandwidth cap for large file replication

[ https://issues.apache.org/jira/browse/SOLR-6557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14146201#comment-14146201 ] Kenji Kikuchi commented on SOLR-6557: - Thank you for pointing to the SOLR-6485. I read

Re: Lucene Benchmark

I use the benchmark module for spatial and I intend to for highlighting performance next month. On Wednesday, September 24, 2014, Mikhail Khludnev mkhlud...@griddynamics.com wrote: Hi John, It's obvious

[jira] [Commented] (SOLR-5961) Solr gets crazy on /overseer/queue state change

[ https://issues.apache.org/jira/browse/SOLR-5961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14146217#comment-14146217 ] Ugo Matrangolo commented on SOLR-5961: -- Happened again :/ After a routine maintenance

[jira] [Comment Edited] (SOLR-5961) Solr gets crazy on /overseer/queue state change

[ https://issues.apache.org/jira/browse/SOLR-5961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14146217#comment-14146217 ] Ugo Matrangolo edited comment on SOLR-5961 at 9/24/14 11:23 AM:

Re: Lucene Benchmark

There's a ticket for Solr too but it is kind of clunky. I plan to spend a few weeks next month on the Solr benchmark suite. On Wed, Sep 24, 2014 at 4:43 PM, david.w.smi...@gmail.com david.w.smi...@gmail.com wrote: I use the benchmark module for spatial and I intend to for highlighting

[jira] [Created] (SOLR-6558) solr does not insert the first line in the csv file

fatih created SOLR-6558: --- Summary: solr does not insert the first line in the csv file Key: SOLR-6558 URL: https://issues.apache.org/jira/browse/SOLR-6558 Project: Solr Issue Type: Bug

[JENKINS] Lucene-Solr-NightlyTests-trunk - Build # 637 - Failure

Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-trunk/637/ 3 tests failed. REGRESSION: org.apache.solr.DistributedIntervalFacetingTest.testDistribSearch Error Message: Captured an uncaught exception in thread: Thread[id=58297, name=Thread-8747, state=RUNNABLE,

[jira] [Commented] (SOLR-6558) solr does not insert the first line in the csv file

[ https://issues.apache.org/jira/browse/SOLR-6558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14146303#comment-14146303 ] Yonik Seeley commented on SOLR-6558: Answered here:

[JENKINS] Lucene-Solr-Tests-trunk-Java7 - Build # 4880 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-Tests-trunk-Java7/4880/ 1 tests failed. REGRESSION: org.apache.solr.cloud.BasicDistributedZk2Test.testDistribSearch Error Message: There are still nodes recoverying - waited for 45 seconds Stack Trace: java.lang.AssertionError: There are still

[VOTE] Release 4.10.1 RC0

Artifacts here: http://people.apache.org/~mikemccand/staging_area/lucene-solr-4.10.1-RC0-rev1627268 Smoke tester: python3 -u dev-tools/scripts/smokeTestRelease.py http://people.apache.org/~mikemccand/staging_area/lucene-solr-4.10.1-RC0-rev1627268 1627268 4.10.1 /tmp/smoke4101 True SUCCESS!

[JENKINS] Lucene-Solr-4.10-Linux (32bit/jdk1.8.0_20) - Build # 4 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-4.10-Linux/4/ Java: 32bit/jdk1.8.0_20 -client -XX:+UseParallelGC 1 tests failed. REGRESSION: org.apache.solr.cloud.CollectionsAPIDistributedZkTest.testDistribSearch Error Message: createcollection the collection error [Watcher fired on path:

Re: [JENKINS] Lucene-Solr-SmokeRelease-5.x - Build # 196 - Still Failing

Thanks for your patience Robert. I’ll look at it today. Steve On Sep 24, 2014, at 6:15 AM, Robert Muir rcm...@gmail.com wrote: I am extremely close from disabling this analytics module, as i mentioned last week. Guys the solr build is still fucking broken. On Wed, Sep 24, 2014 at 4:46

Re: [JENKINS] Lucene-Solr-SmokeRelease-5.x - Build # 196 - Still Failing

Ah, looks like Uwe fixed the immediate problem. I’ll run the smoker locally to see if there’s anything else wrong. Steve On Sep 24, 2014, at 10:09 AM, Steve Rowe sar...@gmail.com wrote: Thanks for your patience Robert. I’ll look at it today. Steve On Sep 24, 2014, at 6:15 AM, Robert

Re: [JENKINS] Lucene-Solr-SmokeRelease-5.x - Build # 196 - Still Failing

I fixed this already. But maybe more failures will happen. Uwe Am 24. September 2014 16:09:06 MESZ, schrieb Steve Rowe sar...@gmail.com: Thanks for your patience Robert. I’ll look at it today. Steve On Sep 24, 2014, at 6:15 AM, Robert Muir rcm...@gmail.com wrote: I am extremely close from

[JENKINS] Lucene-Solr-Tests-5.x-Java7 - Build # 2131 - Failure

Build: https://builds.apache.org/job/Lucene-Solr-Tests-5.x-Java7/2131/ 1 tests failed. REGRESSION: org.apache.solr.cloud.DeleteLastCustomShardedReplicaTest.testDistribSearch Error Message: No live SolrServers available to handle this request:[https://127.0.0.1:17080, https://127.0.0.1:17085,

[jira] [Commented] (SOLR-6485) ReplicationHandler should have an option to throttle the speed of replication

[ https://issues.apache.org/jira/browse/SOLR-6485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14146385#comment-14146385 ] ASF subversion and git services commented on SOLR-6485: --- Commit

[jira] [Commented] (SOLR-6485) ReplicationHandler should have an option to throttle the speed of replication

[ https://issues.apache.org/jira/browse/SOLR-6485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14146389#comment-14146389 ] ASF subversion and git services commented on SOLR-6485: --- Commit

[jira] [Assigned] (SOLR-6241) HttpPartitionTest.testRf3WithLeaderFailover fails sometimes

[ https://issues.apache.org/jira/browse/SOLR-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Potter reassigned SOLR-6241: Assignee: Timothy Potter (was: Shalin Shekhar Mangar)

[jira] [Commented] (SOLR-6241) HttpPartitionTest.testRf3WithLeaderFailover fails sometimes

[ https://issues.apache.org/jira/browse/SOLR-6241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14146394#comment-14146394 ] Timothy Potter commented on SOLR-6241: -- I'm doing some refactoring as part of

[jira] [Resolved] (SOLR-6485) ReplicationHandler should have an option to throttle the speed of replication

[ https://issues.apache.org/jira/browse/SOLR-6485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul resolved SOLR-6485. -- Resolution: Fixed ReplicationHandler should have an option to throttle the speed of replication

[jira] [Updated] (SOLR-6485) ReplicationHandler should have an option to throttle the speed of replication

[ https://issues.apache.org/jira/browse/SOLR-6485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul updated SOLR-6485: - Fix Version/s: Trunk 5.0 ReplicationHandler should have an option to throttle the

[jira] [Commented] (SOLR-6453) Stop throwing an error message from Overseer on Solr exit

[ https://issues.apache.org/jira/browse/SOLR-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14146408#comment-14146408 ] ASF subversion and git services commented on SOLR-6453: --- Commit

[jira] [Commented] (SOLR-6453) Stop throwing an error message from Overseer on Solr exit

[ https://issues.apache.org/jira/browse/SOLR-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14146412#comment-14146412 ] ASF subversion and git services commented on SOLR-6453: --- Commit

[jira] [Resolved] (SOLR-6453) Stop throwing an error message from Overseer on Solr exit

[ https://issues.apache.org/jira/browse/SOLR-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul resolved SOLR-6453. -- Resolution: Fixed Fix Version/s: Trunk 5.0 Stop throwing an error message

[jira] [Commented] (SOLR-6511) Fencepost error in LeaderInitiatedRecoveryThread

[ https://issues.apache.org/jira/browse/SOLR-6511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14146420#comment-14146420 ] ASF subversion and git services commented on SOLR-6511: --- Commit

[jira] [Created] (SOLR-6559) Create an endpoint /update/xml/docs endpoint to do custom xml indexing

Noble Paul created SOLR-6559: Summary: Create an endpoint /update/xml/docs endpoint to do custom xml indexing Key: SOLR-6559 URL: https://issues.apache.org/jira/browse/SOLR-6559 Project: Solr

[jira] [Assigned] (SOLR-6559) Create an endpoint /update/xml/docs endpoint to do custom xml indexing

[ https://issues.apache.org/jira/browse/SOLR-6559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul reassigned SOLR-6559: Assignee: Noble Paul Create an endpoint /update/xml/docs endpoint to do custom xml indexing

[JENKINS] Lucene-Solr-trunk-Linux (64bit/jdk1.8.0_40-ea-b04) - Build # 11320 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/11320/ Java: 64bit/jdk1.8.0_40-ea-b04 -XX:-UseCompressedOops -XX:+UseConcMarkSweepGC 3 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.handler.admin.CoreAdminRequestStatusTest Error Message: 1 thread leaked from

[jira] [Commented] (SOLR-6557) bandwidth cap for large file replication

[ https://issues.apache.org/jira/browse/SOLR-6557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14146454#comment-14146454 ] Varun Thacker commented on SOLR-6557: - You can pass maxWriteMBPerSec from your slave

Re: [VOTE] Release 4.10.1 RC0

+1 SUCCESS! [0:46:29.195055] -- - Mark http://about.me/markrmiller On Wed, Sep 24, 2014 at 9:42 AM, Michael McCandless luc...@mikemccandless.com wrote: Artifacts here: http://people.apache.org/~mikemccand/staging_area/lucene-solr-4.10.1-RC0-rev1627268 Smoke tester: python3 -u

[jira] [Updated] (SOLR-6460) Keep transaction logs around longer

[ https://issues.apache.org/jira/browse/SOLR-6460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Renaud Delbru updated SOLR-6460: Attachment: SOLR-6460.patch Here is a first patch with an initial implementation of the

[jira] [Created] (SOLR-6560) Solr example file has outdated termIndexInterval entry

Tom Burton-West created SOLR-6560: - Summary: Solr example file has outdated termIndexInterval entry Key: SOLR-6560 URL: https://issues.apache.org/jira/browse/SOLR-6560 Project: Solr Issue

[jira] [Updated] (SOLR-6560) Solr example file has outdated termIndexInterval entry

[ https://issues.apache.org/jira/browse/SOLR-6560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Burton-West updated SOLR-6560: -- Attachment: SOLR-6560.patch Patch removes offending lines in example solrconfig.xml Solr

Re: Lucene Benchmark

Thank you Mikhail! Exactly what I was looking for! -John On Wed, Sep 24, 2014 at 12:59 AM, Mikhail Khludnev mkhlud...@griddynamics.com wrote: Hi John, It's obvious http://lucene.apache.org/core/4_8_0/benchmark/org/apache/lucene/benchmark/byTask/package-summary.html It's also described in

[jira] [Commented] (SOLR-6551) ConcurrentModificationException in UpdateLog

[ https://issues.apache.org/jira/browse/SOLR-6551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14146625#comment-14146625 ] Mark Bennett commented on SOLR-6551: This is a comment Noble made to me about this via

[jira] [Commented] (SOLR-6551) ConcurrentModificationException in UpdateLog

[ https://issues.apache.org/jira/browse/SOLR-6551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14146633#comment-14146633 ] Yonik Seeley commented on SOLR-6551: I assume this bug was introduced by SOLR-5441?

Re: How to openIfChanged the most recent merge?

I don't understand what's actually happening / going wrong here. Maybe you can make a test case / give more details? What assertions are broken? Why is it bad if SMS does a merge before you reopen? Why are you using SMS :) Mike McCandless http://blog.mikemccandless.com On Mon, Sep 22, 2014

queryResultMaxDocsCached vs. queryResultWindowSize

Hello, No response on the Solr user list so I thought I would try the dev list. queryResultWindowSize sets the number of documents to cache for each query in the queryResult cache.So if you normally output 10 results per page, and users don't go beyond page 3 of results, you could set

[jira] [Commented] (SOLR-6551) ConcurrentModificationException in UpdateLog

[ https://issues.apache.org/jira/browse/SOLR-6551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14146653#comment-14146653 ] Yonik Seeley commented on SOLR-6551: BTW, we have some very good transaction log stress

[JENKINS-MAVEN] Lucene-Solr-Maven-5.x #713: POMs out of sync

Build: https://builds.apache.org/job/Lucene-Solr-Maven-5.x/713/ 1 tests failed. REGRESSION: org.apache.solr.cloud.CollectionsAPIDistributedZkTest.testDistribSearch Error Message: Error CREATEing SolrCore 'halfcollection_shard1_replica1': Unable to create core [halfcollection_shard1_replica1]

[jira] [Commented] (SOLR-6551) ConcurrentModificationException in UpdateLog

[ https://issues.apache.org/jira/browse/SOLR-6551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14146727#comment-14146727 ] Yonik Seeley commented on SOLR-6551: After a really quick look, it looks like logs is

[jira] [Commented] (SOLR-3015) QParserPlugins can not be SolrCoreAware

[ https://issues.apache.org/jira/browse/SOLR-3015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14146798#comment-14146798 ] Ryan Josal commented on SOLR-3015: -- I ran into a problem with this today. I have a

Re: svn commit: r1627355 - in /lucene/dev/branches/branch_5x: ./ lucene/ lucene/build.xml lucene/site/ lucene/site/xsl/index.xsl

This change somehow caused a newline in the middle of the latest codec link, which broke checkJavadocLinks.py. I don't know how to fix the xsl, but html allows whitespace in the middle of links and browsers just remove it (tested), so I fixed checkJavadocLinks.py to remove inner whitespace. On

[jira] [Created] (LUCENE-5976) Index upgrader should have option to do multiple segments instead of one

Ryan Ernst created LUCENE-5976: -- Summary: Index upgrader should have option to do multiple segments instead of one Key: LUCENE-5976 URL: https://issues.apache.org/jira/browse/LUCENE-5976 Project: Lucene

[jira] [Commented] (LUCENE-5971) Separate backcompat creation script from adding version

[ https://issues.apache.org/jira/browse/LUCENE-5971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14146862#comment-14146862 ] ASF subversion and git services commented on LUCENE-5971: - Commit

[JENKINS] Lucene-Solr-5.x-Windows (64bit/jdk1.8.0_20) - Build # 4232 - Still Failing!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Windows/4232/ Java: 64bit/jdk1.8.0_20 -XX:-UseCompressedOops -XX:+UseSerialGC 2 tests failed. REGRESSION: org.apache.solr.cloud.AliasIntegrationTest.testDistribSearch Error Message: KeeperErrorCode = Session expired for

[jira] [Commented] (LUCENE-5969) Add Lucene50Codec

[ https://issues.apache.org/jira/browse/LUCENE-5969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14146872#comment-14146872 ] Uwe Schindler commented on LUCENE-5969: --- Thanks Robert. Unfortunately I was not

Re: queryResultMaxDocsCached vs. queryResultWindowSize

I think you are right. I think the name is this because it’s considering a series of queries paging a result. The first X pages are going to be cached, but once the limit is reached, no further pages are and the last superset that fitted remains in cache. At least that’s my understanding. After a

[JENKINS] Lucene-Solr-NightlyTests-5.x - Build # 631 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-5.x/631/ 1 tests failed. REGRESSION: org.apache.solr.handler.component.DistributedSpellCheckComponentTest.testDistribSearch Error Message: Captured an uncaught exception in thread: Thread[id=2263, name=Thread-1076, state=RUNNABLE,

[jira] [Created] (SOLR-6561) LBHttpSolrServer's aliveCheckExecutor is leaking connection when ResponseParser is null

Sudhan Moghe created SOLR-6561: -- Summary: LBHttpSolrServer's aliveCheckExecutor is leaking connection when ResponseParser is null Key: SOLR-6561 URL: https://issues.apache.org/jira/browse/SOLR-6561

Re: queryResultMaxDocsCached vs. queryResultWindowSize

On Wed, Sep 24, 2014 at 5:27 PM, Tomás Fernández Löbbe tomasflo...@gmail.com wrote: I think you are right. I think the name is this because it’s considering a series of queries paging a result. The first X pages are going to be cached, but once the limit is reached, no further pages are and the

[JENKINS] Lucene-Solr-trunk-Linux (64bit/jdk1.9.0-ea-b28) - Build # 11324 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/11324/ Java: 64bit/jdk1.9.0-ea-b28 -XX:-UseCompressedOops -XX:+UseG1GC All tests passed Build Log: [...truncated 41406 lines...] BUILD FAILED /mnt/ssd/jenkins/workspace/Lucene-Solr-trunk-Linux/build.xml:524: The following error

[jira] [Commented] (LUCENE-5971) Separate backcompat creation script from adding version

[ https://issues.apache.org/jira/browse/LUCENE-5971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14147133#comment-14147133 ] ASF subversion and git services commented on LUCENE-5971: - Commit

[jira] [Commented] (LUCENE-5902) Add bumpVersion script to increment version after release branch creation

[ https://issues.apache.org/jira/browse/LUCENE-5902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14147136#comment-14147136 ] ASF subversion and git services commented on LUCENE-5902: - Commit

[jira] [Commented] (LUCENE-5902) Add bumpVersion script to increment version after release branch creation

[ https://issues.apache.org/jira/browse/LUCENE-5902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14147137#comment-14147137 ] ASF subversion and git services commented on LUCENE-5902: - Commit

[jira] [Resolved] (LUCENE-5902) Add bumpVersion script to increment version after release branch creation

[ https://issues.apache.org/jira/browse/LUCENE-5902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan Ernst resolved LUCENE-5902. Resolution: Fixed Add bumpVersion script to increment version after release branch creation

[JENKINS] Lucene-Solr-trunk-MacOSX (64bit/jdk1.8.0) - Build # 1848 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-MacOSX/1848/ Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseSerialGC All tests passed Build Log: [...truncated 41267 lines...] BUILD FAILED /Users/jenkins/workspace/Lucene-Solr-trunk-MacOSX/build.xml:491: The following error occurred

[JENKINS-MAVEN] Lucene-Solr-Maven-trunk #1218: POMs out of sync

Build: https://builds.apache.org/job/Lucene-Solr-Maven-trunk/1218/ 2 tests failed. FAILED: org.apache.solr.handler.TestReplicationHandlerBackup.org.apache.solr.handler.TestReplicationHandlerBackup Error Message: 1 thread leaked from SUITE scope at

[JENKINS] Lucene-Solr-Tests-trunk-Java7 - Build # 4881 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-Tests-trunk-Java7/4881/ 1 tests failed. REGRESSION: org.apache.solr.cloud.DeleteReplicaTest.testDistribSearch Error Message: No live SolrServers available to handle this request:[https://127.0.0.1:10821/_hc/j, https://127.0.0.1:17541/_hc/j,

[JENKINS] Lucene-Solr-5.x-MacOSX (64bit/jdk1.8.0) - Build # 1809 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-MacOSX/1809/ Java: 64bit/jdk1.8.0 -XX:-UseCompressedOops -XX:+UseConcMarkSweepGC 2 tests failed. REGRESSION: org.apache.solr.cloud.DeleteLastCustomShardedReplicaTest.testDistribSearch Error Message: No live SolrServers available to handle

Re: [JENKINS] Lucene-Solr-trunk-Linux (64bit/jdk1.9.0-ea-b28) - Build # 11324 - Failure!

From the build log: - [libversions] VERSION CONFLICT: transitive dependency in module(s) langid: [libversions] /com.cybozu.labs/langdetect=1.1-20120112 [libversions] +-- /net.arnx/jsonic=1.2.7 [libversions] +-- /com.google.inject/guice=4.0-beta5 Conflict (direct=3.0, latest=4.0-beta5)

Re: [JENKINS] Lucene-Solr-trunk-Linux (64bit/jdk1.9.0-ea-b28) - Build # 11324 - Failure!

I don't understand why this suddenly started getting flagged - AFAICT the most recent changes to the langid module's ivy.xml file, or to the version of the dependencies in question in ivy-versions.xml, occurred in 2013. Nevertheless, I told check-lib-versions not to complain when it sees this, on

[JENKINS] Lucene-Solr-SmokeRelease-trunk - Build # 205 - Failure

Build: https://builds.apache.org/job/Lucene-Solr-SmokeRelease-trunk/205/ No tests ran. Build Log: [...truncated 51530 lines...] prepare-release-no-sign: [mkdir] Created dir: /usr/home/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-trunk/lucene/build/smokeTestRelease/dist

[jira] [Commented] (SOLR-6561) LBHttpSolrServer's aliveCheckExecutor is leaking connection when ResponseParser is null

[ https://issues.apache.org/jira/browse/SOLR-6561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14147375#comment-14147375 ] Sudhan Moghe commented on SOLR-6561: We have changed our handling and not setting