[
https://issues.jboss.org/browse/TEIID-4034?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-4034:
----------------------------------
Component/s: Misc. Connectors
Description:
The GoogleJSONParser has handling for javascript dates, but only of the form new
Date(...)
However the data result uses datetime/date values that are actually string literals of the
form
"Date(...)"
Also the time format is an array of numbers:
[1,2,3,4]
The translator needs to account for all of these.
Additionally:
- support for ClientLogin should be removed as it is no longer allowed by google.
- there is a collision between resource bundles as they are in the same package between
the connector and api modules.
was:
A VDB connecting to a google spreadsheet datasource fails to create the model, and thus
fails, probably due to the fact that one of the spreadhseet fields is formatted
timestamp, but uses a different format (dd/MM/yyyy hh:mm:ss) than the one the translator
expects (yyyy-mm-dd hh:mm:ss).
This spreadsheet cited in the forum reference is, in particular, directly generated by
google forms, and the timestamp field is created by the form engine to record when the
form if fille dby a user with a timestamp, so no control on the field is possible in the
source...
see forum reference for full details/description
Fix Version/s: 9.0
8.12.5
8.13.2
Summary: Google spreadsheet translator issues (was: date parsing in google
spreadsheet translator expects soecific timestamp format)
Google spreadsheet translator issues
------------------------------------
Key: TEIID-4034
URL:
https://issues.jboss.org/browse/TEIID-4034
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 8.12.3
Reporter: Marco Ardito
Assignee: Steven Hawkins
Fix For: 9.0, 8.12.5, 8.13.2
The GoogleJSONParser has handling for javascript dates, but only of the form new
Date(...)
However the data result uses datetime/date values that are actually string literals of
the form
"Date(...)"
Also the time format is an array of numbers:
[1,2,3,4]
The translator needs to account for all of these.
Additionally:
- support for ClientLogin should be removed as it is no longer allowed by google.
- there is a collision between resource bundles as they are in the same package between
the connector and api modules.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)