November 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-225) LDAP Connector should use base DN for table as base DN for updates as well as queries

by Steven Hawkins (Updated) (JIRA)

[ https://issues.jboss.org/browse/TEIID-225?page=com.atlassian.jira.plugin.... ] Steven Hawkins updated TEIID-225: --------------------------------- Fix Version/s: Open To Community > LDAP Connector should use base DN for table as base DN for updates as well as queries > ------------------------------------------------------------------------------------- > > Key: TEIID-225 > URL: https://issues.jboss.org/browse/TEIID-225 > Project: Teiid > Issue Type: Feature Request > Components: LDAP Connector > Affects Versions: 6.0.0 > Environment: MetaMatrix 5.5.3RC2 > Reporter: Greg Haber > Priority: Minor > Fix For: Open To Community > > > Ramesh had a great idea earlier today on the LDAP connector: > [Ramesh] Why not search base info along with PK information to build the unique > DN? That seems possible right? > [Greg] Yes, that is a great idea! I will put in a JIRA for that (small code change, changing name of "search base" to just "base", and doc change). Probably we should have both relative and fully qualified DNs accepted here. Note however that the base may be several levels higher up in the tree then where you want to put the entry, so the base DN may be "ou=people,dc=company,dc=com", with a relative DN of "uid=ghaber,ou=newyork" here. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-167) Enhancement: Connector Developer's Kit needs overhaul

by Steven Hawkins (Updated) (JIRA)

[ https://issues.jboss.org/browse/TEIID-167?page=com.atlassian.jira.plugin.... ] Steven Hawkins updated TEIID-167: --------------------------------- Fix Version/s: Open To Community (was: 8.0) > Enhancement: Connector Developer's Kit needs overhaul > ----------------------------------------------------- > > Key: TEIID-167 > URL: https://issues.jboss.org/browse/TEIID-167 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Documentation > Affects Versions: 7.0 > Reporter: Ramesh Reddy > Fix For: Open To Community > > > Defect Tracker #24469: The CDK kit is based on the Command Shell framework, this needs to be moved to either MMSehll based or the Beanshell based framework, with better help system -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-403) ESB transport capabilitiy for connector framework

by Steven Hawkins (Updated) (JIRA)

[ https://issues.jboss.org/browse/TEIID-403?page=com.atlassian.jira.plugin.... ] Steven Hawkins updated TEIID-403: --------------------------------- Fix Version/s: Open To Community (was: 9.x) > ESB transport capabilitiy for connector framework > ------------------------------------------------- > > Key: TEIID-403 > URL: https://issues.jboss.org/browse/TEIID-403 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Marc Shirley > Fix For: Open To Community > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-999) Create valid capabilities support for MS Excel and MS Access JDBC-ODBC Connectors

by Steven Hawkins (Updated) (JIRA)

[ https://issues.jboss.org/browse/TEIID-999?page=com.atlassian.jira.plugin.... ] Steven Hawkins updated TEIID-999: --------------------------------- Fix Version/s: Open To Community (was: 8.0) > Create valid capabilities support for MS Excel and MS Access JDBC-ODBC Connectors > --------------------------------------------------------------------------------- > > Key: TEIID-999 > URL: https://issues.jboss.org/browse/TEIID-999 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Environment: MS Excel 2003 > Reporter: Larry O'Leary > Fix For: Open To Community > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Create a capabilities set that can be used by the MS Access and MS Excel connectors. We currently offer the MS Excel connector which is using the generic JDBC capabilities and translators and the MS Access connector which is using its own capabilities and translators but they do not reflect MS Access. > The replacement connector types should work very much like the current ones but reflect the base capabilities offered by MS JET 4 and specific capabilities as defined by the MS Excel and MS Access limitations to the MS JET 4 implementation. At bare minimum we should support push-down of all currently defined capabilities and remove any current ones that are not valid for MS JET/MS Access/MS Excel. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-319) LDAP Connector should re-implement algorithm for translating SQL to LDAP search, using Visitor design pattern

by Steven Hawkins (Updated) (JIRA)

[ https://issues.jboss.org/browse/TEIID-319?page=com.atlassian.jira.plugin.... ] Steven Hawkins updated TEIID-319: --------------------------------- Fix Version/s: Open To Community > LDAP Connector should re-implement algorithm for translating SQL to LDAP search, using Visitor design pattern > ------------------------------------------------------------------------------------------------------------- > > Key: TEIID-319 > URL: https://issues.jboss.org/browse/TEIID-319 > Project: Teiid > Issue Type: Task > Components: LDAP Connector > Affects Versions: 6.0.0 > Reporter: Michael Walker > Priority: Optional > Fix For: Open To Community > > > Though the current approach works, it would be cleaner if the LDAP Connector used the Visitor design pattern to handle each part of a SQL query, and translate it into an LDAP search. This may make future changes easier to implement, and keep the code cleaner. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1741) Record level audit trail in teiid log files

by Monika Ahuja (JIRA)

Record level audit trail in teiid log files ------------------------------------------- Key: TEIID-1741 URL: https://issues.jboss.org/browse/TEIID-1741 Project: Teiid Issue Type: Feature Request Reporter: Monika Ahuja Assignee: Steven Hawkins In order to track the audit trail for patient identified information access, we would like to track the executed queries, results as well as the timestamps for each user's query and its result. Essentially we need a report providing the list of Medical Record Numbers accessed by each user id and I think we can use the Logs to track that (unless you suggest a better way). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
4
0 / 0

[JBoss JIRA] (TEIID-994) Unable to execute Oracle pipelined table function as procedure

by Steven Hawkins (Updated) (JIRA)

[ https://issues.jboss.org/browse/TEIID-994?page=com.atlassian.jira.plugin.... ] Steven Hawkins updated TEIID-994: --------------------------------- Fix Version/s: Open To Community (was: 8.0) > Unable to execute Oracle pipelined table function as procedure > -------------------------------------------------------------- > > Key: TEIID-994 > URL: https://issues.jboss.org/browse/TEIID-994 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors, Query Engine > Reporter: Steven Hawkins > Fix For: Open To Community > > > Oracle pipelined table functions (can be used in Oracle queries as TABLE(...)) that can be put in the FROM clause and used as if they were tables although they are really procedures. We found that we imported this table function, although didn't get it quite right - the result set was wrong, which may just be a deficiency of the JDBC import metadata. We were able to map the proc to a table and execute but when we did we got a PL/SQL error from the db. > Because this is a proc, we are executing it as a CallableStatement down in the JDBC connector which apparently does not work with DataDirect. I'm not sure how we can detect and do something different but seems like we need to have some metadata (procedure name in source?) that can tell us that this proc needs to be run differently and have the Oracle JDBC Connector deal with this properly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-965) Need Excel file importer / connector

by Steven Hawkins (Updated) (JIRA)

[ https://issues.jboss.org/browse/TEIID-965?page=com.atlassian.jira.plugin.... ] Steven Hawkins updated TEIID-965: --------------------------------- Fix Version/s: Open To Community > Need Excel file importer / connector > ------------------------------------ > > Key: TEIID-965 > URL: https://issues.jboss.org/browse/TEIID-965 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 7.0 > Reporter: Steven Hawkins > Fix For: Open To Community > > > Really need to add an Excel connector in SP1. The easiest way to do this is probably with one of the open source JDBC drivers that work over Excel files. > Something like: > https://xlsql.dev.java.net/ - Excel JDBC driver (GPL unfortunately, so we probably can't distribute the driver) > http://www.andykhan.com/jexcelapi/ - Java Excel API (GPL too) > http://xlsjdbc.sourceforge.net/ - LGPL (uses Apache POI), really cheesy and maybe not being updated > http://jakarta.apache.org/poi/ - Excel API, event-based and not particularly friendly > http://www.vistaportal.com/products/vistajdbc-QA.htm - commercial -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1090) Request to add a Google Apps/Calendar Connector

by Steven Hawkins (Updated) (JIRA)

[ https://issues.jboss.org/browse/TEIID-1090?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-1090: ---------------------------------- Fix Version/s: Open To Community > Request to add a Google Apps/Calendar Connector > ------------------------------------------------ > > Key: TEIID-1090 > URL: https://issues.jboss.org/browse/TEIID-1090 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Debbie Steigner > Fix For: Open To Community > > > Customer is requesting that we add a MetaMatrix Google Apps/Calendar Connector to a future release. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-501) Add the 'major' DBMS's system catalogs as 'optional' MMX system catalogs to better 'slide-in' to opportunities.

by Steven Hawkins (Resolved) (JIRA)

[ https://issues.jboss.org/browse/TEIID-501?page=com.atlassian.jira.plugin.... ] Steven Hawkins resolved TEIID-501. ---------------------------------- Fix Version/s: (was: 9.x) Resolution: Incomplete Description This is too vague and too much work as described. Just emulating a single transport, such as postgresql via our odbc transport, requires a substantial amount of work. As needed we can look at doing the same thing for other databases, but each one will be a significant undertaking - and cannot have the expectation of being 100% grammar compatible. Finding sufficient documentation on closed source protocols may also be an issue. > Add the 'major' DBMS's system catalogs as 'optional' MMX system catalogs to better 'slide-in' to opportunities. > --------------------------------------------------------------------------------------------------------------- > > Key: TEIID-501 > URL: https://issues.jboss.org/browse/TEIID-501 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, JDBC Connector, Query Engine > Affects Versions: 8.0 > Reporter: Marc Shirley > > Make MetaMatrix look like an Oracle database or a SQL Server database, including system catalogs as well as query grammar. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2011