You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@asterixdb.apache.org by "Dmitry Lychagin (JIRA)" <ji...@apache.org> on 2017/12/20 05:41:00 UTC
[jira] [Commented] (ASTERIXDB-2193) Dataverse resolution within
function calls should be based on the dataverse in which the function
resides
[ https://issues.apache.org/jira/browse/ASTERIXDB-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16297911#comment-16297911 ]
Dmitry Lychagin commented on ASTERIXDB-2193:
--------------------------------------------
Fixed by https://asterix-gerrit.ics.uci.edu/#/c/2236/
> Dataverse resolution within function calls should be based on the dataverse in which the function resides
> ---------------------------------------------------------------------------------------------------------
>
> Key: ASTERIXDB-2193
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2193
> Project: Apache AsterixDB
> Issue Type: Bug
> Reporter: Steven Jacobs
> Assignee: Dmitry Lychagin
>
> The following will fail, but should succeed. The second call to the function should resolve the dataset based on the experiments dataverse:
> drop dataverse experiments if exists;
> create dataverse experiments;
> use experiments;
> create type TwitterUser if not exists as open{
> screen_name: string,
> friends_count: int32,
> name: string,
> followers_count: int32
> };
> create dataset TwitterUsers(TwitterUser) primary key screen_name;
> create function test_func0() {
> (select * from TwitterUsers)
> };
> test_func0();
> drop dataverse two if exists;
> create dataverse two;
> use two;
> experiments.test_func0();
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)