[jira] [Commented] (KAFKA-4922) Fix several FindBugs warnings in Clients and Connect

["Daan Rennings (JIRA)" <ji...@apache.org>]

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

Daan Rennings commented on KAFKA-4922:
--------------------------------------

I would like to tackle this issue myself. However I am not sure how issues are assigned.

> Fix several FindBugs warnings in Clients and Connect
> ----------------------------------------------------
>
>                 Key: KAFKA-4922
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4922
>             Project: Kafka
>          Issue Type: Improvement
>          Components: clients, KafkaConnect
>    Affects Versions: 0.10.2.0
>         Environment: Identified by FindBugs, non-software and -platform specific
>            Reporter: Daan Rennings
>            Priority: Minor
>              Labels: newbie
>             Fix For: 0.10.2.1
>
>         Attachments: ClientsFindBugsReport.html, ConnectAPIFindBugsReport.html, ConnectRuntimeFindBugsReport.html
>
>
> Four easy to fix warnings (not a complete set of the current FindBugs warnings) as identified by FindBugs and stated in the attached reports:
> -org.apache.kafka.common.utils.Bytes.equals(Object) does not check for null argument (Low priority, Bad Practice)
> -Primitive boxed just to call toString in org.apache.kafka.connect.data.Decimal.builder(int) (High Priority, Performance)
> -Primitive boxed just to call toString in new org.apache.kafka.connect.runtime.Worker(String, Time, ConnectorFactory, WorkerConfig, OffsetBackingStore) (High Priority, Performance)
> -Primitive is boxed to call Integer.compareTo(Integer): use Integer.compare(int, int) instead (High Priority, Performance)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)