[
https://issues.apache.org/jira/browse/IMPALA-7973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16884510#comment-16884510
]
Alex Rodoni commented on IMPALA-7973:
-------------------------------------
[~anuragmantri] [~vihangk1] I do not see a mention of a config change user has
to perform. Could you tell me what to document for this feature? The current
doc already mentions the partition-level events/updates. Thanks!
> Add support for fine-grained updates at partition level
> -------------------------------------------------------
>
> Key: IMPALA-7973
> URL: https://issues.apache.org/jira/browse/IMPALA-7973
> Project: IMPALA
> Issue Type: Sub-task
> Reporter: Vihang Karajgaonkar
> Assignee: Anurag Mantripragada
> Priority: Major
> Fix For: Impala 3.3.0
>
>
> When data is inserted into a partition or a new partition is created in a
> large table, we should not be invalidating the whole table. Instead it should
> be possible to refresh/add/drop certain partitions on the table directly
> based on the event information. This would help with the performance of
> subsequent access to the table by avoiding reloading the large table.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
