Jackie-Jiang commented on pull request #6043: URL: https://github.com/apache/incubator-pinot/pull/6043#issuecomment-708007490
> I think we are having mixed semantics here. Even though it is a combination of 2 queries, our implementation is a transform function. It is not a correct subquery syntax that we usually see in other systems. > > The name of the transform functions should not contain subquery since it is implementation detail. On that note, don't think transform function should even be used to implement subquery semantics in Pinot since that is not the standard SQL semantics. > > We should just have the inner query in parentheses to implement a proper non correlated subquery in SQL. Is it absolutely necessary to have this subquery specified in a transform function? @siddharthteotia Currently our query parser & PinotQuery does not support inner query, thus we use transform function as a work around for this. In the future when we have the inner query support, we can change this to use inner query if necessary. This feature is in experiment phase, and I don't want to block this on the nested query project which has much bigger scope. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
