vinoyang created HUDI-652:
-----------------------------

             Summary: Decouple HoodieReadClient and AbstractHoodieClient to 
brean 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


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)

Reply via email to