April 2014 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2103) NPE validating transformation

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-2103: -------------------------------------- Summary: NPE validating transformation Key: TEIIDDES-2103 URL: https://issues.jboss.org/browse/TEIIDDES-2103 Project: Teiid Designer Issue Type: Bug Components: Transformations Affects Versions: 8.5 Reporter: Barry LaFond Assignee: Paul Richardson Fix For: 8.5 Think this one was obvious... the "result" value is actually not returned. {code:title=org.teiid.runtime.client.Constant} @Override public int hashCode() { final int prime = 31; int result = super.hashCode(); if(this.value != null && !isMultiValued()) { if (this.value instanceof BigDecimal) { BigDecimal bd = (BigDecimal)this.value; int xsign = bd.signum(); if (xsign == 0) return 0; bd = bd.stripTrailingZeros(); result = prime * result + bd.hashCode(); } result = prime * result + this.value.hashCode(); } return this.value.hashCode(); } {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2102) Replace teiid client plugins in the client runtime feature

by Paul Richardson (JIRA)

Paul Richardson created TEIIDDES-2102: ----------------------------------------- Summary: Replace teiid client plugins in the client runtime feature Key: TEIIDDES-2102 URL: https://issues.jboss.org/browse/TEIIDDES-2102 Project: Teiid Designer Issue Type: Task Components: Eclipse Integration Affects Versions: 8.5 Reporter: Paul Richardson Both the deprecated teiid-client plugins (7.7.x, 8.3.x, 8.4.x) and the new teiid-client-runtime plugin are included in the maven build configuration. Only the deprecated plugins are included in the teiid-runtime feature. These need to be rectified once further testing of the teiid-client-runtime plugin has been performed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2102) Replace teiid client plugins in the client runtime feature

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2102?page=com.atlassian.jira.plu... ] Paul Richardson reassigned TEIIDDES-2102: ----------------------------------------- Assignee: Paul Richardson > Replace teiid client plugins in the client runtime feature > ---------------------------------------------------------- > > Key: TEIIDDES-2102 > URL: https://issues.jboss.org/browse/TEIIDDES-2102 > Project: Teiid Designer > Issue Type: Task > Components: Eclipse Integration > Affects Versions: 8.5 > Reporter: Paul Richardson > Assignee: Paul Richardson > > Both the deprecated teiid-client plugins (7.7.x, 8.3.x, 8.4.x) and the new teiid-client-runtime plugin are included in the maven build configuration. > Only the deprecated plugins are included in the teiid-runtime feature. > These need to be rectified once further testing of the teiid-client-runtime plugin has been performed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2097) JDBC Importer fails when importing Access 2013 metadata via JDBC ODBC bridge

by Takayuki Konishi (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2097?page=com.atlassian.jira.plu... ] Takayuki Konishi updated TEIIDDES-2097: --------------------------------------- Description: Probably related to TEIID-2912 Environment: * MS Access 2013 * MS Windows Server 2012 Steps to reproduce: * Created a JDBC ODBC bridge connection profile (class: sun.jdbc.odbc.JdbcOdbcDriver) * Trying to import using JDBC importer, no tables are shown was: Related to: https://c.na7.visual.force.com/apex/Case_View?id=500A000000HozJc&sfdc.ove... Probably related to TEIID-2912 Environment: * MS Access 2013 * MS Windows Server 2012 Steps to reproduce: * Created a JDBC ODBC bridge connection profile (class: sun.jdbc.odbc.JdbcOdbcDriver) * Trying to import using JDBC importer, no tables are shown > JDBC Importer fails when importing Access 2013 metadata via JDBC ODBC bridge > ---------------------------------------------------------------------------- > > Key: TEIIDDES-2097 > URL: https://issues.jboss.org/browse/TEIIDDES-2097 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Filip Nguyen > Priority: Blocker > Attachments: DSN.png, ODBCTesting.mdb > > > Probably related to TEIID-2912 > Environment: > * MS Access 2013 > * MS Windows Server 2012 > Steps to reproduce: > * Created a JDBC ODBC bridge connection profile (class: sun.jdbc.odbc.JdbcOdbcDriver) > * Trying to import using JDBC importer, no tables are shown -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2097) JDBC Importer fails when importing Access 2013 metadata via JDBC ODBC bridge

by Takayuki Konishi (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2097?page=com.atlassian.jira.plu... ] Takayuki Konishi updated TEIIDDES-2097: --------------------------------------- > JDBC Importer fails when importing Access 2013 metadata via JDBC ODBC bridge > ---------------------------------------------------------------------------- > > Key: TEIIDDES-2097 > URL: https://issues.jboss.org/browse/TEIIDDES-2097 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Filip Nguyen > Priority: Blocker > Attachments: DSN.png, ODBCTesting.mdb > > > Probably related to TEIID-2912 > Environment: > * MS Access 2013 > * MS Windows Server 2012 > Steps to reproduce: > * Created a JDBC ODBC bridge connection profile (class: sun.jdbc.odbc.JdbcOdbcDriver) > * Trying to import using JDBC importer, no tables are shown -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2097) JDBC Importer fails when importing Access 2013 metadata via JDBC ODBC bridge

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2097?page=com.atlassian.jira.plu... ] Van Halbert commented on TEIIDDES-2097: --------------------------------------- I assume the workaround could be to use Teiid Connection importer, and specify the same properties indicated in TEIID-2912: <property name="importer.importKeys" value="false"/> <property name="importer.excludeTables" value=".*MSys.*"/> > JDBC Importer fails when importing Access 2013 metadata via JDBC ODBC bridge > ---------------------------------------------------------------------------- > > Key: TEIIDDES-2097 > URL: https://issues.jboss.org/browse/TEIIDDES-2097 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Filip Nguyen > Priority: Blocker > Attachments: DSN.png, ODBCTesting.mdb > > > Related to: https://c.na7.visual.force.com/apex/Case_View?id=500A000000HozJc&sfdc.ove... > Probably related to TEIID-2912 > Environment: > * MS Access 2013 > * MS Windows Server 2012 > Steps to reproduce: > * Created a JDBC ODBC bridge connection profile (class: sun.jdbc.odbc.JdbcOdbcDriver) > * Trying to import using JDBC importer, no tables are shown -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2097) JDBC Importer fails when importing Access 2013 metadata via JDBC ODBC bridge

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2097?page=com.atlassian.jira.plu... ] Van Halbert commented on TEIIDDES-2097: --------------------------------------- Did we determine what needs to be fixed? > JDBC Importer fails when importing Access 2013 metadata via JDBC ODBC bridge > ---------------------------------------------------------------------------- > > Key: TEIIDDES-2097 > URL: https://issues.jboss.org/browse/TEIIDDES-2097 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Filip Nguyen > Priority: Blocker > Attachments: DSN.png, ODBCTesting.mdb > > > Related to: https://c.na7.visual.force.com/apex/Case_View?id=500A000000HozJc&sfdc.ove... > Probably related to TEIID-2912 > Environment: > * MS Access 2013 > * MS Windows Server 2012 > Steps to reproduce: > * Created a JDBC ODBC bridge connection profile (class: sun.jdbc.odbc.JdbcOdbcDriver) > * Trying to import using JDBC importer, no tables are shown -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2060) Cannot select encoding when file model execute preview data

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2060?page=com.atlassian.jira.plu... ] Barry LaFond edited comment on TEIIDDES-2060 at 4/3/14 3:30 PM: ---------------------------------------------------------------- After conversation with Ramesh today... 1) Copying VDB Editors Translator property editor out to the workspace > Either add a "Translator" Properties tab for editing or an action/dialog .... *Edit Translator Override Properties" 2) Inject TO properties (i.e. non-default values) into a source model 3) When adding/synching Source Models in a VDB, extract these TOPs and inject them into the VDB XML with a auto-generated override name 4) User can always tweak/change these TOPs in a VDB editor. Note: it was agreed that TOPs are designed to be source-model-specific and not Data Source type-specific, so managing them for the purpose of re-use doesn't make sense at this time was (Author: blafond): After conversation with Ramesh today... 1) Copying VDB Editors Translator property editor out to the workspace > Either add a "Translator" Properties tab for editing or an action/dialog .... *Edit Translator Override Properties" 2) Inject TO properties (i.e. non-default values) into a source model 3) When adding/synching Source Models in a VDB, extract these TOPs and inject them into the VDB XML with a auto-generated override name 4) User can always tweak/change these TOPs in a VDB editor. Note: it was agreed that TOPs are designed to be source-specific and not Data Source type-specific, so managing them for the purpose of re-use doesn't make sense at this time > Cannot select encoding when file model execute preview data > ----------------------------------------------------------- > > Key: TEIIDDES-2060 > URL: https://issues.jboss.org/browse/TEIIDDES-2060 > Project: Teiid Designer > Issue Type: Bug > Components: Data Preview > Affects Versions: 8.3.1 > Reporter: Eiichi Nagai > Assignee: Barry LaFond > Priority: Blocker > Fix For: 8.5 > > > Teiid designer can select file encoding when create file model using import function. However, it does not effect preview data function and actual VDB. > Actual VDB can set encoding by overriding file translator property. However, VDB for preview data function is created by automatically in teiid designer, so we cannot set encoding. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2060) Cannot select encoding when file model execute preview data

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2060?page=com.atlassian.jira.plu... ] Van Halbert commented on TEIIDDES-2060: --------------------------------------- Not sure I agree with your note, because TOP's are based on the translator that's being used (maybe I misunderstood what you meant by Data Source type-specific). Change the translator, the TOP's could be meaningless, depending on what the translator was changed to. But I do agree that it re-use doesn't make sense. > Cannot select encoding when file model execute preview data > ----------------------------------------------------------- > > Key: TEIIDDES-2060 > URL: https://issues.jboss.org/browse/TEIIDDES-2060 > Project: Teiid Designer > Issue Type: Bug > Components: Data Preview > Affects Versions: 8.3.1 > Reporter: Eiichi Nagai > Assignee: Barry LaFond > Priority: Blocker > Fix For: 8.5 > > > Teiid designer can select file encoding when create file model using import function. However, it does not effect preview data function and actual VDB. > Actual VDB can set encoding by overriding file translator property. However, VDB for preview data function is created by automatically in teiid designer, so we cannot set encoding. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2101) Query resolution fails on procedure that references XmlDocument

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2101?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-2101. ------------------------------------- Resolution: Done Problem was TransformationMetadata.getMappingNode was always returning null pull request for master and 8.3.x https://github.com/Teiid-Designer/teiid-designer/pull/318 https://github.com/Teiid-Designer/teiid-designer/pull/319 > Query resolution fails on procedure that references XmlDocument > --------------------------------------------------------------- > > Key: TEIIDDES-2101 > URL: https://issues.jboss.org/browse/TEIIDDES-2101 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 8.3.1 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.5, 8.3.1 > > > Procedure from customer case fails to validate, with no description. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues April 2014