You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flume.apache.org by "Mike Percy (JIRA)" <ji...@apache.org> on 2017/07/05 17:21:00 UTC

[jira] [Commented] (FLUME-2957) Remove Guava from our public API

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

Mike Percy commented on FLUME-2957:
-----------------------------------

I agree that we should simply expose a Map instead of the Guava ImmutableMap implementation as part of this public API.

> Remove Guava from our public API
> --------------------------------
>
>                 Key: FLUME-2957
>                 URL: https://issues.apache.org/jira/browse/FLUME-2957
>             Project: Flume
>          Issue Type: Task
>    Affects Versions: 1.8.0
>            Reporter: Lior Zeno
>             Fix For: 2.0.0
>
>
> Context.getParameters (flume-ng-configuration module) returns com.google.common.collect.ImmutableMap (Guava). We should clean our API and return either a native java interface or Flume's.
> In addition to the current state being a bad practice, this also means that we are unable to shade Guava in Flume.
> Note: Since this breaks our public API, I'll reschedule this issue to 2.0 once we have this version managed in jira.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)