May 2018 - teiid-issues - Jboss List Archives

[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)

6 years, 7 months

1
0
0 / 0

[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)

6 years, 7 months

1
0
0 / 0

[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)

6 years, 7 months

1
0
0 / 0

[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)

6 years, 7 months

1
0
0 / 0

[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)

6 years, 7 months

1
0
0 / 0

[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)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5009) Add license files to JDBC Driver

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5009?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5009. ----------------------------------- Resolution: Out of Date > Add license files to JDBC Driver > -------------------------------- > > Key: TEIID-5009 > URL: https://issues.jboss.org/browse/TEIID-5009 > Project: Teiid > Issue Type: Task > Components: JDBC Driver > Affects Versions: 8.12.11.6_4, 11.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Blocker > > Adding the license.xml and license.html files to the jdbc driver. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5179) Upgrade hadoop-core jar

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5179?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5179. ----------------------------------- Resolution: Out of Date Resolving as out of date as this is not a community issue and I believe we already addressed on the product side. > Upgrade hadoop-core jar > ----------------------- > > Key: TEIID-5179 > URL: https://issues.jboss.org/browse/TEIID-5179 > Project: Teiid > Issue Type: Quality Risk > Components: Build/Kits, Misc. Connectors > Affects Versions: 8.12.11.6_4 > Reporter: Van Halbert > Assignee: Van Halbert > > The current version of jar: hadoop-core-0.20.2.jar needs to be looked at for upgrading to the 1.+ version. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5302) Support integration with MapR-DB (MapR 5.2.x, 6.x)

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5302?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5302: ---------------------------------- Fix Version/s: Open To Community > Support integration with MapR-DB (MapR 5.2.x, 6.x) > -------------------------------------------------- > > Key: TEIID-5302 > URL: https://issues.jboss.org/browse/TEIID-5302 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Craig Carpenter > Fix For: Open To Community > > > As a user of Teiid, I need to be able to reference MapR-DB as a datasource to incorporate full data content into Teiid (VDB). > To accept, at a minimum, data read, support should be based on (at least) the current 6.x release. Ideally full RUD support would be available. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-160) Remove redundant self-joins

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-160?page=com.atlassian.jira.plugin.... ] Steven Hawkins resolved TEIID-160. ---------------------------------- Resolution: Deferred > Remove redundant self-joins > --------------------------- > > Key: TEIID-160 > URL: https://issues.jboss.org/browse/TEIID-160 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Steven Hawkins > Priority: Minor > Original Estimate: 2 days > Remaining Estimate: 2 days > > Query minimization should be used to remove self-joins on unique columns. This could be added as part of RuleRemoveOptionalJoins (but the rule may need to be run again after join planning). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2018