You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Slim Bouguerra (Jira)" <ji...@apache.org> on 2020/08/03 18:48:00 UTC

[jira] [Created] (SAMZA-2572) Umbrella Jira for Samza SQL type system improvement

Slim Bouguerra created SAMZA-2572:
-------------------------------------

             Summary: Umbrella Jira for Samza SQL type system improvement
                 Key: SAMZA-2572
                 URL: https://issues.apache.org/jira/browse/SAMZA-2572
             Project: Samza
          Issue Type: Improvement
          Components: sql
            Reporter: Slim Bouguerra


This an umbrella Jira to keep track of related improvements and fix that will tackle as part of Samza SQL Type system and SQL translation.

The goal here is to ensure that most of the type checking can be done at Query compile time. In the other hand adding more type checking and schema aware data structure will enable more robust runtime type checking.


Here is the list of items that will be tackled in the short term, and other item(s) is/are welcome.
 * Ensure that the Calcite Schema top level column order is the same as the Samza input Rel Message.
 * Ensure that the Primary Key Column of remote tables (__key__) is typed and listable as part of the table describe via shell.
 * Ensure that the join Condition for case of remote table is checked at compile time aka making sure that the join predicate is in the form of __key__ = c and (any other predicate)
 * Ensure that the Remote Table Join table key converter is type safe and can be type checked at compile time (SamzaRelTableKeyConverter). Today this is exposed as an Object and it is hard to check at runtime or compile time.

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)