March 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2418) Converting all source symbol data types not reflected in Type Resolver

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2418?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2418: ----------------------------------- Fix Version/s: 8.6.2 Beta1 9.0.2 Beta1 > Converting all source symbol data types not reflected in Type Resolver > ---------------------------------------------------------------------- > > Key: TEIIDDES-2418 > URL: https://issues.jboss.org/browse/TEIIDDES-2418 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs, Transformations > Affects Versions: 9.0.2 > Reporter: Andrej Šmigala > Assignee: Mark Drilling > Priority: Minor > Fix For: 9.1, 8.6.2 Beta1, 9.0.2 Beta1, 9.0.2, 8.6.2 > > Attachments: TyperesolverProject.zip > > > When using the Type Resolver, clicking the Convert all source SQL symbol datatypes does not show the changed expression in the Source SQL Symbol column. Other than that, it works as expected, i.e. the type conflict message goes away, and after clicking OK, the Reconciller actually contains the correct CONVERT statements. > However, clicking the left arrows for each column correctly changes the Source SQL Symbol. > Clicking Change all target column datatypes shows similar behaviour. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2418) Converting all source symbol data types not reflected in Type Resolver

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2418?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2418: ---------------------------------------- 9.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/961a6a7006bbcaab5... 8.6.x: https://github.com/Teiid-Designer/teiid-designer/commit/3cfc6319690cf4cd7... > Converting all source symbol data types not reflected in Type Resolver > ---------------------------------------------------------------------- > > Key: TEIIDDES-2418 > URL: https://issues.jboss.org/browse/TEIIDDES-2418 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs, Transformations > Affects Versions: 9.0.2 > Reporter: Andrej Šmigala > Assignee: Mark Drilling > Priority: Minor > Fix For: 9.1, 9.0.2, 8.6.2 > > Attachments: TyperesolverProject.zip > > > When using the Type Resolver, clicking the Convert all source SQL symbol datatypes does not show the changed expression in the Source SQL Symbol column. Other than that, it works as expected, i.e. the type conflict message goes away, and after clicking OK, the Reconciller actually contains the correct CONVERT statements. > However, clicking the left arrows for each column correctly changes the Source SQL Symbol. > Clicking Change all target column datatypes shows similar behaviour. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2453) Kerberos support for Connection Profile wizard

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2453?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2453: ---------------------------------------- [~cb11] if you got the DDL, all you need to do is in Designer use "DDL Importer" import option to create a source model. > Kerberos support for Connection Profile wizard > ---------------------------------------------- > > Key: TEIIDDES-2453 > URL: https://issues.jboss.org/browse/TEIIDDES-2453 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 8.3.4 > Reporter: Hisanobu Okuda > > Need Kerberos support for Connection Profile wizard to import meta data from a data source. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2398) Inconsistent column datatypes when importing

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2398?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2398: ---------------------------------------- The problem we're getting into is that Designer is still supporting more and different datatypes than the Teiid Runtime. For example the SMALLINT and INT types below end up with different Design-time types: JDBC Import >>> | *NATIVE TYPE* | *JDBC Type* | *Design Time Type* | | SMALLINT | SMALLINT | *short* | | INT | INT | *int* | Teiid Connection Import >>> | *NATIVE TYPE* | *DDL Type* | *Design Time Type* | | SMALLINT | integer | *int* | | INT | long | *long* | So we can change the JDBC mapping to try and match the Teiid Runtime type, but all it has is NATIVE TYPE, but maybe that's enough? > Inconsistent column datatypes when importing > -------------------------------------------- > > Key: TEIIDDES-2398 > URL: https://issues.jboss.org/browse/TEIIDDES-2398 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Modeling > Reporter: Andrej Šmigala > Assignee: Mark Drilling > Fix For: 9.1, 9.0.2, 8.6.2 > > Attachments: datatypes.png, MySQL_BQT_DDL.ddl > > > There are multiple discrepancies in the column datatypes when importing using JDBC importer vs when using Teiid Connection importer. > Also some of the imported datatypes seem completely wrong (e.g. bigdecimal for almost all numeric datatypes in oracle) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2453) Kerberos support for Connection Profile wizard

by Corey Barrett (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2453?page=com.atlassian.jira.plu... ] Corey Barrett commented on TEIIDDES-2453: ----------------------------------------- Hi Ramesh, We have been spending the last couple of weeks trying to figure out the alternative solution: "...generating the DDL for your Coludera schema externally and then importing into Designer. " Is there a good set of steps for doing this? We have reviewed the following links. http://docs.jboss.org/teiid/7.6.0.Final/quick-start-example/en-US/html/bu... http://teiid.blogspot.com/2012/03/dynamic-vdbs-are-back-with-punch.html https://docs.jboss.org/author/display/TEIID/Dynamic+VDBs but don't understand where to place the file, nor do we see the any example dynamic vdb that were referenced in the instructions to follow. > Kerberos support for Connection Profile wizard > ---------------------------------------------- > > Key: TEIIDDES-2453 > URL: https://issues.jboss.org/browse/TEIIDDES-2453 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 8.3.4 > Reporter: Hisanobu Okuda > > Need Kerberos support for Connection Profile wizard to import meta data from a data source. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2418) Converting all source symbol data types not reflected in Type Resolver

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2418?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-2418. ------------------------------------- Resolution: Done The refresh method calls were incorrect in DatatypeReconcilerPanel. We were incorrectly passing a 'true' arg. For full table refresh, now using the no arg refresh method. Restested OK for me. https://github.com/Teiid-Designer/teiid-designer/pull/443 > Converting all source symbol data types not reflected in Type Resolver > ---------------------------------------------------------------------- > > Key: TEIIDDES-2418 > URL: https://issues.jboss.org/browse/TEIIDDES-2418 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs, Transformations > Affects Versions: 9.0.2 > Reporter: Andrej Šmigala > Assignee: Mark Drilling > Priority: Minor > Fix For: 9.1, 9.0.2, 8.6.2 > > Attachments: TyperesolverProject.zip > > > When using the Type Resolver, clicking the Convert all source SQL symbol datatypes does not show the changed expression in the Source SQL Symbol column. Other than that, it works as expected, i.e. the type conflict message goes away, and after clicking OK, the Reconciller actually contains the correct CONVERT statements. > However, clicking the left arrows for each column correctly changes the Source SQL Symbol. > Clicking Change all target column datatypes shows similar behaviour. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2405) Teiid Importer *MUST* not require class-name property working with Teiid Sources

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2405?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2405: ---------------------------------------- Thanks [~mdrillin], will test once 9.0.2 is available > Teiid Importer *MUST* not require class-name property working with Teiid Sources > -------------------------------------------------------------------------------- > > Key: TEIIDDES-2405 > URL: https://issues.jboss.org/browse/TEIIDDES-2405 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.6 > Reporter: Ramesh Reddy > Assignee: Mark Drilling > Priority: Critical > Fix For: 9.1, 8.6.2 Beta1, 9.0.2 Beta1, 9.0.2, 8.6.2 > > Attachments: cassandra-ra.txt > > > When working with "new" and "custom" translators in Teiid, the Teiid Importer fails to recognize the class-name property from the retrieved metadata. The following the excerpt from CLI command on a cassandra data source > {code} > {"managedconnectionfactory-class" => { > "type" => STRING, > "display" => "managedconnectionfactory-class", > "read-only" => "true", > "advanced" => "true", > "default" => "org.teiid.resource.adapter.cassandra.CassandraManagedConnectionFactory" > }}, > {code} > That property needs to be used as the "class-name", there must not be any hard coding of this to only known source types. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2405) Teiid Importer *MUST* not require class-name property working with Teiid Sources

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2405?page=com.atlassian.jira.plu... ] Mark Drilling commented on TEIIDDES-2405: ----------------------------------------- [~rareddy] this was code reviewed with [~blafond] - no there are no hardcoded names. To our knowledge it is working as expected. recommend additional testing by QE to verify. > Teiid Importer *MUST* not require class-name property working with Teiid Sources > -------------------------------------------------------------------------------- > > Key: TEIIDDES-2405 > URL: https://issues.jboss.org/browse/TEIIDDES-2405 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.6 > Reporter: Ramesh Reddy > Assignee: Mark Drilling > Priority: Critical > Fix For: 9.1, 8.6.2 Beta1, 9.0.2 Beta1, 9.0.2, 8.6.2 > > Attachments: cassandra-ra.txt > > > When working with "new" and "custom" translators in Teiid, the Teiid Importer fails to recognize the class-name property from the retrieved metadata. The following the excerpt from CLI command on a cassandra data source > {code} > {"managedconnectionfactory-class" => { > "type" => STRING, > "display" => "managedconnectionfactory-class", > "read-only" => "true", > "advanced" => "true", > "default" => "org.teiid.resource.adapter.cassandra.CassandraManagedConnectionFactory" > }}, > {code} > That property needs to be used as the "class-name", there must not be any hard coding of this to only known source types. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2405) Teiid Importer *MUST* not require class-name property working with Teiid Sources

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2405?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2405: ---------------------------------------- [~mdrillin]I just want to make the solution you are providing works with *any* custom translator that is deployed into the Teiid runtime, not just to known types of translators. We should not depend upon *any* hard coded names/class-names any where. I have not looked at your code, but just wanting to confirm. > Teiid Importer *MUST* not require class-name property working with Teiid Sources > -------------------------------------------------------------------------------- > > Key: TEIIDDES-2405 > URL: https://issues.jboss.org/browse/TEIIDDES-2405 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.6 > Reporter: Ramesh Reddy > Assignee: Mark Drilling > Priority: Critical > Fix For: 9.1, 8.6.2 Beta1, 9.0.2 Beta1, 9.0.2, 8.6.2 > > Attachments: cassandra-ra.txt > > > When working with "new" and "custom" translators in Teiid, the Teiid Importer fails to recognize the class-name property from the retrieved metadata. The following the excerpt from CLI command on a cassandra data source > {code} > {"managedconnectionfactory-class" => { > "type" => STRING, > "display" => "managedconnectionfactory-class", > "read-only" => "true", > "advanced" => "true", > "default" => "org.teiid.resource.adapter.cassandra.CassandraManagedConnectionFactory" > }}, > {code} > That property needs to be used as the "class-name", there must not be any hard coding of this to only known source types. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2398) Inconsistent column datatypes when importing

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2398?page=com.atlassian.jira.plu... ] Mark Drilling updated TEIIDDES-2398: ------------------------------------ Attachment: MySQL_BQT_DDL.ddl We are processing the DDL from teiid. For example on the MySQL 'MediumB' table the DDL specifies the IntKey type as 'long'. See attached DDL. Need to check with teiid about the DDL generation and processing > Inconsistent column datatypes when importing > -------------------------------------------- > > Key: TEIIDDES-2398 > URL: https://issues.jboss.org/browse/TEIIDDES-2398 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Modeling > Reporter: Andrej Šmigala > Assignee: Mark Drilling > Fix For: 9.1, 9.0.2, 8.6.2 > > Attachments: datatypes.png, MySQL_BQT_DDL.ddl > > > There are multiple discrepancies in the column datatypes when importing using JDBC importer vs when using Teiid Connection importer. > Also some of the imported datatypes seem completely wrong (e.g. bigdecimal for almost all numeric datatypes in oracle) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues March 2015