hudi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "vinoyang (Jira)" <j...@apache.org>
Subject [jira] [Updated] (HUDI-652) Decouple HoodieReadClient and AbstractHoodieClient to break the inheritance chain
Date Wed, 04 Mar 2020 13:21:00 GMT

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

vinoyang updated HUDI-652:
--------------------------
    Summary: Decouple HoodieReadClient and AbstractHoodieClient to break the inheritance chain
 (was: Decouple HoodieReadClient and AbstractHoodieClient to brean the inheritance chain)

> 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
>
> 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)

Mime
View raw message