asterixdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Carey <dtab...@gmail.com>
Subject Re: Metadata.Dataset vs asterix.Dataset
Date Fri, 08 Dec 2017 02:02:55 GMT
(And we should be phasing out AQL....)


On 12/7/17 2:38 PM, Dmitry Lychagin wrote:
> Steven,
>
> I recently merged a change that fixes namespaces for all function signatures that SQLPP
compiler generates to match namespaces defined in BuiltinFunctions and AlgebricksBuiltinFunctions
(so ‘asterix’ / ‘algebricks’). I have not reviewed AQL code at that point, so it might
still generate them in the ‘Metadata’ namespace.
>
> Thanks,
> -- Dmitry
>   
>
> On 12/7/17, 12:17 PM, "Steven Jacobs" <sjaco002@ucr.edu> wrote:
>
>      Hi all,
>      Right now when we compile an AQL FLWOR vs an SQL SELECT we get two
>      different function signatures for "Dataset"
>      
>      SQL calls "asterix.Dataset" while AQL calls "Metadata.Dataset"
>      
>      Does anyone know why these are distinct?
>      
>      To see an example, look at the rewrittenResult in
>      QueryTranslator.rewriteCompileQuery for the following:
>      
>        for $x in dataset TwitterUsers
>        return $x;
>      
>      
>      vs
>      
>        select * from TwitterUsers;
>      
>      
>      Steven
>      
>


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message