[jira] [Commented] (SOLR-9577) SolrConfig edit operations should not need to reload core

[ https://issues.apache.org/jira/browse/SOLR-9577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15531885#comment-15531885 ] Noble Paul commented on SOLR-9577: -- Let's review our internal components that use closehooks and

[jira] [Resolved] (SOLR-9576) Make FieldAnalysisRequestHandler & DocumentAnalysisRequestHandler implicit

[ https://issues.apache.org/jira/browse/SOLR-9576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul resolved SOLR-9576. -- Resolution: Fixed Fix Version/s: master (7.0) 6.3 > Make

[JENKINS-EA] Lucene-Solr-6.x-Linux (64bit/jdk-9-ea+136) - Build # 1827 - Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-6.x-Linux/1827/ Java: 64bit/jdk-9-ea+136 -XX:-UseCompressedOops -XX:+UseG1GC 2 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.cloud.DeleteInactiveReplicaTest Error Message: 1 thread leaked from SUITE scope at

[JENKINS] Lucene-Solr-master-Windows (32bit/jdk1.8.0_102) - Build # 6145 - Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Windows/6145/ Java: 32bit/jdk1.8.0_102 -client -XX:+UseG1GC 1 tests failed. FAILED: org.apache.solr.util.TestSolrCLIRunExample.testInteractiveSolrCloudExample Error Message: Expected 10 to be found in the testCloudExamplePrompt

Re: Kudos to Jan

Jan has been so quick to prioritize the JIRA's. Thanks Jan for your promptness. Thanks, Susheel On Wed, Sep 28, 2016 at 8:03 PM, Martin Gainty wrote: > many apache projects contain 2 groups of people > > -managers who get the credit for the project > > -contributors who

[GitHub] lucene-solr pull request #85: Allow updating configs like port # on forced u...

GitHub user jasondemorrow opened a pull request: https://github.com/apache/lucene-solr/pull/85 Allow updating configs like port # on forced upgrade You can merge this pull request into a Git repository by running: $ git pull https://github.com/jasondemorrow/lucene-solr master

RE: Kudos to Jan

many apache projects contain 2 groups of people -managers who get the credit for the project -contributors who do the work for the project I would like to see Jan the contributor promoted to the group who gets credit for the project Agreed? Martin

[JENKINS] Lucene-Solr-SmokeRelease-master - Build # 587 - Failure

Build: https://builds.apache.org/job/Lucene-Solr-SmokeRelease-master/587/ No tests ran. Build Log: [...truncated 40574 lines...] prepare-release-no-sign: [mkdir] Created dir: /x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-master/lucene/build/smokeTestRelease/dist [copy]

[JENKINS] Lucene-Solr-NightlyTests-6.2 - Build # 10 - Failure

Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-6.2/10/ 9 tests failed. FAILED: org.apache.lucene.codecs.simpletext.TestSimpleTextDocValuesFormat.testSortedNumericsSingleValuedVsStoredFields Error Message: Test abandoned because suite timeout was reached. Stack Trace:

[jira] [Commented] (SOLR-6203) cast exception while searching with sort function and result grouping

[ https://issues.apache.org/jira/browse/SOLR-6203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15531054#comment-15531054 ] Judd Krishef commented on SOLR-6203: Hello, does anybody know if this issue has been resolved in Solr

[jira] [Updated] (SOLR-9442) Add json.nl=arrnvp (array of NamedValuePair) style in JSONResponseWriter

[ https://issues.apache.org/jira/browse/SOLR-9442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonny Marks updated SOLR-9442: -- Attachment: SOLR-9442.patch Attaching full patch > Add json.nl=arrnvp (array of NamedValuePair) style

[jira] [Updated] (SOLR-9554) Multiple ManagedIndexSchemaFactory upgrades running simultaneously can clash, causing cores not to load

[ https://issues.apache.org/jira/browse/SOLR-9554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Khludnev updated SOLR-9554: --- Attachment: SOLR-9554.patch Attaching a simplified test without that latch. Now it's just

[jira] [Commented] (SOLR-9579) Reuse lucene FieldType in createField flow during ingestion

[ https://issues.apache.org/jira/browse/SOLR-9579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530812#comment-15530812 ] Mikhail Khludnev commented on SOLR-9579: yep.. hadoop API is known for such optimization, and

[jira] [Updated] (SOLR-9579) Reuse lucene FieldType in createField flow during ingestion

[ https://issues.apache.org/jira/browse/SOLR-9579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Call updated SOLR-9579: Security: (was: Public) > Reuse lucene FieldType in createField flow during ingestion >

[jira] [Updated] (SOLR-9579) Reuse lucene FieldType in createField flow during ingestion

[ https://issues.apache.org/jira/browse/SOLR-9579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Call updated SOLR-9579: Attachment: SOLR-9579.patch This patch is an initial attempt at reusing lucene FieldType. It was created

[jira] [Created] (SOLR-9579) Reuse lucene FieldType in createField flow during ingestion

John Call created SOLR-9579: --- Summary: Reuse lucene FieldType in createField flow during ingestion Key: SOLR-9579 URL: https://issues.apache.org/jira/browse/SOLR-9579 Project: Solr Issue Type:

[jira] [Commented] (SOLR-9369) SolrCloud should not compare commitTimeMSec to see if replicas are in sync

[ https://issues.apache.org/jira/browse/SOLR-9369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530492#comment-15530492 ] Pushkar Raste commented on SOLR-9369: - [SOLR-9446|https://issues.apache.org/jira/browse/SOLR-9446]

Re: Solr configuration format fracturing

On 9/25/2016 11:41 AM, Shawn Heisey wrote: > Thoughts? Is this too scary to contemplate? Should I open an umbrella > issue in Jira to get the ball rolling? I think we've had a decent discussion, with an indication that we need to at least consider some action. JSON still looks like the winner.

[jira] [Created] (SOLR-9578) Implement document level security in Solr

Hrishikesh Gadre created SOLR-9578: -- Summary: Implement document level security in Solr Key: SOLR-9578 URL: https://issues.apache.org/jira/browse/SOLR-9578 Project: Solr Issue Type: Bug

[GitHub] lucene-solr pull request #84: Solr 9506 Parallalize/Cache per segment finger...

GitHub user praste opened a pull request: https://github.com/apache/lucene-solr/pull/84 Solr 9506 Parallalize/Cache per segment fingerprint Removed old serial fingerprint computation You can merge this pull request into a Git repository by running: $ git pull

Re: Kudos to Jan

Definitely a great effort. Not only closing/cleaning up JIRAs but putting in a lot of effort to making logging more sane. Kevin Risden On Wed, Sep 28, 2016 at 11:50 AM, Alexandre Rafalovitch wrote: > +1 > > I tried doing that too, so I know the effort it takes :-) > >

Re: Kudos to Jan

+1 I tried doing that too, so I know the effort it takes :-) Regards, Alex. Newsletter and resources for Solr beginners and intermediates: http://www.solr-start.com/ On 28 September 2016 at 23:10, David Smiley wrote: > Yes; thanks Jan! > > > On Wed, Sep 28,

[jira] [Commented] (LUCENE-7468) ASCIIFoldingFilter should not emit duplicated tokens when preserve original is on

[ https://issues.apache.org/jira/browse/LUCENE-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530177#comment-15530177 ] David Causse commented on LUCENE-7468: -- Yes I plan to use a filter that removes duplicates to

Re: Kudos to Jan

Yes; thanks Jan! On Wed, Sep 28, 2016 at 11:38 AM Erick Erickson wrote: > Jan: > > Wanted to send a public thanks for your efforts to clean up old JIRAs. > We even have more JIRAs closed than opened in the last 30 days! > > It's a thankless task, much appreciated. > >

[jira] [Commented] (LUCENE-7468) ASCIIFoldingFilter should not emit duplicated tokens when preserve original is on

[ https://issues.apache.org/jira/browse/LUCENE-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530085#comment-15530085 ] Erick Erickson commented on LUCENE-7468: I think it's still a good point that saving the same

[jira] [Commented] (LUCENE-7468) ASCIIFoldingFilter should not emit duplicated tokens when preserve original is on

[ https://issues.apache.org/jira/browse/LUCENE-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530076#comment-15530076 ] Steve Rowe commented on LUCENE-7468: [~dcausse], couldn't you just use RemoveDuplicatesTokenFilter?

Re: Kudos to Jan

+1 Mike McCandless http://blog.mikemccandless.com On Wed, Sep 28, 2016 at 5:37 PM, Erick Erickson wrote: > Jan: > > Wanted to send a public thanks for your efforts to clean up old JIRAs. > We even have more JIRAs closed than opened in the last 30 days! > > It's a

[jira] [Updated] (SOLR-6266) Couchbase plug-in for Solr

[ https://issues.apache.org/jira/browse/SOLR-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joel Bernstein updated SOLR-6266: - Assignee: (was: Joel Bernstein) > Couchbase plug-in for Solr > -- > >

Kudos to Jan

Jan: Wanted to send a public thanks for your efforts to clean up old JIRAs. We even have more JIRAs closed than opened in the last 30 days! It's a thankless task, much appreciated. Erick - To unsubscribe, e-mail:

[JENKINS] Lucene-Solr-6.x-Windows (32bit/jdk1.8.0_102) - Build # 481 - Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-6.x-Windows/481/ Java: 32bit/jdk1.8.0_102 -server -XX:+UseParallelGC 1 tests failed. FAILED: org.apache.solr.security.BasicAuthIntegrationTest.testBasicAuth Error Message: expected:<200> but was:<403> Stack Trace: java.lang.AssertionError:

[jira] [Comment Edited] (SOLR-9554) Multiple ManagedIndexSchemaFactory upgrades running simultaneously can clash, causing cores not to load

[ https://issues.apache.org/jira/browse/SOLR-9554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529863#comment-15529863 ] Mikhail Khludnev edited comment on SOLR-9554 at 9/28/16 2:43 PM: - I make

[jira] [Updated] (SOLR-9554) Multiple ManagedIndexSchemaFactory upgrades running simultaneously can clash, causing cores not to load

[ https://issues.apache.org/jira/browse/SOLR-9554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Khludnev updated SOLR-9554: --- Attachment: SOLR-9554.patch I make test really really mad. It synchronizes race to reproduce

[jira] [Commented] (SOLR-9576) Make FieldAnalysisRequestHandler & DocumentAnalysisRequestHandler implicit

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

[jira] [Commented] (SOLR-9576) Make FieldAnalysisRequestHandler & DocumentAnalysisRequestHandler implicit

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

[jira] [Commented] (SOLR-9577) SolrConfig edit operations should not need to reload core

[ https://issues.apache.org/jira/browse/SOLR-9577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529682#comment-15529682 ] Shalin Shekhar Mangar commented on SOLR-9577: - In that case, let us deprecate close hooks from

[JENKINS] Lucene-Solr-Tests-6.x - Build # 457 - Unstable

Build: https://builds.apache.org/job/Lucene-Solr-Tests-6.x/457/ 6 tests failed. FAILED: org.apache.solr.cloud.CdcrVersionReplicationTest.testCdcrDocVersions Error Message: Captured an uncaught exception in thread: Thread[id=54168, name=qtp1123913138-54168, state=RUNNABLE,

[jira] [Assigned] (SOLR-8370) Display Similarity Factory in use in Schema-Browser

[ https://issues.apache.org/jira/browse/SOLR-8370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl reassigned SOLR-8370: - Assignee: Jan Høydahl > Display Similarity Factory in use in Schema-Browser >

[jira] [Updated] (SOLR-8370) Display Similarity Factory in use in Schema-Browser

[ https://issues.apache.org/jira/browse/SOLR-8370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl updated SOLR-8370: -- Attachment: SOLR-8370.patch First patch. Adds "similarity" to Luke response, and displays it below "id"

[jira] [Updated] (LUCENE-7468) ASCIIFoldingFilter should not emit duplicated tokens when preserve original is on

[ https://issues.apache.org/jira/browse/LUCENE-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Causse updated LUCENE-7468: - Attachment: (was: LUCENE-7468.patch) > ASCIIFoldingFilter should not emit duplicated tokens

[jira] [Updated] (LUCENE-7468) ASCIIFoldingFilter should not emit duplicated tokens when preserve original is on

[ https://issues.apache.org/jira/browse/LUCENE-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Causse updated LUCENE-7468: - Attachment: LUCENE-7468.patch > ASCIIFoldingFilter should not emit duplicated tokens when

[jira] [Updated] (LUCENE-7468) ASCIIFoldingFilter should not emit duplicated tokens when preserve original is on

[ https://issues.apache.org/jira/browse/LUCENE-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Causse updated LUCENE-7468: - Attachment: LUCENE-7468.patch > ASCIIFoldingFilter should not emit duplicated tokens when

[jira] [Updated] (LUCENE-7468) ASCIIFoldingFilter should not emit duplicated tokens when preserve original is on

[ https://issues.apache.org/jira/browse/LUCENE-7468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Causse updated LUCENE-7468: - Description: The ASCIIFoldingFilter seems to make the bold assumption that any tokens that

[jira] [Created] (LUCENE-7468) ASCIIFoldingFilter should not emit duplicated tokens when preserve original is on

David Causse created LUCENE-7468: Summary: ASCIIFoldingFilter should not emit duplicated tokens when preserve original is on Key: LUCENE-7468 URL: https://issues.apache.org/jira/browse/LUCENE-7468

[jira] [Commented] (SOLR-9553) Solr 6.2 boolean dynamic fields (_b suffix) are always setting to false even if explicitly setting a field to true

[ https://issues.apache.org/jira/browse/SOLR-9553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529497#comment-15529497 ] Daniel Rossi Marinho commented on SOLR-9553: SOLR 6.2.1 fixed the issue!! Thanks! > Solr 6.2

[jira] [Issue Comment Deleted] (SOLR-9553) Solr 6.2 boolean dynamic fields (_b suffix) are always setting to false even if explicitly setting a field to true

[ https://issues.apache.org/jira/browse/SOLR-9553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Rossi Marinho updated SOLR-9553: --- Comment: was deleted (was: SOLR 6.2.1 fixes the issue!) > Solr 6.2 boolean dynamic

[jira] [Resolved] (SOLR-9553) Solr 6.2 boolean dynamic fields (_b suffix) are always setting to false even if explicitly setting a field to true

[ https://issues.apache.org/jira/browse/SOLR-9553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Rossi Marinho resolved SOLR-9553. Resolution: Fixed Fix Version/s: (was: 5.5) 6.2.1 SOLR

[JENKINS-EA] Lucene-Solr-6.x-Linux (64bit/jdk-9-ea+136) - Build # 1822 - Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-6.x-Linux/1822/ Java: 64bit/jdk-9-ea+136 -XX:-UseCompressedOops -XX:+UseConcMarkSweepGC 1 tests failed. FAILED: org.apache.solr.update.AutoCommitTest.testCommitWithin Error Message: Exception during query Stack Trace:

[jira] [Comment Edited] (SOLR-8611) Incorrect logging in ZkController

[ https://issues.apache.org/jira/browse/SOLR-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529332#comment-15529332 ] Stephan Lagraulet edited comment on SOLR-8611 at 9/28/16 11:31 AM: --- This

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

[ https://issues.apache.org/jira/browse/SOLR-7236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl closed SOLR-7236. - Resolution: Implemented Closing this old umbrella. > Securing Solr (umbrella issue) >

[jira] [Commented] (SOLR-8611) Incorrect logging in ZkController

[ https://issues.apache.org/jira/browse/SOLR-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529332#comment-15529332 ] Stephan Lagraulet commented on SOLR-8611: - This only occured on our production node when a massive

[jira] [Closed] (SOLR-2823) Re-use of UpdateProcessor configurations in multiple UpdateChains

[ https://issues.apache.org/jira/browse/SOLR-2823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl closed SOLR-2823. - Resolution: Implemented Closing this as we since have much more flexibility in defining chains etc. >

[jira] [Closed] (SOLR-2842) Re-factor UpdateChain and UpdateProcessor interfaces

[ https://issues.apache.org/jira/browse/SOLR-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl closed SOLR-2842. - Resolution: Won't Fix I'm abandoning this idea and closing the issue :-) > Re-factor UpdateChain and

[jira] [Closed] (SOLR-2841) Scriptable UpdateRequestChain

[ https://issues.apache.org/jira/browse/SOLR-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl closed SOLR-2841. - Resolution: Later Closing this as "later" as I am not going to work on it and there has not been much

[JENKINS] Lucene-Solr-SmokeRelease-6.2 - Build # 10 - Failure

Build: https://builds.apache.org/job/Lucene-Solr-SmokeRelease-6.2/10/ No tests ran. Build Log: [...truncated 40545 lines...] prepare-release-no-sign: [mkdir] Created dir: /x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-6.2/lucene/build/smokeTestRelease/dist [copy] Copying

[jira] [Commented] (SOLR-9120) Luke NoSuchFileException

[ https://issues.apache.org/jira/browse/SOLR-9120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529228#comment-15529228 ] Henry Cleland commented on SOLR-9120: - Same is on Solr 6.2.1, it blocks the admin interface and then

[jira] [Comment Edited] (SOLR-9577) SolrConfig edit operations should not need to reload core

[ https://issues.apache.org/jira/browse/SOLR-9577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529198#comment-15529198 ] Noble Paul edited comment on SOLR-9577 at 9/28/16 10:25 AM: bq. IMO, the close

[jira] [Commented] (SOLR-9577) SolrConfig edit operations should not need to reload core

[ https://issues.apache.org/jira/browse/SOLR-9577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529198#comment-15529198 ] Noble Paul commented on SOLR-9577: -- bq. IMO, the close hooks are a workaround for the fact that our

[jira] [Closed] (SOLR-3090) When running a ZK ensemble within Solr, the info logging is too verbose.

[ https://issues.apache.org/jira/browse/SOLR-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl closed SOLR-3090. - Resolution: Cannot Reproduce This is already fixed by setting zookeeper logging level to WARN in

[jira] [Updated] (SOLR-3090) When running a ZK ensemble within Solr, the info logging is too verbose.

[ https://issues.apache.org/jira/browse/SOLR-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl updated SOLR-3090: -- Fix Version/s: (was: 6.0) (was: 4.9) > When running a ZK ensemble within

[jira] [Commented] (SOLR-6377) Admin UI Logging tab doesn't work with different loggers

[ https://issues.apache.org/jira/browse/SOLR-6377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529169#comment-15529169 ] Jan Høydahl commented on SOLR-6377: --- What happened to this new logWatcher? > Admin UI Logging tab

[jira] [Commented] (SOLR-7506) Roll over GC logs by default via bin/solr scripts

[ https://issues.apache.org/jira/browse/SOLR-7506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529158#comment-15529158 ] Jan Høydahl commented on SOLR-7506: --- Unfortunately the JVM is not that smart. It *always* starts writing

[jira] [Assigned] (SOLR-9570) Logs backed up on restart are kept forever

[ https://issues.apache.org/jira/browse/SOLR-9570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl reassigned SOLR-9570: - Assignee: Jan Høydahl > Logs backed up on restart are kept forever >

[JENKINS] Lucene-Solr-6.x-Linux (32bit/jdk1.8.0_102) - Build # 1821 - Failure!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-6.x-Linux/1821/ Java: 32bit/jdk1.8.0_102 -client -XX:+UseParallelGC 1 tests failed. FAILED: org.apache.solr.cloud.CdcrVersionReplicationTest.testCdcrDocVersions Error Message: Captured an uncaught exception in thread: Thread[id=134,

[jira] [Commented] (SOLR-5901) Shutdown logs a bunch of scary warnings around failed leader election that are expected in the normal course of operations and should not be logged.

[ https://issues.apache.org/jira/browse/SOLR-5901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529145#comment-15529145 ] Jan Høydahl commented on SOLR-5901: --- Related to the work we're doing in SOLR-6677.

[JENKINS] Lucene-Solr-SmokeRelease-6.x - Build # 153 - Still Failing

Build: https://builds.apache.org/job/Lucene-Solr-SmokeRelease-6.x/153/ No tests ran. Build Log: [...truncated 40545 lines...] prepare-release-no-sign: [mkdir] Created dir: /x1/jenkins/jenkins-slave/workspace/Lucene-Solr-SmokeRelease-6.x/lucene/build/smokeTestRelease/dist [copy] Copying

[jira] [Commented] (SOLR-6677) Reduce logging during startup and shutdown

[ https://issues.apache.org/jira/browse/SOLR-6677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529135#comment-15529135 ] Jan Høydahl commented on SOLR-6677: --- Looks like SOLR-5901 is related too. It has an old patch.

[jira] [Commented] (SOLR-8016) CloudSolrClient has extremely verbose error logging

[ https://issues.apache.org/jira/browse/SOLR-8016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529128#comment-15529128 ] Jan Høydahl commented on SOLR-8016: --- Any conclusion on this? > CloudSolrClient has extremely verbose

[jira] [Updated] (SOLR-9554) Multiple ManagedIndexSchemaFactory upgrades running simultaneously can clash, causing cores not to load

[ https://issues.apache.org/jira/browse/SOLR-9554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Kudryavtsev updated SOLR-9554: - Attachment: SOLR-9554.patch > Multiple ManagedIndexSchemaFactory upgrades running

[jira] [Commented] (SOLR-9043) Cleanup unwanted logging statement from CollectionsHandler on 5x

[ https://issues.apache.org/jira/browse/SOLR-9043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529096#comment-15529096 ] Jan Høydahl commented on SOLR-9043: --- Are you done with this issue, can it be closed? > Cleanup unwanted

[jira] [Commented] (SOLR-8611) Incorrect logging in ZkController

[ https://issues.apache.org/jira/browse/SOLR-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529093#comment-15529093 ] Jan Høydahl commented on SOLR-8611: --- Can you help with some steps to reproduce in the simplest possible

[jira] [Commented] (SOLR-9554) Multiple ManagedIndexSchemaFactory upgrades running simultaneously can clash, causing cores not to load

[ https://issues.apache.org/jira/browse/SOLR-9554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529090#comment-15529090 ] Andrey Kudryavtsev commented on SOLR-9554: -- {{ManagedIndexSchemaFactory#create}} contains a pretty

[jira] [Commented] (SOLR-8611) Incorrect logging in ZkController

[ https://issues.apache.org/jira/browse/SOLR-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529013#comment-15529013 ] Stephan Lagraulet commented on SOLR-8611: - That's right, core node information is not updated. As

[jira] [Closed] (SOLR-5785) Turn down absurdly verbose test logging (megabytes)

[ https://issues.apache.org/jira/browse/SOLR-5785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl closed SOLR-5785. - Resolution: Resolved Closing this as resolved now that we have tuned down the logs quite a bit. Although

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

[ https://issues.apache.org/jira/browse/SOLR-7329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529005#comment-15529005 ] Jan Høydahl commented on SOLR-7329: --- Looks like this was committed, but never resolved. It is not

[jira] [Commented] (SOLR-8611) Incorrect logging in ZkController

[ https://issues.apache.org/jira/browse/SOLR-8611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15528997#comment-15528997 ] Jan Høydahl commented on SOLR-8611: --- Could not reproduce this. Can you provide instructions on how to

[JENKINS-EA] Lucene-Solr-master-Linux (64bit/jdk-9-ea+136) - Build # 17919 - Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/17919/ Java: 64bit/jdk-9-ea+136 -XX:+UseCompressedOops -XX:+UseG1GC 1 tests failed. FAILED: org.apache.solr.cloud.LeaderFailoverAfterPartitionTest.test Error Message: Expected 2 of 3 replicas to be active but only found 1;

[jira] [Closed] (SOLR-2903) MalformedURLException logging in TikaEntityProcessor

[ https://issues.apache.org/jira/browse/SOLR-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl closed SOLR-2903. - Resolution: Incomplete Closing this as incomplete, as we do not have any information on what

[jira] [Closed] (SOLR-5341) Output version number in logs

[ https://issues.apache.org/jira/browse/SOLR-5341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl closed SOLR-5341. - Resolution: Duplicate Closing as duplicate now that we print version on startup. Although we print this

[jira] [Closed] (SOLR-9244) Lots of "Previous SolrRequestInfo was not closed" in Solr log

[ https://issues.apache.org/jira/browse/SOLR-9244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl closed SOLR-9244. - Resolution: Duplicate Closing as duplicate > Lots of "Previous SolrRequestInfo was not closed" in Solr

[jira] [Resolved] (SOLR-7436) Solr stops printing stacktraces in log and output

[ https://issues.apache.org/jira/browse/SOLR-7436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl resolved SOLR-7436. --- Added the {{-XX:-OmitStackTraceInFastThrow}} option to solr.in files > Solr stops printing stacktraces in

[jira] [Updated] (SOLR-7436) Solr stops printing stacktraces in log and output

[ https://issues.apache.org/jira/browse/SOLR-7436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl updated SOLR-7436: -- Fix Version/s: (was: 5.5) master (7.0) 6.3 > Solr stops

[jira] [Assigned] (SOLR-7436) Solr stops printing stacktraces in log and output

[ https://issues.apache.org/jira/browse/SOLR-7436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl reassigned SOLR-7436: - Assignee: Jan Høydahl > Solr stops printing stacktraces in log and output >

Re: Solr configuration format fracturing

On Mon, 2016-09-26 at 14:56 +0700, Alexandre Rafalovitch wrote: > So, a single format (JSON if it works, > JSON+comments/quotes that Solr actually supports, or whatever). But > then the inputs and outputs should be consistent so that the same > tooling could be used for everything. This is a very

[jira] [Commented] (SOLR-7436) Solr stops printing stacktraces in log and output

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

[jira] [Commented] (SOLR-7436) Solr stops printing stacktraces in log and output

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

[jira] [Updated] (SOLR-9554) Multiple ManagedIndexSchemaFactory upgrades running simultaneously can clash, causing cores not to load

[ https://issues.apache.org/jira/browse/SOLR-9554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Khludnev updated SOLR-9554: --- Attachment: SOLR-9554.patch when I tried to catch this race with debugger, I found that mock

[jira] [Issue Comment Deleted] (SOLR-8033) useless if branch (commented out log.debug in HdfsTransactionLog constructor)

[ https://issues.apache.org/jira/browse/SOLR-8033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl updated SOLR-8033: -- Comment: was deleted (was: Commit 1716160 from [~ehatcher] in branch 'dev/trunk' [

[jira] [Issue Comment Deleted] (SOLR-8033) useless if branch (commented out log.debug in HdfsTransactionLog constructor)

[ https://issues.apache.org/jira/browse/SOLR-8033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl updated SOLR-8033: -- Comment: was deleted (was: oops on the wrong JIRA mentioned in my commit message, sorry about that. It

[jira] [Issue Comment Deleted] (SOLR-8033) useless if branch (commented out log.debug in HdfsTransactionLog constructor)

[ https://issues.apache.org/jira/browse/SOLR-8033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl updated SOLR-8033: -- Comment: was deleted (was: Commit 1716161 from [~ehatcher] in branch 'dev/branches/branch_5x' [

[jira] [Closed] (SOLR-7388) warning log about deprecated class things

[ https://issues.apache.org/jira/browse/SOLR-7388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl closed SOLR-7388. - Resolution: Not A Problem Closing issue since this is not a bug > warning log about deprecated class

[jira] [Commented] (SOLR-9577) SolrConfig edit operations should not need to reload core

[ https://issues.apache.org/jira/browse/SOLR-9577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15528708#comment-15528708 ] Shalin Shekhar Mangar commented on SOLR-9577: - bq. if the component does not implement this

[jira] [Created] (SOLR-9577) SolrConfig edit operations should not need to reload core

Noble Paul created SOLR-9577: Summary: SolrConfig edit operations should not need to reload core Key: SOLR-9577 URL: https://issues.apache.org/jira/browse/SOLR-9577 Project: Solr Issue Type:

[jira] [Created] (SOLR-9576) Make FieldAnalysisRequestHandler & DocumentAnalysisRequestHandler implicit

Noble Paul created SOLR-9576: Summary: Make FieldAnalysisRequestHandler & DocumentAnalysisRequestHandler implicit Key: SOLR-9576 URL: https://issues.apache.org/jira/browse/SOLR-9576 Project: Solr

[jira] [Resolved] (SOLR-9572) config API to show expanded useParams for request handlers inline

[ https://issues.apache.org/jira/browse/SOLR-9572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul resolved SOLR-9572. -- Resolution: Fixed Fix Version/s: master (7.0) 6.3 > config API to show

[jira] [Commented] (SOLR-9572) config API to show expanded useParams for request handlers inline

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

[jira] [Commented] (SOLR-9572) config API to show expanded useParams for request handlers inline

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