[
https://issues.apache.org/jira/browse/IMPALA-7971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16830405#comment-16830405
]
ASF subversion and git services commented on IMPALA-7971:
---------------------------------------------------------
Commit 095d609260ba8957c13e61c539892ab37c5da10b in impala's branch
refs/heads/master from Todd Lipcon
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=095d609 ]
IMPALA-7971 (follow-up). Fix compilation error
15a33d1ba was committed at about the same time as 5ced9160bd6, which
renamed one of the methods of the FileDescriptor class, causing a
compilation error. This follow-up mixes the semantic conflict.
Tested tests/custom_cluster/test_event_processing.py manually.
Change-Id: I8071b421f0dcbae2d303bd9f1e1f6f64657c49c0
Reviewed-on: http://gerrit.cloudera.org:8080/13184
Reviewed-by: Todd Lipcon <t...@apache.org>
Tested-by: Todd Lipcon <t...@apache.org>
> Add support to detect insert events from Impala
> -----------------------------------------------
>
> Key: IMPALA-7971
> URL: https://issues.apache.org/jira/browse/IMPALA-7971
> Project: IMPALA
> Issue Type: Sub-task
> Reporter: Vihang Karajgaonkar
> Assignee: Anurag Mantripragada
> Priority: Major
>
> When data is inserted into existing tables and partitions, Catalog does not
> issue any metastore API calls. Metastore provides a API called
> {{fire_listener_event}} which can be used to add a {{INSERT_EVENT}} to the
> metastore notification log. This event can be used by other Impala instances
> to invalidate or update the filemetada information when data is inserted or
> overrwriten on a given table or partition.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
