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

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Solaris/1096/ Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseSerialGC All tests passed Build Log: [...truncated 13189 lines...] [junit4] JVM J0: stderr was not empty, see:

Re: [jira] [Commented] (SOLR-6761) Ability to ignore commit and optimize requests from clients when running in SolrCloud mode.

> Recommendation shouldn’t be enforced I think the discussion is just about adding the ability to ignore such requests, not ignoring them by default. My suggestion, in the case when admins don't want regular users to commit/optimize, is to enable authorization and hence allow/disallow only

[JENKINS] Lucene-Solr-master-MacOSX (64bit/jdk1.8.0) - Build # 3796 - Still Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-MacOSX/3796/ Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseParallelGC 1 tests failed. FAILED: org.apache.solr.cloud.PeerSyncReplicationTest.test Error Message: timeout waiting to see all nodes active Stack Trace:

Re: Lucene/Solr 7

LOL, "ambiguous" perhaps; I don't think "dangerous". +1 to Adrien's plan. On Tue, Jan 24, 2017 at 2:04 PM Michael McCandless < luc...@mikemccandless.com> wrote: > Early may is exactly what I meant by "a few months". > > I guess "few" is a dangerous word! > > Mike McCandless > >

[JENKINS] Lucene-Solr-NightlyTests-6.x - Build # 266 - Failure

Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-6.x/266/ 5 tests failed. FAILED: org.apache.lucene.index.TestIndexingSequenceNumbers.testStressConcurrentCommit Error Message: this IndexWriter is closed Stack Trace: org.apache.lucene.store.AlreadyClosedException: this IndexWriter

Missing hyperlinks in Solr 6.4 release notes (html version)

I just noticed that in the HTML version of the shipped release notes, the "LUCENE_CHANGES.txt" is no longer hyperlinked to the online version of the Lucene changes document. In the 6.3 release and before, it was hyperlinked. I am not sure if that's a perl script change, missed process step or

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

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Windows/6369/ Java: 32bit/jdk1.8.0_121 -client -XX:+UseConcMarkSweepGC 2 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.core.TestConfigSets Error Message: Could not remove the following files (in the order of attempts):

[jira] [Commented] (SOLR-9555) Leader incorrectly publishes state for replica when it puts replica into LIR.

[ https://issues.apache.org/jira/browse/SOLR-9555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836899#comment-15836899 ] Mark Miller commented on SOLR-9555: --- bq. The potential downside here is that we end up keeping two copies

[jira] [Commented] (SOLR-9555) Leader incorrectly publishes state for replica when it puts replica into LIR.

[ https://issues.apache.org/jira/browse/SOLR-9555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836870#comment-15836870 ] Mike Drob commented on SOLR-9555: - I've been thinking about this a bunch and have some observations. We

[jira] [Commented] (SOLR-10026) JavaBinCodec should initialize maps and namedLists with known capacity

[ https://issues.apache.org/jira/browse/SOLR-10026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836833#comment-15836833 ] ASF GitHub Bot commented on SOLR-10026: --- Github user johnthcall closed the pull request at:

[GitHub] lucene-solr pull request #142: SOLR-10026 - JavaBinCodec should initialize m...

Github user johnthcall closed the pull request at: https://github.com/apache/lucene-solr/pull/142 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[jira] [Commented] (LUCENE-6959) Remove ToParentBlockJoinCollector

[ https://issues.apache.org/jira/browse/LUCENE-6959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836779#comment-15836779 ] Martijn van Groningen commented on LUCENE-6959: --- +1 To remove this collector in the master

[JENKINS] Lucene-Solr-6.x-Solaris (64bit/jdk1.8.0) - Build # 632 - Still Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-6.x-Solaris/632/ Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC 1 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.cloud.TestSolrCloudWithSecureImpersonation Error Message: 1 thread leaked from SUITE scope

[JENKINS] Lucene-Solr-master-Solaris (64bit/jdk1.8.0) - Build # 1095 - Still Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Solaris/1095/ Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseSerialGC 1 tests failed. FAILED: org.apache.solr.security.hadoop.TestDelegationWithHadoopAuth.testDelegationTokenCancelFail Error Message: expected:<200> but was:<404>

[jira] [Updated] (SOLR-10026) JavaBinCodec should initialize maps and namedLists with known capacity

[ https://issues.apache.org/jira/browse/SOLR-10026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul updated SOLR-10026: -- Fix Version/s: 6.5 > JavaBinCodec should initialize maps and namedLists with known capacity >

[jira] [Commented] (SOLR-10026) JavaBinCodec should initialize maps and namedLists with known capacity

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

[jira] [Resolved] (SOLR-10026) JavaBinCodec should initialize maps and namedLists with known capacity

[ https://issues.apache.org/jira/browse/SOLR-10026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul resolved SOLR-10026. --- Resolution: Fixed > JavaBinCodec should initialize maps and namedLists with known capacity >

[jira] [Commented] (SOLR-10026) JavaBinCodec should initialize maps and namedLists with known capacity

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

[jira] [Updated] (SOLR-6246) Core fails to reload when AnalyzingInfixSuggester is used as a Suggester

[ https://issues.apache.org/jira/browse/SOLR-6246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Rowe updated SOLR-6246: - Attachment: SOLR-6246-test.patch Patch that adds a random dictionary with configurable size and new tests

[jira] [Assigned] (SOLR-10026) JavaBinCodec should initialize maps and namedLists with known capacity

[ https://issues.apache.org/jira/browse/SOLR-10026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul reassigned SOLR-10026: - Assignee: Noble Paul > JavaBinCodec should initialize maps and namedLists with known capacity >

Re: Inquiry for Solr Cloud Authentication

Yes, you should setup basic auth without SSL it in a very protected network only On Wed, Jan 25, 2017 at 3:27 AM, Steve Davids wrote: > Don't let "basic auth" without SSL think there is inherent security, if > someone has access to the network it is trivial to sniff network

Re: Lucene/Solr 7

Early may is exactly what I meant by "a few months". I guess "few" is a dangerous word! Mike McCandless http://blog.mikemccandless.com On Tue, Jan 24, 2017 at 1:02 PM, Joel Bernstein wrote: > I was feeling more comfortable with the early may timeframe. > > Joel Bernstein

[jira] [Assigned] (SOLR-10016) SQL should support sorting by random_

[ https://issues.apache.org/jira/browse/SOLR-10016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Potter reassigned SOLR-10016: - Assignee: Timothy Potter > SQL should support sorting by random_ >

[jira] [Commented] (SOLR-10016) SQL should support sorting by random_

[ https://issues.apache.org/jira/browse/SOLR-10016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15836376#comment-15836376 ] Timothy Potter commented on SOLR-10016: --- thanks Joel, will get started on this using the Calcite SQL

Re: Lucene/Solr 7

+1 to Adrien's proposal. Tommaso Il giorno mar 24 gen 2017 alle ore 17:52 Adrien Grand ha scritto: > Hi all, > > We have accumulated some good changes in master, like point support in > Solr or sparse norms/doc-values in Lucene. I think it would be nice to > expose these new

Re: Lucene/Solr 7

I was feeling more comfortable with the early may timeframe. Joel Bernstein http://joelsolr.blogspot.com/ On Tue, Jan 24, 2017 at 12:43 PM, Michael McCandless < luc...@mikemccandless.com> wrote: > +1 to push 7.0 out in a few months... > > Mike McCandless > > http://blog.mikemccandless.com > > >

Re: Lucene/Solr 7

+1 to push 7.0 out in a few months... Mike McCandless http://blog.mikemccandless.com On Tue, Jan 24, 2017 at 11:52 AM, Adrien Grand wrote: > Hi all, > > We have accumulated some good changes in master, like point support in Solr > or sparse norms/doc-values in Lucene. I

Re: Lucene/Solr 7

+1 Joel Bernstein http://joelsolr.blogspot.com/ On Tue, Jan 24, 2017 at 12:16 PM, Ishan Chattopadhyaya < ichattopadhy...@gmail.com> wrote: > I would love to see SOLR-5944, SOLR-8029, SOLR-9835 in a 7.0 release. I > think all of these are very close to landing up on master. > > On Tue, Jan 24,

[JENKINS] Lucene-Solr-master-MacOSX (64bit/jdk1.8.0) - Build # 3795 - Still Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-MacOSX/3795/ Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC 3 tests failed. FAILED: org.apache.solr.cloud.CollectionsAPIDistributedZkTest.testCollectionsAPI Error Message: Error from server at

Re: Lucene/Solr 7

I would love to see SOLR-5944, SOLR-8029, SOLR-9835 in a 7.0 release. I think all of these are very close to landing up on master. On Tue, Jan 24, 2017 at 10:22 PM, Adrien Grand wrote: > Hi all, > > We have accumulated some good changes in master, like point support in > Solr

Re: Inquiry for Solr Cloud Authentication

Don't let "basic auth" without SSL think there is inherent security, if someone has access to the network it is trivial to sniff network traffic and pickup the username/password (as noted in the caveats section ). There

Lucene/Solr 7

Hi all, We have accumulated some good changes in master, like point support in Solr or sparse norms/doc-values in Lucene. I think it would be nice to expose these new features to our users, so what would you think about starting to work on making master ready to be released? Since the question

Re: Test passes, build fails with "Could not remove temporary path"

Hi, The problem is also the security manager and it's policy file. This is why we have the temp dir in current folder. As there is no easy way to have an absolute path in the policy file, we have it like this. Another way would be to pass a sys prop for the temp directory and add a policy file

Re: Test passes, build fails with "Could not remove temporary path"

Check this out: (FYI this is my test; doesn't exist upstream yet): > ant test -Dtestcase=HeatmapSpatialFieldTest BUILD SUCCESSFUL, 1 minute 40 seconds > ant test-core -Dtestcase=HeatmapSpatialFieldTest BUILD FAILED, 25 seconds So it turns out the "-init-totals" task sets up the temp dir

[GitHub] lucene-solr pull request #66: SOLR-8146: Allowing SolrJ CloudSolrClient to h...

Github user susheelks closed the pull request at: https://github.com/apache/lucene-solr/pull/66 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

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

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Windows/6368/ Java: 32bit/jdk1.8.0_121 -server -XX:+UseConcMarkSweepGC 1 tests failed. FAILED: org.apache.solr.cloud.TestCloudRecovery.leaderRecoverFromLogOnStartupTest Error Message: expected:<0> but was:<5> Stack Trace:

[JENKINS] Lucene-Solr-6.x-Solaris (64bit/jdk1.8.0) - Build # 631 - Still Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-6.x-Solaris/631/ Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseParallelGC 2 tests failed. FAILED: junit.framework.TestSuite.org.apache.solr.cloud.TestSolrCloudWithSecureImpersonation Error Message: 2 threads leaked from SUITE scope at

Re: Test passes, build fails with "Could not remove temporary path"

It's exactly that, actually. We place java.io.tmpdir under ./, so this directory always remains after the tests are done. I filed this issue: https://github.com/randomizedtesting/randomizedtesting/issues/247 But I honestly don't know what the "right" way to fix it is. The runner assumes cwd

[JENKINS] Lucene-Solr-NightlyTests-master - Build # 1221 - Failure

Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-master/1221/ 6 tests failed. FAILED: org.apache.lucene.index.TestIndexSorting.testRandom3 Error Message: Java heap space Stack Trace: java.lang.OutOfMemoryError: Java heap space at

[JENKINS] Lucene-Solr-master-Solaris (64bit/jdk1.8.0) - Build # 1094 - Still Unstable!

Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Solaris/1094/ Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseParallelGC 3 tests failed. FAILED: org.apache.solr.cloud.TestSolrCloudWithSecureImpersonation.testForwarding Error Message: No live SolrServers available to handle this