[
https://issues.apache.org/jira/browse/HIVE-9271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14294519#comment-14294519
]
Sushanth Sowmyan commented on HIVE-9271:
----------------------------------------
No documentation needed here - this is not intended to be publicly visible and
is hive internal mechanics.
Basically, what's happening here is that some commands like INSERT might modify
hive data without changing any metadata - thus, we want to have a way for the
client to tell the metastore that it's making a change so there's a record of
it in those cases for people checking the metastore for changes, such as the
in-development replication subsystem. So, this adds support for the client to
send us that information. HIVE-9273 will address actually making those changes
from the client side.
When the Replication system itself is done, there will be a documentation need
for that, and that will enumerate all the events it's acting on, and it will
eventually be exposed through there.
> Add ability for client to request metastore to fire an event
> ------------------------------------------------------------
>
> Key: HIVE-9271
> URL: https://issues.apache.org/jira/browse/HIVE-9271
> Project: Hive
> Issue Type: New Feature
> Components: Metastore
> Reporter: Alan Gates
> Assignee: Alan Gates
> Fix For: 0.15.0
>
> Attachments: HIVE-9271.patch
>
>
> Currently all events in Hive are fired by the metastore. However, there are
> events that only the client fully understands, such as DML operations. There
> should be a way for the client to request the metastore to fire a particular
> event.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
