December 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3818) Issues with ODBC metadata foreign key queries

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3818?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3818: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1288199 Bugzilla Update: Perform > Issues with ODBC metadata foreign key queries > --------------------------------------------- > > Key: TEIID-3818 > URL: https://issues.jboss.org/browse/TEIID-3818 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 8.4 > Environment: Most likely not OS / hardware dependent. > Reporter: Dave Nicodemus > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.12.2, 8.13 > > > The current foreign key handling should return imported key, but instead returns exported keys. > When exported keys are asked for an exception is thrown: > While attempting to use Client Microsoft's Power BI desktop using ODBC connecting to Teiid Embedded server using VDB with metadata tags. > Received the following errors : > {code} > [36.864]ERROR from backend during send_query: 'SERROR' > [36.865]ERROR from backend during send_query: 'C50000' > [36.869]ERROR from backend during send_query: 'MTEIID31100 Parsing error: Encountered "('ScottTestMart' AS [*]name[*]) as" at line 1, column 33. > Was expecting: "string" | "varbinary" | "varchar" | "boolean" | "byte" | "tinyint" | "short" | "smallint" | "char" | "integer" ...' > [36.875]ERROR from backend during send_query: 'Dorg.teiid.jdbc.TeiidSQLException: TEIID31100 Parsing error: Encountered "('ScottTestMart' AS [*]name[*]) as" at line 1, column 33. > Was expecting: "string" | "varbinary" | "varchar" | "boolean" | "byte" | "tinyint" | "short" | "smallint" | "char" | "integer" ...' > [37.397]STATEMENT ERROR: func=PGAPI_ForeignKeys, desc='', errnum=1, errmsg='PGAPI_ForeignKeys query error' > {code} > Due to this query being generated by the BI tool : > {code} > 'select 'ScottTestMart'::name as PKTABLE_CAT, > n2.nspname as PKTABLE_SCHEM, > c2.relname as PKTABLE_NAME, > a2.attname as PKCOLUMN_NAME, > 'ScottTestMart'::name as FKTABLE_CAT, > n1.nspname as FKTABLE_SCHEM, > c1.relname as FKTABLE_NAME, > a1.attname as FKCOLUMN_NAME, > i::int2 as KEY_SEQ, > case ref.confupdtype > when 'c' then 0::int2 > when 'n' then 2::int2 > when 'd' then 4::int2 > when 'r' then 1::int2 > else 3::int2 > end as UPDATE_RULE, > case ref.confdeltype > when 'c' then 0::int2 > when 'n' then 2::int2 > when 'd' then 4::int2 > when 'r' then 1::int2 > else 3::int2 > end as DELETE_RULE, > ref.conname as FK_NAME, > cn.conname as PK_NAME, > case > when ref.condeferrable then > case > when ref.condeferred then 5::int2 > else 6::int2 > end > else 7::int2 > end as DEFERRABLITY > from > ((((((( (select cn.oid, conrelid, conkey, confrelid, confkey, > generate_series(array_lower(conkey, 1), array_upper(conkey, 1)) as i, > confupdtype, confdeltype, conname, > condeferrable, condeferred > from pg_catalog.pg_constraint cn, > pg_catalog.pg_class c, > pg_catalog.pg_namespace n > where contype = 'f' > and confrelid = c.oid > and relname = 'Categories' > and n.oid = c.relnamespace > and n.nspname = 'ScottTestMart' > ) ref > inner join pg_catalog.pg_class c1 > on c1.oid = ref.conrelid) > inner join pg_catalog.pg_namespace n1 > on n1.oid = c1.relnamespace) > inner join pg_catalog.pg_attribute a1 > on a1.attrelid = c1.oid > and a1.attnum = conkey[i]) > inner join pg_catalog.pg_class c2 > on c2.oid = ref.confrelid) > inner join pg_catalog.pg_namespace n2 > on n2.oid = c2.relnamespace) > inner join pg_catalog.pg_attribute a2 > on a2.attrelid = c2.oid > and a2.attnum = confkey[i]) > left outer join pg_catalog.pg_constraint cn > on cn.conrelid = ref.confrelid > and cn.contype = 'p') > order by ref.oid, ref.i' > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3760) endswith defined with wrong return type

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3760?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3760: --------------------------------- Fix Version/s: 8.7.2.6_2 8.7.6 > endswith defined with wrong return type > --------------------------------------- > > Key: TEIID-3760 > URL: https://issues.jboss.org/browse/TEIID-3760 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.3 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.2.6_2, 8.12.1, 8.13, 8.7.6 > > > The ends with function is marked as returning string instead of boolean. Also there is inconsistent accounting for parameter ordering in the odata logic. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3436) OData V2: Add array type support to the odata translator

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3436?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3436: --------------------------------- Fix Version/s: 8.7.2.6_2 8.7.6 > OData V2: Add array type support to the odata translator > -------------------------------------------------------- > > Key: TEIID-3436 > URL: https://issues.jboss.org/browse/TEIID-3436 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 8.7.2.6_2, 8.12.1, 8.13, 8.7.6 > > > Arrays of basic types in odata responses should be convertible into a runtime array type. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3757) OData V2: $top doesn't work with virtual procedures

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3757?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3757: --------------------------------- Fix Version/s: 8.7.2.6_2 8.7.6 > OData V2: $top doesn't work with virtual procedures > --------------------------------------------------- > > Key: TEIID-3757 > URL: https://issues.jboss.org/browse/TEIID-3757 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7.1.6_2 > Reporter: Debbie Steigner > Assignee: Ramesh Reddy > Fix For: 8.7.2.6_2, 8.12.1, 8.7.6 > > Attachments: odat.vdb > > > When using OData to query a virtual procedure with a input parameter $top gets ignored: > http://127.0.0.1:8080/odata/odat/proctest?string_in='30'&$top=5 > Returns all the rows. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3757) OData V2: $top doesn't work with virtual procedures

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3757?page=com.atlassian.jira.plugin... ] Johnathon Lee closed TEIID-3757. -------------------------------- Resolution: Done > OData V2: $top doesn't work with virtual procedures > --------------------------------------------------- > > Key: TEIID-3757 > URL: https://issues.jboss.org/browse/TEIID-3757 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7.1.6_2 > Reporter: Debbie Steigner > Assignee: Ramesh Reddy > Fix For: 8.7.2.6_2, 8.7.6, 8.12.1 > > Attachments: odat.vdb > > > When using OData to query a virtual procedure with a input parameter $top gets ignored: > http://127.0.0.1:8080/odata/odat/proctest?string_in='30'&$top=5 > Returns all the rows. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3757) OData V2: $top doesn't work with virtual procedures

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3757?page=com.atlassian.jira.plugin... ] Johnathon Lee reopened TEIID-3757: ---------------------------------- > OData V2: $top doesn't work with virtual procedures > --------------------------------------------------- > > Key: TEIID-3757 > URL: https://issues.jboss.org/browse/TEIID-3757 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7.1.6_2 > Reporter: Debbie Steigner > Assignee: Ramesh Reddy > Fix For: 8.12.1 > > Attachments: odat.vdb > > > When using OData to query a virtual procedure with a input parameter $top gets ignored: > http://127.0.0.1:8080/odata/odat/proctest?string_in='30'&$top=5 > Returns all the rows. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3375) Support Kerberos handshake for mutual auth

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3375?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3375: --------------------------------- Fix Version/s: 8.7.6 > 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, 8.7.2.6_2, 8.7.6 > > > 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.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3666) VDB can deploy before datasource is bound

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3666?page=com.atlassian.jira.plugin... ] Johnathon Lee reopened TEIID-3666: ---------------------------------- > VDB can deploy before datasource is bound > ----------------------------------------- > > Key: TEIID-3666 > URL: https://issues.jboss.org/browse/TEIID-3666 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.3 > Environment: JDBC driver for datasource is deployed in deployments/ directory of standalone instance > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 8.12, 8.11.3, 8.7.2.6_2 > > > A VDB can be deployed before the datasources it depends on are fully deployed and bound, resulting in the VDB never being marked as ACTIVE. This appears to be exclusive to environments where the JDBC driver for the datasource is deployed through use of the standalone deployments/ directory. If the driver is deployed as a module, then the risk of the issue is lowered or eliminated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3666) VDB can deploy before datasource is bound

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3666?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-3666: --------------------------------- Fix Version/s: 8.7.5 > VDB can deploy before datasource is bound > ----------------------------------------- > > Key: TEIID-3666 > URL: https://issues.jboss.org/browse/TEIID-3666 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.3 > Environment: JDBC driver for datasource is deployed in deployments/ directory of standalone instance > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 8.12, 8.11.3, 8.7.5, 8.7.2.6_2 > > > A VDB can be deployed before the datasources it depends on are fully deployed and bound, resulting in the VDB never being marked as ACTIVE. This appears to be exclusive to environments where the JDBC driver for the datasource is deployed through use of the standalone deployments/ directory. If the driver is deployed as a module, then the risk of the issue is lowered or eliminated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3666) VDB can deploy before datasource is bound

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3666?page=com.atlassian.jira.plugin... ] Johnathon Lee closed TEIID-3666. -------------------------------- Resolution: Done > VDB can deploy before datasource is bound > ----------------------------------------- > > Key: TEIID-3666 > URL: https://issues.jboss.org/browse/TEIID-3666 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.3 > Environment: JDBC driver for datasource is deployed in deployments/ directory of standalone instance > Reporter: Marc Shirley > Assignee: Steven Hawkins > Fix For: 8.7.2.6_2, 8.7.5, 8.11.3, 8.12 > > > A VDB can be deployed before the datasources it depends on are fully deployed and bound, resulting in the VDB never being marked as ACTIVE. This appears to be exclusive to environments where the JDBC driver for the datasource is deployed through use of the standalone deployments/ directory. If the driver is deployed as a module, then the risk of the issue is lowered or eliminated. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2015