> As David mentioned, there isn’t a
> single true ‘solution’ for this problem so the more information we provide
> the better.
Think of it in terms of how your repository is structured:
This issue was *fixed* on git branches [x,y,z] and *affected* tags [a,b,c].
This gives a clear an unambiguous
Build: https://builds.apache.org/job/Lucene-Solr-Tests-7.x/9/
1 tests failed.
FAILED:
org.apache.solr.handler.admin.StatsReloadRaceTest.testParallelReloadAndStats
Error Message:
Key SEARCHER.searcher.indexVersion not found in registry solr.core.collection1
Stack Trace:
java.lang.AssertionError
Build: https://jenkins.thetaphi.de/job/Lucene-Solr-7.x-Windows/8/
Java: 64bit/jdk-9-ea+173 -XX:-UseCompressedOops -XX:+UseSerialGC
2 tests failed.
FAILED:
org.apache.solr.cloud.CdcrBootstrapTest.testConvertClusterToCdcrAndBootstrap
Error Message:
Document mismatch on target after sync expected:
[
https://issues.apache.org/jira/browse/SOLR-11011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075934#comment-16075934
]
Shalin Shekhar Mangar commented on SOLR-11011:
--
Nice Dat! Although this was c
Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-7.x/2/
1 tests failed.
FAILED: org.apache.solr.cloud.hdfs.HdfsUnloadDistributedZkTest.test
Error Message:
Could not find collection : unloadcollection
Stack Trace:
org.apache.solr.common.SolrException: Could not find collection :
un
Thanks for the insight hoss :). I agree that I went into this with my
assumptions.
> A user who sees that a bug is fixed in "6.6.1" has no way to be
> confident that the same bug is fixed in "7.0" just because the major
> number is greater -- because we might releast 6.6.1 after 7.0 is release
Build: https://jenkins.thetaphi.de/job/Lucene-Solr-7.x-Solaris/7/
Java: 64bit/jdk1.8.0 -XX:-UseCompressedOops -XX:+UseG1GC
1 tests failed.
FAILED:
org.apache.solr.cloud.TestMiniSolrCloudClusterSSL.testNoSslButSillyClientAuth
Error Message:
Could not find collection:second_collection
Stack Trac
: Here’s my issue with that approach. Say I commit something that would be
: released with 7.0 but obviously, I also commit to master at this point.
: Going with your approach here are the fix versions I’ll end up with on
: the JIRA - master (8.0), 7.1, and 7.0.
:
: This confuses me, as anythi
Build: https://jenkins.thetaphi.de/job/Lucene-Solr-7.x-MacOSX/7/
Java: 64bit/jdk1.8.0 -XX:-UseCompressedOops -XX:+UseConcMarkSweepGC
2 tests failed.
FAILED:
org.apache.solr.cloud.CustomCollectionTest.testRouteFieldForImplicitRouter
Error Message:
Collection not found: withShardField
Stack Trac
: I think my confusion stems from the smoke checker allowing ant 1.8 OR 1.9,
: then.
:
https://github.com/apache/lucene-solr/blob/master/dev-tools/scripts/smokeTestRelease.py#L193
That seems bad to me - the explicit check for the minimum version of ant
(used to make the jars) is suppose to be d
[
https://issues.apache.org/jira/browse/SOLR-11016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-11016:
Attachment: SOLR-11016.patch
Silly test bug -- the helper methods for verifying the facet results don't
acc
[
https://issues.apache.org/jira/browse/SOLR-11016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man reassigned SOLR-11016:
---
Assignee: Hoss Man
> TestCloudJSONFacetJoinDomain.testBespoke() failures
> --
[
https://issues.apache.org/jira/browse/SOLR-10726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-10726:
Attachment: SOLR-10726.semaphore.newsearcher.test.patch
semaphore.newsearcher.test.log.txt
[
https://issues.apache.org/jira/browse/SOLR-10983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075666#comment-16075666
]
Scott Blum commented on SOLR-10983:
---
BTW: this issue most likely affects all 6.x release
Build: https://jenkins.thetaphi.de/job/Lucene-Solr-7.x-Windows/7/
Java: 64bit/jdk1.8.0_131 -XX:-UseCompressedOops -XX:+UseParallelGC
1 tests failed.
FAILED: org.apache.solr.handler.admin.MetricsHandlerTest.testPropertyFilter
Error Message:
Stack Trace:
java.lang.AssertionError
at
__ra
[
https://issues.apache.org/jira/browse/SOLR-10983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Blum resolved SOLR-10983.
---
Resolution: Fixed
Fix Version/s: 7.1
master (8.0)
7.0
> F
[
https://issues.apache.org/jira/browse/SOLR-10983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075663#comment-16075663
]
ASF subversion and git services commented on SOLR-10983:
Commit 17
[
https://issues.apache.org/jira/browse/SOLR-10983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075664#comment-16075664
]
ASF subversion and git services commented on SOLR-10983:
Commit 51
[
https://issues.apache.org/jira/browse/SOLR-10983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075662#comment-16075662
]
ASF subversion and git services commented on SOLR-10983:
Commit 38
[
https://issues.apache.org/jira/browse/SOLR-10317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075623#comment-16075623
]
Michael Sun commented on SOLR-10317:
[~vivek.nar...@uga.edu] I saw you made some good
[
https://issues.apache.org/jira/browse/SOLR-10317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075617#comment-16075617
]
Michael Sun commented on SOLR-10317:
Just uploaded a second cut of Solr benchmark fram
[
https://issues.apache.org/jira/browse/SOLR-10317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Sun updated SOLR-10317:
---
Attachment: SOLR-10317.patch
> Solr Nightly Benchmarks
> ---
>
> K
[
https://issues.apache.org/jira/browse/LUCENE-6513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075601#comment-16075601
]
Timothy M. Rodriguez commented on LUCENE-6513:
--
[~romseygeek] we've written
[
https://issues.apache.org/jira/browse/SOLR-8495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl closed SOLR-8495.
-
Resolution: Duplicate
Closing as duplicate of SOLR-9526
> Schemaless mode cannot index large text fields
>
I’ve put this on a wiki page, and did that as a ‘trivial change’, which
shouldn’t have triggered any emails to anyone other than Steve (sorry about
that). I’m not sure how to have that as a permanent setting for this page
though.
Anyone?
Here’s the page: https://wiki.apache.org/lucene-java/Set
[
https://issues.apache.org/jira/browse/SOLR-10123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075535#comment-16075535
]
Hoss Man commented on SOLR-10123:
-
bq. Houston is working on a new batch of tests that wi
This would be good to see as part of the How To Contribute guide, I think,
or at least linked from there.
On Wed, Jul 5, 2017 at 5:10 PM, David Smiley
wrote:
> This makes sense to me. It's easy to forget this stuff though. Perhaps
> we can propose a policy, vote on it, and post it somewhere?
[
https://issues.apache.org/jira/browse/SOLR-11013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075515#comment-16075515
]
Jan Høydahl commented on SOLR-11013:
I think perhaps the collections endpoint is speci
This makes sense to me. It's easy to forget this stuff though. Perhaps we
can propose a policy, vote on it, and post it somewhere? We could even do
this in the Wiki (MoinMoin) -- so create a page, put "Draft/Proposal"
prominently at the top, and then share a link. Keep it particularly
succinct
@Dawid: I remember that discussion, and I think things were fixed for the issue
back then.
My concern right now is that we will end up in a similar situation again with
everyone interpreting the fixVersion differently.
@Erick
Here’s my issue with that approach. Say I commit something that would
[
https://issues.apache.org/jira/browse/SOLR-10967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Varun Thacker resolved SOLR-10967.
--
Resolution: Fixed
Fix Version/s: 7.0
Thanks Jason and Jan !
> Cleanup the default config
[
https://issues.apache.org/jira/browse/SOLR-10967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075493#comment-16075493
]
ASF subversion and git services commented on SOLR-10967:
Commit 8e
[
https://issues.apache.org/jira/browse/SOLR-10967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075489#comment-16075489
]
ASF subversion and git services commented on SOLR-10967:
Commit e3
[
https://issues.apache.org/jira/browse/SOLR-10967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075488#comment-16075488
]
ASF subversion and git services commented on SOLR-10967:
Commit d1
Build: https://builds.apache.org/job/Lucene-Solr-Tests-7.x/8/
3 tests failed.
FAILED: org.apache.solr.cloud.ChaosMonkeyNothingIsSafeWithPullReplicasTest.test
Error Message:
Timeout occured while waiting response from server at: http://127.0.0.1:52106
Stack Trace:
org.apache.solr.client.solrj.So
Susheel Kumar created SOLR-11017:
Summary: Add support for unique metric to facet streaming function
Key: SOLR-11017
URL: https://issues.apache.org/jira/browse/SOLR-11017
Project: Solr
Issue
I'm just including a fix version for each push I make. I.e.
If I push to master I'll add "master (8.0)".
If I push to 7x, at this point I'll add 7.1
If I push to 7_0 I'll add 7.0
If I push to 6x I'll add 6.7
If for some reason I wanted to push it to branch_6_6 I'd add 6.6.1
I think one push == on
[
https://issues.apache.org/jira/browse/SOLR-11015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075430#comment-16075430
]
ASF subversion and git services commented on SOLR-11015:
Commit 33
[
https://issues.apache.org/jira/browse/SOLR-11015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075427#comment-16075427
]
ASF subversion and git services commented on SOLR-11015:
Commit 11
[
https://issues.apache.org/jira/browse/SOLR-11015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075426#comment-16075426
]
ASF subversion and git services commented on SOLR-11015:
Commit 16
I pushed a fix for these failures.
Mike McCandless
http://blog.mikemccandless.com
On Wed, Jul 5, 2017 at 4:30 PM, Policeman Jenkins Server <
jenk...@thetaphi.de> wrote:
> Build: https://jenkins.thetaphi.de/job/Lucene-Solr-7.x-Solaris/6/
> Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseG1GC
There's been a fairly recent discussion about it on the mailing list
(David Smiley and were involved in that discussion, among other
people). There are many different takes on how to handle fix-for and
branches. I don't think we can find the "best" strategy, although
perhaps we can agree on somethi
Related to SOLR-11015. I missed the case of the ChaosMonkeyNothingIsSafe*, that
creates a different client with an explicit timeout for creating this
collection.
> On Jul 5, 2017, at 1:22 PM, Apache Jenkins Server
> wrote:
>
> Build: https://builds.apache.org/job/Lucene-Solr-Tests-master/194
[
https://issues.apache.org/jira/browse/SOLR-11004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anshum Gupta resolved SOLR-11004.
-
Resolution: Fixed
> Consolidate SolrClient Builder code in abstract parent class
> ---
[
https://issues.apache.org/jira/browse/SOLR-11004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anshum Gupta updated SOLR-11004:
Fix Version/s: (was: master (8.0))
> Consolidate SolrClient Builder code in abstract parent clas
Hi,
I was a bit confused in terms of setting the ‘fix version’ for JIRAs that are
being committed right now. I think it makes sense for the fixVersion to just be
7.0, and nothing else for everything that is going into branch_7_0, instead of
being both 7.0, and master (8.0).
Any thoughts?
-An
[
https://issues.apache.org/jira/browse/SOLR-11004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075388#comment-16075388
]
ASF subversion and git services commented on SOLR-11004:
Commit ec
[
https://issues.apache.org/jira/browse/SOLR-10996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075369#comment-16075369
]
Andrzej Bialecki edited comment on SOLR-10996 at 7/5/17 8:33 PM:
--
[
https://issues.apache.org/jira/browse/SOLR-10996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrzej Bialecki updated SOLR-10996:
-
Attachment: SOLR-10996.patch
Patch for review:
* some refactoring to clarify what are the
Build: https://jenkins.thetaphi.de/job/Lucene-Solr-7.x-Solaris/6/
Java: 64bit/jdk1.8.0 -XX:+UseCompressedOops -XX:+UseG1GC
1 tests failed.
FAILED:
org.apache.lucene.index.TestMixedDocValuesUpdates.testManyReopensAndFields
Error Message:
invalid numeric value for doc=0, field=f0,
reader=_g(7.1.
Build: https://builds.apache.org/job/Lucene-Solr-Tests-master/1945/
3 tests failed.
FAILED: org.apache.solr.cloud.ChaosMonkeyNothingIsSafeWithPullReplicasTest.test
Error Message:
Timeout occured while waiting response from server at:
http://127.0.0.1:35634/d/d
Stack Trace:
org.apache.solr.clie
Build: https://jenkins.thetaphi.de/job/Lucene-Solr-7.x-Linux/13/
Java: 32bit/jdk1.8.0_131 -client -XX:+UseConcMarkSweepGC
3 tests failed.
FAILED:
junit.framework.TestSuite.org.apache.solr.cloud.ChaosMonkeyNothingIsSafeTest
Error Message:
9 threads leaked from SUITE scope at
org.apache.solr.clo
[
https://issues.apache.org/jira/browse/SOLR-10668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev updated SOLR-10668:
Summary: NPE on sort=childfield(field) desc (was: add a test for
sort=childfield(name,$anot
[
https://issues.apache.org/jira/browse/SOLR-10668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16044265#comment-16044265
]
Mikhail Khludnev edited comment on SOLR-10668 at 7/5/17 7:55 PM:
---
[
https://issues.apache.org/jira/browse/SOLR-10668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev updated SOLR-10668:
Issue Type: Bug (was: Test)
> add a test for sort=childfield(name,$another_bjq) desc
>
[
https://issues.apache.org/jira/browse/SOLR-10668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev reassigned SOLR-10668:
---
Assignee: Mikhail Khludnev
> add a test for sort=childfield(name,$another_bjq) desc
>
[
https://issues.apache.org/jira/browse/SOLR-10668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Khludnev updated SOLR-10668:
Attachment: SOLR-10668.patch
[^SOLR-10668.patch] is mostly NPE fix&test
> add a test for so
[
https://issues.apache.org/jira/browse/SOLR-10668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16012365#comment-16012365
]
Mikhail Khludnev edited comment on SOLR-10668 at 7/5/17 7:50 PM:
---
[
https://issues.apache.org/jira/browse/SOLR-10123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075269#comment-16075269
]
ASF GitHub Bot commented on SOLR-10123:
---
Github user dennisgove commented on the iss
Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/20067/
Java: 32bit/jdk1.8.0_131 -server -XX:+UseG1GC
3 tests failed.
FAILED:
junit.framework.TestSuite.org.apache.solr.cloud.ChaosMonkeyNothingIsSafeTest
Error Message:
9 threads leaked from SUITE scope at
org.apache.solr.cloud.Ch
Github user dennisgove commented on the issue:
https://github.com/apache/lucene-solr/pull/215
This all looks good to me so far
`%> ant precommit` passes
`%> ant test` passes
Houston is working on a new batch of tests that will specifically test the
new analytics e
Build: https://jenkins.thetaphi.de/job/Lucene-Solr-7.x-MacOSX/6/
Java: 64bit/jdk1.8.0 -XX:-UseCompressedOops -XX:+UseParallelGC
3 tests failed.
FAILED: org.apache.solr.cloud.ChaosMonkeyNothingIsSafeWithPullReplicasTest.test
Error Message:
Timeout occured while waiting response from server at: ht
[
https://issues.apache.org/jira/browse/SOLR-10583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075260#comment-16075260
]
Steve Rowe commented on SOLR-10583:
---
{{TestCloudJSONFacetJoinDomain}}, introduced on thi
[
https://issues.apache.org/jira/browse/SOLR-11016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe updated SOLR-11016:
--
Description:
Policeman Jenkins found a reproducing branch_6x seed
[https://jenkins.thetaphi.de/job/Luce
[
https://issues.apache.org/jira/browse/SOLR-11016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe moved LUCENE-7900 to SOLR-11016:
---
Security: Public
Lucene Fields: (was: New)
Key: SOLR-
Steve Rowe created LUCENE-7900:
--
Summary: TestCloudJSONFacetJoinDomain.testBespoke() failures
Key: LUCENE-7900
URL: https://issues.apache.org/jira/browse/LUCENE-7900
Project: Lucene - Core
Issue
[
https://issues.apache.org/jira/browse/SOLR-11015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075258#comment-16075258
]
ASF subversion and git services commented on SOLR-11015:
Commit 7e
[
https://issues.apache.org/jira/browse/SOLR-11004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075255#comment-16075255
]
ASF subversion and git services commented on SOLR-11004:
Commit 45
[
https://issues.apache.org/jira/browse/SOLR-11015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075253#comment-16075253
]
ASF subversion and git services commented on SOLR-11015:
Commit 2b
[
https://issues.apache.org/jira/browse/SOLR-11015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075248#comment-16075248
]
ASF subversion and git services commented on SOLR-11015:
Commit f0
[
https://issues.apache.org/jira/browse/SOLR-11004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anshum Gupta updated SOLR-11004:
Fix Version/s: 7.0
> Consolidate SolrClient Builder code in abstract parent class
>
[
https://issues.apache.org/jira/browse/SOLR-11004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anshum Gupta updated SOLR-11004:
Affects Version/s: (was: master (8.0))
> Consolidate SolrClient Builder code in abstract parent
[
https://issues.apache.org/jira/browse/SOLR-11004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anshum Gupta reassigned SOLR-11004:
---
Assignee: Anshum Gupta
> Consolidate SolrClient Builder code in abstract parent class
> -
[
https://issues.apache.org/jira/browse/SOLR-11004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075234#comment-16075234
]
ASF subversion and git services commented on SOLR-11004:
Commit 30
[
https://issues.apache.org/jira/browse/SOLR-11004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anshum Gupta updated SOLR-11004:
Attachment: SOLR-11004.patch
Updated patch
> Consolidate SolrClient Builder code in abstract parent
[
https://issues.apache.org/jira/browse/SOLR-11015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomás Fernández Löbbe updated SOLR-11015:
-
Attachment: SOLR-11015.patch
Patch to increase the socket timeout in the {{createN
[
https://issues.apache.org/jira/browse/SOLR-11004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075172#comment-16075172
]
Anshum Gupta commented on SOLR-11004:
-
Thanks Jason, I've changed this a bit to remove
Tomás Fernández Löbbe created SOLR-11015:
Summary: SocketTimeoutException in ChaosMonkey tests when creating
testcollection
Key: SOLR-11015
URL: https://issues.apache.org/jira/browse/SOLR-11015
[
https://issues.apache.org/jira/browse/LUCENE-7899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075150#comment-16075150
]
ASF subversion and git services commented on LUCENE-7899:
-
Commit
[
https://issues.apache.org/jira/browse/LUCENE-7899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075149#comment-16075149
]
ASF subversion and git services commented on LUCENE-7899:
-
Commit
Oh, I'll add a line of text there. Thanks Uwe.
+1 to rename our Markdown files to .md!
Mike McCandless
http://blog.mikemccandless.com
On Wed, Jul 5, 2017 at 11:36 AM, Uwe Schindler wrote:
> Hi,
>
> we now have an entry heading at the end of the migrate.txt file (which is
> formatted in Markd
[
https://issues.apache.org/jira/browse/LUCENE-7896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075125#comment-16075125
]
Dawid Weiss commented on LUCENE-7896:
-
Thanks Simon.
> Upgrade to RandomizedRunner 2
[
https://issues.apache.org/jira/browse/SOLR-11014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Le Floc'h updated SOLR-11014:
-
Description:
in the top folder, in build.xml
[https://github.com/apache/lucene-solr/blob/b
[
https://issues.apache.org/jira/browse/SOLR-9526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075116#comment-16075116
]
Steve Rowe edited comment on SOLR-9526 at 7/5/17 5:36 PM:
--
Attachi
Antoine Le Floc'h created SOLR-11014:
Summary: server/solr-webapp/** missing for the eclipse exclusions
in build.xml
Key: SOLR-11014
URL: https://issues.apache.org/jira/browse/SOLR-11014
Project:
[
https://issues.apache.org/jira/browse/SOLR-9526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe updated SOLR-9526:
-
Attachment: SOLR-9526.patch
Attaching patch brought up to date with master (in particular, collapsing of
{
If we use the -Werror flag be sure to NOT enable all warnings and disable some
of them (this makes build non-reproducible if JVM changes). So when using
-Werror, we should list all warnings we want to see explicit (so no “all”
warning). For Eclipse’s ECJ do the same.
In general with the Ecli
Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Windows/6710/
Java: 64bit/jdk-9-ea+173 -XX:-UseCompressedOops -XX:+UseG1GC
3 tests failed.
FAILED: org.apache.solr.cloud.ChaosMonkeyNothingIsSafeTest.test
Error Message:
Timeout occured while waiting response from server at:
http://127.0
I think most of us want to get a bunch of stuff in for the 7.0 release, so it
would make sense for us to open up 7.0 ONLY for improvements (code/usability),
deprecations, and bug fixes for the rest of this week. I would request that all
of us wrap everything but blocker bug fixes by the end of t
[
https://issues.apache.org/jira/browse/SOLR-11013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075090#comment-16075090
]
Varun Thacker commented on SOLR-11013:
--
Since it's marked as an experimental feature
[
https://issues.apache.org/jira/browse/SOLR-11013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christine Poerschke updated SOLR-11013:
---
Attachment: SOLR-11013.patch
Attaching proposed patch, tests seem to pass with these c
Christine Poerschke created SOLR-11013:
--
Summary: remove /v2/c alias in favour of /v2/collections only
Key: SOLR-11013
URL: https://issues.apache.org/jira/browse/SOLR-11013
Project: Solr
Hi Anshum,
I'd like to get SOLR-10967 in as well. It contains some changes to the
default configset and no code changes.
On Wed, Jul 5, 2017 at 8:06 AM, Christine Poerschke (BLOOMBERG/ LONDON) <
cpoersc...@bloomberg.net> wrote:
> I'd like to see https://issues.apache.org/jira/browse/SOLR-10985
Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/20066/
Java: 64bit/jdk-9-ea+175 -XX:-UseCompressedOops -XX:+UseSerialGC
--illegal-access=deny
3 tests failed.
FAILED:
junit.framework.TestSuite.org.apache.solr.cloud.ChaosMonkeyNothingIsSafeTest
Error Message:
8 threads leaked fro
[
https://issues.apache.org/jira/browse/SOLR-11011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075033#comment-16075033
]
Varun Thacker commented on SOLR-11011:
--
Nice catch!
> Assign.buildCoreName can lead
I think you can do this with the -Werror flag and supress annotating
everything else.
On Wed, Jul 5, 2017 at 10:45 AM, Erick Erickson
wrote:
> bq: making precommit fail for some but not all resource leaks.
> Implementation wise, how might one go about that?
>
> No clue, hoping somebody who _doe
bq: making precommit fail for some but not all resource leaks.
Implementation wise, how might one go about that?
No clue, hoping somebody who _does_ have clue will just say "oh, you
just specify blah blah blah" ;)
On Wed, Jul 5, 2017 at 8:39 AM, Christine Poerschke (BLOOMBERG/
LONDON) wrote:
>
Hi Erick,
Thanks for the extra context re: JavaBinCodec and SOLR-10779.
I agree that backporting warning fixes to 6x is optional at this point and for
complex fixes probably not worth the risk of introducing subtle bugs in the
process.
+1 to your idea of making precommit fail for some but not
Hi,
we now have an entry heading at the end of the migrate.txt file (which is
formatted in Markdown). We should maybe add some line of text.
I think after changing the README.txt filename to README.md, we should maybe do
the same with the other Markdown formatted files (see the ant process-webp
[
https://issues.apache.org/jira/browse/LUCENE-7896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16074949#comment-16074949
]
ASF subversion and git services commented on LUCENE-7896:
-
Commit
1 - 100 of 209 matches
Mail list logo
