[jira] [Work logged] (HIVE-26370) Check stats are up-to-date when getting materialized view state

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HIVE-26370?focusedWorklogId=787823&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-787823 ]

ASF GitHub Bot logged work on HIVE-26370:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 05/Jul/22 12:31
            Start Date: 05/Jul/22 12:31
    Worklog Time Spent: 10m 
      Work Description: kasakrisz opened a new pull request, #3414:
URL: https://github.com/apache/hive/pull/3414

   <!--
   Thanks for sending a pull request!  Here are some tips for you:
     1. If this is your first time, please read our contributor guidelines: https://cwiki.apache.org/confluence/display/Hive/HowToContribute
     2. Ensure that you have created an issue on the Hive project JIRA: https://issues.apache.org/jira/projects/HIVE/summary
     3. Ensure you have added or run the appropriate tests for your PR: 
     4. If the PR is unfinished, add '[WIP]' in your PR title, e.g., '[WIP]HIVE-XXXXX:  Your PR title ...'.
     5. Be sure to keep the PR description updated to reflect all changes.
     6. Please write your PR title to summarize what this PR proposes.
     7. If possible, provide a concise example to reproduce the issue for a faster review.
   
   -->
   
   ### What changes were proposed in this pull request?
   <!--
   Please clarify what changes you are proposing. The purpose of this section is to outline the changes and how this PR fixes the issue. 
   If possible, please consider writing useful notes for better and faster reviews in your PR. See the examples below.
     1. If you refactor some codes with changing classes, showing the class hierarchy will help reviewers.
     2. If you fix some SQL features, you can provide some references of other DBMSes.
     3. If there is design documentation, please add the link.
     4. If there is a discussion in the mailing list, please add the link.
   -->
   
   
   ### Why are the changes needed?
   <!--
   Please clarify why the changes are needed. For instance,
     1. If you propose a new API, clarify the use case for a new API.
     2. If you fix a bug, you can clarify why it is a bug.
   -->
   
   
   ### Does this PR introduce _any_ user-facing change?
   <!--
   Note that it means *any* user-facing change including all aspects such as the documentation fix.
   If yes, please clarify the previous behavior and the change this PR proposes - provide the console output, description, screenshot and/or a reproducable example to show the behavior difference if possible.
   If possible, please also clarify if this is a user-facing change compared to the released Hive versions or within the unreleased branches such as master.
   If no, write 'No'.
   -->
   
   
   ### How was this patch tested?
   ```
   mvn test -Dtest.output.overwrite -DskipSparkTests -Dtest=TestMiniLlapLocalCliDriver -Dqfile=materialized_view_create_rewrite_10.q -pl itests/qtest -Pitests
   mvn test -Dtest=TestTxnHandler -pl ql
   ```




Issue Time Tracking
-------------------

            Worklog Id:     (was: 787823)
    Remaining Estimate: 0h
            Time Spent: 10m

> Check stats are up-to-date when getting materialized view state
> ---------------------------------------------------------------
>
>                 Key: HIVE-26370
>                 URL: https://issues.apache.org/jira/browse/HIVE-26370
>             Project: Hive
>          Issue Type: Bug
>          Components: Materialized views, Statistics, Transactions
>            Reporter: Krisztian Kasa
>            Assignee: Krisztian Kasa
>            Priority: Major
>             Fix For: 4.0.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Since HIVE-25656 materialized view state depends on the number of affected rows of transactions made on the source tables.
> If 
> {code}
> hive.stats.autogather=false;
> {code}
> the number of affected rows of transactions are not collected and it can cause invalid stats of source tables which leads to false indications about MV status.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)