paul-rogers opened a new pull request, #13912:
URL: https://github.com/apache/druid/pull/13912

   Breaks out catalog-specific changes from the [Catalog Calcite integration 
PR](https://github.com/apache/druid/pull/13686) to allow easier reviewing.
   
   * Changes catalog table entries to Druid types
   * Enhanced support for external tables, including functions
   * Revised catalog sync API
   
   The key change here is to use Druid types, rather than SQL types, when 
declaring the schema of a table in the catalog. Druid types better match the 
actual Druid implementation whereas SQL types are just a SQL "view" on top of 
the actual Druid types. This change will allow us to use complex types which 
will be useful for specifying aggregate columns.
   
   #### Release note
   
   No user-visible changes yet. The docs for the catalog will appear in a later 
PR after the Calcite integration is complete.
   
   <hr>
   
   This PR has:
   
   - [X] been self-reviewed.
   - [ ] added documentation for new or modified features or behaviors.
   - [X] a release note entry in the PR description.
   - [X] added Javadocs for most classes and all non-trivial methods. Linked 
related entities via Javadoc links.
   - [X] added comments explaining the "why" and the intent of the code 
wherever would not be obvious for an unfamiliar reader.
   - [X] added unit tests or modified existing tests to cover new code paths, 
ensuring the threshold for [code 
coverage](https://github.com/apache/druid/blob/master/dev/code-review/code-coverage.md)
 is met.
   - [ ] been tested in a test Druid cluster.
   


-- 
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]

Reply via email to