[teiid-issues] [JBoss JIRA] (TEIID-3374) Teiid DDL Importer Processor Error: "Unparsable table body constraint" when importing from SAP HANA
Ted Jones (JIRA)
issues at jboss.org
Fri Mar 6 10:38:49 EST 2015
[ https://issues.jboss.org/browse/TEIID-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13047067#comment-13047067 ]
Ted Jones commented on TEIID-3374:
----------------------------------
Moved to Teiid to address DDL generation issues.
> Teiid DDL Importer Processor Error: "Unparsable table body constraint" when importing from SAP HANA
> ---------------------------------------------------------------------------------------------------
>
> Key: TEIID-3374
> URL: https://issues.jboss.org/browse/TEIID-3374
> Project: Teiid
> Issue Type: Bug
> Reporter: Ted Jones
> Assignee: Steven Hawkins
> Attachments: exportedDDL.ddl
>
>
> When importing from an SAP HANA DB using the Teiid Connection importer in Designer, I get an "Unparsable table body constraint error". The highlighted row is:
> {code:sql}
> INDEX string(1024) NOT NULL OPTIONS (NAMEINSOURCE '"INDEX"', NATIVE_TYPE 'NVARCHAR'),
> {code}
> for the CREATE statement:
> {code:sql}
> CREATE FOREIGN TABLE "_SYS_STATISTICS.GLOBAL_COLUMN_TABLES_SIZE" (
> SNAPSHOT_ID timestamp NOT NULL OPTIONS (NAMEINSOURCE '"SNAPSHOT_ID"', CHAR_OCTET_LENGTH 16, NATIVE_TYPE 'TIMESTAMP'),
> INDEX string(1024) NOT NULL OPTIONS (NAMEINSOURCE '"INDEX"', NATIVE_TYPE 'NVARCHAR'),
> SERVER_TIMESTAMP timestamp OPTIONS (NAMEINSOURCE '"SERVER_TIMESTAMP"', CHAR_OCTET_LENGTH 16, NATIVE_TYPE 'TIMESTAMP'),
> DATA_SEQ integer OPTIONS (NAMEINSOURCE '"DATA_SEQ"', CHAR_OCTET_LENGTH 4, NATIVE_TYPE 'INTEGER'),
> ESTIMATED_MAX_MEMORY_SIZE_IN_TOTAL long OPTIONS (NAMEINSOURCE '"ESTIMATED_MAX_MEMORY_SIZE_IN_TOTAL"', CHAR_OCTET_LENGTH 20, NATIVE_TYPE 'BIGINT'),
> LAST_COMPRESSED_RECORD_COUNT long OPTIONS (NAMEINSOURCE '"LAST_COMPRESSED_RECORD_COUNT"', CHAR_OCTET_LENGTH 20, NATIVE_TYPE 'BIGINT'),
> MEMORY_SIZE_IN_DELTA long OPTIONS (NAMEINSOURCE '"MEMORY_SIZE_IN_DELTA"', CHAR_OCTET_LENGTH 20, NATIVE_TYPE 'BIGINT'),
> MEMORY_SIZE_IN_HISTORY_DELTA long OPTIONS (NAMEINSOURCE '"MEMORY_SIZE_IN_HISTORY_DELTA"', CHAR_OCTET_LENGTH 20, NATIVE_TYPE 'BIGINT'),
> MEMORY_SIZE_IN_HISTORY_MAIN long OPTIONS (NAMEINSOURCE '"MEMORY_SIZE_IN_HISTORY_MAIN"', CHAR_OCTET_LENGTH 20, NATIVE_TYPE 'BIGINT'),
> MEMORY_SIZE_IN_MAIN long OPTIONS (NAMEINSOURCE '"MEMORY_SIZE_IN_MAIN"', CHAR_OCTET_LENGTH 20, NATIVE_TYPE 'BIGINT'),
> MEMORY_SIZE_IN_TOTAL long OPTIONS (NAMEINSOURCE '"MEMORY_SIZE_IN_TOTAL"', CHAR_OCTET_LENGTH 20, NATIVE_TYPE 'BIGINT'),
> PART_COUNT long OPTIONS (NAMEINSOURCE '"PART_COUNT"', CHAR_OCTET_LENGTH 20, NATIVE_TYPE 'BIGINT'),
> RAW_RECORD_COUNT_IN_DELTA long OPTIONS (NAMEINSOURCE '"RAW_RECORD_COUNT_IN_DELTA"', CHAR_OCTET_LENGTH 20, NATIVE_TYPE 'BIGINT'),
> RAW_RECORD_COUNT_IN_HISTORY_DELTA long OPTIONS (NAMEINSOURCE '"RAW_RECORD_COUNT_IN_HISTORY_DELTA"', CHAR_OCTET_LENGTH 20, NATIVE_TYPE 'BIGINT'),
> RAW_RECORD_COUNT_IN_HISTORY_MAIN long OPTIONS (NAMEINSOURCE '"RAW_RECORD_COUNT_IN_HISTORY_MAIN"', CHAR_OCTET_LENGTH 20, NATIVE_TYPE 'BIGINT'),
> RAW_RECORD_COUNT_IN_MAIN long OPTIONS (NAMEINSOURCE '"RAW_RECORD_COUNT_IN_MAIN"', CHAR_OCTET_LENGTH 20, NATIVE_TYPE 'BIGINT'),
> RECORD_COUNT long OPTIONS (NAMEINSOURCE '"RECORD_COUNT"', CHAR_OCTET_LENGTH 20, NATIVE_TYPE 'BIGINT'),
> SCHEMA_NAME string(256) OPTIONS (NAMEINSOURCE '"SCHEMA_NAME"', NATIVE_TYPE 'NVARCHAR'),
> TABLE_COLUMN_COUNT long OPTIONS (NAMEINSOURCE '"TABLE_COLUMN_COUNT"', CHAR_OCTET_LENGTH 20, NATIVE_TYPE 'BIGINT'),
> TABLE_NAME string(256) OPTIONS (NAMEINSOURCE '"TABLE_NAME"', NATIVE_TYPE 'NVARCHAR')
> ) OPTIONS (NAMEINSOURCE '"_SYS_STATISTICS"."GLOBAL_COLUMN_TABLES_SIZE"', UPDATABLE TRUE);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
More information about the teiid-issues
mailing list