FrankChen021 commented on issue #11929: URL: https://github.com/apache/druid/issues/11929#issuecomment-973816864
> I think this would be pretty straight-forward to do, so I think it makes sense to add a few of these common ones before we ship the feature. (In addition to "fall-back" EXTERN.) > > Btw, I feel it's kind of annoying to have the type signature there, but the reason it's there is that the planner needs to know the signature of the data that is being selected, before the data is actually inspected. At some point I'd like to explore ways we can get rid of the type signature in some cases or even all cases. But I had it there for now, because it fits into the existing planner better. > > Anyway, what do you think? @gianm I think it's OK for us to start with a JSON formatted parameter. As for the type signature, I want to know do we have plan to support DDL such as CREATE TABLE? If DDL is supported, we can split the type signatures into a CREATE TABLE statement which would be more convenient for users to get started with Druid. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
