March 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Closed: (TEIID-164) Connector api overhaul

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-164?page=com.atlassian.jira.plug... ] Steven Hawkins closed TEIID-164. -------------------------------- Resolution: Done All 6.0.0 issues are out of the way. The documentation changes will be made with 6.1.0. > Connector api overhaul > ---------------------- > > Key: TEIID-164 > URL: https://jira.jboss.org/jira/browse/TEIID-164 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Documentation, Misc. Connectors, Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 6.0.0 > > > Proposed changes: > Remove getMetadata from connection - if and when it is implemented it will be an optional interface. > Rename Connection.release to close and PoolAwareConnection.releaseCalled to closeCalled > Remove ConnectorCapabilities.supportsExecutionMode and replace Asynch/SynchQuery, Asynch/SynchQueryCommand, Batched Executions with ResultSetExecution, also remove BatchedUpdate and BulkInsert Executions, which can be generalized on UpdateExecution. > BatchedUpdate and BulkInsert support would be indicated by capabilities on ConnectorCapabilities. > Execution mode integer constants would no longer be used, instead the ICommand object would be passed to the Connection.createExecution method. > Asynch Connectors are created by modifying execution logic to throw a DataNotAvailableException, which contains the next poll interval. This removes the need for special executions. > ResultSetExecution would use an iteration approach, which removes the need for Batch and BasicBatch (FEDERATE-311) > Connector batch size would be available on the ExecutionContext, rather than explicitly being passed to the execute method. > Additionally all deprecated classes would be removed and a 5.5. compatibility layer created. Current deprecations are: > Deprecated ConnectorCapabilities scope, and added GlobalCapabilitiesProvider > Deprecated ConnectionPool/DisabledConnectionPool/ConnectionPoolException, since pooling can be provided automatically > Deprecated Asynch/SynchQueryExecution, and added Asynch/SynchQueryCommandExecution -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-352) JDBC SQLTranslator issues

by Steven Hawkins (JIRA)

JDBC SQLTranslator issues ------------------------- Key: TEIID-352 URL: https://jira.jboss.org/jira/browse/TEIID-352 Project: Teiid Issue Type: Bug Components: JDBC Connector Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.1.0 SQLTranslators are extremely cumbersome and not well documented. We need something much more like Hibernate's dialect. Also the time literal for Access/SQLServer is incorrect and the limit with set op will also fail for Access/SQLServer. -- 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, 2 months

1
4
0 / 0

[JBoss JIRA] Resolved: (TEIID-243) Add the ability to support vararg functions

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-243?page=com.atlassian.jira.plug... ] Steven Hawkins resolved TEIID-243. ---------------------------------- Fix Version/s: 6.0.0 (was: 6.2.0) Resolution: Done Add this ability for system functions, but there's no udf metadata to use varargs from the designer. > Add the ability to support vararg functions > ------------------------------------------- > > Key: TEIID-243 > URL: https://jira.jboss.org/jira/browse/TEIID-243 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 6.0.0 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > It would be good to add resolving/metadata support for vararg functions. For example coalesce is a vararg function, and in general UDFs would benefit from utilizing varargs. -- 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, 2 months

1
0
0 / 0

[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.0 (was: 6.0.0) Affects Version/s: 6.0.0 (was: 6.1.0) > 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 > Priority: Minor > Fix For: 6.1.0 > > > 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-414) UDF and system functions should be allowed to have a type specific signature

by Steven Hawkins (JIRA)

UDF and system functions should be allowed to have a type specific signature ---------------------------------------------------------------------------- Key: TEIID-414 URL: https://jira.jboss.org/jira/browse/TEIID-414 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.0.0 We currently document that functions need an all object signature, this makes writing the corresponding method cumbersome. Since we already have type information we should match based upon the expected signature. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (TEIID-415) Long to double and integer to float conversions should be narrowing

by Steven Hawkins (JIRA)

Long to double and integer to float conversions should be narrowing ------------------------------------------------------------------- Key: TEIID-415 URL: https://jira.jboss.org/jira/browse/TEIID-415 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.0.0 There is a possible loss of precision with these conversions -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Commented: (TEIID-193) MembershipService does not show failure in Console when unable to connect to LDAP database

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-193?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIID-193: -------------------------------------- That's close to what you would want (except you still need an aggregate membershipservice concept to account for domain ordering). Representing something as a service (either as individual MembershipServices or MembershipDomainServices) has ramifications for it's configuration and creation that of course would require quite a bit of work to do, that's why this keeps getting pushed. > MembershipService does not show failure in Console when unable to connect to LDAP database > ------------------------------------------------------------------------------------------ > > Key: TEIID-193 > URL: https://jira.jboss.org/jira/browse/TEIID-193 > Project: Teiid > Issue Type: Feature Request > Components: Console > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Minor > Fix For: 6.2.0 > > > Defect Tracker #2865 : Set up MembershipService to have MetaMatrix and LDAP users. Server PC was unable to communicate with Unix box hosting LDAP database. Server started and MembershipService showed Running even though it had failed to read LDAP users. There is an exception in MetaMatrixVM log but need a visual clue in Console. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIID-193) MembershipService does not show failure in Console when unable to connect to LDAP database

by Larry O'Leary (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-193?page=com.atlassian.jira.plug... ] Larry O'Leary commented on TEIID-193: ------------------------------------- Can we not expose each membership domain as a separate service in the service list? Basically all components that are derived (marked) as membership service could be displayed as a separate service with its own service status in the service state panel of the Console. So, if I had a file membership domain defined called file01.dom and an LDAP membership domain defined called ldap01.dom then I would see in the service panel: PlatformStandard | +--MembershipService: file01.dom -- Running +--MembershipService: ldap01.dom -- Failed Initialization > MembershipService does not show failure in Console when unable to connect to LDAP database > ------------------------------------------------------------------------------------------ > > Key: TEIID-193 > URL: https://jira.jboss.org/jira/browse/TEIID-193 > Project: Teiid > Issue Type: Feature Request > Components: Console > Affects Versions: 6.x > Reporter: Steven Hawkins > Priority: Minor > Fix For: 6.2.0 > > > Defect Tracker #2865 : Set up MembershipService to have MetaMatrix and LDAP users. Server PC was unable to communicate with Unix box hosting LDAP database. Server started and MembershipService showed Running even though it had failed to read LDAP users. There is an exception in MetaMatrixVM log but need a visual clue in Console. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-411) Add join columns to process plan string for join nodes

by Steven Hawkins (JIRA)

Add join columns to process plan string for join nodes ------------------------------------------------------ Key: TEIID-411 URL: https://jira.jboss.org/jira/browse/TEIID-411 Project: Teiid Issue Type: Task Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Optional Fix For: 6.0.0 -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (TEIID-410) Simplify command collector visitor

by Steven Hawkins (JIRA)

Simplify command collector visitor ---------------------------------- Key: TEIID-410 URL: https://jira.jboss.org/jira/browse/TEIID-410 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.0.0 Command collector visitor modes are confusing and error prone. -- 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, 2 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2009