[JBoss JIRA] (TEIID-3375) Support Kerberos handshake for mutual auth
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3375?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-3375.
---------------------------------
Resolution: Done
Corrected as mentioned as in the forum thread
> Support Kerberos handshake for mutual auth
> ------------------------------------------
>
> Key: TEIID-3375
> URL: https://issues.jboss.org/browse/TEIID-3375
> Project: Teiid
> Issue Type: Feature Request
> Components: Embedded, ODBC
> Affects Versions: 8.9.1
> Environment: Postgres JDBC 9.4-1201 client on Windows 7, Teiid server on either Windows 7 or RHEL Linux 2.6 (behaved same on both platforms).
> Reporter: Ben Kibler
> Assignee: Ramesh Reddy
> Fix For: 8.11
>
>
> When using Teiid Embedded with Kerberos, the GSS handshake with the Postgres JDBC client is failing while trying to establish mutual authentication.
> The ODBCRemoteServerImpl.login() method should send both an AuthenticationGSSContinue and AuthenticationOk message when the client is requesting mutual authentication.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (TEIID-3372) Support multiple metadata tags
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3372?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3372:
---------------------------------------
This is more complicated than it should be. The choice to make the metadata type/text as direct children of the model means that we don't have a good way of associating the metadata as each metadata repository is called to load. I think we'll have to redo either the load call or associate the text with the MetadataRepository as we chain things together.
> Support multiple metadata tags
> ------------------------------
>
> Key: TEIID-3372
> URL: https://issues.jboss.org/browse/TEIID-3372
> Project: Teiid
> Issue Type: Feature Request
> Components: Server
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.11
>
>
> To allow for a more flexible configuration, we should support multiple metadata tags under a model, rather than relying on comma separated values.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (TEIID-3375) Support Kerberos handshake for mutual auth
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3375?page=com.atlassian.jira.plugin... ]
Ramesh Reddy updated TEIID-3375:
--------------------------------
Fix Version/s: 8.11
> Support Kerberos handshake for mutual auth
> ------------------------------------------
>
> Key: TEIID-3375
> URL: https://issues.jboss.org/browse/TEIID-3375
> Project: Teiid
> Issue Type: Feature Request
> Components: Embedded, ODBC
> Affects Versions: 8.9.1
> Environment: Postgres JDBC 9.4-1201 client on Windows 7, Teiid server on either Windows 7 or RHEL Linux 2.6 (behaved same on both platforms).
> Reporter: Ben Kibler
> Assignee: Ramesh Reddy
> Fix For: 8.11
>
>
> When using Teiid Embedded with Kerberos, the GSS handshake with the Postgres JDBC client is failing while trying to establish mutual authentication.
> The ODBCRemoteServerImpl.login() method should send both an AuthenticationGSSContinue and AuthenticationOk message when the client is requesting mutual authentication.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (TEIID-3375) Support Kerberos handshake for mutual auth
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3375?page=com.atlassian.jira.plugin... ]
Ramesh Reddy reassigned TEIID-3375:
-----------------------------------
Assignee: Ramesh Reddy (was: Steven Hawkins)
> Support Kerberos handshake for mutual auth
> ------------------------------------------
>
> Key: TEIID-3375
> URL: https://issues.jboss.org/browse/TEIID-3375
> Project: Teiid
> Issue Type: Feature Request
> Components: Embedded, ODBC
> Affects Versions: 8.9.1
> Environment: Postgres JDBC 9.4-1201 client on Windows 7, Teiid server on either Windows 7 or RHEL Linux 2.6 (behaved same on both platforms).
> Reporter: Ben Kibler
> Assignee: Ramesh Reddy
>
> When using Teiid Embedded with Kerberos, the GSS handshake with the Postgres JDBC client is failing while trying to establish mutual authentication.
> The ODBCRemoteServerImpl.login() method should send both an AuthenticationGSSContinue and AuthenticationOk message when the client is requesting mutual authentication.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (TEIID-3374) Teiid DDL Importer Processor Error: "Unparsable table body constraint" when importing from SAP HANA
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3374?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3374:
---------------------------------------
If the Designer/Modeshape parser requires index to be handled as a reserved word, then we could look at making a change. Otherwise our parser uses a lookhead in this situation, thus there's no issue from a Teiid perspective.
> 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)
11 years, 1 month
[JBoss JIRA] (TEIID-3375) Support Kerberos handshake for mutual auth
by Ben Kibler (JIRA)
Ben Kibler created TEIID-3375:
---------------------------------
Summary: Support Kerberos handshake for mutual auth
Key: TEIID-3375
URL: https://issues.jboss.org/browse/TEIID-3375
Project: Teiid
Issue Type: Feature Request
Components: Embedded, ODBC
Affects Versions: 8.9.1
Environment: Postgres JDBC 9.4-1201 client on Windows 7, Teiid server on either Windows 7 or RHEL Linux 2.6 (behaved same on both platforms).
Reporter: Ben Kibler
Assignee: Steven Hawkins
When using Teiid Embedded with Kerberos, the GSS handshake with the Postgres JDBC client is failing while trying to establish mutual authentication.
The ODBCRemoteServerImpl.login() method should send both an AuthenticationGSSContinue and AuthenticationOk message when the client is requesting mutual authentication.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 1 month
[JBoss JIRA] (TEIID-3374) Teiid DDL Importer Processor Error: "Unparsable table body constraint" when importing from SAP HANA
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3374?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3374.
-----------------------------------
Resolution: Rejected
There is no Teiid issue here. INDEX is a non reserved word, and does not have to appear in quotes.
> 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)
11 years, 1 month
[JBoss JIRA] (TEIID-3374) Teiid DDL Importer Processor Error: "Unparsable table body constraint" when importing from SAP HANA
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3374?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-3374:
-------------------------------------------
Bugzilla Update: (was: Perform)
Bugzilla References: (was: https://bugzilla.redhat.com/show_bug.cgi?id=1196803)
> 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)
11 years, 1 month
[JBoss JIRA] (TEIID-3374) Teiid DDL Importer Processor Error: "Unparsable table body constraint" when importing from SAP HANA
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIID-3374?page=com.atlassian.jira.plugin... ]
Ted Jones reassigned TEIID-3374:
--------------------------------
Assignee: Steven Hawkins (was: Ted Jones)
> 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)
11 years, 1 month