hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zoltan Haindrich (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-18285) StatsTask uses a cached ql.metadata.Table object
Date Tue, 19 Dec 2017 09:23:00 GMT

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

Zoltan Haindrich commented on HIVE-18285:
-----------------------------------------

There were some efforts to reduce the used metastore calls; but ddltask sends the table object
to metastore - and since statstask needs to update the stats (which are currently stored in
properties ; sends a second table call.... I think this could be avoided later somehow ; when
statstask makes less metastore calls ; I've opened HIVE-18302.

I don't feel right to change the table object fundamentally in metastore listeners...I've
found examples where inputformat have been changed to some other...

[~ekoifman]: Could you please add a testcase to protect this usecase in the future?

> StatsTask uses a cached ql.metadata.Table object
> ------------------------------------------------
>
>                 Key: HIVE-18285
>                 URL: https://issues.apache.org/jira/browse/HIVE-18285
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore, Statistics
>            Reporter: Eugene Koifman
>            Assignee: Eugene Koifman
>         Attachments: HIVE-18285.01.patch
>
>
> this then causes BasicStatsTask.aggregateStats(Hive) to call Hive.alterTable() with a
stale Table object.  (It misses any changes made by any MetaStorePreEventListener)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message