[ https://issues.jboss.org/browse/TEIID-4825?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIID-4825 at 3/24/17 3:23 PM: ---------------------------------------------------------------- This is similar to TEIID-4672. Essentially the google-api has it's own rules as to when a column value is header or not. If there is just a header row or even just string data - it's just treated as a data row. With numeric content - it's automatically a header. This is a little thorny for us to undo. Even if we make the metadata match what we expect, queries that expect a header, such as update, operations will fail. I'll look again to see if there is a quick resolution. Otherwise it's simply the case that to google there is no header for the sheet in question and our metadata shouldn't treat it as having one. was (Author: shawkins): This is similar to TEIID-4672. Essentially the google-api has it's own rules as to when a column value is header or not. If there is just a header row or even just string data - it's just treated as a data row. With numeric content - it's automatically a header. This is a little thorny for us to undo. As even if we make the metadata match what we expect queries that expect a header, such as update operations will fail. I'll look again to see if there is a quick resolution. Otherwise it's simply the case that to google there is no header for the sheet in question and our metadata shouldn't treat it as having one. -- This message was sent by Atlassian JIRA (v7.2.3#72005)