[
https://issues.apache.org/jira/browse/IMPALA-7131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16769949#comment-16769949
]
ASF subversion and git services commented on IMPALA-7131:
---------------------------------------------------------
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]>
> Support external data sources without catalogd
> ----------------------------------------------
>
> Key: IMPALA-7131
> URL: https://issues.apache.org/jira/browse/IMPALA-7131
> Project: IMPALA
> Issue Type: Sub-task
> Components: Catalog, Frontend
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Minor
>
> Currently it seems that external data sources are not persisted except in
> memory on the catalogd. This means that it will be somewhat more difficult to
> support this feature in the design of impalad without a catalogd.
> This JIRA is to eventually figure out a way to support this feature -- either
> by supporting in-memory on a per-impalad basis, or perhaps by figuring out a
> way to register them persistently in a file system directory, etc.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
