[jira] [Created] (SOLR-8429) add a flag blockUnauthenticated to BasicAutPlugin

Noble Paul created SOLR-8429: Summary: add a flag blockUnauthenticated to BasicAutPlugin Key: SOLR-8429 URL: https://issues.apache.org/jira/browse/SOLR-8429 Project: Solr Issue Type: Improvement

[jira] [Commented] (LUCENE-6922) Improve svn to git workaround script

[ https://issues.apache.org/jira/browse/LUCENE-6922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15060771#comment-15060771 ] Paul Elschot commented on LUCENE-6922: -- While testing this I noticed that on the trunk branch there

[jira] [Commented] (LUCENE-6922) Improve svn to git workaround script

[ https://issues.apache.org/jira/browse/LUCENE-6922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15060811#comment-15060811 ] Terry Smith commented on LUCENE-6922: - Does LUCENE-6933 affect this ticket? > Improve svn to git

[jira] [Commented] (LUCENE-6922) Improve svn to git workaround script

[ https://issues.apache.org/jira/browse/LUCENE-6922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15060838#comment-15060838 ] Dawid Weiss commented on LUCENE-6922: - Absolutely! There is actually no promise that we will switch

[jira] [Updated] (SOLR-8429) add a flag blockUnauthenticated to BasicAutPlugin

[ https://issues.apache.org/jira/browse/SOLR-8429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul updated SOLR-8429: - Description: If authentication is setup with BasicAuthPlugin, it let's all requests go through if no

[jira] [Updated] (SOLR-8429) add a flag blockUnauthenticated to BasicAutPlugin

[ https://issues.apache.org/jira/browse/SOLR-8429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul updated SOLR-8429: - Description: If authentication is setup with BasicAuthPlugin, it let's all requests go through if no

[jira] [Commented] (LUCENE-6922) Improve svn to git workaround script

[ https://issues.apache.org/jira/browse/LUCENE-6922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15060801#comment-15060801 ] Paul Elschot commented on LUCENE-6922: -- After the git-svn mirror is turned off, this could be used

[jira] [Updated] (SOLR-6398) Add IterativeMergeStrategy to support Parallel Iterative Algorithms

[ https://issues.apache.org/jira/browse/SOLR-6398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Bernstein updated SOLR-6398: - Description: This ticket builds on the existing AnalyticsQuery / MergeStrategy framework by

[jira] [Commented] (SOLR-8423) DELETESHARD should cleanup the instance and data directory, like DELETEREPLICA

[ https://issues.apache.org/jira/browse/SOLR-8423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15060299#comment-15060299 ] Erick Erickson commented on SOLR-8423: -- I don't think this breaks back-compat 'cause I don't see any

[jira] [Updated] (SOLR-8424) Admin UI not reachable in Solr 5.4 under path /solr/ when running in JBoss

[ https://issues.apache.org/jira/browse/SOLR-8424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Heisey updated SOLR-8424: --- Summary: Admin UI not reachable in Solr 5.4 under path /solr/ when running in JBoss (was: Admin UI

Re: 5.3.2 bug fix release

Why don't people just upgrade to 5.4? Why do we need another release in the 5.3.x range? Upayavira On Wed, Dec 16, 2015, at 09:12 PM, Shawn Heisey wrote: > On 12/16/2015 1:08 PM, Anshum Gupta wrote: > > There are a bunch of important bug fixes that call for a 5.3.2 in my > > opinion. I'm

[jira] [Updated] (SOLR-8393) Component for Solr resource usage planning

[ https://issues.apache.org/jira/browse/SOLR-8393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Molloy updated SOLR-8393: --- Attachment: SOLR-8393.patch Adjust to work with small and empty indexes, also add num docs used for

[jira] [Commented] (SOLR-6398) Add IterativeMergeStrategy to support running Parallel Iterative Algorithms inside of Solr

[ https://issues.apache.org/jira/browse/SOLR-6398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15060664#comment-15060664 ] ASF subversion and git services commented on SOLR-6398: --- Commit 1720422 from

[jira] [Updated] (SOLR-8428) create an 'all' permission to protect all paths

[ https://issues.apache.org/jira/browse/SOLR-8428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul updated SOLR-8428: - Attachment: SOLR-8428.patch > create an 'all' permission to protect all paths >

5.3.2 bug fix release

There are a bunch of important bug fixes that call for a 5.3.2 in my opinion. I'm specifically talking about security plugins related fixes but I'm sure there are others too. Unless someone else wants to do it, I'd volunteer to do the release and cut an RC next Tuesday. -- Anshum Gupta

[jira] [Commented] (LUCENE-6922) Improve svn to git workaround script

[ https://issues.apache.org/jira/browse/LUCENE-6922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15060823#comment-15060823 ] Dawid Weiss commented on LUCENE-6922: - LUCENE-6933 is an attempt to clean up and consolidate all the

[jira] [Updated] (SOLR-8422) Basic Authentication plugin is not working correctly in solrcloud

[ https://issues.apache.org/jira/browse/SOLR-8422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul updated SOLR-8422: - Attachment: SOLR-8422.patch > Basic Authentication plugin is not working correctly in solrcloud >

[jira] [Closed] (SOLR-6398) Add IterativeMergeStrategy to support running Parallel Iterative Algorithms inside of Solr

[ https://issues.apache.org/jira/browse/SOLR-6398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Bernstein closed SOLR-6398. Resolution: Fixed > Add IterativeMergeStrategy to support running Parallel Iterative Algorithms >

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

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-MacOSX/2891/ Java: 64bit/jdk1.7.0 -XX:+UseCompressedOops -XX:+UseParallelGC 1 tests failed. FAILED: org.apache.solr.cloud.HttpPartitionTest.test Error Message: Could not load collection from ZK:c8n_crud_1x2 Stack Trace:

[jira] [Commented] (LUCENE-6922) Improve svn to git workaround script

[ https://issues.apache.org/jira/browse/LUCENE-6922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15060830#comment-15060830 ] Terry Smith commented on LUCENE-6922: - Ah, so I could consider this as a backup plan until

[jira] [Commented] (LUCENE-6922) Improve svn to git workaround script

[ https://issues.apache.org/jira/browse/LUCENE-6922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15060845#comment-15060845 ] Paul Elschot commented on LUCENE-6922: -- LUCENE-6933 could affect this in the sense of the choice of

Re: 5.3.2 bug fix release

On 12/16/2015 1:08 PM, Anshum Gupta wrote: > There are a bunch of important bug fixes that call for a 5.3.2 in my > opinion. I'm specifically talking about security plugins related fixes > but I'm sure there are others too. > > Unless someone else wants to do it, I'd volunteer to do the release >

[jira] [Commented] (LUCENE-6922) Improve svn to git workaround script

please fetch the trunk.svn.20151216 tag into an existing lucene-solr repository: {code}git fetch https://github.com/PaulElschot/lucene-solr.git trunk.svn.20151216{code} > Improve svn to git workaround script > > > Key:

[jira] [Comment Edited] (LUCENE-6922) Improve svn to git workaround script

an impression of what this is currently doing please fetch the trunk.svn.20151216 tag into an existing lucene-solr repository: {code}git fetch https://github.com/PaulElschot/lucene-solr.git trunk.svn.20151216{code} was (Author: paul.elsc...@xs4all.nl): I to get an impression of what

[jira] [Closed] (SOLR-8424) Admin UI not reachable in Solr 5.4 under path /solr/ when running in JBoss

[ https://issues.apache.org/jira/browse/SOLR-8424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Heisey closed SOLR-8424. -- Resolution: Cannot Reproduce Running in third-party containers is no longer officially supported as of

[jira] [Updated] (LUCENE-6922) Improve svn to git workaround script

[ https://issues.apache.org/jira/browse/LUCENE-6922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Elschot updated LUCENE-6922: - Attachment: svnBranchToGit.py Script of 16 December 2015. This was a major overhaul: Added a

[jira] [Commented] (SOLR-8416) Solr collection creation API should return after all cores are alive

[ https://issues.apache.org/jira/browse/SOLR-8416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15060419#comment-15060419 ] Mark Miller commented on SOLR-8416: --- Thanks for the patch, a couple comments: * Usually it's better to

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

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-MacOSX/2946/ Java: 64bit/jdk1.8.0 -XX:-UseCompressedOops -XX:+UseSerialGC 2 tests failed. FAILED: org.apache.solr.cloud.HttpPartitionTest.test Error Message: Test abandoned because suite timeout was reached. Stack Trace:

[jira] [Commented] (SOLR-6398) Add IterativeMergeStrategy to support running Parallel Iterative Algorithms inside of Solr

[ https://issues.apache.org/jira/browse/SOLR-6398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15060463#comment-15060463 ] Joel Bernstein commented on SOLR-6398: -- This is looking ready to commit to trunk I believe. I'll be

[jira] [Assigned] (SOLR-8422) Basic Authentication plugin is not working correctly in solrcloud

[ https://issues.apache.org/jira/browse/SOLR-8422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul reassigned SOLR-8422: Assignee: Noble Paul > Basic Authentication plugin is not working correctly in solrcloud >

[jira] [Updated] (SOLR-6398) Add IterativeMergeStrategy to support Parallel Iterative Algorithms

[ https://issues.apache.org/jira/browse/SOLR-6398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Bernstein updated SOLR-6398: - Description: This ticket builds on the existing AnalyticsQuery / MergeStrategy framework by

Re: JSON "fields" vs defaults

To respond to your last question Yonik, the "fl" in the query params behaves the same as the "fl" in the JSON params block, so no bug there. There is a difference though, between those and the top level "fields" param, as Jack pointed out it appends to the defaults instead of overriding them like

[jira] [Updated] (SOLR-8416) Solr collection creation API should return after all cores are alive

[ https://issues.apache.org/jira/browse/SOLR-8416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Sun updated SOLR-8416: -- Attachment: (was: CDH-33586.patch) > Solr collection creation API should return after all cores are

[jira] [Updated] (SOLR-8416) Solr collection creation API should return after all cores are alive

[ https://issues.apache.org/jira/browse/SOLR-8416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Sun updated SOLR-8416: -- Attachment: CDH-33586.patch > Solr collection creation API should return after all cores are alive >

[jira] [Updated] (SOLR-6398) Add IterativeMergeStrategy to support Parallel Iterative Algorithms

[ https://issues.apache.org/jira/browse/SOLR-6398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Bernstein updated SOLR-6398: - Description: This ticket builds on the existing AnalyticsQuery / MergeStrategy framework by

[jira] [Updated] (SOLR-6398) Add IterativeMergeStrategy to support Parallel Iterative Algorithms

[ https://issues.apache.org/jira/browse/SOLR-6398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Bernstein updated SOLR-6398: - Description: This ticket builds on the existing AnalyticsQuery / MergeStrategy framework by

[jira] [Created] (SOLR-8428) create an 'all' permission to protect all paths

Noble Paul created SOLR-8428: Summary: create an 'all' permission to protect all paths Key: SOLR-8428 URL: https://issues.apache.org/jira/browse/SOLR-8428 Project: Solr Issue Type: Improvement

[jira] [Updated] (SOLR-8416) Solr collection creation API should return after all cores are alive

[ https://issues.apache.org/jira/browse/SOLR-8416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Sun updated SOLR-8416: -- Attachment: SOLR-8416.patch > Solr collection creation API should return after all cores are alive >

[jira] [Updated] (SOLR-6398) Add IterativeMergeStrategy to support running Parallel Iterative Algorithms inside of Solr

[ https://issues.apache.org/jira/browse/SOLR-6398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Bernstein updated SOLR-6398: - Summary: Add IterativeMergeStrategy to support running Parallel Iterative Algorithms inside of

[jira] [Commented] (SOLR-8416) Solr collection creation API should return after all cores are alive

[ https://issues.apache.org/jira/browse/SOLR-8416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15060396#comment-15060396 ] Michael Sun commented on SOLR-8416: --- A patch is uploaded. Here are some thoughts: 1. The patch pulls

[jira] [Comment Edited] (SOLR-8368) Investigate a leader using older versions than it's replicas has for leader election peer sync after a 'crash' shutdown.

[ https://issues.apache.org/jira/browse/SOLR-8368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15060426#comment-15060426 ] Mark Miller edited comment on SOLR-8368 at 12/16/15 6:02 PM: - I've renamed this

[jira] [Commented] (SOLR-8368) Investigate a leader using older versions than it's replicas has for leader election peer sync after a 'crash' shutdown.

[ https://issues.apache.org/jira/browse/SOLR-8368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15060426#comment-15060426 ] Mark Miller commented on SOLR-8368: --- I've renamed this investigation. Given we work from uncapped tlogs,

[jira] [Updated] (SOLR-6398) Add IterativeMergeStrategy to support Parallel Iterative Algorithms

[ https://issues.apache.org/jira/browse/SOLR-6398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Bernstein updated SOLR-6398: - Fix Version/s: (was: 5.2) > Add IterativeMergeStrategy to support Parallel Iterative

[jira] [Commented] (SOLR-8416) Solr collection creation API should return after all cores are alive

[ https://issues.apache.org/jira/browse/SOLR-8416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15060441#comment-15060441 ] Mark Miller commented on SOLR-8416: --- bq. 1. The patch pulls shard status from zk and returns if they are

[jira] [Commented] (SOLR-8191) CloudSolrStream close method NullPointerException

[ https://issues.apache.org/jira/browse/SOLR-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15060895#comment-15060895 ] Joel Bernstein commented on SOLR-8191: -- Ok, this looks fine to me. > CloudSolrStream close method

[jira] [Closed] (SOLR-8191) Guard against CloudSolrStream close method NullPointerException

[ https://issues.apache.org/jira/browse/SOLR-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Bernstein closed SOLR-8191. Resolution: Fixed > Guard against CloudSolrStream close method NullPointerException >

Re: 5.3.2 bug fix release

Anshum, If there happens to be a security bugfix release, I'd like to have SOLR-8373 included as well. It is a deal breaker for anyone who uses Kerberos support and wants to have more than one solr node per host. Thanks, Ishan On Thu, Dec 17, 2015 at 2:45 AM, Upayavira wrote:

Re: 5.3.2 bug fix release

Historical aside: I was thinking we’d never produced a bugfix release on a previous minor branch, but I went looking and found that 4.9.1, released 9/21/14, was just such a one: 4.10.0 was released on 9/4/14. AFAICT Mike McCandless initially proposed a 4.9.1 release on 9/16/14 here:

[jira] [Commented] (LUCENE-6933) Create a (cleaned up) SVN history in git

[ https://issues.apache.org/jira/browse/LUCENE-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15061015#comment-15061015 ] Dawid Weiss commented on LUCENE-6933: - After some more digging and experiments it seems realistic

[jira] [Commented] (SOLR-8191) Guard against CloudSolrStream close method NullPointerException

[ https://issues.apache.org/jira/browse/SOLR-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15060931#comment-15060931 ] ASF subversion and git services commented on SOLR-8191: --- Commit 1720460 from

[jira] [Created] (LUCENE-6938) Convert build to work with Git rather than SVN.

Mark Miller created LUCENE-6938: --- Summary: Convert build to work with Git rather than SVN. Key: LUCENE-6938 URL: https://issues.apache.org/jira/browse/LUCENE-6938 Project: Lucene - Core Issue

Re: svn commit: r1720085 - /lucene/cms/trunk/content/core/quickstart.mdtext

I thought there was a macro to refer to the latest stable version# so edits like this didn't need to be made after every release? And isn't there a redirect path for the same purpose? Something like this i think (looking at other existing pages)... Lucene {% include

[JENKINS-EA] Lucene-Solr-trunk-Linux (64bit/jdk-9-ea+95) - Build # 15223 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15223/ Java: 64bit/jdk-9-ea+95 -XX:-UseCompressedOops -XX:+UseSerialGC -XX:-CompactStrings 3 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.cloud.CollectionsAPIDistributedZkTest Error Message: 5 threads leaked from

[jira] [Commented] (SOLR-8190) Implement Closeable on TupleStream

[ https://issues.apache.org/jira/browse/SOLR-8190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15060966#comment-15060966 ] Joel Bernstein commented on SOLR-8190: -- Gave this a quick review. I like the idea of implementing

[jira] [Comment Edited] (LUCENE-6933) Create a (cleaned up) SVN history in git

[ https://issues.apache.org/jira/browse/LUCENE-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15061035#comment-15061035 ] Dawid Weiss edited comment on LUCENE-6933 at 12/16/15 10:38 PM: They will

Re: Lucene/Solr git mirror will soon turn off

I filed LUCENE-6937 as a parent issue for an SVN->Git migration. I've linked the issue that Dawid is working on, as well as a new issue for converting the build to work correctly in a Git checkout rather than SVN. - Mark On Tue, Dec 15, 2015 at 1:26 PM Mark Miller wrote:

[jira] [Commented] (SOLR-8416) Solr collection creation API should return after all cores are alive

[ https://issues.apache.org/jira/browse/SOLR-8416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15060912#comment-15060912 ] Michael Sun commented on SOLR-8416: --- Thanks [~markrmil...@gmail.com] for reviewing. > Solr collection

[jira] [Updated] (SOLR-8426) Make /export, /stream and /sql handlers implicit

[ https://issues.apache.org/jira/browse/SOLR-8426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shalin Shekhar Mangar updated SOLR-8426: Attachment: SOLR-8426.patch Patch which fixes a failure in

Re: 5.3.2 bug fix release

On 12/16/2015 2:15 PM, Upayavira wrote: > Why don't people just upgrade to 5.4? Why do we need another release in > the 5.3.x range? I am using a third-party custom Solr plugin. The latest version of that plugin (which I have on my dev server) has only been certified to work with Solr 5.3.x.

[jira] [Commented] (LUCENE-6933) Create a (cleaned up) SVN history in git

[ https://issues.apache.org/jira/browse/LUCENE-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15061035#comment-15061035 ] Dawid Weiss commented on LUCENE-6933: - They will break (because we plan to remove JARs and binary

[jira] [Commented] (LUCENE-6937) Migrate Lucene project from SVN to Git.

[ https://issues.apache.org/jira/browse/LUCENE-6937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15061043#comment-15061043 ] Mark Miller commented on LUCENE-6937: - As mentioned in LUCENE-6933,

[jira] [Commented] (SOLR-7885) Add support for loading HTTP resources

[ https://issues.apache.org/jira/browse/SOLR-7885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15060905#comment-15060905 ] Aaron LaBella commented on SOLR-7885: - BTW, trying to call command=reload-config=... on the DIH doesn't

[jira] [Created] (SOLR-8430) ReplicationHandler throttling should be applied across all concurrent replication requests

Shalin Shekhar Mangar created SOLR-8430: --- Summary: ReplicationHandler throttling should be applied across all concurrent replication requests Key: SOLR-8430 URL:

Re: [jira] [Updated] (LUCENE-6933) Create a (cleaned up) SVN history in git

We can't touch Apache's SVN so it definitely stays! :) This was also something that crossed my mind -- we effectively have multiple separate projects in one git repo. While it's something SVN can take, it's a more problematic issue with git. I don't know if one Apache project can have multiple

Re: [jira] [Updated] (LUCENE-6933) Create a (cleaned up) SVN history in git

> I personally don't care. Git has been a non-issue in PyLucene. > It can move with Lucene or stay in SVN, either way is fine by me. I don't see a problem with it staying in SVN, we'd just clean up dev, much like it has been done before when Solr and Lucene were merged (in fact, this is what you

Re: [jira] [Updated] (LUCENE-6933) Create a (cleaned up) SVN history in git

One project can have multiple git repos. Apparently there's one or more with 100+ repos, so all is good there if pylucene wants to shift to git also. Upayavira On Wed, Dec 16, 2015, at 09:48 PM, Dawid Weiss wrote: > >> I personally don't care. Git has been a non-issue in PyLucene. >> It can

[jira] [Comment Edited] (LUCENE-6933) Create a (cleaned up) SVN history in git

[ https://issues.apache.org/jira/browse/LUCENE-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15061015#comment-15061015 ] Dawid Weiss edited comment on LUCENE-6933 at 12/16/15 10:27 PM: After

[jira] [Commented] (SOLR-7885) Add support for loading HTTP resources

[ https://issues.apache.org/jira/browse/SOLR-7885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15060901#comment-15060901 ] Aaron LaBella commented on SOLR-7885: - I'm closing this issue as I literally just took my patch and

[jira] [Closed] (SOLR-7885) Add support for loading HTTP resources

[ https://issues.apache.org/jira/browse/SOLR-7885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron LaBella closed SOLR-7885. --- Resolution: Not A Problem > Add support for loading HTTP resources >

[jira] [Commented] (SOLR-8191) Guard against CloudSolrStream close method NullPointerException

[ https://issues.apache.org/jira/browse/SOLR-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15060943#comment-15060943 ] ASF subversion and git services commented on SOLR-8191: --- Commit 1720461 from

[jira] [Commented] (SOLR-8426) Make /export, /stream and /sql handlers implicit

[ https://issues.apache.org/jira/browse/SOLR-8426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15060986#comment-15060986 ] ASF subversion and git services commented on SOLR-8426: --- Commit 1720468 from

[jira] [Commented] (SOLR-8190) Implement Closeable on TupleStream

[ https://issues.apache.org/jira/browse/SOLR-8190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15061076#comment-15061076 ] Kevin Risden commented on SOLR-8190: The getTuples method was added recently which is the only place

[jira] [Updated] (SOLR-8426) Make /export, /stream and /sql handlers implicit

[ https://issues.apache.org/jira/browse/SOLR-8426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shalin Shekhar Mangar updated SOLR-8426: Attachment: SOLR-8426.patch > Make /export, /stream and /sql handlers implicit >

Re: [jira] [Updated] (LUCENE-6933) Create a (cleaned up) SVN history in git

On Wed, 16 Dec 2015, Dawid Weiss (JIRA) wrote: [ https://issues.apache.org/jira/browse/LUCENE-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dawid Weiss updated LUCENE-6933: Description: Goals: * selectively drop projects

[jira] [Updated] (SOLR-8191) Guard against CloudSolrStream close method NullPointerException

[ https://issues.apache.org/jira/browse/SOLR-8191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Bernstein updated SOLR-8191: - Summary: Guard against CloudSolrStream close method NullPointerException (was: CloudSolrStream

Re: [jira] [Updated] (LUCENE-6933) Create a (cleaned up) SVN history in git

On Wed, 16 Dec 2015, Dawid Weiss wrote: We can't touch Apache's SVN so it definitely stays! :) This was also something that crossed my mind -- we effectively have multiple separate projects in one git repo. While it's something SVN can take, it's a more problematic issue with git. I don't

[jira] [Commented] (SOLR-7885) Add support for loading HTTP resources

[ https://issues.apache.org/jira/browse/SOLR-7885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15060946#comment-15060946 ] Jan Høydahl commented on SOLR-7885: --- With SolrCloud, you could use ZooKeeper as integration point and let

[jira] [Resolved] (SOLR-8426) Make /export, /stream and /sql handlers implicit

[ https://issues.apache.org/jira/browse/SOLR-8426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shalin Shekhar Mangar resolved SOLR-8426. - Resolution: Fixed Assignee: Shalin Shekhar Mangar > Make /export, /stream

[jira] [Commented] (LUCENE-6933) Create a (cleaned up) SVN history in git

[ https://issues.apache.org/jira/browse/LUCENE-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15061027#comment-15061027 ] Upayavira commented on LUCENE-6933: --- [~dweiss] Just for clarity's sake - what impact will this have on

[jira] [Created] (LUCENE-6937) Migrate Lucene project from SVN to Git.

Mark Miller created LUCENE-6937: --- Summary: Migrate Lucene project from SVN to Git. Key: LUCENE-6937 URL: https://issues.apache.org/jira/browse/LUCENE-6937 Project: Lucene - Core Issue Type:

[jira] [Updated] (SOLR-445) Update Handlers abort with bad documents

[ https://issues.apache.org/jira/browse/SOLR-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoss Man updated SOLR-445: -- Attachment: SOLR-445.patch I started playing arround with this patch a bit to see if I could help move it

Re: Lucene/Solr git mirror will soon turn off

On 12/16/2015 5:53 PM, Alexandre Rafalovitch wrote: > On 16 December 2015 at 00:44, Dawid Weiss wrote: >> 4) The size of JARs is really not an issue. The entire SVN repo I mirrored >> locally (including empty interim commits to cater for svn:mergeinfos) is 4G. >> If you

[JENKINS] Lucene-Solr-trunk-MacOSX (64bit/jdk1.8.0) - Build # 2947 - Still Failing!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-MacOSX/2947/ Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseG1GC 6 tests failed. FAILED: org.apache.solr.handler.dataimport.TestContentStreamDataSource.testCommitWithin Error Message: IOException occured when talking to server at:

[JENKINS-EA] Lucene-Solr-trunk-Linux (64bit/jdk-9-ea+95) - Build # 15225 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/15225/ Java: 64bit/jdk-9-ea+95 -XX:+UseCompressedOops -XX:+UseParallelGC -XX:-CompactStrings 35 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.cloud.DistributedVersionInfoTest Error Message: Suite timeout exceeded

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

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Solaris/265/ Java: 64bit/jdk1.8.0 -XX:-UseCompressedOops -XX:+UseParallelGC 4 tests failed. FAILED: org.apache.solr.cloud.RecoveryAfterSoftCommitTest.test Error Message: Error from server at http://127.0.0.1:50070/collection1: Service

[jira] [Commented] (SOLR-8220) Read field from docValues for non stored fields

[ https://issues.apache.org/jira/browse/SOLR-8220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15061581#comment-15061581 ] Shalin Shekhar Mangar commented on SOLR-8220: - Thanks Ishan. # The

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

Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-5.x/1048/ 1 tests failed. FAILED: org.apache.solr.cloud.TestMiniSolrCloudCluster.testStopAllStartAll Error Message: Address already in use Stack Trace: java.net.BindException: Address already in use at

Re: 5.3.2 bug fix release

Yes, there was already a 5.3.2 version in JIRA. I will start back-porting stuff to the lucene_solr_5_3 branch later in the day today. On Thu, Dec 17, 2015 at 11:35 AM, Noble Paul wrote: > Agree with Shawn here. > > If a company has already done the work to upgrade their

Re: 5.3.2 bug fix release

Thanks for explaining it so well Shawn :) Yes, that's pretty much the reason why it makes sense to have a 5.3.2 release. We might even need a 5.4.1 after that as there are more security bug fixes that are getting committed as the feature is being tried by users and bugs are being reported. On

Re: 5.3.2 bug fix release

Agree with Shawn here. If a company has already done the work to upgrade their systems to 5.3.1 , they would rather have a bug fix for the old version . So anshum, is there a 5.3.2 version created in JIRA? can we start tagging issues to that release so that we can have a definitive list of bugs

[JENKINS] Lucene-Solr-5.x-Solaris (multiarch/jdk1.7.0) - Build # 263 - Failure!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-5.x-Solaris/263/ Java: multiarch/jdk1.7.0 -d64 -XX:+UseCompressedOops -XX:+UseSerialGC 2 tests failed. FAILED: org.apache.solr.schema.TestCloudSchemaless.test Error Message: QUERY FAILED:

[jira] [Updated] (SOLR-8279) Add a new SolrCloud test that stops and starts the cluster while indexing data.

[ https://issues.apache.org/jira/browse/SOLR-8279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller updated SOLR-8279: -- Attachment: SOLR-8279.patch All the nocommits and such are out, I think this is pretty close, still need

[jira] [Updated] (SOLR-8279) Add a new SolrCloud test that stops and starts the cluster while indexing data with fault injection.

[ https://issues.apache.org/jira/browse/SOLR-8279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller updated SOLR-8279: -- Summary: Add a new SolrCloud test that stops and starts the cluster while indexing data with fault

[jira] [Commented] (SOLR-8416) Solr collection creation API should return after all cores are alive

[ https://issues.apache.org/jira/browse/SOLR-8416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15061319#comment-15061319 ] Gregory Chanan commented on SOLR-8416: -- I'd see what hbase or other systems do. > Solr collection

[JENKINS] Lucene-Solr-Tests-trunk-Java8 - Build # 703 - Failure

Build: https://builds.apache.org/job/Lucene-Solr-Tests-trunk-Java8/703/ 3 tests failed. FAILED: org.apache.solr.cloud.CollectionsAPIDistributedZkTest.test Error Message: Error from server at http://127.0.0.1:48794/p/cz/awholynewcollection_0: non ok status: 500, message:Server Error Stack

[jira] [Commented] (SOLR-8429) add a flag blockUnauthenticated to BasicAutPlugin

[ https://issues.apache.org/jira/browse/SOLR-8429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15061360#comment-15061360 ] Noble Paul commented on SOLR-8429: -- I don't think we need to change the default and change the default

Re: Lucene/Solr git mirror will soon turn off

+1 totally agree. Any way; the bloat should largely be the binaries & unrelated projects, not code (small text files). On Wed, Dec 16, 2015 at 10:36 PM Doug Turnbull < dturnb...@opensourceconnections.com> wrote: > In defense of more history immediately available--it is often far more > useful

[jira] [Commented] (SOLR-8429) add a flag blockUnauthenticated to BasicAutPlugin

[ https://issues.apache.org/jira/browse/SOLR-8429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15061208#comment-15061208 ] Jan Høydahl commented on SOLR-8429: --- Let's make it default to true from 5.5, aligning with what people

Re: Lucene/Solr git mirror will soon turn off

On Thu, Dec 17, 2015, at 12:53 AM, Alexandre Rafalovitch wrote: > On 16 December 2015 at 00:44, Dawid Weiss wrote: > > 4) The size of JARs is really not an issue. The entire SVN repo I mirrored > > locally (including empty interim commits to cater for svn:mergeinfos) is

[JENKINS] Lucene-Solr-trunk-Windows (64bit/jdk1.8.0_66) - Build # 5477 - Still Failing!

Build: http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Windows/5477/ Java: 64bit/jdk1.8.0_66 -XX:+UseCompressedOops -XX:+UseG1GC 2 tests failed. FAILED: org.apache.solr.search.AnalyticsMergeStrategyTest.test Error Message: Error from server at https://127.0.0.1:53866//collection1:

  1   2   >