[ https://issues.apache.org/jira/browse/DRILL-2661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jacques Nadeau resolved DRILL-2661. ----------------------------------- Resolution: Invalid Drill supports schemaed and non-schemaed data sources. If a source is schemaed, we validate the schema. If the source is non-schemaed, we can't validate the schema upfront and thus return null values to the user. Information schema, Hive and most Views are schemaed and thus share this behavior. > Inconsistent non-existent column handling in INFORMATION_SCHEMA; intended? > -------------------------------------------------------------------------- > > Key: DRILL-2661 > URL: https://issues.apache.org/jira/browse/DRILL-2661 > Project: Apache Drill > Issue Type: Bug > Components: Client - JDBC > Affects Versions: 0.8.0 > Reporter: Daniel Barclay (Drill) > > References to columns that do not exist in INFORMATION_SCHEMA tables/views > yield errors, which is inconsistent with the behavior elsewhere, in which > references to columns that do not exist simply yield null. > Is this intentional (e.g., because for INFORMATION_SCHEMA tables we know what > columns we provide (i.e., they're not user data files which might have > different columns at different points in time))? -- This message was sent by Atlassian JIRA (v6.3.4#6332)