[
https://issues.apache.org/jira/browse/IMPALA-7128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16769948#comment-16769948
]
ASF subversion and git services commented on IMPALA-7128:
---------------------------------------------------------
Commit 85906dd6ac141c1015d1abebef1228c9b8b66d90 in impala's branch
refs/heads/2.x from Todd Lipcon
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=85906dd ]
IMPALA-7128 (part 2): add an interface for data sources
This changes most of the usage of DataSource and DataSourceTable to use
interfaces instead of implementation classes. There are still various
usages of the implementation for functionality like creating and
dropping data sources. We'll address those as part of IMPALA-7131 at a
later date.
Change-Id: Ibe704197dc2ad7c09b8340865f17567096aa630e
Reviewed-on: http://gerrit.cloudera.org:8080/10626
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Extract interfaces for frontend interaction with catalog objects
> ----------------------------------------------------------------
>
> Key: IMPALA-7128
> URL: https://issues.apache.org/jira/browse/IMPALA-7128
> Project: IMPALA
> Issue Type: Sub-task
> Components: Catalog, Frontend
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Major
> Fix For: Impala 3.1.0
>
>
> Currently both the catalogd and the impalad use the same implementation
> classes for catalog objects such as Table, Function, HdfsPartition, etc.
> Those implementations are fairly tightly coupled to the current design of the
> catalog.
> For the new catalog design, it will be easier to have a new set of classes
> rather than attempting to reuse or modify the existing ones for a few reasons:
> - the existing ones are mutable in the catalogd and thus have to worry quite
> a bit about synchronization, whereas the new design uses immutable catalog
> objects
> - the existing ones assume "all or nothing" loading whereas the new design
> involves lazy-loading relevant bits of info
> - we don't want to destabilize the existing implementation, so we want to
> avoid any nontrivial modifications of the existing code.
> Extracting a set of interfaces such as 'FeTable', 'FeDb', etc, will help
> decouple the frontend from the particular catalog implementation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
