March 2015 - teiid-issues - Jboss List Archives

[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 moved MODE-2419 to TEIID-3374: ---------------------------------------- Project: Teiid (was: ModeShape) Key: TEIID-3374 (was: MODE-2419) Workflow: classic default workflow (was: GIT Pull Request workflow ) Component/s: (was: Sequencers) Fix Version/s: (was: 4.3) > 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: Ted Jones > 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)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1942) Add the support for accessing Coherence

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-1942?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-1942: ------------------------------------- Looks like they support JSR-107 https://coherencedownunder.wordpress.com/2014/06/27/coherence-12-1-3-rele... Memcached is another to investigate https://blogs.oracle.com/OracleCoherence/entry/getting_started_with_the_c... http://docs.oracle.com/middleware/1213/coherence/integrate/memcached.htm#... This github I came across https://github.com/coherence-community/ take a look see if any helpful Look here https://java.net/projects/cohinc/ ask question in their forum to see if there is public maven repo or supplied from oracle. We need to make sure there is no compile time dependency when somebody else executes Teiid build, and never include the JAR file. > Add the support for accessing Coherence > --------------------------------------- > > Key: TEIID-1942 > URL: https://issues.jboss.org/browse/TEIID-1942 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.10 > Reporter: Van Halbert > Assignee: Van Halbert > > Add the support for using the Coherence -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1942) Add the support for accessing Coherence

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-1942?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-1942: ------------------------------------ Since there is no open source API, nor any of the coherence code open sourced to be available to perform a maven build, where would you like to put this code such that it can be built (after downloading from oracle)? Or should I create a profile that only builds the connector/translator related code? > Add the support for accessing Coherence > --------------------------------------- > > Key: TEIID-1942 > URL: https://issues.jboss.org/browse/TEIID-1942 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.10 > Reporter: Van Halbert > Assignee: Van Halbert > > Add the support for using the Coherence -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3350) Add system functions for EWKT & KML

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3350?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3350: --------------------------------------- Yes, PostGIS does transform, so we'll add an SRID restriction for now. For GML we can add a srsName, but it needs to be in the format name:id for compatibility with PostGIS - while other systems expect the full URI. > Add system functions for EWKT & KML > ----------------------------------- > > Key: TEIID-3350 > URL: https://issues.jboss.org/browse/TEIID-3350 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Tom Arnold > Assignee: Steven Hawkins > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3350) Add system functions for EWKT & KML

by Tom Arnold (JIRA)

[ https://issues.jboss.org/browse/TEIID-3350?page=com.atlassian.jira.plugin... ] Tom Arnold commented on TEIID-3350: ----------------------------------- Hmmm... I think unlike GML, the SRID for KML is assumed to be 4326 or something similar. {quote} KML geographic 2D coordinate reference system (adapted from EPSG-4326). {quote} https://portal.opengeospatial.org/files/?artifact_id=27810 The PostGIS docs show this working with 4326, and the function explicitly says that it will work only if geometry has SRID so I'm thinking they reproject if it isn't 4326. A little experimentation should be able to confirm if this is the case. http://postgis.org/docs/ST_AsKML.html In the short term we should probably just have an assertion in the code that SRID = 4326 when using ST_AsKML, and a note in the docs explaining why. > Add system functions for EWKT & KML > ----------------------------------- > > Key: TEIID-3350 > URL: https://issues.jboss.org/browse/TEIID-3350 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Tom Arnold > Assignee: Steven Hawkins > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3356) Minor text issues with the sizing tool

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-3356?page=com.atlassian.jira.plugin... ] Kylin Soong closed TEIID-3356. ------------------------------ > Minor text issues with the sizing tool > -------------------------------------- > > Key: TEIID-3356 > URL: https://issues.jboss.org/browse/TEIID-3356 > Project: Teiid > Issue Type: Bug > Components: Sizing Application > Affects Versions: 8.9.1 > Reporter: Thomas Hauser > Assignee: Kylin Soong > Priority: Minor > > There are a few minor issues with some of the text in the tool. > I'll enumerate them below: > CPU Core Estimation: > 2. What is the average row could from each physical source? > The word "could" is probably meant to be "count". Whatever the solution, it's not meant to be "could" :D > 2nd Paragraph of the "Red Hat Enterprise Linux is Recommended" section at the end, 2nd sentence: > Red Hat Ente on other modern processor architectures. > This is a sentence fragment and looks like a cut-off or something. > I didn't see any others, sweet tool! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3132) Upgrade Groovy version

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3132?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3132. --------------------------------- > Upgrade Groovy version > ---------------------- > > Key: TEIID-3132 > URL: https://issues.jboss.org/browse/TEIID-3132 > Project: Teiid > Issue Type: Component Upgrade > Components: AdminApi > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.9 > > > Upgrade groovy for admin shell to a later version. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2938) Provide ability to write command and audit logging to database

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2938?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2938. --------------------------------- > Provide ability to write command and audit logging to database > -------------------------------------------------------------- > > Key: TEIID-2938 > URL: https://issues.jboss.org/browse/TEIID-2938 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Ramesh Reddy > Fix For: 8.8, 8.7.1 > > > Provide ability for command logging and audit logging to write to the database. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3191) Teiid global temporary table error with first invocation

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3191?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3191. --------------------------------- > Teiid global temporary table error with first invocation > -------------------------------------------------------- > > Key: TEIID-3191 > URL: https://issues.jboss.org/browse/TEIID-3191 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Reporter: Jan Stastny > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.9 > > Attachments: nativeSQL.vdb > > > When working with global temporary table in teiid an error occurs while accessing the temp table for the first time. > Error: org.teiid.metadata.Column cannot be cast to org.teiid.query.metadata.TempMetadataID > All the following invocations of the global temporary table run fine. > Global temporary table is defined through Teiid designer within my vdb. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3057) Kerberos ODBC connection on Teiid 8.8.0

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3057?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3057. --------------------------------- > Kerberos ODBC connection on Teiid 8.8.0 > --------------------------------------- > > Key: TEIID-3057 > URL: https://issues.jboss.org/browse/TEIID-3057 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 8.8 > Environment: Teiid 8.8.0 > EAP 6.1.1 > Reporter: Cristiano Nicolai > Assignee: Ramesh Reddy > Priority: Blocker > Labels: Alpha1 > Fix For: 8.7.1, 8.9 > > > After upgrading from version 8.7.0.Final to version 8.8.0.Final connections via ODBC using Kerberos/GSS stopped working. > When I try to connect with the new version, on the server I get the following error: > > 12:24:31,755 ERROR [org.teiid.ODBC] (New I/O worker #2) TEIID40015 Unexpected error occurred: java.lang.NullPointerException > at java.util.Hashtable.put(Hashtable.java:514) [rt.jar:1.7.0_55] > at org.teiid.odbc.ODBCServerRemoteImpl.logon(ODBCServerRemoteImpl.java:244) [teiid-runtime-8.8.0.Final.jar:8.8.0.Final] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_55] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_55] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_55] > at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_55] > at org.teiid.transport.ODBCClientInstance.processMessage(ODBCClientInstance.java:127) [teiid-runtime-8.8.0.Final.jar:8.8.0.Final] > at org.teiid.transport.ODBCClientInstance.receivedMessage(ODBCClientInstance.java:116) [teiid-runtime-8.8.0.Final.jar:8.8.0.Final] > at org.teiid.transport.SSLAwareChannelHandler.messageReceived(SSLAwareChannelHandler.java:211) [teiid-runtime-8.8.0.Final.jar:8.8.0.Final] > > From the client I get the following message: psql: duplicate GSS authentication request -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2015