[JBoss JIRA] (TEIID-4612) Infinistpa DSL translator - table names are case sensitive
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIID-4612?page=com.atlassian.jira.plugin... ]
Work on TEIID-4612 stopped by Van Halbert.
------------------------------------------
> Infinistpa DSL translator - table names are case sensitive
> ----------------------------------------------------------
>
> Key: TEIID-4612
> URL: https://issues.jboss.org/browse/TEIID-4612
> Project: Teiid
> Issue Type: Bug
> Components: JDG Connector
> Affects Versions: 8.12.8.6_3
> Reporter: Juraj Duráni
> Assignee: Van Halbert
>
> Table names defined in DDL metadata are case sensitive.
> Example:
> This table name has exact name as object in JDG cache
> {code:sql|title=DDL metadata}
> CREATE FOREIGN TABLE SmallA (intKey integer PRIMARY KEY,...
> {code}
> This query executes correctly:
> {code:sql|title=Query}
> insert into smalla (intkey, stringkey) values (1, '1');
> {code}
> However, changing metadata to this:
> {code:sql|title=Updated DDL metadata}
> CREATE FOREIGN TABLE SMALLA (intKey integer PRIMARY KEY,...
> {code}
> Ends with error:
> {code:plain}
> 14:58:31,509 WARN [org.teiid.CONNECTOR] (Worker17_QueryProcessorQueue224) Connector worker process failed for atomic-request=sUTIOW6woCs0.0.0.57: org.teiid.translator.TranslatorException: TEIID21005 Registered Class not found for table reference SMALLA, check table name or nameInSouce to ensure one matches a registered class in the resource adapter
> at org.teiid.translator.object.util.ObjectUtil.getRegisteredClass(ObjectUtil.java:106) [translator-object-8.12.8.6_3-redhat-1.jar:8.12.8.6_3-redhat-1]
> at org.teiid.translator.object.ObjectUpdateExecution.executeUpdate(ObjectUpdateExecution.java:121) [translator-object-8.12.8.6_3-redhat-1.jar:8.12.8.6_3-redhat-1]
> at org.teiid.translator.object.ObjectUpdateExecution.execute(ObjectUpdateExecution.java:100) [translator-object-8.12.8.6_3-redhat-1.jar:8.12.8.6_3-redhat-1]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem$1.execute(ConnectorWorkItem.java:404) [teiid-engine-8.12.8.6_3-redhat-1.jar:8.12.8.6_3-redhat-1]
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:366) [teiid-engine-8.12.8.6_3-redhat-1.jar:8.12.8.6_3-redhat-1]
> at sun.reflect.GeneratedMethodAccessor90.invoke(Unknown Source) [:1.8.0-internal]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0-internal]
> at java.lang.reflect.Method.invoke(Method.java:483) [rt.jar:1.8.0-internal]
> at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) [teiid-engine-8.12.8.6_3-redhat-1.jar:8.12.8.6_3-redhat-1]
> at com.sun.proxy.$Proxy47.execute(Unknown Source)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) [teiid-engine-8.12.8.6_3-redhat-1.jar:8.12.8.6_3-redhat-1]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) [teiid-engine-8.12.8.6_3-redhat-1.jar:8.12.8.6_3-redhat-1]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) [teiid-engine-8.12.8.6_3-redhat-1.jar:8.12.8.6_3-redhat-1]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0-internal]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) [teiid-engine-8.12.8.6_3-redhat-1.jar:8.12.8.6_3-redhat-1]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:280) [teiid-engine-8.12.8.6_3-redhat-1.jar:8.12.8.6_3-redhat-1]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.12.8.6_3-redhat-1.jar:8.12.8.6_3-redhat-1]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) [teiid-engine-8.12.8.6_3-redhat-1.jar:8.12.8.6_3-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0-internal]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0-internal]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0-internal]
> {code}
> The error happens even with specified NAMEINSOURCE for the table:
> {code:sql|title=DDL metadata}
> CREATE FOREIGN TABLE SmallA (intKey integer PRIMARY KEY,...
> OPTIONS (NAMEINSOURCE 'SmallA', ...)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 5 months
[JBoss JIRA] (TEIID-4760) optional object name manipulations for import
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4760?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4760:
---------------------------------------
I've made this issue more generic, and created a new bug to capture the DDL issue.
> optional object name manipulations for import
> ---------------------------------------------
>
> Key: TEIID-4760
> URL: https://issues.jboss.org/browse/TEIID-4760
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Reporter: Bram Gadeyne
> Assignee: Steven Hawkins
> Labels: ddl, import, import_wizard
> Fix For: 10.3
>
>
> While importing, table (and other object) names are added to the schema with their original names.
> In our previous virtual database we imported two schema's that contain the same objects but one is a production and another is a historical database.
> We then change the name for e.g. table1 to prod_table1 or wh_table1 according to the schema it came from. Some software that interacts with teiid can not distinguish between different schemas and can not handle duplicate table names. So for this reason, this would also come in handy.
> It would come in handy if it is possible to add a prefix to names while importing objects.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 5 months
[JBoss JIRA] (TEIID-5347) low level MetadataFactory properties not honored by DDL import
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-5347:
-------------------------------------
Summary: low level MetadataFactory properties not honored by DDL import
Key: TEIID-5347
URL: https://issues.jboss.org/browse/TEIID-5347
Project: Teiid
Issue Type: Bug
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 10.3.2, 10.2.2
As described in TEIID-4760 the DDL import logic does not handle properties the same as XML vdbs which causes the low level properties dealing with auto correct, duplicates, and name format to not be honored.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 5 months
[JBoss JIRA] (TEIID-4760) optional object name manipulations for import
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4760?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4760:
----------------------------------
Description:
While importing, table (and other object) names are added to the schema with their original names.
In our previous virtual database we imported two schema's that contain the same objects but one is a production and another is a historical database.
We then change the name for e.g. table1 to prod_table1 or wh_table1 according to the schema it came from. Some software that interacts with teiid can not distinguish between different schemas and can not handle duplicate table names. So for this reason, this would also come in handy.
It would come in handy if it is possible to add a prefix to names while importing objects.
was:
While executing IMPORT FOREIGN SCHEMA, table (and other object) names are added to the schema with their original names.
In our previous virtual database we imported two schema's that contain the same objects but one is a production and another is a historical database.
We then change the name for e.g. table1 to prod_table1 or wh_table1 according to the schema it came from. Some software that interacts with teiid can not distinguish between different schemas and can not handle duplicate table names. So for this reason, this would also come in handy.
It would come in handy if it is possible to add a prefix to names while importing objects.
Summary: optional object name manipulations for import (was: optional object name manipulations while executing IMPORT FOREIGN SCHEMA)
> optional object name manipulations for import
> ---------------------------------------------
>
> Key: TEIID-4760
> URL: https://issues.jboss.org/browse/TEIID-4760
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Reporter: Bram Gadeyne
> Assignee: Steven Hawkins
> Labels: ddl, import, import_wizard
> Fix For: 10.3
>
>
> While importing, table (and other object) names are added to the schema with their original names.
> In our previous virtual database we imported two schema's that contain the same objects but one is a production and another is a historical database.
> We then change the name for e.g. table1 to prod_table1 or wh_table1 according to the schema it came from. Some software that interacts with teiid can not distinguish between different schemas and can not handle duplicate table names. So for this reason, this would also come in handy.
> It would come in handy if it is possible to add a prefix to names while importing objects.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 5 months
[JBoss JIRA] (TEIID-4760) optional object name manipulations while executing IMPORT FOREIGN SCHEMA
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4760?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-4760:
---------------------------------------
It works when using an XML VDB, but not DDL as an import option. There is a difference in the property handling such that DDL is adding the import properties after the MetadataFactory is constructed, which is too late. That means that all of the low level properties dealing with column name auto correction, duplicate handling, and name format are not handled in DDL. Sorry I made an invalid assumption that the DDL logic already accounted for this.
> optional object name manipulations while executing IMPORT FOREIGN SCHEMA
> ------------------------------------------------------------------------
>
> Key: TEIID-4760
> URL: https://issues.jboss.org/browse/TEIID-4760
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Reporter: Bram Gadeyne
> Assignee: Steven Hawkins
> Labels: ddl, import, import_wizard
> Fix For: 10.3
>
>
> While executing IMPORT FOREIGN SCHEMA, table (and other object) names are added to the schema with their original names.
> In our previous virtual database we imported two schema's that contain the same objects but one is a production and another is a historical database.
> We then change the name for e.g. table1 to prod_table1 or wh_table1 according to the schema it came from. Some software that interacts with teiid can not distinguish between different schemas and can not handle duplicate table names. So for this reason, this would also come in handy.
> It would come in handy if it is possible to add a prefix to names while importing objects.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 5 months
[JBoss JIRA] (TEIID-4760) optional object name manipulations while executing IMPORT FOREIGN SCHEMA
by Bram Gadeyne (JIRA)
[ https://issues.jboss.org/browse/TEIID-4760?page=com.atlassian.jira.plugin... ]
Bram Gadeyne commented on TEIID-4760:
-------------------------------------
[~shawkins],
I've tested this on 10.3.1 but it does not seem to work.
For the izisprod schema my import statements look like this.
{code:sql}
SET SCHEMA izisprod;
IMPORT FOREIGN SCHEMA dbo FROM SERVER izisprod INTO izisprod
OPTIONS(
importer.catalog 'master',
importer.schemaPattern 'dbo',
importer.importKeys false,
importer.importStatistics false,
importer.tableNamePattern 'syslogins',
importer.useFullSchemaName false,
importer.tableTypes 'SYSTEM TABLE',
importer.nameFormat 'prod_%s'
);
IMPORT FOREIGN SCHEMA dbo FROM SERVER izisprod INTO izisprod
OPTIONS(
importer.catalog 'master',
importer.schemaPattern 'dbo',
importer.importKeys false,
importer.importStatistics false,
importer.tableNamePattern 'sysprocesses',
importer.useFullSchemaName false,
importer.tableTypes 'SYSTEM TABLE',
importer.nameFormat 'prod_%s'
);
IMPORT FOREIGN SCHEMA dbo FROM SERVER izisprod INTO izisprod
OPTIONS(
importer.catalog 'Patient',
importer.schemaPattern 'dbo',
importer.importKeys false,
importer.importStatistics false,
importer.useFullSchemaName false,
importer.tableTypes 'TABLE,VIEW',
importer.nameFormat 'prod_%s'
);
IMPORT FOREIGN SCHEMA dbo FROM SERVER izisprod INTO izisprod
OPTIONS(
importer.catalog 'System',
importer.schemaPattern 'dbo',
importer.importKeys false,
importer.importStatistics false,
importer.useFullSchemaName false,
importer.excludeTables '.*U_PV_PatientLocation.*',
importer.tableTypes 'TABLE,VIEW',
importer.nameFormat 'prod_%s'
);
IMPORT FOREIGN SCHEMA dbo FROM SERVER izisprod INTO izisprod
OPTIONS(
importer.catalog 'Department',
importer.schemaPattern 'dbo',
importer.importKeys false,
importer.importStatistics false,
importer.useFullSchemaName false,
importer.excludeTables '.*sysquerymetrics.*',
importer.tableTypes 'TABLE,VIEW',
importer.nameFormat 'prod_%s'
);
{code}
In the resulting schema the table and view names don't have a prefix "prod_".
> optional object name manipulations while executing IMPORT FOREIGN SCHEMA
> ------------------------------------------------------------------------
>
> Key: TEIID-4760
> URL: https://issues.jboss.org/browse/TEIID-4760
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Reporter: Bram Gadeyne
> Assignee: Steven Hawkins
> Labels: ddl, import, import_wizard
> Fix For: 10.3
>
>
> While executing IMPORT FOREIGN SCHEMA, table (and other object) names are added to the schema with their original names.
> In our previous virtual database we imported two schema's that contain the same objects but one is a production and another is a historical database.
> We then change the name for e.g. table1 to prod_table1 or wh_table1 according to the schema it came from. Some software that interacts with teiid can not distinguish between different schemas and can not handle duplicate table names. So for this reason, this would also come in handy.
> It would come in handy if it is possible to add a prefix to names while importing objects.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 5 months
[JBoss JIRA] (TEIID-5346) Improve costing of literals even with unknown values
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-5346?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5346:
---------------------------------------
I have the changes ready for this. The only downside is that we are more aggressive in creating dependent joins - which in testing scenarios don't appear to be necessary much like the one created by TEIID-5345. I'll spend a little more time on this to see if we can do more to prevent the unnecessary dependent joins.
> Improve costing of literals even with unknown values
> ----------------------------------------------------
>
> Key: TEIID-5346
> URL: https://issues.jboss.org/browse/TEIID-5346
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 11.0
>
>
> In the nodes above a projected literal if there are unknown cardinalities will become ndv unknown - rather than the expected ndv/nnv.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 5 months