[
https://issues.apache.org/jira/browse/HIVE-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14531062#comment-14531062
]
Alan Gates commented on HIVE-10595:
-----------------------------------
bq. So then there is nothing for Worker/Cleaner to do in this case.
Unless the table get's dropped between when the initiator initiates it and the
worker picks it up, same for worker-> cleaner. The issue with the worker can
also be seen if a user initiates compactions of a deleted or non-existent table.
bq. How will data from TXNS, COMPLETED_TXN_COMPONENTS, TXN_COMPONENTS which
relates to these table get cleaned up?
Hmm, that might be a general issue, but it isn't introduced by this. We need
to explore separately whether when compactions get dropped without being done
(for whatever reason) that everything in TXNS etc. get's properly cleaned up.
> Dropping a table can cause NPEs in the compactor
> ------------------------------------------------
>
> Key: HIVE-10595
> URL: https://issues.apache.org/jira/browse/HIVE-10595
> Project: Hive
> Issue Type: Bug
> Components: Metastore
> Affects Versions: 0.14.0, 1.0.0, 1.1.0
> Reporter: Alan Gates
> Assignee: Alan Gates
> Attachments: HIVE-10595.patch
>
>
> Reproduction:
> # start metastore with compactor off
> # insert enough entries in a table to trigger a compaction
> # drop the table
> # stop metastore
> # restart metastore with compactor on
> Result: NPE in the compactor threads. I suspect this would also happen if
> the inserts and drops were done in between a run of the compactor, but I
> haven't proven it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
