[
https://issues.apache.org/jira/browse/DRILL-2721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Barclay (Drill) closed DRILL-2721.
-----------------------------------------
Resolution: Fixed
Closing because superseded by combination of DRILL-3216 (many changes being
made) and DRILL-2763 (also includes other not-yet-resolved items).
> Identify, fix _existing_ INFO._SCHEMA columns in conflict with SQL spec. by
> 1.0
> -------------------------------------------------------------------------------
>
> Key: DRILL-2721
> URL: https://issues.apache.org/jira/browse/DRILL-2721
> Project: Apache Drill
> Issue Type: Bug
> Components: Metadata
> Reporter: Daniel Barclay (Drill)
> Assignee: Daniel Barclay (Drill)
> Fix For: 1.2.0
>
>
> Much of the INFORMATION_SCHEMA.COLUMNS table doesn't follow the SQL
> specification.
> Most cases are columns that simply aren't implemented yet, because they are
> of lower priority, probably because they won't be useful in Drill.
> However, some columns that already exist conflict with what the SQL
> specification specifies for them. (For example, non-applicable precision
> values are represented as -1 rather than NULL.)
> Those existing columns should probably be corrected before GA/version 1.0, so
> that users don't start depending on invalid values, which will make it harder
> to correct things later).
> TBD: enumeration of specific problems/corrections
> (rough notes of current awareness:
> - some -1 should be NULL
> - some -1/NULL for numeric precision should be 0
> - floating-point numeric precision should be in bits, not digits
> - it might be that type names should be canonical names, not
> syntactic-shortcut names (e.g., "VARCHAR" -> "CHARACTER_VARYING")
> - character-type length and numeric precision might be wrongly combined into
> same column
> )
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
