February 2009 - teiid-issues - Jboss List Archives

[JBoss JIRA] Updated: (TEIID-200) Is the "format" property metadata available to the connector API?

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-200?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-200: --------------------------------- Component/s: Connector API Query Engine Affects: [Documentation (Ref Guide, User Guide, etc.), Release Notes] Complexity: Medium > Is the "format" property metadata available to the connector API? > ----------------------------------------------------------------- > > Key: TEIID-200 > URL: https://jira.jboss.org/jira/browse/TEIID-200 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Query Engine > Affects Versions: 6.0.0 > Reporter: Lance Phillips > Assignee: Ramesh Reddy > Fix For: 6.0.0 > > > Defect Tracker #24181: Request was for specifically for "format" property, but all metadata should be exposed. > Inside a custom connector, I'd like to grab the value of the "format" property from columns in a model that have that property set. Is this possible? > In the code, I'm working with a com.metamatrix.data.metadata.runtime.Element. Element provides methods to fetch the NameInSource property, the minimumValue and maximumValue properties, but does not provide a method to fetch Format. It does provide a method to "getProperties", but this seems to be empty, and might usually contain metadata extensions, according to the javadoc. So, is there a way to get Format? -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-199) Integration with JBoss Identity project

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-199?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-199: --------------------------------- Component/s: Server Fix Version/s: 6.x Affects Version/s: 6.0.0 Affects: [Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration, Release Notes] > Integration with JBoss Identity project > --------------------------------------- > > Key: TEIID-199 > URL: https://jira.jboss.org/jira/browse/TEIID-199 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 6.0.0 > Reporter: Greg Haber > Assignee: Steven Hawkins > Fix For: 6.x > > > There is a project underway, JBoss Identity (https://jira.jboss.org/jira/browse/JBID), that aims to provide common identity management support across many JBoss projects/products. According to the project leader's blog (http://anil-identity.blogspot.com/2008/12/federated-identity-support-with...), JBoss Application Server, JBoss Portal, JBoss SOA, JBoss Rules/Drools, and JBoss Seam are all on board with this approach. We should see if it makes sense for us to jump on the bandwagon. > The end goal of using the JBoss Identity stuff would be to replace the custom membership domain provider for authentication, and also to leverage it to provide SAML-based authorization for (ideally fine grained) access to Federate virtual databases. > SAML-based authorization has been a frequent request by prospects/customers for the closed source MetaMatrix product that is an ancestor to Federate. > I'm deliberately logging this one in the Federate project rather than the JBEDSP product JIRA since JBoss Identity itself is also still in project-only status. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-201) Improve ORDER BY handling to allow original column evenwhen it is aliased

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-201?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-201: --------------------------------- Component/s: Query Engine Fix Version/s: 6.0.0 Affects Version/s: 6.0.0 > Improve ORDER BY handling to allow original column evenwhen it is aliased > ------------------------------------------------------------------------- > > Key: TEIID-201 > URL: https://jira.jboss.org/jira/browse/TEIID-201 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Jerry Helbling > Assignee: Jerry Helbling > Priority: Minor > Fix For: 6.0.0 > > > Refer to internal case 225071. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIID-201) Improve ORDER BY handling to allow original column evenwhen it is aliased

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-201?page=com.atlassian.jira.plug... ] Steven Hawkins closed TEIID-201. -------------------------------- > Improve ORDER BY handling to allow original column evenwhen it is aliased > ------------------------------------------------------------------------- > > Key: TEIID-201 > URL: https://jira.jboss.org/jira/browse/TEIID-201 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 6.0.0 > Reporter: Jerry Helbling > Assignee: Jerry Helbling > Priority: Minor > Fix For: 6.0.0 > > > Refer to internal case 225071. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (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 updated TEIID-203: --------------------------------- Fix Version/s: 6.1.0 Affects Version/s: 6.0.0 Affects: [Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration, Release Notes] Complexity: High Priority: Major (was: Minor) > Make connector capabilites more granular. > ----------------------------------------- > > Key: TEIID-203 > URL: https://jira.jboss.org/jira/browse/TEIID-203 > Project: Teiid > Issue Type: Feature Request > 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-202) Salesforce connector should support SOQL Relationship Queries

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-202?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-202: --------------------------------- Component/s: Salesforce Connector Fix Version/s: 6.1.0 Affects Version/s: 6.0.0 > Salesforce connector should support SOQL Relationship Queries > ------------------------------------------------------------- > > Key: TEIID-202 > URL: https://jira.jboss.org/jira/browse/TEIID-202 > Project: Teiid > Issue Type: Feature Request > Components: Salesforce Connector > Affects Versions: 6.0.0 > Reporter: Greg Haber > Assignee: John Doyle > Fix For: 6.1.0 > > > [from loleary mail on 05-23-2008] > Looking at version 8.0 of the sforce API, it seems that SOQL supports > relationship queries. Although these are not JOIN queries, they > function in the same manner as long as the objects in question have a > relationship to the object being queried (i.e. primary/foreign keys). > The document explaining the syntax can be found at: > http://www.salesforce.com/us/developer/docs/api/Content/sforce_api_calls_... > [ghaber] If the salesforce connector had the ability to do relationship queries, it would be a big impact on performance accessing SFDC, given the high per-query cost of accessing SFDC, which makes doing the joins in MM (planned as dependent joins) fairly slow in Genentech's beta testing of the connector. > Since relationship joins require that the join be a LOJ or ROJ only, and further require that the join criteria be PK-FK relationships only, it would be best if these limitations could be reflected in capabilities - see JBEDSP-58 (and my comment on it specifically about Salesforce) for discussion of the desired capabilities API enhancements. > I believe that it is worthwhile to implement relationship joins even without resolution of JBEDSP-58, with joins that cannot be pushed down throwing an exception. You'd also want to have a connector binding property that enabled/disabled this relationship query support (with the join methods in the Capabilities interface returning true if this property is set to enabled and false if set to disabled), so that the SFDC connector could still be used in other join scenarios if necessary. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-205) Capabilities should be able to be specified in an XML file

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-205?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-205: --------------------------------- Component/s: Connector API Query Engine Server Affects: [Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration, Release Notes] The console also has an expert toggle so the capabilities overrides would not be visible by default. We may also want to change them in the config from boolean to string so that it's clearer when no value is supplied. > Capabilities should be able to be specified in an XML file > ---------------------------------------------------------- > > Key: TEIID-205 > URL: https://jira.jboss.org/jira/browse/TEIID-205 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Query Engine, Server > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 6.0.0 > > > Defect Tracker #24258: All connector capabilities should be specifiable in an XML format. Whether this is done directly through the connector binding or through an extension XML file is up to the implementor. This is needed to provide an easy way for users to over-ride default capabilities without creating new java classes. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-207) Forward and Backward Compatibility of MetaMatrix JDBC Driver

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-207?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-207: --------------------------------- Component/s: JDBC Driver Fix Version/s: 6.1.0 Affects Version/s: 6.0.0 Affects: [Compatibility/Configuration, Release Notes] > Forward and Backward Compatibility of MetaMatrix JDBC Driver > ------------------------------------------------------------ > > Key: TEIID-207 > URL: https://jira.jboss.org/jira/browse/TEIID-207 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Driver > Affects Versions: 6.0.0 > Reporter: Marc Shirley > Fix For: 6.1.0 > > > The MetaMatrix JDBC driver should be forward and backward compatible with newer/older versions of Enterprise Server. It is understood that certain protocol changes may break the compatibility but this should only happen in major releases and not affect Service Packs and maintenance releases. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-206) Create a project for federate-server-api

by Steven Hawkins (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-206?page=com.atlassian.jira.plug... ] Steven Hawkins updated TEIID-206: --------------------------------- Component/s: Server Fix Version/s: 6.1.0 Affects Version/s: 6.0.0 > Create a project for federate-server-api > ---------------------------------------- > > Key: TEIID-206 > URL: https://jira.jboss.org/jira/browse/TEIID-206 > Project: Teiid > Issue Type: Feature Request > Components: Server > Affects Versions: 6.0.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 6.1.0 > > > Create new project in the federate svn, "federate-server-api" that contains all the server side extension APIs that users/customers can extend to plugin into the server. These APIs are > - Membership API > - Command Logging API > - Logging API -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-161) Move common type conversion logic into a centralized facility for connectors

by Ramesh Reddy (JIRA)

[ https://jira.jboss.org/jira/browse/TEIID-161?page=com.atlassian.jira.plug... ] Ramesh Reddy updated TEIID-161: ------------------------------- Component/s: Connector API Query Engine Fix Version/s: 6.0.0 Affects Version/s: 6.0.0 > Move common type conversion logic into a centralized facility for connectors > ---------------------------------------------------------------------------- > > Key: TEIID-161 > URL: https://jira.jboss.org/jira/browse/TEIID-161 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 6.0.0 > > > Since we allow the flexibility for physical model types to not actually match source type (as in not simply the closest runtime type), every connector is currently responsible for not only converting to a known runtime type but potentially converting to the desired runtime type. This logic has been encapsulated behind the typefacility converttoruntimetype and transformvalue. It would be nice however to automatically handle the known 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, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2009