Progress DataDirect Cloud™
Progress DataDirect Cloud enables simple, fast connections to cloud and on-premise data regardless of source—SaaS apps, big data stores, or social networks—using a single standards-based ODBC or JDBC driver, or OData enabled application. For example, an organization might want to use a reporting application to predict travel budgets by analyzing travel data stored in the cloud. DataDirect Cloud can provide connectivity with simple configuration instead of extensive coding. In addition, when you install the DataDirect Cloud On-Premise Connector on a machine behind your firewall, you can connect to on-premise data sources using DataDirect Cloud, without opening ports or otherwise configuring the fire wall. The On-Premise Connector establishes a secure connection back to DataDirect Cloud when needed to provide access to the on-premise data stores.
DataDirect Cloud– August 23, 2014
- Progress OpenEdge v11.4 is now supported
- The default value of the Login Timeout connection parameter has been changed to 30 seconds for the following data stores:
- Apache Hadoop Hive
- Microsoft SQL Server
- Malformed ODataSchemaMap string could sometimes cause high CPU usage on the service.
- Specifying Primary Key column(s) in a Table Mapping within the ODataSchemaMap string was not working if the column(s) were not the first column(s) of the table.
- $select query option was not being applied to embedded entities when used in conjunction with $expand.
Even with exhaustive testing, not all issues can be immediately resolved. We are working to fix the following:
- OData - $expand only supports one level deep.
For example, with the entity hierarchy:
| |- OrderItems
The following queries are supported:
However, this query is not supported:
OrderItems is a second level entity with respect to Customers. To query Orders and OrderItems, the query must be rooted at Orders. For example:
- OData – The table names and column names specified in the ODataSchemaMap data source option are case-sensitive. The case of the table and column names must match the case of the tables and column names reported by the data source.
- OData – When using the substring function on properties that map to a CHAR column in the data source, it is data source dependent as to whether the substring function treats the trailing spaces as significant. When going against Oracle, the trailing spaces are preserved. When going against other data sources, the trailing spaces are discarded.
- OData – The $expand clause is not supported with OpenEdge data sources.
- OData – The day scalar function is not working when specified in a $filter clause when querying a DB2 data source.
- OData – The documentation for the current release indicates that OData access is supported for Marketo and Apache Hive data stores. However, DataDirect Cloud does not support OData access for these data stores at this time.
- MySQL – Specifying NULL in a select list when accessing a MySQL data source via the ODBC driver returns the error "NULL SQL type not supported".
- Oracle Service Cloud – The initial connection when the relational map is created can take some time. It is even possible to receive an error "504: Gateway Timeout". When this happens, DataDirect Cloud continues to build the map in the background such that subsequent connection attempts are successful and have full access to the relational map.
- Microsoft Dynamics CRM – The initial on-premise connection when the relational map is created can take some time. It is even possible to receive an error "504: Gateway Timeout". When this happens, DataDirect Cloud continues to build the map in the background such that subsequent connection attempts are successful and have full access to the relational map.
- Reinstalling the On-Premise Connector changes the Connector ID. Any On-Premise data sources defined in DataDirect Cloud must be updated with the new Connector ID.
- On-Premise Connector – Changing the name used to register an On-Premise Connector using an older On-Premise Connector Config Tool may cause the connector to fail to register itself with D2C and cause 504 Gateway timeout errors to be returned. Installing the latest On-Premise connector may resolve this issue.
- On-Premise Connector - It is recommended that Login Timeout not be disabled (set to 0) for a Data Source.
- Using setByte to set parameter values fails when the data source does not support the TINYINT SQL type. Use setShort or setInt to set the parameter value instead of setByte.
- Testing has shown the following two errors from Microsoft Dynamics CRM Online when executing queries against the ImportData and TeamTemplate tables:
- Attribute errortype on Entity ImportData is of type picklist but has Child Attributes Count 0
- Attribute issystem on Entity TeamTemplate is of type bit but has Child Attributes Count 0
Note: We have filed a case with Microsoft and are waiting to hear back about the cause of the issue.
- OpenEdge 10.2b – Setting the MaxPooledStatements data source option in an OpenEdge data store to a value other than zero can cause statement not prepared errors to be returned in some situations.
- Saleforce – When attempting to define a metadata object with multiple fields, the following error may be reported: "Async job could not be executed". This is a known issue with the Salesforce Metadata API. To workaround this issue, log into your organization’s Salesforce Web site and create the metadata object using the Salesforce Web interface.
- See the files d2cjdbcreadme.txt and d2codbcreadme.txt for the latest notes when accessing DataDirect Cloud through the DataDirect Cloud ODBC and JDBC drivers. These files are located in the installation directory for the ODBC and JDBC drivers.
Third Party Acknowledgments
Third party acknowledgments are listed on the following Web page.