Uploaded image for project: 'Teiid'
  1. Teiid
  2. TEIID-203

Make connector capabilites more granular.

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 6.1.0
    • 6.0.0
    • Connector API, Query Engine
    • None
    • Documentation (Ref Guide, User Guide, etc.), Release Notes, Compatibility/Configuration
    • High

    Description

      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.

      Attachments

        Issue Links

          blocks

          Feature Request - Feature requests from customers and/or users TEIID-103 Salesforce Connector: Count(*) did not appear to pushdown to SOQL.

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed
          relates to

          Feature Request - Feature requests from customers and/or users TEIID-202 Salesforce connector should support SOQL Relationship Queries

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Feature Request - Feature requests from customers and/or users TEIID-152 New SQL directive OPTION NOJOINPUSHDOWN that tells query planner to not push down any joins

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Feature Request - Feature requests from customers and/or users TEIID-181 Allow connectors to request replanning of source query by throwing an exception

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              rhn-engineering-shawkins Steven Hawkins
              rhn-engineering-jdoyle John Doyle
              Votes:
              1 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: