Got it. Thanks! Are we still deprecating AQL? Steven On Thu, Dec 7, 2017 at 2:38 PM, Dmitry Lychagin < [email protected]> 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" <[email protected]> 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 > > >
