In ConnectedFeedStatement, a similar piece of code has been commented out. IMO, the AQL parser should just get an AST from a query, but not access the metadata nor do any real work..
Best, Yingyi On Tue, Sep 29, 2015 at 2:46 PM, Ian Maxon <[email protected]> wrote: > I always wondered where that plan's input came from in the CC logs. It gets > generated during a connect statement as well. > > On Tue, Sep 29, 2015 at 2:04 PM, Mike Carey <[email protected]> wrote: > > > I wasn't aware of that statement...! > > On Sep 29, 2015 12:17 PM, "Yingyi Bu" <[email protected]> wrote: > > > > > All right, I will open an issue for that. > > > Thanks! > > > > > > Best, > > > Yingyi > > > > > > On Tue, Sep 29, 2015 at 12:11 PM, abdullah alamoudi < > [email protected]> > > > wrote: > > > > > > > I am not aware of any special reason and it definitely looks a bit > too > > > > hackish to me. > > > > I would say that it needs to be fixed but I don't think it is a > > priority > > > > at this point. Anyway, it is a private command that is not exposed to > > the > > > > end user. > > > > > > > > I would like to know if there is a reason as well. > > > > ~Abdullah. > > > > > > > > Amoudi, Abdullah. > > > > > > > > On Tue, Sep 29, 2015 at 9:53 PM, Yingyi Bu <[email protected]> > wrote: > > > > > > > >> Does anyone know why SubscribeFeedStatement in asterix-aql needs to > > > >> access the MetadataManager to form yet-another AQL insert query > inside > > > it > > > >> and hand that to the AQLParser again? > > > >> > > > >> It seems a bit hackish to me. Is there a particular reason that it > > must > > > >> be done this way? > > > >> Thanks! > > > >> > > > >> Best, > > > >> Yingyi > > > >> > > > >> > > > > > > > > > >
