August 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4365) account for lack of collection types in salesforce

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4365?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4365. ----------------------------------- Resolution: Duplicate Issue Duplicate of TEIID-4271 > account for lack of collection types in salesforce > -------------------------------------------------- > > Key: TEIID-4365 > URL: https://issues.jboss.org/browse/TEIID-4365 > Project: Teiid > Issue Type: Enhancement > Components: Salesforce Connector > Affects Versions: 8.12.x > Reporter: Johnathon Lee > Assignee: Steven Hawkins > > Avoid including the system metadata for the Saleforce Connector. Due to: > {code:java} > Error message: The Entity Data Model type "Collection(Edm.Binary)" isn't supported. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4365) account for lack of collection types in salesforce

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4365?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4365: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1362656 Bugzilla Update: Perform > account for lack of collection types in salesforce > -------------------------------------------------- > > Key: TEIID-4365 > URL: https://issues.jboss.org/browse/TEIID-4365 > Project: Teiid > Issue Type: Enhancement > Components: Salesforce Connector > Affects Versions: 8.12.x > Reporter: Johnathon Lee > Assignee: Steven Hawkins > > Avoid including the system metadata for the Saleforce Connector. Due to: > {code:java} > Error message: The Entity Data Model type "Collection(Edm.Binary)" isn't supported. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4365) account for lack of collection types in salesforce

by Johnathon Lee (JIRA)

Johnathon Lee created TEIID-4365: ------------------------------------ Summary: account for lack of collection types in salesforce Key: TEIID-4365 URL: https://issues.jboss.org/browse/TEIID-4365 Project: Teiid Issue Type: Enhancement Components: Salesforce Connector Affects Versions: 8.12.x Reporter: Johnathon Lee Assignee: Steven Hawkins Avoid including the system metadata for the Saleforce Connector. Due to: {code:java} Error message: The Entity Data Model type "Collection(Edm.Binary)" isn't supported. {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4360) default token type needs to be "bearer" for OAuth2 access code negotiation

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4360?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-4360. --------------------------------- Fix Version/s: 8.13.7 Resolution: Done Added "Bearer" as default type if one is not supplied > default token type needs to be "bearer" for OAuth2 access code negotiation > -------------------------------------------------------------------------- > > Key: TEIID-4360 > URL: https://issues.jboss.org/browse/TEIID-4360 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Marco Ardito > Assignee: Ramesh Reddy > Fix For: 9.1, 8.13.7, 9.0.3 > > > Oauth2 authentication with security domain fails if remote server does not contain token_type in json response (access/refresh tokens), as specified by RFC. See forum reference for more details: in my case a workaround was found by Ramesh Reddy defaulting to "Bearer" tiken type. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4354) patch to CXF no longer needed with new version of the CXF in 9.0 series.

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4354?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-4354: -------------------------------- Fix Version/s: 8.13.7 > patch to CXF no longer needed with new version of the CXF in 9.0 series. > ------------------------------------------------------------------------ > > Key: TEIID-4354 > URL: https://issues.jboss.org/browse/TEIID-4354 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Marco Ardito > Assignee: Ramesh Reddy > Fix For: 9.1, 8.13.7, 9.0.3 > > > Using oauth2 authentication for rest webservice in Teiid (issuing sql request through invokeHTTP method in dynamic VDB), fails with an error like: > ERROR [org.teiid.CONNECTOR] (Worker0_QueryProcessorQueue61) P8QCt6jWv5/F Connector worker process failed for atomic-request=P8QCt6jWv5/F.7.4.35838: java.lang.NoClassDefFoundError: javax/ws/rs/client/ClientException > at org.apache.cxf.rs.security.oauth2.client.OAuthClientUtils.getAccessToken(OAuthClientUtils.java:287) > ...many more > (see forum reference for more stack trace) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2578) add/remove schema elements

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2578?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2578: ------------------------------------- The idea behind this JIRA is to provide new capabilities to Teiid, where the runtime VDB metadata can be created/altered with out redeploying the VDB. This will be a large effort in language support and runtime stitching support. The basic idea is, one can issue following commands against a Teiid runtime using a console (CLI) to create and alter a virtual database. The mandate we will be working towards is "Everything that teiid does in -vdb.xml *should* to be able to represent in DDL". Advanced features like <vdb-import>, <multi-source> need to be further discussed how they will fit in this model. The goal is to provide a clean migration path. This does NOT mean -vdb.xml support is going away, this is providing a more natural RDBMS way to define metadata. Creating database {code} CREATE DATABASE <name> OPTIONS (...); DROP DATABASE <name>; USE DATABASE <name> {code} creating a schema aka (model in vdb.xml) {code} CREATE SCHEMA <name> OPTIONS (VISIBLE xx, VIRTUAL xx) DROP SCHEMA <name>; USE SCHEMA <name> {code} The <USE> statements to switch the context of conversation in the console where user may be executing these statements. For creating a translator in database scope, this could be just a translator, or override translator. All the translator properties in OPTIONS {code} CREATE FOREIGN [<DATA> <WRAPPER>|<TRANSLATOR>] <name> OPTIONS (...) DROP FOREIGN [<DATA> <WRAPPER>|<TRANSLATOR>] <name> {code} For defining a data source, of to just create "source" data as in (-vdb.xml) {code} CREATE SERVER <name> TYPE <type> [VERSION <version>] FOREIGN DATA WRAPPER <wrapper-name> OPTIONS (...) DROP SERVER <name> {code} TYPE: will define the "datasource-template" from Admin API. OPTIONS: will contain any/all properties of the defined "datasource-template" <wrapper-name>: will be translator assigned to this datasource. NOTE: It has been discussed that, creation of data source itself is not mandatory, but defining the "source" information under a physical model as in "-vdb.xml" is minimally required. To import a schema from foreign server {code} IMPORT FOREIGN SCHEMA <schema-name> [ <import qualifications> ] FROM SERVER <server-name> INTO <schema-name> <import qualifications> ::= LIMIT TO (<table name list>) | EXCEPT (<table name list>) {code} Then include all the current DDL Metadata support. Then this feature will be expanded with full ALTER command syntax where needed (this may be phase 2) > add/remove schema elements > -------------------------- > > Key: TEIID-2578 > URL: https://issues.jboss.org/browse/TEIID-2578 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 9.1 > > > Schemas are currently static after load. Modifications can only happen with restarts or new versions. We should allow add/drop at runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4364) Informix - time values are adjusted in "opposite direction"

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4364?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4364. ----------------------------------- Resolution: Duplicate Issue Duplicate of TEIID-3808 > Informix - time values are adjusted in "opposite direction" > ----------------------------------------------------------- > > Key: TEIID-4364 > URL: https://issues.jboss.org/browse/TEIID-4364 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.12.5 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > If translator property _DatabaseTimeZone_ is set, time values are adjusted in "opposite direction" (in compare with date and timestamp values). Note, that I did not change user.timezone system property of the server. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4364) Informix - time values are adjusted in "opposite direction"

by Juraj Duráni (JIRA)

[ https://issues.jboss.org/browse/TEIID-4364?page=com.atlassian.jira.plugin... ] Juraj Duráni commented on TEIID-4364: ------------------------------------- Just one comment regarding TEIID-3808. > _Description:_ Date values are not adjusted at all. I was wrong. Date values are adjusted just like timestamp values are. > Informix - time values are adjusted in "opposite direction" > ----------------------------------------------------------- > > Key: TEIID-4364 > URL: https://issues.jboss.org/browse/TEIID-4364 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.12.5 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > If translator property _DatabaseTimeZone_ is set, time values are adjusted in "opposite direction" (in compare with date and timestamp values). Note, that I did not change user.timezone system property of the server. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4364) Informix - time values are adjusted in "opposite direction"

by Juraj Duráni (JIRA)

Juraj Duráni created TEIID-4364: ----------------------------------- Summary: Informix - time values are adjusted in "opposite direction" Key: TEIID-4364 URL: https://issues.jboss.org/browse/TEIID-4364 Project: Teiid Issue Type: Bug Affects Versions: 8.12.5 Reporter: Juraj Duráni Assignee: Steven Hawkins If translator property _DatabaseTimeZone_ is set, time values are adjusted in "opposite direction" (in compare with date and timestamp values). Note, that I did not change user.timezone system property of the server. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4364) Informix - time values are adjusted in "opposite direction"

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4364?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4364: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1362400 Bugzilla Update: Perform > Informix - time values are adjusted in "opposite direction" > ----------------------------------------------------------- > > Key: TEIID-4364 > URL: https://issues.jboss.org/browse/TEIID-4364 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.12.5 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > > If translator property _DatabaseTimeZone_ is set, time values are adjusted in "opposite direction" (in compare with date and timestamp values). Note, that I did not change user.timezone system property of the server. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 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 August 2016