[jira] [Commented] (SOLR-7319) Workaround the "Four Month Bug" causing GC pause problems

[ https://issues.apache.org/jira/browse/SOLR-7319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388154#comment-14388154 ] Ferenczi Jim commented on SOLR-7319: Most of the java options in the solr.in.cmd should

[jira] [Created] (SOLR-7329) Show core name in logging UI

Ryan McKinley created SOLR-7329: --- Summary: Show core name in logging UI Key: SOLR-7329 URL: https://issues.apache.org/jira/browse/SOLR-7329 Project: Solr Issue Type: Improvement Rep

Re: 5.1 branch created

On Tue, Mar 31, 2015 at 4:57 AM, Timothy Potter wrote: > FYI - We've already agreed that LUCENE-6303 should get committed to > this branch when it is ready. You created the branch after I committed the patch on LUCENE-6303 so this looks good to me already! -- Adrien --

[jira] [Updated] (SOLR-6924) TestSolrConfigHandlerCloud fails frequently.

[ https://issues.apache.org/jira/browse/SOLR-6924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul updated SOLR-6924: - Attachment: SOLR-6924.patch New fix that would invoke a refresh command to each replica to ensure that they

[jira] [Updated] (SOLR-6924) TestSolrConfigHandlerCloud fails frequently.

[ https://issues.apache.org/jira/browse/SOLR-6924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul updated SOLR-6924: - Fix Version/s: 5.1 Trunk > TestSolrConfigHandlerCloud fails frequently. > --

Re: 5.1 branch created

I would like to commit the patch I submitted to SOLR-6924 as well. This is to address the test failuires On Tue, Mar 31, 2015 at 1:01 PM, Adrien Grand wrote: > On Tue, Mar 31, 2015 at 4:57 AM, Timothy Potter > wrote: > > FYI - We've already agreed that LUCENE-6303 should get committed to > > th

[jira] [Updated] (SOLR-7325) Change Slice state into enum

[ https://issues.apache.org/jira/browse/SOLR-7325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shai Erera updated SOLR-7325: - Attachment: SOLR-7325.patch Patch fixes more places which got some tests angry. I also replaced some of the

[jira] [Updated] (SOLR-7329) Show core name in logging UI

[ https://issues.apache.org/jira/browse/SOLR-7329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McKinley updated SOLR-7329: Attachment: SOLR-7329-core-in-logging-ui.patch here is a simple patch. > Show core name in logging

[jira] [Assigned] (SOLR-7325) Change Slice state into enum

[ https://issues.apache.org/jira/browse/SOLR-7325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shai Erera reassigned SOLR-7325: Assignee: Shai Erera > Change Slice state into enum > > >

Early Access builds for JDK 9 b55 and JDK 8u60 b08 are available on java.net

Hi Uwe & Dawid, Early Access build for JDK 9 b55 available on java.net, summary of changes are listed here Early Access build for JDK 8u60 b08 is available on ja

[jira] [Updated] (SOLR-4061) CREATE action in Collections API should allow to upload a new configuration

[ https://issues.apache.org/jira/browse/SOLR-4061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shai Erera updated SOLR-4061: - Fix Version/s: (was: 4.9) (was: Trunk) > CREATE action in Collections API should

[jira] [Created] (LUCENE-6381) DocumentsWriterStallControl's .wait() should have a time limit

Michael McCandless created LUCENE-6381: -- Summary: DocumentsWriterStallControl's .wait() should have a time limit Key: LUCENE-6381 URL: https://issues.apache.org/jira/browse/LUCENE-6381 Project: L

[jira] [Commented] (SOLR-7236) Securing Solr (umbrella issue)

[ https://issues.apache.org/jira/browse/SOLR-7236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388227#comment-14388227 ] Per Steffensen commented on SOLR-7236: -- I am ok with embedding Jetty, and you are righ

[jira] [Commented] (LUCENE-6308) Spans to extend DocIdSetIterator; was: SpansEnum, deprecate Spans

[ https://issues.apache.org/jira/browse/LUCENE-6308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388232#comment-14388232 ] ASF subversion and git services commented on LUCENE-6308: - Commit

[jira] [Commented] (SOLR-7236) Securing Solr (umbrella issue)

[ https://issues.apache.org/jira/browse/SOLR-7236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388230#comment-14388230 ] Per Steffensen commented on SOLR-7236: -- Sorry [~janhoy] - will stop now. The discussio

[jira] [Updated] (LUCENE-6381) DocumentsWriterStallControl's .wait() should have a time limit

[ https://issues.apache.org/jira/browse/LUCENE-6381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-6381: --- Attachment: LUCENE-6381.patch Simple patch, one line change. I'd like to backport to

[jira] [Commented] (LUCENE-6308) Spans to extend DocIdSetIterator; was: SpansEnum, deprecate Spans

[ https://issues.apache.org/jira/browse/LUCENE-6308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388253#comment-14388253 ] ASF subversion and git services commented on LUCENE-6308: - Commit

[jira] [Resolved] (LUCENE-6308) Spans to extend DocIdSetIterator; was: SpansEnum, deprecate Spans

[ https://issues.apache.org/jira/browse/LUCENE-6308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-6308. Resolution: Fixed Fix Version/s: Trunk 5.2 Thanks [~paul.

[jira] [Created] (LUCENE-6382) Don't allow position = Integer.MAX_VALUE going forward

Michael McCandless created LUCENE-6382: -- Summary: Don't allow position = Integer.MAX_VALUE going forward Key: LUCENE-6382 URL: https://issues.apache.org/jira/browse/LUCENE-6382 Project: Lucene - C

[jira] [Commented] (LUCENE-6308) Spans to extend DocIdSetIterator; was: SpansEnum, deprecate Spans

[ https://issues.apache.org/jira/browse/LUCENE-6308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388270#comment-14388270 ] ASF subversion and git services commented on LUCENE-6308: - Commit

[jira] [Commented] (LUCENE-6308) Spans to extend DocIdSetIterator; was: SpansEnum, deprecate Spans

[ https://issues.apache.org/jira/browse/LUCENE-6308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388274#comment-14388274 ] ASF subversion and git services commented on LUCENE-6308: - Commit

[jira] [Commented] (LUCENE-6308) Spans to extend DocIdSetIterator; was: SpansEnum, deprecate Spans

[ https://issues.apache.org/jira/browse/LUCENE-6308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388271#comment-14388271 ] ASF subversion and git services commented on LUCENE-6308: - Commit

[jira] [Commented] (LUCENE-6308) Spans to extend DocIdSetIterator; was: SpansEnum, deprecate Spans

[ https://issues.apache.org/jira/browse/LUCENE-6308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388276#comment-14388276 ] ASF subversion and git services commented on LUCENE-6308: - Commit

[DISCUSS] Change Query API to make queries immutable in 6.0

Recent changes that added automatic filter caching to IndexSearcher uncovered some traps with our queries when it comes to using them as cache keys. The problem comes from the fact that some of our main queries are mutable, and modifying them while they are used as cache keys makes the entry that t

Re: [DISCUSS] Change Query API to make queries immutable in 6.0

+1 For PhraseQuery we could also have a common-case ctor that just takes the terms (and assumes sequential positions)? Mike McCandless http://blog.mikemccandless.com On Tue, Mar 31, 2015 at 5:10 AM, Adrien Grand wrote: > Recent changes that added automatic filter caching to IndexSearcher > un

[JENKINS] Lucene-Solr-Tests-5.x-Java7 - Build # 2864 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-Tests-5.x-Java7/2864/ 3 tests failed. FAILED: org.apache.solr.cloud.LeaderInitiatedRecoveryOnCommitTest.test Error Message: IOException occured when talking to server at: http://127.0.0.1:64623/c8n_1x3_commits_shard1_replica3 Stack Trace: org.ap

RE: 5.1 branch created

Hi, I enabled the Jenkins runs for the 5.1 release branch: - Policman Jenkins standard randomized test run - ASF Jenkins Artifacts builds - ASF Jenkins release smoker Uwe - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -Original Mes

[jira] [Commented] (LUCENE-5879) Add auto-prefix terms to block tree terms dict

[ https://issues.apache.org/jira/browse/LUCENE-5879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388339#comment-14388339 ] Adrien Grand commented on LUCENE-5879: -- +1 to the patch bq. I don't think we should

[JENKINS] Lucene-Solr-trunk-Linux (64bit/jdk1.8.0_60-ea-b06) - Build # 12167 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/12167/ Java: 64bit/jdk1.8.0_60-ea-b06 -XX:-UseCompressedOops -XX:+UseG1GC 1 tests failed. FAILED: org.apache.solr.handler.TestSolrConfigHandlerCloud.test Error Message: Could not get expected value 'P val' for path 'response/params/y

[jira] [Updated] (LUCENE-6378) Fix RuntimeExceptions that are thrown without the root cause

[ https://issues.apache.org/jira/browse/LUCENE-6378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker updated LUCENE-6378: -- Attachment: LUCENE-6378.patch Patch which throws the underlying exception. All tests pass and

[JENKINS] Lucene-Solr-5.x-Linux (64bit/jdk1.9.0-ea-b54) - Build # 12001 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Linux/12001/ Java: 64bit/jdk1.9.0-ea-b54 -XX:+UseCompressedOops -XX:+UseParallelGC 1 tests failed. FAILED: org.apache.solr.handler.TestSolrConfigHandlerCloud.test Error Message: Could not get expected value 'P val' for path 'response/params/

Re: [DISCUSS] Change Query API to make queries immutable in 6.0

Same with BooleanQuery. the go-to ctor should just take 'clauses' On Tue, Mar 31, 2015 at 5:18 AM, Michael McCandless wrote: > +1 > > For PhraseQuery we could also have a common-case ctor that just takes > the terms (and assumes sequential positions)? > > Mike McCandless > > http://blog.mikemccan

[jira] [Updated] (SOLR-6709) ClassCastException in QueryResponse after applying XMLResponseParser on a response containing an "expanded" section

[ https://issues.apache.org/jira/browse/SOLR-6709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Varun Thacker updated SOLR-6709: Attachment: SOLR-6709.patch Added javadocs to {QueryResult.getExpandedResults}. Is there anything els

[jira] [Commented] (SOLR-7236) Securing Solr (umbrella issue)

[ https://issues.apache.org/jira/browse/SOLR-7236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388393#comment-14388393 ] Jan Høydahl commented on SOLR-7236: --- Yep, we need a container agnostic security API like

[jira] [Commented] (SOLR-6709) ClassCastException in QueryResponse after applying XMLResponseParser on a response containing an "expanded" section

[ https://issues.apache.org/jira/browse/SOLR-6709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388403#comment-14388403 ] Joel Bernstein commented on SOLR-6709: -- Looking at the patch, I don't see any issues.

[JENKINS] Lucene-Solr-5.1-Linux (32bit/jdk1.8.0_40) - Build # 176 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.1-Linux/176/ Java: 32bit/jdk1.8.0_40 -server -XX:+UseG1GC 1 tests failed. FAILED: org.apache.solr.cloud.FullSolrCloudDistribCmdsTest.test Error Message: Error from server at http://127.0.0.1:59885/mft/i/compositeid_collection_with_routerfield_

[jira] [Commented] (SOLR-7312) "REST" API is not REST

[ https://issues.apache.org/jira/browse/SOLR-7312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388463#comment-14388463 ] Shai Erera commented on SOLR-7312: -- I find REST a little bit like AGILE - you take what su

[jira] [Updated] (LUCENE-6379) IndexWriter's delete-by-query should optimize/specialize MatchAllDocsQuery

[ https://issues.apache.org/jira/browse/LUCENE-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-6379: --- Attachment: LUCENE-6379.patch Patch w/ simple test showing that Lucene's schema is ac

[jira] [Updated] (SOLR-6637) Solr should have a way to restore a core

[ https://issues.apache.org/jira/browse/SOLR-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul updated SOLR-6637: - Attachment: SOLR-6637.patch I have removed the reentrant lock and the synchronized is good enough . Please

[JENKINS] Lucene-Solr-trunk-Linux (32bit/jdk1.8.0_40) - Build # 12168 - Still Failing!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/12168/ Java: 32bit/jdk1.8.0_40 -client -XX:+UseConcMarkSweepGC 1 tests failed. FAILED: org.apache.solr.cloud.RecoveryAfterSoftCommitTest.test Error Message: Didn't see all replicas for shard shard1 in collection1 come up within 3

[jira] [Commented] (LUCENE-6379) IndexWriter's delete-by-query should optimize/specialize MatchAllDocsQuery

[ https://issues.apache.org/jira/browse/LUCENE-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388481#comment-14388481 ] Adrien Grand commented on LUCENE-6379: -- +1 > IndexWriter's delete-by-query should o

[jira] [Commented] (SOLR-7312) "REST" API is not REST

[ https://issues.apache.org/jira/browse/SOLR-7312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388484#comment-14388484 ] Noble Paul commented on SOLR-7312: -- As I mentioned earlier, I'm +1 for making all write op

[jira] [Commented] (LUCENE-6379) IndexWriter's delete-by-query should optimize/specialize MatchAllDocsQuery

[ https://issues.apache.org/jira/browse/LUCENE-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388486#comment-14388486 ] Robert Muir commented on LUCENE-6379: - +1 > IndexWriter's delete-by-query should opt

[jira] [Commented] (LUCENE-6379) IndexWriter's delete-by-query should optimize/specialize MatchAllDocsQuery

[ https://issues.apache.org/jira/browse/LUCENE-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388497#comment-14388497 ] Adrien Grand commented on LUCENE-6379: -- One minor paranoid nitpick: I just noticed M

[jira] [Commented] (LUCENE-6378) Fix RuntimeExceptions that are thrown without the root cause

[ https://issues.apache.org/jira/browse/LUCENE-6378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388499#comment-14388499 ] Adrien Grand commented on LUCENE-6378: -- +1 > Fix RuntimeExceptions that are thrown

[jira] [Commented] (LUCENE-5879) Add auto-prefix terms to block tree terms dict

[ https://issues.apache.org/jira/browse/LUCENE-5879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388500#comment-14388500 ] Robert Muir commented on LUCENE-5879: - We should be able to add a trivial test to luc

[JENKINS] Lucene-Solr-Tests-5.x-Java7 - Build # 2865 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-Tests-5.x-Java7/2865/ 3 tests failed. FAILED: org.apache.solr.cloud.LeaderInitiatedRecoveryOnCommitTest.test Error Message: IOException occured when talking to server at: http://127.0.0.1:19336/c8n_1x3_commits_shard1_replica2 Stack Trace: org.ap

Re: [DISCUSS] Change Query API to make queries immutable in 6.0

+1. Makes a lot of sense in general I think. Keeps them nicely thread safe as well, and as they are commonly used for keys in caches and such, that's a nice intrinsic property. - Mark On Tue, Mar 31, 2015 at 7:24 AM Robert Muir wrote: > Same with BooleanQuery. the go-to ctor should just take 'c

Re: [DISCUSS] Change Query API to make queries immutable in 6.0

Adrien, I missed the reason that boost is going to stay mutable. Is this to support query rewriting? --Terry On Tue, Mar 31, 2015 at 7:21 AM, Robert Muir wrote: > Same with BooleanQuery. the go-to ctor should just take 'clauses' > > On Tue, Mar 31, 2015 at 5:18 AM, Michael McCandless > wrote

Re: [jira] [Commented] (SOLR-7319) Workaround the "Four Month Bug" causing GC pause problems

Yes and yes. the -a option for the bin/solr command passes stuff through, e.g. bin/solr start -c -z localhost:2181 -p 8981 -s example/cloud/node1/solr -a "-Xmx4G -Xms4G" and the like. It'd be useful I would guess to be able to specify a local file of options as well I should think. Erikc On M

Re: [DISCUSS] Change Query API to make queries immutable in 6.0

Hi Terry, Indeed this is for query rewriting. For instance if you have a boolean query with a boost of 5 that wraps a single MUST clause with a term query, then we rewrite to this to the inner term query and update its boost using clone() and setBoost() in order to not modify in-place a user-modif

[jira] [Commented] (SOLR-6736) A collections-like request handler to manage solr configurations on zookeeper

[ https://issues.apache.org/jira/browse/SOLR-6736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388548#comment-14388548 ] Shai Erera commented on SOLR-6736: -- bq. I'm tempted to just restrict this to support just

[jira] [Commented] (LUCENE-5879) Add auto-prefix terms to block tree terms dict

[ https://issues.apache.org/jira/browse/LUCENE-5879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388560#comment-14388560 ] Robert Muir commented on LUCENE-5879: - +1 to the patch. I can add the tests later if

RE: [DISCUSS] Change Query API to make queries immutable in 6.0

Am I missing something? Across the project, I’m seeing over 1,000 references to BooleanQuery.add(). Already, this seems like a pretty major refactoring. And I haven’t checked the other types of queries: DisjunctionMax, Phrase, and MultiPhrase. At that scale, bugs will be introduced. I’m

Re: [DISCUSS] Change Query API to make queries immutable in 6.0

Adrien, Thanks for the explanation. It seems a pity to make queries just nearly immutable. Do you have any interest in adding a boost parameter to clone() so they really could be immutable? --Terry On Tue, Mar 31, 2015 at 9:44 AM, Adrien Grand wrote: > Hi Terry, > > Indeed this is for query r

[JENKINS] Lucene-Solr-5.x-Windows (32bit/jdk1.8.0_40) - Build # 4502 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Windows/4502/ Java: 32bit/jdk1.8.0_40 -server -XX:+UseG1GC 2 tests failed. FAILED: org.apache.solr.cloud.ChaosMonkeyNothingIsSafeTest.test Error Message: There were too many update fails (28 > 20) - we expect it can happen, but shouldn't eas

[JENKINS] Lucene-Solr-5.1-Linux (64bit/jdk1.8.0_40) - Build # 177 - Still Failing!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.1-Linux/177/ Java: 64bit/jdk1.8.0_40 -XX:-UseCompressedOops -XX:+UseConcMarkSweepGC 1 tests failed. FAILED: org.apache.solr.cloud.FullSolrCloudDistribCmdsTest.test Error Message: Error from server at http://127.0.0.1:60892/compositeid_collecti

Re: [DISCUSS] Change Query API to make queries immutable in 6.0

Hi Charles, On Tue, Mar 31, 2015 at 4:12 PM, Reitzel, Charles wrote: > Am I missing something? Across the project, I’m seeing over 1,000 > references to BooleanQuery.add(). Already, this seems like a pretty major > refactoring. And I haven’t checked the other types of queries: > Disjuncti

Re: [jira] [Commented] (SOLR-7319) Workaround the "Four Month Bug" causing GC pause problems

we should actually fix the script to pass any args that being with -X straight through to the JVM so we don't need the -a part, i.e. bin/solr start -XX:+PerfDisableSharedMem vs. bin/solr start -a "-XX:+PerfDisableSharedMem" On Tue, Mar 31, 2015 at 6:43 AM, Erick Erickson wrote: > Yes and yes. >

[jira] [Commented] (SOLR-7312) "REST" API is not REST

[ https://issues.apache.org/jira/browse/SOLR-7312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388669#comment-14388669 ] Mark Haase commented on SOLR-7312: -- The curmudgeonly bonbon learns a hard lesson from a di

[jira] [Commented] (SOLR-7324) No need to call isIndexStale if full copy is already needed

[ https://issues.apache.org/jira/browse/SOLR-7324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388673#comment-14388673 ] ASF subversion and git services commented on SOLR-7324: --- Commit 16703

Re: [DISCUSS] Change Query API to make queries immutable in 6.0

On Tue, Mar 31, 2015 at 4:32 PM, Terry Smith wrote: > Thanks for the explanation. It seems a pity to make queries just nearly > immutable. Do you have any interest in adding a boost parameter to clone() > so they really could be immutable? We could have a single method, but if we do it I would ra

About Apache Solr Contribution

Dev Team, I am currently working with Apache Solr.While using the Apache Solr suggestion module an idea came to my mind and I want to contribute this to the Solr Project. While using Solr we pass the requests and receive response using rest on http why don't we use the Web Socket.Rather than sendin

Re: 5.1 branch created

Tim, I think it is really important to get https://issues.apache.org/jira/browse/LUCENE-6271 in for 5.1. The positings refactorings that happened for 5.1 have left the semantics of getting postings information in an odd state. There is a branch there to fix all the uses within lucene/solr/tests,

[jira] [Commented] (SOLR-6736) A collections-like request handler to manage solr configurations on zookeeper

[ https://issues.apache.org/jira/browse/SOLR-6736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388723#comment-14388723 ] Noble Paul commented on SOLR-6736: -- This does more. It is done securely. > A collections

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

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-MacOSX/2119/ Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC 1 tests failed. FAILED: org.apache.solr.client.solrj.TestLBHttpSolrClient.testReliability Error Message: No live SolrServers available to handle this request

[jira] [Commented] (SOLR-6736) A collections-like request handler to manage solr configurations on zookeeper

[ https://issues.apache.org/jira/browse/SOLR-6736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388727#comment-14388727 ] Anshum Gupta commented on SOLR-6736: I think it would make sense to hold this until SOL

[jira] [Commented] (SOLR-6924) TestSolrConfigHandlerCloud fails frequently.

[ https://issues.apache.org/jira/browse/SOLR-6924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388731#comment-14388731 ] Timothy Potter commented on SOLR-6924: -- Seems like {{waitForAllReplicasState}} is doin

[jira] [Commented] (LUCENE-6308) Spans to extend DocIdSetIterator; was: SpansEnum, deprecate Spans

[ https://issues.apache.org/jira/browse/LUCENE-6308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388736#comment-14388736 ] Paul Elschot commented on LUCENE-6308: -- My pleasure. I'll share the thanks with [~rc

[jira] [Commented] (LUCENE-6271) PostingsEnum should have consistent flags behavior

[ https://issues.apache.org/jira/browse/LUCENE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388742#comment-14388742 ] ASF subversion and git services commented on LUCENE-6271: - Commit

Re: 5.1 branch created

Yes, let's include this for 5.1. Please backport as soon as you can, so we can keep an eye out for Jenkins failures over the next couple of days. Thanks. Tim On Tue, Mar 31, 2015 at 8:22 AM, Ryan Ernst wrote: > Tim, > > I think it is really important to get > https://issues.apache.org/jira/brows

[jira] [Commented] (SOLR-7319) Workaround the "Four Month Bug" causing GC pause problems

[ https://issues.apache.org/jira/browse/SOLR-7319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388744#comment-14388744 ] ASF subversion and git services commented on SOLR-7319: --- Commit 16703

[jira] [Commented] (SOLR-7319) Workaround the "Four Month Bug" causing GC pause problems

[ https://issues.apache.org/jira/browse/SOLR-7319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388745#comment-14388745 ] ASF subversion and git services commented on SOLR-7319: --- Commit 16703

[jira] [Commented] (SOLR-7319) Workaround the "Four Month Bug" causing GC pause problems

[ https://issues.apache.org/jira/browse/SOLR-7319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388747#comment-14388747 ] ASF subversion and git services commented on SOLR-7319: --- Commit 16703

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

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Linux/12003/ Java: 64bit/jdk1.8.0_40 -XX:-UseCompressedOops -XX:+UseParallelGC 1 tests failed. FAILED: org.apache.solr.cloud.FullSolrCloudDistribCmdsTest.test Error Message: Error from server at http://127.0.0.1:43860/implicit_collection_wit

[jira] [Created] (SOLR-7330) Merge the code for schema sync and config sync

Noble Paul created SOLR-7330: Summary: Merge the code for schema sync and config sync Key: SOLR-7330 URL: https://issues.apache.org/jira/browse/SOLR-7330 Project: Solr Issue Type: Task

[jira] [Commented] (LUCENE-6271) PostingsEnum should have consistent flags behavior

[ https://issues.apache.org/jira/browse/LUCENE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388762#comment-14388762 ] ASF subversion and git services commented on LUCENE-6271: - Commit

[jira] [Reopened] (SOLR-7319) Workaround the "Four Month Bug" causing GC pause problems

[ https://issues.apache.org/jira/browse/SOLR-7319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Heisey reopened SOLR-7319: Reverted the commits, re-opening the issue for further discussion. > Workaround the "Four Month Bug" cau

Re: 5.1 branch created

Noble, Go ahead and commit / backport the fix for SOLR-6924 to 5.1 - we'll clean up the similar code paths in 5.2 under SOLR-7330 Cheers, Tim On Tue, Mar 31, 2015 at 12:40 AM, Noble Paul wrote: > I would like to commit the patch I submitted to SOLR-6924 as well. This is > to address the test fa

[jira] [Updated] (SOLR-7319) Workaround the "Four Month Bug" causing GC pause problems

[ https://issues.apache.org/jira/browse/SOLR-7319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Heisey updated SOLR-7319: --- Fix Version/s: (was: 5.1) > Workaround the "Four Month Bug" causing GC pause problems > ---

[jira] [Commented] (SOLR-6924) TestSolrConfigHandlerCloud fails frequently.

[ https://issues.apache.org/jira/browse/SOLR-6924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388772#comment-14388772 ] ASF subversion and git services commented on SOLR-6924: --- Commit 16703

Re: 5.1 branch created

On 3/30/2015 8:57 PM, Timothy Potter wrote: The 5.1 branch has been created - https://svn.apache.org/repos/asf/lucene/dev/branches/lucene_solr_5_1/ I have reverted SOLR-7319 in trunk, branch_5x, and lucene_solr_5_1 so we aren't destroying any monitoring capabilities until/unless consensus is

[jira] [Resolved] (SOLR-7226) Make /query/* jmx/* , requestDispatcher/*, properties in solrconfig.xml editable

[ https://issues.apache.org/jira/browse/SOLR-7226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul resolved SOLR-7226. -- Resolution: Fixed Fix Version/s: 5.1 Trunk > Make /query/* jmx/* , requestDispa

[jira] [Commented] (SOLR-6924) TestSolrConfigHandlerCloud fails frequently.

[ https://issues.apache.org/jira/browse/SOLR-6924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388789#comment-14388789 ] ASF subversion and git services commented on SOLR-6924: --- Commit 16703

[jira] [Commented] (SOLR-6924) TestSolrConfigHandlerCloud fails frequently.

[ https://issues.apache.org/jira/browse/SOLR-6924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388800#comment-14388800 ] ASF subversion and git services commented on SOLR-6924: --- Commit 16703

[jira] [Resolved] (SOLR-6924) TestSolrConfigHandlerCloud fails frequently.

[ https://issues.apache.org/jira/browse/SOLR-6924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul resolved SOLR-6924. -- Resolution: Fixed > TestSolrConfigHandlerCloud fails frequently. > --

[jira] [Commented] (LUCENE-6271) PostingsEnum should have consistent flags behavior

[ https://issues.apache.org/jira/browse/LUCENE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388806#comment-14388806 ] ASF subversion and git services commented on LUCENE-6271: - Commit

Re: 5.1 branch created

I've committed SOLR-6924 . Thanks everyone On Tue, Mar 31, 2015 at 9:49 PM, Shawn Heisey wrote: > On 3/30/2015 8:57 PM, Timothy Potter wrote: > >> The 5.1 branch has been created - >> https://svn.apache.org/repos/asf/lucene/dev/branches/lucene_solr_5_1/ >> > > I have reverted SOLR-7319 in trunk,

[jira] [Updated] (LUCENE-6382) Don't allow position = Integer.MAX_VALUE going forward

[ https://issues.apache.org/jira/browse/LUCENE-6382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-6382: --- Attachment: LUCENE-6382.patch Patch. Adds IndexWriter.MAX_POSITION (= Integer.MAX_VA

Re: About Apache Solr Contribution

The first step is to get the source code, compile and test it. Here's the page that'll help you get started: http://wiki.apache.org/solr/HowToContribute There are also sections on setting up IDEs etc. Do note that there are some formatting guidelines, and for IntelliJ, Eclipse and (maybe) Netbean

[jira] [Updated] (LUCENE-6379) IndexWriter's delete-by-query should optimize/specialize MatchAllDocsQuery

[ https://issues.apache.org/jira/browse/LUCENE-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-6379: --- Attachment: LUCENE-6379.patch bq. So maybe we should make MatchAllDocsQuery final or

[jira] [Commented] (LUCENE-6379) IndexWriter's delete-by-query should optimize/specialize MatchAllDocsQuery

[ https://issues.apache.org/jira/browse/LUCENE-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388838#comment-14388838 ] Adrien Grand commented on LUCENE-6379: -- +1! > IndexWriter's delete-by-query should

Re: About Apache Solr Contribution

Dear Erick, Thank you for the positive response. Regards, Luqman Ul Khair On Tue, Mar 31, 2015 at 9:49 PM, Erick Erickson wrote: > The first step is to get the source code, compile and test it. Here's > the page that'll help you get started: > > http://wiki.apache.org/solr/HowToContribute > > Th

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

Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-5.x/803/ 1 tests failed. FAILED: junit.framework.TestSuite.org.apache.lucene.replicator.IndexAndTaxonomyReplicationClientTest Error Message: file handle leaks: [FileChannel(/usr/home/jenkins/jenkins-slave/workspace/Lucene-Solr-Night

[jira] [Commented] (LUCENE-6271) PostingsEnum should have consistent flags behavior

[ https://issues.apache.org/jira/browse/LUCENE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388856#comment-14388856 ] ASF subversion and git services commented on LUCENE-6271: - Commit

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

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-MacOSX/2075/ Java: 64bit/jdk1.7.0 -XX:-UseCompressedOops -XX:+UseParallelGC 1 tests failed. FAILED: org.apache.solr.handler.TestSolrConfigHandlerCloud.test Error Message: Could not get expected value 'null' for path 'config/searchComponent/t

[JENKINS] Lucene-Solr-5.x-Linux (64bit/jdk1.8.0_60-ea-b06) - Build # 12004 - Still Failing!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Linux/12004/ Java: 64bit/jdk1.8.0_60-ea-b06 -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC 1 tests failed. FAILED: org.apache.solr.cloud.FullSolrCloudDistribCmdsTest.test Error Message: Error from server at http://127.0.0.1:46380/compositeid

Re: About Apache Solr Contribution

On 31 March 2015 at 20:52, luqman ulkhair wrote: > Dev Team, > I am currently working with Apache Solr.While using the Apache Solr > suggestion module an idea came to my mind and I want to contribute this to > the Solr Project. [...] You might want to start with http://wiki.apache.org/solr/HowToC

[jira] [Commented] (LUCENE-6271) PostingsEnum should have consistent flags behavior

[ https://issues.apache.org/jira/browse/LUCENE-6271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388911#comment-14388911 ] ASF subversion and git services commented on LUCENE-6271: - Commit

[jira] [Commented] (LUCENE-6379) IndexWriter's delete-by-query should optimize/specialize MatchAllDocsQuery

[ https://issues.apache.org/jira/browse/LUCENE-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388935#comment-14388935 ] ASF subversion and git services commented on LUCENE-6379: - Commit

  1   2   3   >