You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Reuven Lax (JIRA)" <ji...@apache.org> on 2018/04/17 04:15:00 UTC

[jira] [Commented] (BEAM-4081) Review of schema metadata vs schema types

    [ https://issues.apache.org/jira/browse/BEAM-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440363#comment-16440363 ] 

Reuven Lax commented on BEAM-4081:
----------------------------------

agree, however I would recommend being conservative about what we promote to be a basic type, and err on keeping the Beam-level type set small. e.g. right now I see no good reason for Beam to distinguish between CHAR and VARCHAR, even though SQL does need to make this distinction (though maybe we will find a good reason for Beam to care).

> Review of schema metadata vs schema types
> -----------------------------------------
>
>                 Key: BEAM-4081
>                 URL: https://issues.apache.org/jira/browse/BEAM-4081
>             Project: Beam
>          Issue Type: Sub-task
>          Components: sdk-java-core
>            Reporter: Kenneth Knowles
>            Priority: Major
>
> The Schema basic types have a place for metadata that can say "this int is really millis since epoch". This deserves some careful design review and perhaps some of these need to be promoted to basic types.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)