[ 
https://issues.apache.org/jira/browse/SOLR-9285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hoss Man updated SOLR-9285:
---------------------------
    Attachment: SOLR-9285.patch


Updated patch:
* fully fleshed out {{TestRandomFlRTGCloud}}
* added the previously proposed {{needsSolrIndexSearcher}} method to 
{{DocTransformer}}
** default impl always returns {{false}}
** {{ValueSourceAugmenter}} overrides to always returns {{true}}
** {{DocTransformers}} overrides to return {{true}} if any of the wrapped/child 
transformers return {{true}}

There are almost certainly some other {{DocTransformer}} subclasses that should 
return true from this method, but I'd like to move forward with committing as 
is and target fixing any other classes (and adding test coverage for them) in 
other issues.  (As things stand in this patch they are no worse off then 
before.)

Unless there are objections, I'll try to commit/backport this on monday. 
(possibly after filing some new issues so i can update some TODO comments in 
tests with concrete jira IDs)


> ArrayIndexOutOfBoundsException when ValueSourceAugmenter used with RTG on 
> uncommitted doc
> -----------------------------------------------------------------------------------------
>
>                 Key: SOLR-9285
>                 URL: https://issues.apache.org/jira/browse/SOLR-9285
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Hoss Man
>         Attachments: SOLR-9285.patch, SOLR-9285.patch, SOLR-9285.patch, 
> SOLR-9285.patch
>
>
> Found in SOLR-9180 testing.
> Even in single node solr envs, doing an RTG for an uncommitted doc that uses 
> ValueSourceAugmenter (ie: simple field aliasing, or functions in fl) causes 
> an ArrayIndexOutOfBoundsException



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Reply via email to