[ 
https://issues.apache.org/jira/browse/SOLR-12963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871410#comment-17871410
 ] 

Chris M. Hostetter commented on SOLR-12963:
-------------------------------------------

[~houston] - git bisect has identified b0ab58ef87538ac05ab73d9e2e4cdb6fba4aac56 
as the cause of recent 100% reproducible jenkins test failures from 
DistribDocExpirationUpdateProcessorTest like these...

 
{noformat}
$ ./gradlew -p solr/core test --tests DistribDocExpirationUpdateProcessorTest 
-Dtests.seed=11EF0AA307058EA1 -Dtests.nightly=true -Dtests.locale=en-NL 
-Dtests.timezone=Africa/El_Aaiun -Dtests.asserts=true 
-Dtests.file.encoding=UTF-8
...
  2> 69591 INFO  
(TEST-DistribDocExpirationUpdateProcessorTest.testNoAuth-seed#[11EF0AA307058EA1])
 [n: c: s: r: x: t:] o.a.s.SolrTestCaseJ4 ###Ending testNoAuth
   >     java.lang.AssertionError: Give up waiting for no results: 
q=should_expire_s:yup&rows=0&_trace=init_batch_check&_stateVer_=expiring:13 
expected:<0> but was:<32>
   >         at 
__randomizedtesting.SeedInfo.seed([11EF0AA307058EA1:CD5AB0CEBDD35C89]:0)
   >         at org.junit.Assert.fail(Assert.java:89)
   >         at org.junit.Assert.failNotEquals(Assert.java:835)
   >         at org.junit.Assert.assertEquals(Assert.java:647)
   >         at 
org.apache.solr.cloud.DistribDocExpirationUpdateProcessorTest.waitForNoResults(DistribDocExpirationUpdateProcessorTest.java:349)
   >         at 
org.apache.solr.cloud.DistribDocExpirationUpdateProcessorTest.runTest(DistribDocExpirationUpdateProcessorTest.java:171)
   >         at 
org.apache.solr.cloud.DistribDocExpirationUpdateProcessorTest.testNoAuth(DistribDocExpirationUpdateProcessorTest.java:112)
{noformat}
 
{noformat}
$ git bisect log
# bad: [988e9e3c2666784638475f4cd4827bc2fe77c707] Add branch protection for 
branch_9_7
# good: [ffde4199a094136bde4f63ca4037b05f6388e488] SOLR-13350: multi-threaded 
search: default to 'available processors' thread count (#2569)
git bisect start '988e9e3c2666784638475f4cd4827bc2fe77c707' 
'ffde4199a094136bde4f63ca4037b05f6388e488'
# bad: [8ab0278644e2c2731faae9f43c50c959bbe2f712] SOLR-13350, SOLR-17298: 
multi-threaded search: revert TestFiltering.java change (#2589)
git bisect bad 8ab0278644e2c2731faae9f43c50c959bbe2f712
# good: [57fa8b968b1f6b82e048362a62906cda1bc153e7] Refactor: Move Collection 
Properties backend out of ZkStateReader (#2585)
git bisect good 57fa8b968b1f6b82e048362a62906cda1bc153e7
# bad: [6bbfdcde6a30ea2e85ee020a6738a59c05e1f973] SOLR-12963: Fix 
EnumFieldTest.testEnumSort
git bisect bad 6bbfdcde6a30ea2e85ee020a6738a59c05e1f973
# bad: [b0ab58ef87538ac05ab73d9e2e4cdb6fba4aac56] SOLR-12963: Default 
uninvertible=false in schema version 1.7 (#2601)
git bisect bad b0ab58ef87538ac05ab73d9e2e4cdb6fba4aac56
# first bad commit: [b0ab58ef87538ac05ab73d9e2e4cdb6fba4aac56] SOLR-12963: 
Default uninvertible=false in schema version 1.7 (#2601)
{noformat}
 

 

> change default for 'uninvertible' to 'false' (dependent on new schema 
> 'version')
> --------------------------------------------------------------------------------
>
>                 Key: SOLR-12963
>                 URL: https://issues.apache.org/jira/browse/SOLR-12963
>             Project: Solr
>          Issue Type: Sub-task
>            Reporter: Chris M. Hostetter
>            Assignee: Houston Putman
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 9.7
>
>         Attachments: SOLR-12963.patch
>
>          Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> We should consider changing the default behavior of the {{uninvertible}} 
> field option to be dependnt on the schema {{version}} property, such that 
> moving forward the fields/fieldtypes will default to {{uninvertible == 
> false}} unless an explicit {{uninvertible=true}} is specified by the user.
> There are a lot of considerations regarding the existing behavior of 
> functionality (like faceting) when the (effective) value of {{uninvertible}} 
> is false because we move forward with changing this in a way that could 
> suprise/confuse new users or existing users w/ long heald expectations that 
> certain behavior would just "work" w/o understanding that was because of 
> FieldCache/uninversion.
> See parent issue for more background/discussion.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to