lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Rowe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LUCENE-4974) CommitIndexTask is broken if no params are set
Date Fri, 10 May 2013 22:47:16 GMT

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

Steve Rowe updated LUCENE-4974:
-------------------------------

    Labels: lucene-4.3.1-candidate  (was: )
    
> CommitIndexTask is broken if no params are set
> ----------------------------------------------
>
>                 Key: LUCENE-4974
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4974
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: modules/benchmark
>            Reporter: Shai Erera
>            Assignee: Shai Erera
>              Labels: lucene-4.3.1-candidate
>             Fix For: 5.0, 4.4
>
>         Attachments: LUCENE-4974.patch
>
>
> If you put a CommitIndex in a benchmark algorithm with no params, you get NPE from IW.setCommitData,
because you are not allowed to pass null. It's a trivial fix - CommitIndexTask should call
setCommitData only if commitData is not null.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

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


Mime
View raw message