August 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4333) Change default of SupportsComapareCriteriaOrdered to true

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4333?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-4333: ------------------------------- Fix Version/s: 9.1 Git Pull Request: https://github.com/teiid/teiid/pull/782 > Change default of SupportsComapareCriteriaOrdered to true > --------------------------------------------------------- > > Key: TEIID-4333 > URL: https://issues.jboss.org/browse/TEIID-4333 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 9.1 > > > Change the default of translator capability SupportsComapareCriteriaOrdered from false to true. In JDG 6.6, a fix was made to correct the issue with querying LT, LTE, GT and GTE on string columns. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4333) Change default of SupportsComapareCriteriaOrdered to true

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-4333?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-4333: ------------------------------------ will be updating doc's. > Change default of SupportsComapareCriteriaOrdered to true > --------------------------------------------------------- > > Key: TEIID-4333 > URL: https://issues.jboss.org/browse/TEIID-4333 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 9.1 > > > Change the default of translator capability SupportsComapareCriteriaOrdered from false to true. In JDG 6.6, a fix was made to correct the issue with querying LT, LTE, GT and GTE on string columns. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4271) Consume Teiid OData from Salesforce

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4271?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4271: --------------------------------------- This could still be an issue with OData4 - just not for SYS/SYSADMIN. But it could be a problem for any user schema that has an array type. > Consume Teiid OData from Salesforce > ----------------------------------- > > Key: TEIID-4271 > URL: https://issues.jboss.org/browse/TEIID-4271 > Project: Teiid > Issue Type: Feature Request > Components: OData > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 9.x > > > At least when consuming OData 2, Salesforce does not support Collection(Int16|Int32|String). Since we expose our system metadata, including pg metadata, in the OData metadata, this means that Salesforce won't consume. If the pg metadata is disabled and there are not primitive array columns in the rest of the metadata, then Salesforce can consume. > Since this is working around a Salesforce issue, we shouldn't introduce too intrusive of a mechanism for this. And in general we may need to use extension metadata to allow users to exclude objects in a more granular way from being exposed in OData metadata. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4271) Consume Teiid OData from Salesforce

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4271?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4271: ------------------------------------- This would not be an issue with OData4 as the $metadata is provided per schema basis. > Consume Teiid OData from Salesforce > ----------------------------------- > > Key: TEIID-4271 > URL: https://issues.jboss.org/browse/TEIID-4271 > Project: Teiid > Issue Type: Feature Request > Components: OData > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 9.x > > > At least when consuming OData 2, Salesforce does not support Collection(Int16|Int32|String). Since we expose our system metadata, including pg metadata, in the OData metadata, this means that Salesforce won't consume. If the pg metadata is disabled and there are not primitive array columns in the rest of the metadata, then Salesforce can consume. > Since this is working around a Salesforce issue, we shouldn't introduce too intrusive of a mechanism for this. And in general we may need to use extension metadata to allow users to exclude objects in a more granular way from being exposed in OData metadata. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4271) Consume Teiid OData from Salesforce

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4271?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-4271: ----------------------------------- Assignee: Ramesh Reddy > Consume Teiid OData from Salesforce > ----------------------------------- > > Key: TEIID-4271 > URL: https://issues.jboss.org/browse/TEIID-4271 > Project: Teiid > Issue Type: Feature Request > Components: OData > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 9.x > > > At least when consuming OData 2, Salesforce does not support Collection(Int16|Int32|String). Since we expose our system metadata, including pg metadata, in the OData metadata, this means that Salesforce won't consume. If the pg metadata is disabled and there are not primitive array columns in the rest of the metadata, then Salesforce can consume. > Since this is working around a Salesforce issue, we shouldn't introduce too intrusive of a mechanism for this. And in general we may need to use extension metadata to allow users to exclude objects in a more granular way from being exposed in OData metadata. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4271) Consume Teiid OData from Salesforce

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4271?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4271: --------------------------------------- In a forward looking sense this needs to be looked at for OData 4 as the OData 2 service has been removed. Also this was written from the perspective of older releases - the SYS/SYSADMIN schemas now also have array types. A vdb could use a property to exclude system metadata from odata metadata, but that would only be needed for legacy branches. > Consume Teiid OData from Salesforce > ----------------------------------- > > Key: TEIID-4271 > URL: https://issues.jboss.org/browse/TEIID-4271 > Project: Teiid > Issue Type: Feature Request > Components: OData > Reporter: Steven Hawkins > Fix For: 9.x > > > At least when consuming OData 2, Salesforce does not support Collection(Int16|Int32|String). Since we expose our system metadata, including pg metadata, in the OData metadata, this means that Salesforce won't consume. If the pg metadata is disabled and there are not primitive array columns in the rest of the metadata, then Salesforce can consume. > Since this is working around a Salesforce issue, we shouldn't introduce too intrusive of a mechanism for this. And in general we may need to use extension metadata to allow users to exclude objects in a more granular way from being exposed in OData metadata. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 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: (was: https://bugzilla.redhat.com/show_bug.cgi?id=1362656) Bugzilla Update: (was: 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)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4271) Consume Teiid OData from Salesforce

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4271?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4271: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1362656 Bugzilla Update: Perform > Consume Teiid OData from Salesforce > ----------------------------------- > > Key: TEIID-4271 > URL: https://issues.jboss.org/browse/TEIID-4271 > Project: Teiid > Issue Type: Feature Request > Components: OData > Reporter: Steven Hawkins > Fix For: 9.x > > > At least when consuming OData 2, Salesforce does not support Collection(Int16|Int32|String). Since we expose our system metadata, including pg metadata, in the OData metadata, this means that Salesforce won't consume. If the pg metadata is disabled and there are not primitive array columns in the rest of the metadata, then Salesforce can consume. > Since this is working around a Salesforce issue, we shouldn't introduce too intrusive of a mechanism for this. And in general we may need to use extension metadata to allow users to exclude objects in a more granular way from being exposed in OData metadata. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4271) Consume Teiid OData from Salesforce

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4271?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4271: --------------------------------- > Consume Teiid OData from Salesforce > ----------------------------------- > > Key: TEIID-4271 > URL: https://issues.jboss.org/browse/TEIID-4271 > Project: Teiid > Issue Type: Feature Request > Components: OData > Reporter: Steven Hawkins > Fix For: 9.x > > > At least when consuming OData 2, Salesforce does not support Collection(Int16|Int32|String). Since we expose our system metadata, including pg metadata, in the OData metadata, this means that Salesforce won't consume. If the pg metadata is disabled and there are not primitive array columns in the rest of the metadata, then Salesforce can consume. > Since this is working around a Salesforce issue, we shouldn't introduce too intrusive of a mechanism for this. And in general we may need to use extension metadata to allow users to exclude objects in a more granular way from being exposed in OData metadata. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[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)

8 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2016