[
https://issues.apache.org/jira/browse/PIG-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12836080#action_12836080
]
Pradeep Kamath commented on PIG-966:
------------------------------------
In retrospect, I think we can skip on creating a LoadFuncInterface since
currently there is no real use case for an interface - we are adding it to keep
symmetry with StoreFuncINterface and to allow implementations which extends
other classes to implement this interface. The first motivation is not very
strong and second also can be achieved through composition rather than
inheritance - it is unclear how inheriting a different class would benefit a
Loader implementation over composition to delegation functionality. By
introducing a LoadFuncInterface we would be exposing users who implement it to
backward incompatible additions in the future. So I think we should not add a
LoadFuncInterface now and ONLY if a real need arises add it. The rest of my
proposal (making StoreFunc an abstract class and add a new StoreFuncInterface)
still holds.
> Proposed rework for LoadFunc, StoreFunc, and Slice/r interfaces
> ---------------------------------------------------------------
>
> Key: PIG-966
> URL: https://issues.apache.org/jira/browse/PIG-966
> Project: Pig
> Issue Type: Improvement
> Components: impl
> Reporter: Alan Gates
> Assignee: Alan Gates
>
> I propose that we rework the LoadFunc, StoreFunc, and Slice/r interfaces
> significantly. See http://wiki.apache.org/pig/LoadStoreRedesignProposal for
> full details
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
