[
https://issues.apache.org/jira/browse/DRILL-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Barclay (Drill) updated DRILL-2522:
------------------------------------------
Description:
[TBD: intro.]
A. {{COLUMNS}} columns existing in Drill that are not compliant with standard
SQL:
- {{COLUMNS.ORDINAL_POSITION}} values are zero-based rather than being
one-based.
- {{COLUMNS}} columns {{CHARACTER_MAXIMUM_LENGTH}},
{{NUMERIC_PRECISION_RADIX}}, {{NUMERIC_SCALE}}, and {{NUMERIC_PRECISION}} use
{{-1}} instead of {{NULL}} for the "not-applicable" case.
- {{NUMERIC_SCALE}} for integral exact numeric types (e.g., {{INTEGER}}) is
{{-1}} (logical null) instead of {{0}}.
- {{NUMERIC_SCALE}} for approximate numeric types (e.g., {{DOUBLE}}) is {{-1}}
instead of the number of bits of precision (24 and 53(?)).
- {{NUMERIC_PRECISION_RADIX}} for non-{{DECIMAL}} exact numeric types is {{-1}}
instead of {{10}}.
- {{NUMERIC_PRECISION_RADIX}} for approximate exact numeric types is {{-1}}
rather than {{2}}.
- {{CHARACTER_MAXIMUM_LENGTH}} for types {{CHAR}}, {{BINARY}}, and {{VAR
BINARY}} is {{-1}} instead of the corresponding length.
- {{COLUMNS.DATA_TYPE}} values for non-atomic types seem to be type descriptors
(<data type> syntax), e.g., "{{VARCHAR(65536) ARRAY}}" instead of just data
type names (e.g., "{{ARRAY}}").
B. Standard {{COLUMNS}columns that don't exist in Drill and that probably are
more relevant:
[TBD]
C. Standard {{COLUMNS}columns that don't exist in Drill and that probably are
less relevant:
[TBD]
was:
A: Non-compliance with standard in existing columns:
- COLUMNS.ORDINAL_POSITION values are zero-based rather than one-based.
-
- COLUMNS.DATA_TYPE values for non-atomic types are not just data type names.
B. Non-existent standard columns:
> Implement INFORMATION_SCHEMA enough for relevant tools [umbrella/tracking bug]
> ------------------------------------------------------------------------------
>
> Key: DRILL-2522
> URL: https://issues.apache.org/jira/browse/DRILL-2522
> Project: Apache Drill
> Issue Type: Bug
> Components: Storage - Information Schema
> Reporter: Daniel Barclay (Drill)
> Assignee: Daniel Barclay (Drill)
> Priority: Critical
> Fix For: 1.0.0
>
>
> [TBD: intro.]
> A. {{COLUMNS}} columns existing in Drill that are not compliant with standard
> SQL:
> - {{COLUMNS.ORDINAL_POSITION}} values are zero-based rather than being
> one-based.
> - {{COLUMNS}} columns {{CHARACTER_MAXIMUM_LENGTH}},
> {{NUMERIC_PRECISION_RADIX}}, {{NUMERIC_SCALE}}, and {{NUMERIC_PRECISION}} use
> {{-1}} instead of {{NULL}} for the "not-applicable" case.
> - {{NUMERIC_SCALE}} for integral exact numeric types (e.g., {{INTEGER}}) is
> {{-1}} (logical null) instead of {{0}}.
> - {{NUMERIC_SCALE}} for approximate numeric types (e.g., {{DOUBLE}}) is
> {{-1}} instead of the number of bits of precision (24 and 53(?)).
> - {{NUMERIC_PRECISION_RADIX}} for non-{{DECIMAL}} exact numeric types is
> {{-1}} instead of {{10}}.
> - {{NUMERIC_PRECISION_RADIX}} for approximate exact numeric types is {{-1}}
> rather than {{2}}.
> - {{CHARACTER_MAXIMUM_LENGTH}} for types {{CHAR}}, {{BINARY}}, and {{VAR
> BINARY}} is {{-1}} instead of the corresponding length.
> - {{COLUMNS.DATA_TYPE}} values for non-atomic types seem to be type
> descriptors (<data type> syntax), e.g., "{{VARCHAR(65536) ARRAY}}" instead of
> just data type names (e.g., "{{ARRAY}}").
> B. Standard {{COLUMNS}columns that don't exist in Drill and that probably
> are more relevant:
> [TBD]
> C. Standard {{COLUMNS}columns that don't exist in Drill and that probably are
> less relevant:
> [TBD]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
