asterixdb-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Jacobs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ASTERIXDB-1695) More entities in the default dataverse
Date Mon, 24 Oct 2016 16:53:58 GMT

    [ https://issues.apache.org/jira/browse/ASTERIXDB-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15602554#comment-15602554
] 

Steven Jacobs commented on ASTERIXDB-1695:
------------------------------------------

I looked at this more, and the issue that I had was actually unrelated (and fixed now).

> More entities in the default dataverse
> --------------------------------------
>
>                 Key: ASTERIXDB-1695
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1695
>             Project: Apache AsterixDB
>          Issue Type: Bug
>            Reporter: Yingyi Bu
>            Assignee: Abdullah Alamoudi
>
> The following query works fine.
> {noformat}
> DROP function foo if exists;
> CREATE function foo(){
>   1
> }
> SELECT Default.foo();
> {noformat}
> But the next one doesn't work:
> {noformat}
> DROP function foo if exists;
> CREATE function foo(){
>   1
> }
> SELECT foo();
> {noformat}
> I got this error message:
> "msg": "function null.foo@0 is not defined",
> I'm guessing that it is related to the default dataverse change.
> I guess we need to verify all metadata entities can work under the default dataverse.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message