March 2016 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2408) Add remaining SQL/XML functions

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2408?page=com.atlassian.jira.plu... ] Matus Makovy reopened TEIIDDES-2408: ------------------------------------ [~blafond] I verified today, that Transformation editor recognizes all these functions, but XMLEXISTS and XMLCAST is not included in Expression builder. You cannot choose these functions when using Expression builder. > Add remaining SQL/XML functions > ------------------------------- > > Key: TEIIDDES-2408 > URL: https://issues.jboss.org/browse/TEIIDDES-2408 > Project: Teiid Designer > Issue Type: Task > Components: Patch Release, Teiid Integration > Reporter: Steven Hawkins > Assignee: Barry LaFond > Fix For: 10.0.1, 9.2.1 > > > Teiid added support for: > XMLTEXT - just a regular function > XMLEXISTS - a predicate with syntax similar to XMLQUERY > XMLCAST - similar to CAST > All are in the documentation and match the sql standard - https://docs.jboss.org/author/display/TEIID/XML+Functions -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2466) Create Preview VDB for only the model containing the table that is being preview

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2466?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2466: ---------------------------------------- Example Preview VDB XML with virtual base layer and top view model with a simple join table. Note that the contents of each model only contain the necessary source tables (DDL) to perform the actual query. {code:xml} <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <vdb name="PREVIEW_PartsViewsTop_PartsInfo" version="1"> <description>Importer VDB</description> <property name="UseConnectorMetadata" value="true" /> <property name="deployment-name" value="PREVIEW_PartsViewsTop_PartsInfo-vdb.xml" /> <model name="PartsViewsTop" type="VIRTUAL" visible="true"> <metadata type="DDL"><![CDATA[ CREATE VIEW PartsInfo ( PART_ID string(50) NOT NULL OPTIONS(UPDATABLE 'FALSE'), PART_NAME string(255) OPTIONS(UPDATABLE 'FALSE'), PART_COLOR string(30) OPTIONS(UPDATABLE 'FALSE'), PART_WEIGHT string(255) OPTIONS(UPDATABLE 'FALSE'), SUPPLIER_ID string(10) NOT NULL OPTIONS(UPDATABLE 'FALSE') ) AS SELECT PartsViewsBase.PARTS.PART_ID, PartsViewsBase.PARTS.PART_NAME, PartsViewsBase.PARTS.PART_COLOR, PartsViewsBase.PARTS.PART_WEIGHT, PartsViewsBase.SUPPLIER_PARTS.SUPPLIER_ID FROM PartsViewsBase.PARTS, PartsViewsBase.SUPPLIER_PARTS WHERE PartsViewsBase.SUPPLIER_PARTS.PART_ID = PartsViewsBase.PARTS.PART_ID; ]]></metadata> </model> <model name="PartsViewsBase" type="VIRTUAL" visible="true"> <metadata type="DDL"><![CDATA[ CREATE VIEW SUPPLIER_PARTS ( SUPPLIER_ID string(10) NOT NULL OPTIONS(NAMEINSOURCE '"SUPPLIER_ID"', NATIVE_TYPE 'varchar', UPDATABLE 'FALSE'), PART_ID string(50) NOT NULL OPTIONS(NAMEINSOURCE '"PART_ID"', NATIVE_TYPE 'varchar', UPDATABLE 'FALSE'), QUANTITY bigdecimal OPTIONS(NAMEINSOURCE '"QUANTITY"', NATIVE_TYPE 'numeric', UPDATABLE 'FALSE', FIXED_LENGTH 'TRUE'), SHIPPER_ID bigdecimal OPTIONS(NAMEINSOURCE '"SHIPPER_ID"', NATIVE_TYPE 'numeric', UPDATABLE 'FALSE', FIXED_LENGTH 'TRUE') ) OPTIONS(NAMEINSOURCE '"dbo"."SUPPLIER_PARTS"', UPDATABLE 'FALSE') AS SELECT * FROM PartsSQL2000.SUPPLIER_PARTS; CREATE VIEW PARTS ( PART_ID string(50) NOT NULL OPTIONS(NAMEINSOURCE '"PART_ID"', NATIVE_TYPE 'varchar', UPDATABLE 'FALSE'), PART_NAME string(255) OPTIONS(NAMEINSOURCE '"PART_NAME"', NATIVE_TYPE 'varchar', UPDATABLE 'FALSE'), PART_COLOR string(30) OPTIONS(NAMEINSOURCE '"PART_COLOR"', NATIVE_TYPE 'varchar', UPDATABLE 'FALSE'), PART_WEIGHT string(255) OPTIONS(NAMEINSOURCE '"PART_WEIGHT"', NATIVE_TYPE 'varchar', UPDATABLE 'FALSE') ) OPTIONS(NAMEINSOURCE '"dbo"."PARTS"', UPDATABLE 'FALSE') AS SELECT * FROM PartsSQL2000.PARTS; ]]></metadata> </model> <model name="PartsSQL2000" type="PHYSICAL" visible="true"> <source name="PartsSQL2000" translator-name="sqlserver" connection-jndi-name="PartsSQL2000_DS" /> <metadata type="DDL"><![CDATA[ CREATE FOREIGN TABLE SUPPLIER_PARTS ( SUPPLIER_ID string(10) NOT NULL OPTIONS(NAMEINSOURCE '"SUPPLIER_ID"', NATIVE_TYPE 'varchar'), PART_ID string(50) NOT NULL OPTIONS(NAMEINSOURCE '"PART_ID"', NATIVE_TYPE 'varchar'), QUANTITY bigdecimal OPTIONS(NAMEINSOURCE '"QUANTITY"', NATIVE_TYPE 'numeric', FIXED_LENGTH 'TRUE'), SHIPPER_ID bigdecimal OPTIONS(NAMEINSOURCE '"SHIPPER_ID"', NATIVE_TYPE 'numeric', FIXED_LENGTH 'TRUE') ) OPTIONS(NAMEINSOURCE '"dbo"."SUPPLIER_PARTS"') CREATE FOREIGN TABLE PARTS ( PART_ID string(50) NOT NULL OPTIONS(NAMEINSOURCE '"PART_ID"', NATIVE_TYPE 'varchar'), PART_NAME string(255) OPTIONS(NAMEINSOURCE '"PART_NAME"', NATIVE_TYPE 'varchar'), PART_COLOR string(30) OPTIONS(NAMEINSOURCE '"PART_COLOR"', NATIVE_TYPE 'varchar'), PART_WEIGHT string(255) OPTIONS(NAMEINSOURCE '"PART_WEIGHT"', NATIVE_TYPE 'varchar') ) OPTIONS(NAMEINSOURCE '"dbo"."PARTS"') ]]></metadata> </model> </vdb> {code} > Create Preview VDB for only the model containing the table that is being preview > -------------------------------------------------------------------------------- > > Key: TEIIDDES-2466 > URL: https://issues.jboss.org/browse/TEIIDDES-2466 > Project: Teiid Designer > Issue Type: Feature Request > Components: Data Preview, Documentation, Patch Release > Affects Versions: 9.0 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 10.0.1 > > Attachments: custom-preview-data-preview-sql-tab.png, custom-preview-data-preview-vdbxml-tab.png, data-source-definition-options-jdbc-import.png, data-source-definition-options-page-flat-file.png > > > RFE > Currently once you preview one table a Preview VDB is created for all the models in the project, request that the Preview VDB only be created for the model containing the table that is being previewed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2812) Add ability to reverse engineer into a Pojo object from a table or view

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2812?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2812: ---------------------------------------- Those could be two options on the .class file generator for packaging > Add ability to reverse engineer into a Pojo object from a table or view > ----------------------------------------------------------------------- > > Key: TEIIDDES-2812 > URL: https://issues.jboss.org/browse/TEIIDDES-2812 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling, Usability > Affects Versions: 9.0.6 > Reporter: Van Halbert > Assignee: Barry LaFond > > The scenario is: select table/view, right mouse click select Create Pojo, present dialog, need a file chooser to select location to save output. > Label of action: Create Pojo (or something to indicates the process) > Dialog title: Create Pojo from Table [tableName] > Message: This will create a Pojo class, and packaged in a jar, that is meant to be used when JDG will be used in materialization or accessed as a data source. > Options: > - file chooser option to select folder to save pojo jar > - drop-down: <select option> > Access JDG in Library Mode > Access JDG via Hot Rod Client > - pojo package name (default = org.teiid.pojo) > - pojo jar name (default = pojo.jar) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2812) Add ability to reverse engineer into a Pojo object from a table or view

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2812?page=com.atlassian.jira.plu... ] Van Halbert commented on TEIIDDES-2812: --------------------------------------- I'm thinking that the artifact to create is a zip that contains a module to be deployed. That way the user only has to unizp it into the modules directory and go. The other alternative is to name the jar: {name}.jar.deployment > Add ability to reverse engineer into a Pojo object from a table or view > ----------------------------------------------------------------------- > > Key: TEIIDDES-2812 > URL: https://issues.jboss.org/browse/TEIIDDES-2812 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling, Usability > Affects Versions: 9.0.6 > Reporter: Van Halbert > Assignee: Barry LaFond > > The scenario is: select table/view, right mouse click select Create Pojo, present dialog, need a file chooser to select location to save output. > Label of action: Create Pojo (or something to indicates the process) > Dialog title: Create Pojo from Table [tableName] > Message: This will create a Pojo class, and packaged in a jar, that is meant to be used when JDG will be used in materialization or accessed as a data source. > Options: > - file chooser option to select folder to save pojo jar > - drop-down: <select option> > Access JDG in Library Mode > Access JDG via Hot Rod Client > - pojo package name (default = org.teiid.pojo) > - pojo jar name (default = pojo.jar) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2466) Create Preview VDB for only the model containing the table that is being preview

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2466?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2466: ----------------------------------- Attachment: custom-preview-data-preview-sql-tab.png custom-preview-data-preview-vdbxml-tab.png > Create Preview VDB for only the model containing the table that is being preview > -------------------------------------------------------------------------------- > > Key: TEIIDDES-2466 > URL: https://issues.jboss.org/browse/TEIIDDES-2466 > Project: Teiid Designer > Issue Type: Feature Request > Components: Data Preview, Documentation, Patch Release > Affects Versions: 9.0 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 10.0.1 > > Attachments: custom-preview-data-preview-sql-tab.png, custom-preview-data-preview-vdbxml-tab.png, data-source-definition-options-jdbc-import.png, data-source-definition-options-page-flat-file.png > > > RFE > Currently once you preview one table a Preview VDB is created for all the models in the project, request that the Preview VDB only be created for the model containing the table that is being previewed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2466) Create Preview VDB for only the model containing the table that is being preview

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2466?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2466: ---------------------------------------- master: https://github.com/Teiid-Designer/teiid-designer/commit/c5126fd651c1eedc1... Added seeding of initial jndi names based on initial/default source model name + "_DS" > Create Preview VDB for only the model containing the table that is being preview > -------------------------------------------------------------------------------- > > Key: TEIIDDES-2466 > URL: https://issues.jboss.org/browse/TEIIDDES-2466 > Project: Teiid Designer > Issue Type: Feature Request > Components: Data Preview, Documentation, Patch Release > Affects Versions: 9.0 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 10.0.1 > > Attachments: data-source-definition-options-jdbc-import.png, data-source-definition-options-page-flat-file.png > > > RFE > Currently once you preview one table a Preview VDB is created for all the models in the project, request that the Preview VDB only be created for the model containing the table that is being previewed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2466) Create Preview VDB for only the model containing the table that is being preview

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2466?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2466. ------------------------------------ Resolution: Done > Create Preview VDB for only the model containing the table that is being preview > -------------------------------------------------------------------------------- > > Key: TEIIDDES-2466 > URL: https://issues.jboss.org/browse/TEIIDDES-2466 > Project: Teiid Designer > Issue Type: Feature Request > Components: Data Preview, Documentation, Patch Release > Affects Versions: 9.0 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 10.0.1 > > Attachments: data-source-definition-options-jdbc-import.png, data-source-definition-options-page-flat-file.png > > > RFE > Currently once you preview one table a Preview VDB is created for all the models in the project, request that the Preview VDB only be created for the model containing the table that is being previewed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2436) StackOverflow Exception Importing VDB via JDBC Importer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2436?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2436. ------------------------------------ Fix Version/s: (was: 9.2.1) Resolution: Done > StackOverflow Exception Importing VDB via JDBC Importer > ------------------------------------------------------- > > Key: TEIIDDES-2436 > URL: https://issues.jboss.org/browse/TEIIDDES-2436 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Patch Release > Affects Versions: 9.0.1 > Reporter: Ted Jones > Assignee: Barry LaFond > Priority: Critical > Fix For: 10.0.1 > > Attachments: import-vdb.png, JdbcImoprtObjectsPage_TEIIDDES_2436.patch > > > Receiving StackOverflow exception importing a VDB via the JDBC importer using the following steps: > 1. Import a JDBC source (any source) > a. On page 3, select "Show Selected Schemas". > 2. Now try importing a deployed VDB. You will receive a StackOverflow exception. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2570) RelationalTable contains methods for single UniqueConstraint and collection of UniqueConstraints

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2570?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2570. ------------------------------------ Fix Version/s: (was: 9.2.1) Resolution: Done master : https://github.com/Teiid-Designer/teiid-designer/commit/a040ac893463027db... > RelationalTable contains methods for single UniqueConstraint and collection of UniqueConstraints > ------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-2570 > URL: https://issues.jboss.org/browse/TEIIDDES-2570 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Patch Release > Affects Versions: 9.0.1 > Reporter: Paul Richardson > Assignee: Barry LaFond > Fix For: 10.0.1 > > Attachments: edit-unique-constraint-dialog.png, unique-constraint-tab.png > > > While round tripping DDL import and export, the RelationalTable is used to store table unique constraint. The DDL Importer stores the new constraints in the uniqueConstraints collection. However, when saving the model to the BasicTableImpl instance, it actually only looks at the single uniqueConstraint so values are lost. > Dynamic Vdb work has united these fields but retained the getUniqueConstraint() and setUniqueConstraint() methods for backward compatibility with the RelationalTableEditorPanel and ViewTableEditorPanel. These methods are deprecated and the panels should be fixed to support entering multiple unique constraints. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2813) LDAP importer does not prevent invalid characters in table names

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2813?page=com.atlassian.jira.plu... ] Steven Hawkins commented on TEIIDDES-2813: ------------------------------------------ = is a valid character, you just have to quote the identifier. Providing an option to create simple identifiers would be an good enhancement, but this is not a bug. > LDAP importer does not prevent invalid characters in table names > ---------------------------------------------------------------- > > Key: TEIIDDES-2813 > URL: https://issues.jboss.org/browse/TEIIDDES-2813 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 9.0.5 > Reporter: Marc Shirley > > Import prefills table names with the LDAP object such as "ou=people" which includes the invalid character '='. The import wizard should prevent a user from naming objects with invalid characters. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues March 2016