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

ASF GitHub Bot commented on PHOENIX-3817:
-----------------------------------------

Github user karanmehta93 commented on a diff in the pull request:

    https://github.com/apache/phoenix/pull/309#discussion_r219293433
  
    --- Diff: 
phoenix-core/src/main/java/org/apache/phoenix/mapreduce/util/PhoenixConfigurationUtil.java
 ---
    @@ -371,20 +396,31 @@ public static void setUpsertStatement(final 
Configuration configuration, String
             }
             return selectColumnList;
         }
    -    
    +
         public static String getSelectStatement(final Configuration 
configuration) throws SQLException {
    +        return getSelectStatement(configuration, false);
    +    }
    +
    +    public static String getSelectStatement(final Configuration 
configuration,
    +            boolean isTargetStatement) throws SQLException {
             Preconditions.checkNotNull(configuration);
    -        String selectStmt = configuration.get(SELECT_STATEMENT);
    +        String selectKey = (isTargetStatement) ? SELECT_TARGET_STATEMENT : 
SELECT_STATEMENT;
    +        String selectStmt = configuration.get(selectKey);
             if(isNotEmpty(selectStmt)) {
    --- End diff --
    
    Please add a info LOG line here.


> VerifyReplication using SQL
> ---------------------------
>
>                 Key: PHOENIX-3817
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3817
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Alex Araujo
>            Assignee: Akshita Malhotra
>            Priority: Minor
>             Fix For: 4.15.0
>
>         Attachments: PHOENIX-3817-final.patch, PHOENIX-3817-final2.patch, 
> PHOENIX-3817.v1.patch, PHOENIX-3817.v2.patch, PHOENIX-3817.v3.patch, 
> PHOENIX-3817.v4.patch, PHOENIX-3817.v5.patch, PHOENIX-3817.v6.patch, 
> PHOENIX-3817.v7.patch
>
>
> Certain use cases may copy or replicate a subset of a table to a different 
> table or cluster. For example, application topologies may map data for 
> specific tenants to different peer clusters.
> It would be useful to have a Phoenix VerifyReplication tool that accepts an 
> SQL query, a target table, and an optional target cluster. The tool would 
> compare data returned by the query on the different tables and update various 
> result counters (similar to HBase's VerifyReplication).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to