[jira] [Resolved] (KUDU-724) [java client] Separate interfaces from implementations

["Jean-Daniel Cryans (JIRA)" <ji...@apache.org>]

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

Jean-Daniel Cryans resolved KUDU-724.
-------------------------------------
          Resolution: Won't Fix
       Fix Version/s: n/a
    Target Version/s:   (was: 1.4.0)

Resolving as won't fix like Todd suggested almost a year ago.

> [java client] Separate interfaces from implementations
> ------------------------------------------------------
>
>                 Key: KUDU-724
>                 URL: https://issues.apache.org/jira/browse/KUDU-724
>             Project: Kudu
>          Issue Type: Sub-task
>          Components: client
>    Affects Versions: M5
>            Reporter: Jean-Daniel Cryans
>             Fix For: n/a
>
>
> From [~adar]:
> {quote}
> As you clean up the Java client, I'd be a fan of strictly separating interfaces from implementations, and moving the former into a different Java package. In general this is painful and annoying when there's only one implementation, but I think it's valuable when you're trying to showcase a public API because users won't be distracted by any implementation details at all.
> {quote}



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