[
https://issues.jboss.org/browse/TEIID-2998?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2998:
---------------------------------------
Its odd that what they return seems to flip back and forth. Sometimes
is does use the column label. Whenever it is returned as concat data values, there is a
corresponding NAMEINSOURCE option that has the correct column label.
To clarify there are two names we are dealing with. A column label and a column id. The
column ids are always A, B ... While the labels are inferred by google docs (I
haven't tested, but they also may be used for a named range containing the column).
If the metadata provides us with a label we use that as the column name and set the name
in source to the id. Otherwise we just use the id as the column name - we could also set
the name in source here, but we know that the column ids are simple identifiers so there
is no special handling involved.
Is there any way to detect that and force it to use the column
label?
No, I'm saying that you may want an option to not use the column label and instead
just go with the id (A, B, ...)
problems with DDL returned for dynamic vdb with google spreadsheet
source
-------------------------------------------------------------------------
Key: TEIID-2998
URL:
https://issues.jboss.org/browse/TEIID-2998
Project: Teiid
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: AdminApi
Affects Versions: 8.7
Reporter: Mark Drilling
Assignee: Steven Hawkins
Attachments: ChromeSheet.png, FirefoxSheet.png, GoogleSpreadsheetJIRA.txt
I am seeing inconsistent DDL returned for dynamic VDB with a google spreadsheet source.
In the same google account, I created two spreadsheets. One was created in firefox
browser, one was created in chrome browser (don't know why that matters)
See the attached document showing a comparison of the dynamic VDBs and the DDL that I got
back. The only difference is that the source was pointing to a different spreadsheet.
Notice that the DDL for the "ChromeSheet" returns the concatenated datavalues
for the column name. But it includes a NIS OPTION for the column name.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)