[ https://issues.apache.org/jira/browse/SQOOP-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508058#comment-13508058
]
Jarek Jarcec Cecho commented on SQOOP-638:
------------------------------------------
Failure in profile hadoop200 is expected due to SQOOP-731.
Jarcec
> Add an optional, simple and extensible validation framework for sqoop
> ---------------------------------------------------------------------
>
> Key: SQOOP-638
> URL: https://issues.apache.org/jira/browse/SQOOP-638
> Project: Sqoop
> Issue Type: Improvement
> Affects Versions: 1.4.2
> Reporter: Venkatesh Seetharam
> Assignee: Venkatesh Seetharam
> Priority: Minor
> Fix For: 1.4.3
>
> Attachments: SQOOP-638.patch, SQOOP-638-r6.patch
>
>
> Attempt to add an extensible validation framework to Sqoop. Adds an optional CLI option:
--validate
> There are 3 basic interfaces:
> ValidationThreshold - Determines if the error margin between the source and target are
acceptable: Absolute, Percentage Tolerant, etc.
> Default implementation is AbsoluteValidationThreshold which ensures the row counts from
source and targets are the same.
> ValidationFailureHandler - Responsible for handling failures: log an error/warning, abort,
etc. Default implementation logs a warning message to the configured logger.
> Validator - Drives the validation logic by delegating the decision to ValidationThreshold
and delegating failure handling to ValidationFailureHandler. The default implementation comes
with a RowCountValidator which validates the row counts from source and the target.
> You could extend these interfaces for more specific implementations and override 'em
in sqoop configuration that is picked up.
--
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
|