[ 
https://issues.apache.org/jira/browse/PIG-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13780485#comment-13780485
 ] 

Jeremy Karn commented on PIG-3457:
----------------------------------

Writing tools that have to support different versions of the same Java 
interface is a pain.  I think there will be tools (Mortar and Lipstick at 
least) that will want to support 0.12 and 0.13 at the same time they're still 
supporting at least 0.11.

Given that the PPNL is very 'public facing' I think ideally we'd actually have 
a deprecation path that doesn't cause compile time problems.

I think something like:

* Leave PPNL in its current state.  Deprecate methods w/ JobStats as a parameter
* Add BasePPNL which implements PPNL.  Have it offer new methods w/ 
JobStatsBase as the parameter and offer no-op implementations
* Change ScriptState to allow registering both PPNLs and BasePPNLs. New events 
will only be emitted to BasePPNLs.  

I think this would let 3rd party tools take advantage of new methods in the 
PPNL while still easily working with older versions of Pig.
                
> Provide backward compatibility for PigStatsUtil and JobStats
> ------------------------------------------------------------
>
>                 Key: PIG-3457
>                 URL: https://issues.apache.org/jira/browse/PIG-3457
>             Project: Pig
>          Issue Type: Bug
>          Components: impl
>            Reporter: Daniel Dai
>            Assignee: Daniel Dai
>             Fix For: 0.12.0
>
>         Attachments: PIG-3457-1.patch, PIG-3457-2.patch, PIG-3457-3.patch, 
> PIG-3457-4.patch, PIG-3457-5.patch
>
>
> PIG-3419 restructured PigStatsUtil which break downstream projects such as 
> Oozie. Oozie uses PigStatsUtil.{HDFS_BYTES_WRITTEN, MAP_INPUT_RECORDS, 
> MAP_OUTPUT_RECORDS, REDUCE_INPUT_RECORDS, REDUCE_OUTPUT_RECORDS}. We need to 
> provide a backward compatible way.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to