April 2017 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-3046) Unable to preview data of file-based data source when the JNDI name already exist on the server runtime

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3046?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-3046: ---------------------------------------- [~rareddy] So what are the rules for data source *uniqueness*? So can 2 data sources have unique *pool-name*'s but the same *jndi-name* ? > Unable to preview data of file-based data source when the JNDI name already exist on the server runtime > ------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-3046 > URL: https://issues.jboss.org/browse/TEIIDDES-3046 > Project: Teiid Designer > Issue Type: Bug > Components: Data Preview > Affects Versions: 10.0.2 > Environment: MacOS > Red Hat JBoss Developer Studio 10.3.0.GA with JBoss Developer Studio Integration Stack 10.0.2 installed > Reporter: Cojan van Ballegooijen > Assignee: Barry LaFond > Fix For: 11.0.2 > > Attachments: Screen Shot 2017-03-01 at 10.16.26.png, Screen Shot 2017-03-01 at 10.16.46.png > > > If a data source is already created on the JDV server runtime unable to preview data on the models. > Workaround is to add these models into a VDB, deploy/execute VDB but Preview data should work despite the fact that the datasource JNDI names already exists on the server side. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3046) Unable to preview data of file-based data source when the JNDI name already exist on the server runtime

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3046?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-3046: ---------------------------------------- Yes, what is returned is not the JNDI name, but pool name. > Unable to preview data of file-based data source when the JNDI name already exist on the server runtime > ------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-3046 > URL: https://issues.jboss.org/browse/TEIIDDES-3046 > Project: Teiid Designer > Issue Type: Bug > Components: Data Preview > Affects Versions: 10.0.2 > Environment: MacOS > Red Hat JBoss Developer Studio 10.3.0.GA with JBoss Developer Studio Integration Stack 10.0.2 installed > Reporter: Cojan van Ballegooijen > Assignee: Barry LaFond > Fix For: 11.0.2 > > Attachments: Screen Shot 2017-03-01 at 10.16.26.png, Screen Shot 2017-03-01 at 10.16.46.png > > > If a data source is already created on the JDV server runtime unable to preview data on the models. > Workaround is to add these models into a VDB, deploy/execute VDB but Preview data should work despite the fact that the datasource JNDI names already exists on the server side. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3046) Unable to preview data of file-based data source when the JNDI name already exist on the server runtime

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3046?page=com.atlassian.jira.plu... ] Barry LaFond edited comment on TEIIDDES-3046 at 4/13/17 3:43 PM: ----------------------------------------------------------------- [~rareddy] Ran through the steps and reproduced this issue. With any data source configured though Designer, we're giving the Admin API a JNDI name. When we ask the Admin API for the data source names, this name shows up in the list. However, in the above scenario, the JNDI name isn't in the list of data sources, but the *pool-name* (i.e. fileDS) is the name of the data source. In Designer, we've been assuming that JNDI name was the "key/name" of each Teiid data source object. I looked through your Admin8Factory, but I couldn't tell from the logic what *names* were getting gathered and from where. Should we, instead, assume that the getDataSourceNames() returns a list of pool-name's and then have a method to obtain the JNDI name property whenever needed? I think this would clean up this issue.... was (Author: blafond): [~rareddy] Ran through the steps and reproduced this issue. With any data source configured though Designer, we're giving the Admin API a JNDI name. When we ask the Admin API for the data source names, this name shows up in the list. However, in the above scenario, the JNDI name isn't in the list of data sources, but the *pool-name* (i.e. fileDS) is the name of the data source. In Designer, we've been assuming that JNDI name was the "key/name" of each Teiid data source object. Should we, instead, assume that the getDataSourceNames() returns a list of pool-name's and then have a method to obtain the JNDI name property whenever needed? I think this would clean up this issue.... > Unable to preview data of file-based data source when the JNDI name already exist on the server runtime > ------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-3046 > URL: https://issues.jboss.org/browse/TEIIDDES-3046 > Project: Teiid Designer > Issue Type: Bug > Components: Data Preview > Affects Versions: 10.0.2 > Environment: MacOS > Red Hat JBoss Developer Studio 10.3.0.GA with JBoss Developer Studio Integration Stack 10.0.2 installed > Reporter: Cojan van Ballegooijen > Assignee: Barry LaFond > Fix For: 11.0.2 > > Attachments: Screen Shot 2017-03-01 at 10.16.26.png, Screen Shot 2017-03-01 at 10.16.46.png > > > If a data source is already created on the JDV server runtime unable to preview data on the models. > Workaround is to add these models into a VDB, deploy/execute VDB but Preview data should work despite the fact that the datasource JNDI names already exists on the server side. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3046) Unable to preview data of file-based data source when the JNDI name already exist on the server runtime

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3046?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-3046: ---------------------------------------- [~rareddy] Ran through the steps and reproduced this issue. With any data source configured though Designer, we're giving the Admin API a JNDI name. When we ask the Admin API for the data source names, this name shows up in the list. However, in the above scenario, the JNDI name isn't in the list of data sources, but the *pool-name* (i.e. fileDS) is the name of the data source. In Designer, we've been assuming that JNDI name was the "key/name" of each Teiid data source object. Should we, instead, assume that the getDataSourceNames() returns a list of pool-name's and then have a method to obtain the JNDI name property whenever needed? I think this would clean up this issue.... > Unable to preview data of file-based data source when the JNDI name already exist on the server runtime > ------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-3046 > URL: https://issues.jboss.org/browse/TEIIDDES-3046 > Project: Teiid Designer > Issue Type: Bug > Components: Data Preview > Affects Versions: 10.0.2 > Environment: MacOS > Red Hat JBoss Developer Studio 10.3.0.GA with JBoss Developer Studio Integration Stack 10.0.2 installed > Reporter: Cojan van Ballegooijen > Assignee: Barry LaFond > Fix For: 11.0.2 > > Attachments: Screen Shot 2017-03-01 at 10.16.26.png, Screen Shot 2017-03-01 at 10.16.46.png > > > If a data source is already created on the JDV server runtime unable to preview data on the models. > Workaround is to add these models into a VDB, deploy/execute VDB but Preview data should work despite the fact that the datasource JNDI names already exists on the server side. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2910) LDAP translator and multi-valued arrays

by Debbie Steigner (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2910?page=com.atlassian.jira.plu... ] Debbie Steigner updated TEIIDDES-2910: -------------------------------------- Issue Type: Bug (was: Feature Request) Description: TEIID-3411 added more flexibility in how multi-valued attributes are handled through extension metadata. It would be good to have design time support especially during import to support these options. Add the new teiid_ldap extension model to Teiid Designer: teiid_ldap:unwrap, teiid_ldap:dn_prefix, teiid_ldap:rdn_type was:TEIID-3411 added more flexibility in how multi-valued attributes are handled through extension metadata. It would be good to have design time support especially during import to support these options. > LDAP translator and multi-valued arrays > --------------------------------------- > > Key: TEIIDDES-2910 > URL: https://issues.jboss.org/browse/TEIIDDES-2910 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Teiid Integration > Reporter: Debbie Steigner > Assignee: Barry LaFond > > TEIID-3411 added more flexibility in how multi-valued attributes are handled through extension metadata. It would be good to have design time support especially during import to support these options. > Add the new teiid_ldap extension model to Teiid Designer: > teiid_ldap:unwrap, teiid_ldap:dn_prefix, teiid_ldap:rdn_type -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2910) LDAP translator and multi-valued arrays

by Debbie Steigner (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2910?page=com.atlassian.jira.plu... ] Debbie Steigner reassigned TEIIDDES-2910: ----------------------------------------- Assignee: Barry LaFond > LDAP translator and multi-valued arrays > --------------------------------------- > > Key: TEIIDDES-2910 > URL: https://issues.jboss.org/browse/TEIIDDES-2910 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export, Teiid Integration > Reporter: Debbie Steigner > Assignee: Barry LaFond > > TEIID-3411 added more flexibility in how multi-valued attributes are handled through extension metadata. It would be good to have design time support especially during import to support these options. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3070) Neon NPE in database explorer connect

by Don Krapohl (JIRA)

Don Krapohl created TEIIDDES-3070: ------------------------------------- Summary: Neon NPE in database explorer connect Key: TEIIDDES-3070 URL: https://issues.jboss.org/browse/TEIIDDES-3070 Project: Teiid Designer Issue Type: Bug Components: Eclipse Integration Affects Versions: 11.0 Environment: Version: Neon.3 Release (4.6.3) Build id: 20170314-1500 Windows Reporter: Don Krapohl Attachments: teiiddes-npe.png In teiiddes, database development perspective, data source explorer frame, opening a connection by double-clicking or using the left-click "connect" context menu results in NPE. The connection is successful but an error occurs and the data source explorer frame does not show the subelements in the treeview under the connection. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2865) JDBC importer imports MSSQL Server datatype numeric(9, [0-9]) as bigdecimal with zero precision

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2865?page=com.atlassian.jira.plu... ] Barry LaFond edited comment on TEIIDDES-2865 at 4/12/17 11:46 AM: ------------------------------------------------------------------ 11.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/63e7cdef53c052810... 11.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/1a2597d1766cbdea2... was (Author: blafond): 11.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/63e7cdef53c052810... > JDBC importer imports MSSQL Server datatype numeric(9,[0-9]) as bigdecimal with zero precision > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2865 > URL: https://issues.jboss.org/browse/TEIIDDES-2865 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 10.0, 9.0.5, 9.0.6, 9.0.7 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 11.0.2 > > > JDBC importer imports MSSQL Server datatype numeric(9,[0-9]) as bigdecimal with zero precision and should be 9. I believe this https://issues.jboss.org/browse/TEIIDDES-2746 may have changed the behavior, in version 9.0.3 it imports correctly. > You can use jdbc:sqlserver://ENGNTDBS14.mw.lab.eng.bos.redhat.com:1433;databaseName=mss_eds > user - mss_eds > password - mss_eds > table - debtest2, both columns are numeric(9,2) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2854) Support Oracle comments when performing JDBC import

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2854?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2854: ----------------------------------- Fix Version/s: 11.2 (was: 11.0.2) > Support Oracle comments when performing JDBC import > --------------------------------------------------- > > Key: TEIIDDES-2854 > URL: https://issues.jboss.org/browse/TEIIDDES-2854 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Affects Versions: 9.1, 10.0.1 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 11.2 > > > When performing JDBC import from oracle, the column comments should be imported as part of the metadata that used to create the source model. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2854) Support Oracle comments when performing JDBC import

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2854?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2854: ---------------------------------------- Currently, Designer's JDBC importer is checking the *remarks* field in the result set for the getTables() request in JdbcTableTypesImpl {code} resultSet = metadata.getTables(catalogName,schemaName,WILDCARD_PATTERN,tableTypes); while (resultSet != null && resultSet.next()) { final String tableName = resultSet.getString(3); final String remarks = resultSet.getString(5); final JdbcTableImpl table = new JdbcTableImpl(this,tableName); table.setRemarks(remarks); children.add(table); } {code} Teiid's *JDBCMetdataProcessor.getTables()* method uses a similar call to retrieve available remarks and sets the table *annotation* if not null. This issue requests using Oracle COMMENTS which is probably different than standard JDBC. We currently have no framework to make additional calls for each JDBC type that might support *COMMENTS* or like information > Support Oracle comments when performing JDBC import > --------------------------------------------------- > > Key: TEIIDDES-2854 > URL: https://issues.jboss.org/browse/TEIIDDES-2854 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Affects Versions: 9.1, 10.0.1 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 11.0.2 > > > When performing JDBC import from oracle, the column comments should be imported as part of the metadata that used to create the source model. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 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 April 2017