abhishekrb19 commented on issue #14346: URL: https://github.com/apache/druid/issues/14346#issuecomment-1570700301
@vogievetsky, the proposal is based on the SQL 1999 specification - http://web.cecs.pdx.edu/~len/sql1999.pdf. Specifically for `INFORMATION_SCHEMA.ROUTINES`, please see the relevant sections: - Section 20.45 - ROUTINES view - A mention in section 4.24 and section 20.69 The column definitions are sort of scattered throughout the spec. Then I was also looking at a few [vendor implementations](https://en.wikipedia.org/wiki/Information_schema). The spec notes several columns that may not apply to Druid. For example, `CREATED` and `LAST_ALTERED` information only applies to stored procedures. So a few follow-up questions: 1. Should we add most/all columns from the spec to the table and mark them as "unused" (similar to what's [documented](https://druid.apache.org/docs/latest/querying/sql-metadata-tables.html) for the `INFORMATION_SCHEMA.COLUMNS` and `INFORMATION_SCHEMA.SCHEMATA` tables). Worth noting that the "unused" columns we document is an incomplete list from the spec, so I wonder if they're just there for legacy reasons. 2. Should we include the specific columns that apply to Druid selectively? I think 2 makes sense, but let me know what your thoughts are. -- 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]
