[zebra] Using typed APIs for Zebra's Map/Reduce interface
---------------------------------------------------------
Key: PIG-1125
URL: https://issues.apache.org/jira/browse/PIG-1125
Project: Pig
Issue Type: Improvement
Affects Versions: 0.4.0
Reporter: Chao Wang
Assignee: Chao Wang
Fix For: 0.6.0, 0.7.0
We plan to modify Zebra's M/R interface to use typed APIs, i.e., APIs taking
object arguments, instead of String arguments.
Take TableInputFormat as an example:
setSchema(jobConf conf, String schema) is changing to setSchema(jobConf conf,
ZebraSchemaInfo schemaInfo)
setProjection(jobConf conf, String projection) is changing to
setProjection(jobConf conf, ZebraProjectionInfo projectionInfo)
and so on.
Benefits: 1) Typed APIs make it easier to detect usage mistakes earlier and 2)
Typed APIs are richer and hide things better.
In the meanwhile, we plan to make the old APIs deprecated, instead of removing
them, for the sake of safety.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
