December 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1277) Add documentation/article about how to use the "import web-service as relational model" generated model.

by Ramesh Reddy (JIRA)

Add documentation/article about how to use the "import web-service as relational model" generated model. -------------------------------------------------------------------------------------------------------- Key: TEIID-1277 URL: https://jira.jboss.org/browse/TEIID-1277 Project: Teiid Issue Type: Task Components: Documentation Affects Versions: 7.1 Reporter: Ramesh Reddy Fix For: 7.1.1 Currently there is no documentation about how to use the models generated by WSDL to Relational Model importer in the Teiid Designer. I am not sure where the document needs to exist, as to in Teiid or Teiid Designer or just as an WIKI article, but Teiid MUST have this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1362) salesforce push down queries won't get resolved correctly

by Wanja Pernath (JIRA)

salesforce push down queries won't get resolved correctly --------------------------------------------------------- Key: TEIID-1362 URL: https://jira.jboss.org/browse/TEIID-1362 Project: Teiid Issue Type: Bug Components: Salesforce Connector Affects Versions: 7.2 Environment: Teiid 7.2 final on JBoss EAP 5.1 with sun java 1.6.0_20 Reporter: Wanja Pernath Assignee: Steven Hawkins GIVEN: select a.name, b.sumary from Opp a OUTER JOIN OLI b ON a.id = b.foreignId JoinQueryVisitor of SFDC translator correctly creates: select a.name, (select b.summary from OLI b) from Opp a As of SFDC docs: http://www.salesforce.com/us/developer/docs/api/index_Left.htm#StartTopic... you get a result set of for example: "opp #1", [b] QueryResult for row #1 "opp #2", [b] QueryResult for row #2 Which must be transformed into something like this (EXPECTED) "opp #1", 100 "opp #1", 150 "opp #1", 43000 "opp #2", 10000 "opp #2", 100 etc. Right now, it gets transformed into something like (CURRENT) "opp #1", null "opp #2", null "opp #3", null etc. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
7
0 / 0

[JBoss JIRA] Created: (TEIID-1378) Client Jar in Teiid Jopr Plugin Jar Causes Zip Exception in JBossAS 5.1

by Ted Jones (JIRA)

Client Jar in Teiid Jopr Plugin Jar Causes Zip Exception in JBossAS 5.1 ----------------------------------------------------------------------- Key: TEIID-1378 URL: https://jira.jboss.org/browse/TEIID-1378 Project: Teiid Issue Type: Bug Components: Jopr Plugin Affects Versions: 7.1.1 Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.1.1 The Teiid client jar was added to the build process of the Teiid Jopr plugin's lib folder. This was needed to support Teiid in a JON instance. This jar is causing errors in JBossAS 5.1 and is not required for Jopr so it should be removed from the community build. The product build needs to be changed to add the jar and https://jira.jboss.org/browse/SOA-2609 was logged to address this change. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-1049) Create data source for each VDB deployed automaticaly

by Ramesh Reddy (JIRA)

Create data source for each VDB deployed automaticaly ----------------------------------------------------- Key: TEIID-1049 URL: https://jira.jboss.org/jira/browse/TEIID-1049 Project: Teiid Issue Type: Feature Request Components: Embedded Affects Versions: 7.0 Reporter: Ramesh Reddy Priority: Minor Fix For: 7.0 When a VDB is deployed, auto create a data source for the deployed VDB using the Teiid's "embedded" data source class. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIID-1306) Add support for JSON data sources (JSON translator, JSON-to-table mapping functions).

by Ken Johnson (JIRA)

Add support for JSON data sources (JSON translator, JSON-to-table mapping functions). ------------------------------------------------------------------------------------- Key: TEIID-1306 URL: https://jira.jboss.org/browse/TEIID-1306 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors Affects Versions: 7.1 Reporter: Ken Johnson Assignee: Steven Hawkins Fix For: 7.2 Consider adding support in Teiid to consume services (as data sources) that return JSON payloads rather than XML payloads. This is an increasingly common integration scenario. The approach used for XML processing seems to be a compatible pattern for this use case. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
6
0 / 0

[JBoss JIRA] Created: (TEIID-586) Like pushdown handling

by Steven Hawkins (JIRA)

Like pushdown handling ---------------------- Key: TEIID-586 URL: https://jira.jboss.org/jira/browse/TEIID-586 Project: Teiid Issue Type: Bug Components: LDAP Connector, Query Engine, Salesforce Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.2.0 Both salesforce and ldap like semantics are not the same as SQL. We could capture this with more capabilities supportsLikeCaseSensitive and supportsLikeWildcardSingleCharacter repectively, or another approach would be to allow the connector to generically indicate partial support and have the query engine both push down the conjunct and leave a copy to be applied after the query. With either explicit supports or generic partial support it would only applicable to top level where clause conjuncts. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1170) Support subqueries in temp table update/delete criteria

by Steve Hawkins (JIRA)

Support subqueries in temp table update/delete criteria ------------------------------------------------------- Key: TEIID-1170 URL: https://jira.jboss.org/browse/TEIID-1170 Project: Teiid Issue Type: Feature Request Affects Versions: 6.0.0 Reporter: Steve Hawkins Assignee: Steve Hawkins Priority: Minor Fix For: 8.0 Subqueries are currently not supported in temp table update/delete criteria. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (TEIID-784) Enhance distinct set op processing

by Steven Hawkins (JIRA)

Enhance distinct set op processing ---------------------------------- Key: TEIID-784 URL: https://jira.jboss.org/jira/browse/TEIID-784 Project: Teiid Issue Type: Feature Request Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.3.0 The sort operation should be able to pushed for each set op child (distinct is already eligible for pushing, but typically won't be because there's no order by). Also for union the sorted children should be fed directly into the second phase of sorting. All of this relies on the connector guaranteeing null ordering (TEIID-715 should be repurposed to cover the language enhancement of nulls first|last) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1035) Replace Existing XML Document Functionality with other JBoss Technologies

by Ted Jones (JIRA)

Replace Existing XML Document Functionality with other JBoss Technologies ------------------------------------------------------------------------- Key: TEIID-1035 URL: https://jira.jboss.org/jira/browse/TEIID-1035 Project: Teiid Issue Type: Task Affects Versions: 7.0 Reporter: Ted Jones Assignee: Steven Hawkins Fix For: 8.0 The current XML Document homegrown technologies in the Teiid Designer with existing JBoss technologies. The following use cases should be satisfied: 1. Start with an XML Schema to build a Document that can be filled with relational, heterogeneous data and "shipped around" 2. Given an XML document/message definition, submit a query on the document with criteria defined within the document structure 3. Send an input document, produce and output document -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (TEIID-587) Better pushdown support for exotic joins

by Steven Hawkins (JIRA)

Better pushdown support for exotic joins ---------------------------------------- Key: TEIID-587 URL: https://jira.jboss.org/jira/browse/TEIID-587 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.2.0 Our optimizations get in the way of Salesforce pushdown. Specifically rewriting like when possible to = and converting outer joins to inner joins. In both cases we would need to not perform the optimization in the first place or convert into an acceptable form prior to pushdown. The next is that salesforce, while requiring key criteria also allows other criteria in the left outer join on clause (which would be the same as having criteria on the nested relationship query in the salesforce query). With the capabilities as currently defined this would cause the query to not be pushed down. We should consider adding a relational supported join criteria type that requires key criteria but allows for outside criteria. Also we should treat the lack of inner join support to mean that criteria on the inner side of an outer join cannot be pushed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues December 2010