sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Veena Basavaraj (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-1801) Delta Fetch Merge Config API : Validations for the Delta Fetch/Merge Configs
Date Thu, 15 Jan 2015 17:25:35 GMT

    [ https://issues.apache.org/jira/browse/SQOOP-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14278973#comment-14278973

Veena Basavaraj commented on SQOOP-1801:

Again, there is not much work in this ticket, It will mainly document how config validation
can happen and provide probable examples connectors can use to provide inputs and validation
for the inputs in the config classes for delta read and delta writes

> Delta Fetch Merge Config API : Validations for the Delta Fetch/Merge Configs
> ----------------------------------------------------------------------------
>                 Key: SQOOP-1801
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1801
>             Project: Sqoop
>          Issue Type: Sub-task
>            Reporter: Veena Basavaraj
>            Assignee: Veena Basavaraj
>             Fix For: 1.99.5
> The configs will mainly have the operators, columns and values
> 1. Required/ Optional validation
> operators (Required, or we default to > ) , column (Required)  and values ( optional)
and the las-value in the from config will be used
> 2. Enum of supported operators and its semantics and check if the operator is valid
> Supported operators ( < , >, LIKE, IN BETWEEN...) to begin with 
> 3. Validate if the column exists in the data source.
> 4. Validate that the corresponding connectors support the incremental.
> Few more are possible depending on how much feedback we want to give in the early stages...

This message was sent by Atlassian JIRA

View raw message