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

Steve Rowe commented on SOLR-9161:
----------------------------------

My Jenkins found a seed that reproduces for me for 
{{SolrPluginUtils.testinvokeSetters()}}:

{noformat}
Checking out Revision 50658dd93d16eec37e906a24446146609cc93706 
(refs/remotes/origin/master)
[...]
   [junit4]   2> NOTE: reproduce with: ant test  -Dtestcase=SolrPluginUtilsTest 
-Dtests.method=testInvokeSetters -Dtests.seed=5040127289756128 
-Dtests.slow=true 
-Dtests.linedocsfile=/home/jenkins/lucene-data/enwiki.random.lines.txt 
-Dtests.locale=ar-SY -Dtests.timezone=Asia/Kuching -Dtests.asserts=true 
-Dtests.file.encoding=UTF-8
   [junit4] ERROR   0.01s J6  | SolrPluginUtilsTest.testInvokeSetters <<<
   [junit4]    > Throwable #1: java.lang.IllegalArgumentException: argument 
type mismatch
   [junit4]    >        at 
__randomizedtesting.SeedInfo.seed([5040127289756128:395FB9727C430383]:0)
   [junit4]    >        at 
org.apache.solr.util.SolrPluginUtils.invokeSetters(SolrPluginUtils.java:1071)
   [junit4]    >        at 
org.apache.solr.util.SolrPluginUtilsTest.implTestInvokeSetters(SolrPluginUtilsTest.java:482)
   [junit4]    >        at 
org.apache.solr.util.SolrPluginUtilsTest.testInvokeSetters(SolrPluginUtilsTest.java:474)
   [junit4]    >        at java.lang.Thread.run(Thread.java:745)
{noformat}

> SolrPluginUtils.invokeSetters should accommodate setter variants
> ----------------------------------------------------------------
>
>                 Key: SOLR-9161
>                 URL: https://issues.apache.org/jira/browse/SOLR-9161
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Christine Poerschke
>            Assignee: Christine Poerschke
>            Priority: Minor
>         Attachments: SOLR-9161.patch
>
>
> The code currently assumes that there is only one setter (or if there are 
> several setters then the first one found is used and it could mismatch on the 
> arg type).
> Context and motivation is that a class with a
> {code}
> void setAFloat(float val) {
>   this.val = val;
> }
> {code}
> setter may wish to also provide a
> {code}
> void setAFloat(String val) {
>   this.val = Float.parseFloat(val);
> }
> {code}
> convenience setter.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to