[
https://issues.apache.org/jira/browse/PIG-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Gates updated PIG-157:
---------------------------
Attachment: exceptions.patch
I have attached a patch that contains a rework of the exceptions. I'm trying
to rework the exception handling according to pig cookbook
(http://wiki.apache.org/pig/PigDeveloperCookbook). In this patch I've only
reworked areas that we've rewritten, I have not reworked areas we haven't
touched (yet). We can adapt exceptions in other areas as we rework them.I have
also not altered any interfaces, so there are a number of places I end up
converting exception types (e.g. in the builtin functions exec functions).
Major changes I made:
* Changed LogicalOperator.getSchema to throw FronendException instead of
IOException
* Added PlanException to org.apache.pig.impl.plan package and changed
OperatorPlan.connect to throw PlanException instead of IOException.
PlanException extends FrontendException. Also made VisitorException extend
PlanException.
* Changed DataType conversion routines to throw ExecException instead of
IOException
* Changed Tuple.get, Tuple.set, and a few other Tuple methods to throw
ExecException instead of IOException.
> Add types and rework execution pipeline
> ---------------------------------------
>
> Key: PIG-157
> URL: https://issues.apache.org/jira/browse/PIG-157
> Project: Pig
> Issue Type: New Feature
> Components: impl
> Reporter: Alan Gates
> Assignee: Alan Gates
> Attachments: Core.patch.zip, exceptions.patch, incr1.zip, patcher.sh
>
>
> This is the tracking bug for the work to add types to pig and rework the
> execution pipeline. Individual components of this work are covered in
> subtasks.
> Functional and design specs for this work are:
> http://wiki.apache.org/pig/PigTypesFunctionalSpec
> http://wiki.apache.org/pig/PigTypesDesign
> http://wiki.apache.org/pig/PigExecutionModel
> This work is being done on the branch types, since it is large and
> disruptive, and we want to be able to do incremental checkins without causing
> issues for the trunk.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
