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

ASF GitHub Bot commented on TRAFODION-2263:
-------------------------------------------

GitHub user anoopsharma00 opened a pull request:

    https://github.com/apache/incubator-trafodion/pull/749

    jira TRAFODION-2263 updated regression filter file

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/anoopsharma00/incubator-trafodion 
ansharma_simcheck_br

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-trafodion/pull/749.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #749
    
----
commit ec54d8b0c247795569b6ade220fd3c67b029e9d6
Author: Anoop Sharma <[email protected]>
Date:   2016-10-08T14:01:29Z

    jira TRAFODION-2263 updated regression filter file

----


> Move Similarity check for hive tables to master executor root operator
> ----------------------------------------------------------------------
>
>                 Key: TRAFODION-2263
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-2263
>             Project: Apache Trafodion
>          Issue Type: Improvement
>            Reporter: Anoop Sharma
>            Assignee: Anoop Sharma
>            Priority: Minor
>
> Query plans for hive tables include location of data directories/files
> and the plan depends on it.
> If data changes in a hive file/dir after a query has been compiled and
> before it is executed, then that change is detected at runtime by
> comparing compile time and runtime dir timestamps.
> A mismatch causes that query to recompile using AQR and a new
> plan is generated with latest dir location.
> This detection is currently being done at leaf operators (scan, insert) when
> that operator is executed.
> This jira is to move that check (called Similarity Check) to the root 
> operator before starting query execution. That way plan consistency
> checks will be done before running the query and will not depend
> on the actual operator being executed. It will also result in checks not
> being done at various processes and operators like an ESP process.
> All checks will be done at one place in master executor and code will not
> be spread across multiple operators as it is now.
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to