May 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Updated: (TEIID-405) Allow importing a VDB file from a URL (not just the local file system)

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-405?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-405: --------------------------------- Fix Version/s: 6.1.1 (was: 6.1.0) Affects: [Documentation (Ref Guide, User Guide, etc.), Release Notes] (was: [Documentation (Ref Guide, User Guide, etc.)]) Priority: Major (was: Minor) > Allow importing a VDB file from a URL (not just the local file system) > ---------------------------------------------------------------------- > > Key: TEIID-405 > URL: https://jira.jboss.org/jira/browse/TEIID-405 > Project: Teiid > Issue Type: Feature Request > Components: Console > Affects Versions: 6.0.0 > Reporter: Randall Hauch > Fix For: 6.1.1 > > > The Console currently has the ability to import a VDB file from the local file system. A great enhancement to this would be the ability to import a VDB from a URL, allowing an administrator to import a VDB file that is located anywhere accessible via a URL (e.g., SVN, DNA, WebDAV, etc.), without requiring the administrator to fetch the file locally first. Of course, fetching it locally is still a valid (and not difficult) workaround. -- 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

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-560) Designer configuration.xml contains wrong port number for SQL Server XA Connector

by Barry LaFond (JIRA)

Designer configuration.xml contains wrong port number for SQL Server XA Connector --------------------------------------------------------------------------------- Key: TEIID-560 URL: https://jira.jboss.org/jira/browse/TEIID-560 Project: Teiid Issue Type: Bug Reporter: Barry LaFond Assignee: Steven Hawkins Priority: Minor Port number is currently 50000, should be 1433. -- 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

15 years, 1 month

2
2
0 / 0

[JBoss JIRA] Commented: (TEIID-203) Make connector capabilites more granular.

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-203?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIID-203: -------------------------------------- Implemented the above. If the salesforce connector declares support for outer joins and only accepts key criteria, then join pushdown will be allowed. Also the ldap connector should be able to add function support for filters, but with supportsSelectExpressions left as false, they will not be pushed down in the select clause. There are a couple of issues though. Our optimizations get in the way of 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. I'm leaning toward the latter. 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. 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. > Make connector capabilites more granular. > ----------------------------------------- > > Key: TEIID-203 > URL: https://jira.jboss.org/jira/browse/TEIID-203 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Query Engine > Affects Versions: 6.0.0 > Reporter: John Doyle > Assignee: Steven Hawkins > Fix For: 6.1.0 > > > Some connector capabilites are only available in combination with others. For example, if you wish to support the SupportsAggregatesCount capability, you have to also support the SupportsAggregates capability(GROUP BY and HAVING). This requirement creates additional requirements for a connector where the source syustem cabilities do not correspond with the relationships we have defined between capabilites. > For instance, the SQL supported by salesforce can include the count(*) function, but it does not support GROUP BY or HAVING. Because we require c connector to support SupportsAggregates befrore it can support count(*), the connector is required to implement those functions if it wishes to pus down count(*). -- 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

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-553) check for element comparable in pushdown of sort/group by/and dup removal

by Steven Hawkins (JIRA)

check for element comparable in pushdown of sort/group by/and dup removal ------------------------------------------------------------------------- Key: TEIID-553 URL: https://jira.jboss.org/jira/browse/TEIID-553 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.1.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Since the validation visitor no longer checks for element supports (it is just looking for runtime type TEIID-384), these need to be checked prior to pushdown. -- 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

15 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-552) check for source not criteria support with negated abstractsetcriteria and isnull

by Steven Hawkins (JIRA)

check for source not criteria support with negated abstractsetcriteria and isnull --------------------------------------------------------------------------------- Key: TEIID-552 URL: https://jira.jboss.org/jira/browse/TEIID-552 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.1.0 We currently only check for not support on negated like criteria, this check needs expanded. -- 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

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (TEIID-555) add not support to the ldap connector

by Steven Hawkins (JIRA)

add not support to the ldap connector ------------------------------------- Key: TEIID-555 URL: https://jira.jboss.org/jira/browse/TEIID-555 Project: Teiid Issue Type: Feature Request Components: LDAP Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.1.0 I noticed with the capabilities refactoring that not was not supported, but it is trivial to add. -- 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

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Resolved: (TEIID-103) Salesforce Connector: Count(*) did not appear to pushdown to SOQL.

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-103?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-103. ---------------------------------- Resolution: Done Based upon the new connector capabilities, added count start support without implying support for group by or having. Set TestVisitors > Salesforce Connector: Count(*) did not appear to pushdown to SOQL. > ------------------------------------------------------------------ > > Key: TEIID-103 > URL: https://jira.jboss.org/jira/browse/TEIID-103 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector > Affects Versions: 6.0.0 > Reporter: John Doyle > Assignee: Steven Hawkins > Priority: Minor > Fix For: 6.1.0 > > > Count(*) did not appear to pushdown to SOQL. -- 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

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-556) add 'not' and 'or' support to the salesforce connector

by Steven Hawkins (JIRA)

add 'not' and 'or' support to the salesforce connector ------------------------------------------------------ Key: TEIID-556 URL: https://jira.jboss.org/jira/browse/TEIID-556 Project: Teiid Issue Type: Feature Request Components: Salesforce Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.1.0 With the upcoming capabilities changes we are more diligently checking for not support, the salesforce connector should implement it to ensure push down of "not in", "not like", etc. -- 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

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (TEIID-557) NPE in the Embedded when UDF is being loaded

by Ramesh Reddy (JIRA)

NPE in the Embedded when UDF is being loaded -------------------------------------------- Key: TEIID-557 URL: https://jira.jboss.org/jira/browse/TEIID-557 Project: Teiid Issue Type: Bug Components: Embedded Affects Versions: 6.0.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 6.1.0 Caused by: java.lang.NullPointerException at com.metamatrix.dqp.embedded.services.EmbeddedConfigurationService.loadUDF(EmbeddedConfigurationService.java:930) at com.metamatrix.dqp.embedded.services.EmbeddedConfigurationService.initializeService(EmbeddedConfigurationService.java:996) at com.metamatrix.dqp.embedded.services.EmbeddedBaseDQPService.initialize(EmbeddedBaseDQPService.java:59) at com.metamatrix.common.application.Application.start(Application.java:62) at org.teiid.dqp.internal.process.DQPCore.start(DQPCore.java:563) at com.metamatrix.jdbc.EmbeddedConnectionFactoryImpl.initialize(EmbeddedConnectionFactoryImpl.java:113) at com.metamatrix.jdbc.EmbeddedConnectionFactoryImpl.createConnection(EmbeddedConnectionFactoryImpl.java:79) at com.metamatrix.jdbc.EmbeddedDriver$EmbeddedTransport.createConnection(EmbeddedDriver.java:502) at com.metamatrix.jdbc.EmbeddedDriver.createConnection(EmbeddedDriver.java:134) -- 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

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-548) When a cluster node added the original certificate is not being copied

by Ramesh Reddy (JIRA)

When a cluster node added the original certificate is not being copied ---------------------------------------------------------------------- Key: TEIID-548 URL: https://jira.jboss.org/jira/browse/TEIID-548 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 6.0.0 Reporter: Ramesh Reddy Fix For: 6.1.0 Cluster host setup is not copying the keystore certificate from the original host to the newly added cluster node. Now that "JGroups" messages are by default encrypted, not having this will result in node not being joined in the cluster as JGroups discards any messages it gets with wrong keystore. -- 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

15 years, 1 month

2
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2009