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

ASF GitHub Bot commented on KAFKA-3611:
---------------------------------------

GitHub user Ishiihara opened a pull request:

    https://github.com/apache/kafka/pull/1259

    KAFKA-3611: Remove warnings when using reflections

    @ewencp @granders Can you take a look? Thanks!

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/Ishiihara/kafka fix-warning

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/1259.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1259
    
----
commit 3319c946c4e217600ad455adf73362e83055cdd7
Author: Liquan Pei <liquan...@gmail.com>
Date:   2016-04-23T04:45:05Z

    Remove warnings when using reflections

----


> Remove WARNs when using reflections 
> ------------------------------------
>
>                 Key: KAFKA-3611
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3611
>             Project: Kafka
>          Issue Type: Improvement
>          Components: KafkaConnect
>    Affects Versions: 0.10.0.0
>            Reporter: Liquan Pei
>            Assignee: Liquan Pei
>             Fix For: 0.10.0.0
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> When using reflections, there are logs with WARN level are created when some 
> URL types are not recognized by Vfs.  Removing these WARN logs will improve 
> use experiences. 
> Also, the way we create CLASSPATH in kafka-run-class.sh will cause 
> reflections to search for the directory running the script and will cause 
> some classes in test packages to be included in the list of subclass of the 
> Connector class. However, as the test jars may not be available, WARN level 
> logs will also be generated in this case. 



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

Reply via email to