June 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3052) Error on using MAKEDEP hint within union

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3052?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3052. --------------------------------- > Error on using MAKEDEP hint within union > ---------------------------------------- > > Key: TEIID-3052 > URL: https://issues.jboss.org/browse/TEIID-3052 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7 > Reporter: Mark Addleman > Assignee: Steven Hawkins > Fix For: 8.9 > > > The following anon proc block fails with error TEIID30226 Remote org.teiid.api.exception.query.QueryProcessingException: TEIID30226 Temporary table "table_spaces_v6" does not exist > BEGIN > create local temporary table ssid_version (sysplex varchar, lpar varchar, ssid varchar, version varchar); > insert into ssid_version(sysplex, lpar, ssid, version) values ('plex1', 'ca11', 'd91a', 'v5'); > insert into ssid_version(sysplex, lpar, ssid, version) values ('plex1', 'ca11', 'd91b', 'v6'); > > > create local temporary table table_spaces_v5 (sysplex varchar, lpar varchar, ssid varchar, table_space_id varchar); > insert into table_spaces_v5 (sysplex, lpar, ssid, table_space_id) values ('plex1', 'ca11', 'd91a', 'ts1'); > > > create local temporary table table_spaces_v6 (sysplex varchar, lpar varchar, ssid varchar, table_space_id varchar); > insert into table_spaces_v6 (sysplex, lpar, ssid, table_space_id) values ('plex1', 'ca11', 'd91b', 'ts2'); > > > select table_space_id from > ( > select * from (select v.sysplex, v.lpar, v.ssid, t.table_space_id from ssid_version v join table_spaces_v5 t on t.sysplex=v.sysplex and t.lpar=v.lpar and t.ssid=v.ssid option makedep table_spaces_v5) t > union all > select * from (select v.sysplex, v.lpar, v.ssid, t.table_space_id from ssid_version v join table_spaces_v6 t on t.sysplex=v.sysplex and t.lpar=v.lpar and t.ssid=v.ssid option makedep table_spaces_v6) t > ) t > where ssid='d91a'; > END > It also fails when the /*+ MAKEDEP */ form is used instead of "option makedep" > I don't believe there should be any failure -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3264) Database Logging: Problems with Sybase

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3264?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3264. --------------------------------- > Database Logging: Problems with Sybase > -------------------------------------- > > Key: TEIID-3264 > URL: https://issues.jboss.org/browse/TEIID-3264 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1 > Reporter: Jan Stastny > Assignee: Steven Hawkins > Attachments: server.log > > > When using Sybase DB for Database Logging in Teiid, an error is thrown upon each command, which should be logged. > The root cause says java.sql.SQLException: JZ006: Caught IOException: java.io.IOException: JZ0SL: Unsupported SQL type 2004. > But see the server.log for further info -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3110) name in source should not be omitted in ddl

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3110?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3110. --------------------------------- > name in source should not be omitted in ddl > ------------------------------------------- > > Key: TEIID-3110 > URL: https://issues.jboss.org/browse/TEIID-3110 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.9 > > > When creating the ddl string we'll omit the name in source if it matches the table name. While this is valid for several translators (jdbc, object, mongodb, and others), it is not valid for all - salesforce, ldap, odata, and others. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2811) Accumulo RowID VARBINARY conversion

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2811?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2811. --------------------------------- > Accumulo RowID VARBINARY conversion > ----------------------------------- > > Key: TEIID-2811 > URL: https://issues.jboss.org/browse/TEIID-2811 > Project: Teiid > Issue Type: Bug > Components: Connector API > Affects Versions: 8.7 > Reporter: devin pinkston > Assignee: Ramesh Reddy > Labels: Accumulo, Alpha2 > Fix For: 8.7 > > > Converting ROWID from byte to VARBINARY causes a metadata error. Switch to String to accomodate for handling other characters in the RowID. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3497) INSERT statement with Object value fails - Unsupported Types value: 2, 000 [postgres]

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3497?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3497. --------------------------------- > INSERT statement with Object value fails - Unsupported Types value: 2,000 [postgres] > ------------------------------------------------------------------------------------ > > Key: TEIID-3497 > URL: https://issues.jboss.org/browse/TEIID-3497 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7.1.6_2 > Environment: OS: Fedora 20 > arch: x86_64 > java: oracle 1.8 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > The INSERT query with Object value fails with the root exception: > Caused by: org.postgresql.util.PSQLException: Unsupported Types value: 2,000 > at org.postgresql.jdbc2.AbstractJdbc2Statement.setObject(AbstractJdbc2Statement.java:1858) > ... > Insert query [1], source specific command [2], postgres table [3], teiid vdb[4]. > [1] INSERT INTO smalla VALUES (55,'0',NULL,'-24',-24.00,-24,-24.0,-128,{d'2000-01-01'},{t'00:00:00'},{ts'2000-01-01 00:00:00.0'},0,'1',-32768,-24,-24,'-24') > [2] INSERT INTO smalla (IntKey, StringKey, IntNum, StringNum, FloatNum, LongNum, DoubleNum, ByteNum, DateValue, TimeValue, TimestampValue, BooleanValue, CharValue, ShortValue, BigIntegerValue, BigDecimalValue, ObjectValue) VALUES (55, '0', NULL, '-24', -24.0, -24, -24.0, -128, DATE '2000-01-01', TIME '00:00:00', TIMESTAMP '2000-01-01 00:00:00.0', FALSE, '1', -32768, -24, -24, ?) > [3] > create table SmallA (StringNum varchar(15), > IntNum integer, > DoubleNum double precision, > StringKey varchar(15), > BigDecimalValue numeric(15,5), > IntKey integer, > ByteNum smallint, > DateValue date, > TimeValue time, > TimestampValue timestamp, > BooleanValue boolean, > CharValue char(1), > ShortValue smallint, > FloatNum real, > LongNum bigint, > BigIntegerValue numeric(15,0), > ObjectValue text); > [4] > <vdb name="vdb-tmp" version="1"> > <model name="Source"> > <source name="local" translator-name="postgresql" connection-jndi-name="java:/localPostgreSQL"/> > <metadata type="DDL"><![CDATA[ > CREATE FOREIGN TABLE smalla(IntKey integer, StringKey string, IntNum integer, StringNum string, FloatNum float, LongNum long, DoubleNum double, ByteNum byte, DateValue date, TimeValue time, TimestampValue timestamp, BooleanValue boolean, CharValue char, ShortValue short, BigIntegerValue biginteger, BigDecimalValue bigdecimal, ObjectValue object) OPTIONS (UPDATABLE 'TRUE'); > ]]> > </metadata> > </model> > </vdb> -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3230) Sybase translator changes

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3230?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3230. --------------------------------- > Sybase translator changes > ------------------------- > > Key: TEIID-3230 > URL: https://issues.jboss.org/browse/TEIID-3230 > Project: Teiid > Issue Type: Quality Risk > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.10 > > > The logic for supporting date formats is in the code, but not exposed via a capability. Also the type mapping in the translator should account for when time is supported as a type. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3448) User query should be terminated when TEIID30001

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3448?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-3448. --------------------------------- > User query should be terminated when TEIID30001 > ----------------------------------------------- > > Key: TEIID-3448 > URL: https://issues.jboss.org/browse/TEIID-3448 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Environment: JDV6.0, 6.1 > Reporter: Hisanobu Okuda > Assignee: Steven Hawkins > Attachments: buffertest.vdb, create_db.sql, jdv_client.zip, standalone.xml, testdata_a.csv.gz, testdata_b.csv.gz > > > Even if I get the following error when I access a mat view for the first time just after starting JDV:- > {code} > 12:45:46,404 ERROR [org.teiid.BUFFER_MGR] (BufferManager Cleaner) TEIID30001 Max block number exceeded by 1 0. Increase the maxStorageObjectSize to support larger storage objects. Alternatively you could make the processor batch size smaller. > {code} > the result for the query returns sucessfully. > However, the 2nd access to the mat view gives an error at client side:- > {code} > org.teiid.jdbc.TeiidSQLException: Batch not found in storage 0 > at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:135) > at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:71) > at org.teiid.jdbc.StatementImpl.postReceiveResults(StatementImpl.java:668) > {code} > And server side:- > {code} > 12:52:50,961 ERROR [org.teiid.PROCESSOR] (Worker3_QueryProcessorQueue6) TEIID30019 Unexpected exception for request LdGNTpFDRwjr.0: java.lang.AssertionError: Batch not found in storage 0 > at org.teiid.common.buffer.impl.BufferManagerImpl$BatchManagerImpl.getBatch(BufferManagerImpl.java:306) [teiid-engine-8.7.1.redhat-8.jar:8.7.1.redhat-8] > at org.teiid.common.buffer.SPage.getValues(SPage.java:237) [teiid-engine-8.7.1.redhat-8.jar:8.7.1.redhat-8] > at org.teiid.common.buffer.TupleBrowser.nextTuple(TupleBrowser.java:223) [teiid-engine-8.7.1.redhat-8.jar:8.7.1.redhat-8] > at org.teiid.query.tempdata.TempTable$QueryTupleSource.nextTuple(TempTable.java:192) [teiid-engine-8.7.1.redhat-8.jar:8.7.1.redhat-8] > at org.teiid.query.tempdata.TempTableDataManager$ProxyTupleSource.nextTuple(TempTableDataManager.java:110) [teiid-engine-8.7.1.redhat-8.jar:8.7.1.redhat-8] > at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:369) [teiid-engine-8.7.1.redhat-8.jar:8.7.1.redhat-8] > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.7.1.redhat-8.jar:8.7.1.redhat-8] > at org.teiid.query.processor.relational.LimitNode.nextBatchDirect(LimitNode.java:102) [teiid-engine-8.7.1.redhat-8.jar:8.7.1.redhat-8] > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.7.1.redhat-8.jar:8.7.1.redhat-8] > at org.teiid.query.processor.BatchCollector$BatchProducerTupleSource.nextTuple(BatchCollector.java:89) [teiid-engine-8.7.1.redhat-8.jar:8.7.1.redhat-8] > at org.teiid.query.processor.relational.GroupingNode.groupPhase(GroupingNode.java:405) [teiid-engine-8.7.1.redhat-8.jar:8.7.1.redhat-8] > at org.teiid.query.processor.relational.GroupingNode.nextBatchDirect(GroupingNode.java:336) [teiid-engine-8.7.1.redhat-8.jar:8.7.1.redhat-8] > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.7.1.redhat-8.jar:8.7.1.redhat-8] > at org.teiid.query.processor.relational.ProjectNode.nextBatchDirect(ProjectNode.java:146) [teiid-engine-8.7.1.redhat-8.jar:8.7.1.redhat-8] > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:278) [teiid-engine-8.7.1.redhat-8.jar:8.7.1.redhat-8] > at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:136) [teiid-engine-8.7.1.redhat-8.jar:8.7.1.redhat-8] > at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:151) [teiid-engine-8.7.1.redhat-8.jar:8.7.1.redhat-8] > at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) [teiid-engine-8.7.1.redhat-8.jar:8.7.1.redhat-8] > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:159) [teiid-engine-8.7.1.redhat-8.jar:8.7.1.redhat-8] > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:141) [teiid-engine-8.7.1.redhat-8.jar:8.7.1.redhat-8] > at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:444) [teiid-engine-8.7.1.redhat-8.jar:8.7.1.redhat-8] > at org.teiid.dqp.internal.process.RequestWorkItem.process(RequestWorkItem.java:326) [teiid-engine-8.7.1.redhat-8.jar:8.7.1.redhat-8] > at org.teiid.dqp.internal.process.AbstractWorkItem.run(AbstractWorkItem.java:51) [teiid-engine-8.7.1.redhat-8.jar:8.7.1.redhat-8] > ... > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2948) Implement Access Controls on management operations in Teiid

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2948?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2948: ---------------------------------- Fix Version/s: 8.9 > Implement Access Controls on management operations in Teiid > ----------------------------------------------------------- > > Key: TEIID-2948 > URL: https://issues.jboss.org/browse/TEIID-2948 > Project: Teiid > Issue Type: Feature Request > Components: Server > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.7.1, 8.9 > > > EAP 6.2 and above provides facilities to implement access controls on the management operations. Teiid should implement them on the management operations so that they can be controlled by access level of the user. > Unfortunately this is not in EAP 6.1.Alpha, so it becomes hard to pull the changes upstream into 8.8 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3410) OData object URI does not resolve to a usable URL.

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3410?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3410: ------------------------------- Fix Version/s: 8.7.1.6_2 > OData object URI does not resolve to a usable URL. > -------------------------------------------------- > > Key: TEIID-3410 > URL: https://issues.jboss.org/browse/TEIID-3410 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 8.7.1.6_2, 8.11 > > > OData object URI does not resolve to a usable URL. When accessing a VDB via odata with a browser either via JSON or XML the uri listed in the metadata is not valid, it doesn't have the FQN of the table, only the type shows FQN: > "__metadata" : { > "uri" : "http://localhost:8080/odata/ODataRHQ/rhq_agent(10001)", > "type" : "RHQ32.rhq_agent" -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3358) Issues with entity set names

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3358?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3358. ----------------------------------- Resolution: Done Leaving the original issue as resolved. See TEIID-3410 > Issues with entity set names > ---------------------------- > > Key: TEIID-3358 > URL: https://issues.jboss.org/browse/TEIID-3358 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Labels: Alpha1 > Fix For: 8.7.1.6_2, 8.11, 8.7.3 > > > The entity set name used for sql generation should be the fully qualified name. If there is for example two table with the same names in schemas visible to odata, but one of the tables does not have a key, then an ambiguous name exception will be thrown if an odata url is used with only the base table name. > It also appears that the URI link in the results metadata uses the non-qualified table name, which will have issues in the scenario above. > We may also need to document or add an additional check for ambiguity as the OData4j findEdmEntitySet logic will return the first matching entity, which is generally against our approach to resolving. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2015