[ https://issues.apache.org/jira/browse/DRILL2522?page=com.atlassian.jira.plugin.system.issuetabpanels:alltabpanel
]
Daniel Barclay (Drill) updated DRILL2522:

Description:
[TBD: intro.]
A. {{COLUMNS}} columns existing in Drill that are not compliant with standard SQL:
1. {{COLUMNS.ORDINAL_POSITION}} values are zerobased rather than being onebased.
2. {{COLUMNS}} columns {{CHARACTER_MAXIMUM_LENGTH}}, {{NUMERIC_PRECISION_RADIX}}, {{NUMERIC_SCALE}},
and {{NUMERIC_PRECISION}} use {{1}} instead of {{NULL}} for the "notapplicable" case.
3. {{NUMERIC_PRECISION}} for integral exact numeric types (e.g., {{INTEGER}}) and approximate
numeric types (e.g., {{DOUBLE}}) is {{1}} (logical null) instead of the specified values.
3. {{NUMERIC_SCALE}} for integral exact numeric types is {{1}} instead of {{0}}.
4. {{NUMERIC_SCALE}} for approximate numeric types is {{1}} instead of the number of bits
of precision (24 and 53(?)).
5. {{NUMERIC_PRECISION_RADIX}} for non{{DECIMAL}} exact numeric types is {{1}} instead of
{{10}}.
6. {{NUMERIC_PRECISION_RADIX}} for approximate exact numeric types is {{1}} instead of {{2}}.
7. {{CHARACTER_MAXIMUM_LENGTH}} for types {{CHAR}}, {{BINARY}}, and {{VAR BINARY}} is {{1}}
instead of the corresponding length.
8. {{COLUMNS.DATA_TYPE}} values for {{INTERVAL}} with {{YEAR}} and/or {{MONTH}} and for {{INTERVAL}}
with {{DAY}}, {{HOUR}}, {{MINUTE}}, and/or {{SECOND}} are "{{INTERVAL_YEAR_MONTH}}" and "{{INTERVAL_DATA_TIME}}",
respectively, instead of the data type name "{{INTERVAL}}".
9. {{COLUMNS.DATA_TYPE}} values for nonatomic types seem to be type descriptors ({{<data
type>}} syntax), e.g., "{{VARCHAR(65536) ARRAY}}" instead of just data type names (e.g.,
"{{ARRAY}}").
10. *TDB*: {{COLUMNS.COLUMN_NAME}} holds the original form of the name but _might_ need to
be uppercased here to be compliant.
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:
[TBD: intro.]
A. {{COLUMNS}} columns existing in Drill that are not compliant with standard SQL:
1. {{COLUMNS.ORDINAL_POSITION}} values are zerobased rather than being onebased.
2. {{COLUMNS}} columns {{CHARACTER_MAXIMUM_LENGTH}}, {{NUMERIC_PRECISION_RADIX}}, {{NUMERIC_SCALE}},
and {{NUMERIC_PRECISION}} use {{1}} instead of {{NULL}} for the "notapplicable" case.
3. {{NUMERIC_SCALE}} for integral exact numeric types (e.g., {{INTEGER}}) is {{1}} (logical
null) instead of {{0}}.
4. {{NUMERIC_SCALE}} for approximate numeric types (e.g., {{DOUBLE}}) is {{1}} instead of
the number of bits of precision (24 and 53(?)).
5. {{NUMERIC_PRECISION_RADIX}} for non{{DECIMAL}} exact numeric types is {{1}} instead of
{{10}}.
6. {{NUMERIC_PRECISION_RADIX}} for approximate exact numeric types is {{1}} instead of {{2}}.
7. {{CHARACTER_MAXIMUM_LENGTH}} for types {{CHAR}}, {{BINARY}}, and {{VAR BINARY}} is {{1}}
instead of the corresponding length.
8. {{COLUMNS.DATA_TYPE}} values for {{INTERVAL}} with {{YEAR}} and/or {{MONTH}} and for {{INTERVAL}}
with {{DAY}}, {{HOUR}}, {{MINUTE}}, and/or {{SECOND}} are "{{INTERVAL_YEAR_MONTH}}" and "{{INTERVAL_DATA_TIME}}",
respectively, instead of the data type name "{{INTERVAL}}".
9. {{COLUMNS.DATA_TYPE}} values for nonatomic types seem to be type descriptors (<data
type> syntax), e.g., "{{VARCHAR(65536) ARRAY}}" instead of just data type names (e.g.,
"{{ARRAY}}").
10. *TDB*: {{COLUMNS.COLUMN_NAME}} might not represent properly"cased" (uppercased?) version
of name.
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]
> Implement INFORMATION_SCHEMA enough for relevant tools [umbrella/tracking bug]
> 
>
> Key: DRILL2522
> URL: https://issues.apache.org/jira/browse/DRILL2522
> 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:
> 1. {{COLUMNS.ORDINAL_POSITION}} values are zerobased rather than being onebased.
> 2. {{COLUMNS}} columns {{CHARACTER_MAXIMUM_LENGTH}}, {{NUMERIC_PRECISION_RADIX}}, {{NUMERIC_SCALE}},
and {{NUMERIC_PRECISION}} use {{1}} instead of {{NULL}} for the "notapplicable" case.
> 3. {{NUMERIC_PRECISION}} for integral exact numeric types (e.g., {{INTEGER}}) and approximate
numeric types (e.g., {{DOUBLE}}) is {{1}} (logical null) instead of the specified values.
> 3. {{NUMERIC_SCALE}} for integral exact numeric types is {{1}} instead of {{0}}.
> 4. {{NUMERIC_SCALE}} for approximate numeric types is {{1}} instead of the number of
bits of precision (24 and 53(?)).
> 5. {{NUMERIC_PRECISION_RADIX}} for non{{DECIMAL}} exact numeric types is {{1}} instead
of {{10}}.
> 6. {{NUMERIC_PRECISION_RADIX}} for approximate exact numeric types is {{1}} instead
of {{2}}.
> 7. {{CHARACTER_MAXIMUM_LENGTH}} for types {{CHAR}}, {{BINARY}}, and {{VAR BINARY}} is
{{1}} instead of the corresponding length.
> 8. {{COLUMNS.DATA_TYPE}} values for {{INTERVAL}} with {{YEAR}} and/or {{MONTH}} and for
{{INTERVAL}} with {{DAY}}, {{HOUR}}, {{MINUTE}}, and/or {{SECOND}} are "{{INTERVAL_YEAR_MONTH}}"
and "{{INTERVAL_DATA_TIME}}", respectively, instead of the data type name "{{INTERVAL}}".
> 9. {{COLUMNS.DATA_TYPE}} values for nonatomic types seem to be type descriptors ({{<data
type>}} syntax), e.g., "{{VARCHAR(65536) ARRAY}}" instead of just data type names (e.g.,
"{{ARRAY}}").
> 10. *TDB*: {{COLUMNS.COLUMN_NAME}} holds the original form of the name but _might_ need
to be uppercased here to be compliant.
> 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)
