[jira] [Updated] (HUDI-652) Decouple HoodieReadClient and AbstractHoodieClient to break the inheritance chain

["Vinoth Chandar (Jira)" <ji...@apache.org>]

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

Vinoth Chandar updated HUDI-652:
--------------------------------
    Fix Version/s: 0.5.3
                   0.6.0

> Decouple HoodieReadClient and AbstractHoodieClient to break the inheritance chain
> ---------------------------------------------------------------------------------
>
>                 Key: HUDI-652
>                 URL: https://issues.apache.org/jira/browse/HUDI-652
>             Project: Apache Hudi (incubating)
>          Issue Type: Sub-task
>            Reporter: vinoyang
>            Assignee: vinoyang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.6.0, 0.5.3
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Since we decide to restructure the {{hudi-client}} module so that the write-specific classes could be moved to {{hudi-write-common}}. Currently, {{HoodieReadClient}} and {{HoodieWriteClient}} shared the same super class, it's {{AbstractHoodieClient}}. To do that, we should decouple {{HoodieReadClient}} and {{AbstractHoodieClient}}. Frome the source code, I found {{HoodieReadClient}} does not depend on {{AbstractHoodieClient}} deeply.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)