[teiid-issues] [JBoss JIRA] (TEIID-4900) limit to / exclude import option issues

[Steven Hawkins (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-4900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steven Hawkins updated TEIID-4900:
----------------------------------
    Description: 
TEIID-4899 removed support for LIMIT TO / EXCLUDE since the semantics of LIMIT TO / EXCLUDE does not match the regex base support in several of the translators.  Also JDBC does not support a specific include, only exclude.

There are two options:

These need to be handled at the engine level as general options instead - and leave the import settings to be importer specific.  However that requires generic logic for repairing the metadata should a foreign key or other references be made to an excluded table.

If they are mapped to translator options then we'll need to translate the table names in the an appropriate regex expression.

  was:
The import LIMIT TO option is not implemented by any importer.   Mapping to importer.includeTables effectively does nothing.

Also the semantics of exclude does not match the regex based exclusion supported by the jdbc translator.

These need to be handled at the engine level as general options instead - and leave the import settings to be importer specific.



> limit to / exclude import option issues
> ---------------------------------------
>
>                 Key: TEIID-4900
>                 URL: https://issues.jboss.org/browse/TEIID-4900
>             Project: Teiid
>          Issue Type: Sub-task
>          Components: Misc. Connectors, Query Engine
>    Affects Versions: 9.2
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 10.x
>
>
> TEIID-4899 removed support for LIMIT TO / EXCLUDE since the semantics of LIMIT TO / EXCLUDE does not match the regex base support in several of the translators.  Also JDBC does not support a specific include, only exclude.
> There are two options:
> These need to be handled at the engine level as general options instead - and leave the import settings to be importer specific.  However that requires generic logic for repairing the metadata should a foreign key or other references be made to an excluded table.
> If they are mapped to translator options then we'll need to translate the table names in the an appropriate regex expression.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)