[
https://issues.apache.org/jira/browse/ASTERIXDB-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17775334#comment-17775334
]
ASF subversion and git services commented on ASTERIXDB-3259:
------------------------------------------------------------
Commit 3869f2f913b1d940f578229b071573f996a4c6b2 in asterixdb's branch
refs/heads/master from Ali Alsuliman
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=3869f2f913 ]
[ASTERIXDB-3259][MTD] Implement database name resolution
- user model changes: no
- storage format changes: no
- interface changes: yes
Details:
Currently, qualification to database objects are resolved
as DataverseName only. That is a multipart identifier is
resolved as pure DataverseName only and the
database name is defaulted to 'System'/'Default'.
This patch is to resolve qualification to database objects
as database_name + dataverse_name + database_object.
This resolution is only applicable when database is used.
That is when cloud deployment is used.
Change-Id: Ic3f1d7b2019fcf62e5dcbce8c05a78d18cc0a710
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/17861
Reviewed-by: Murtadha Hubail <[email protected]>
Integration-Tests: Jenkins <[email protected]>
Tested-by: Ali Alsuliman <[email protected]>
> Introduce DATABASE level metadata entity
> ----------------------------------------
>
> Key: ASTERIXDB-3259
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-3259
> Project: Apache AsterixDB
> Issue Type: Improvement
> Components: COMP - Compiler, MTD - Metadata, SQL - Translator SQL++
> Affects Versions: 0.9.9
> Reporter: Ali Alsuliman
> Assignee: Ali Alsuliman
> Priority: Major
> Labels: triaged
> Fix For: 0.9.9
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
