February 2017 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2355) Provide an option to import pushdown functions

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2355?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2355: ----------------------------------- Fix Version/s: 11.1 (was: 11.0.1) > Provide an option to import pushdown functions > ---------------------------------------------- > > Key: TEIIDDES-2355 > URL: https://issues.jboss.org/browse/TEIIDDES-2355 > Project: Teiid Designer > Issue Type: Feature Request > Components: Patch Release, Teiid Integration > Reporter: Steven Hawkins > Assignee: Barry LaFond > Fix For: 11.1 > > Attachments: pushDown.zip > > > The import property importer.importPushdownFunctions can be set to have Teiid include the pushdown functions as part of the imported schema and there by the ddl used by designer. With TEIID-3098 will prevent there from being ambiguity from doing so (either from multiple models or from the pushdown functions). So Designer should allow users to import these functions if they wish (it could even be a default option). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3010) High-level event handling

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3010?page=com.atlassian.jira.plu... ] Steven Hawkins commented on TEIIDDES-3010: ------------------------------------------ Added a doc update - https://github.com/teiid/teiid-documents/commit/01de0a3831034cd818d463af4... > High-level event handling > ------------------------- > > Key: TEIIDDES-3010 > URL: https://issues.jboss.org/browse/TEIIDDES-3010 > Project: Teiid Designer > Issue Type: Enhancement > Reporter: Steven Hawkins > Assignee: Barry LaFond > Priority: Blocker > Fix For: 12.0 > > > TEIID-4627 adds support for source level triggers to be called after CDC events. > The triggers are similar to what is supported by views, but "INSTEAD OF" is not supported - just AFTER. > CREATE TRIGGER name ON table AFTER (INSERT|UPDATE|DELETE) FOR EACH ROW statement > Just like view triggers new/old/changing values can be referenced. Note that unlike view triggers, these must be named as an arbitrary number of them are supported per table (like other of our constructs they are scoped to the table, not to the schema). > We may eventually want to support multiple event types for a single trigger and may need to support internal events as well. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3028) Add "LoadNumber" column to Materialized View cache tables

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIIDDES-3028: -------------------------------------- Summary: Add "LoadNumber" column to Materialized View cache tables Key: TEIIDDES-3028 URL: https://issues.jboss.org/browse/TEIIDDES-3028 Project: Teiid Designer Issue Type: Enhancement Components: Modeling Reporter: Ramesh Reddy Priority: Blocker Based on TEIID-4628, to work with eager updates on materiliazed view, a materialized view's cached table MUST contain an additional column called "LoadNumber" along with rest of view columns. This column is used track the and update the cache contents according to the {code} SYSADMIN.updatematView {code} procedure. The relevant document can be found at https://teiid.gitbooks.io/documents/content/caching/External_Materializat... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3026) Name in source not included when doing preview

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3026?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-3026. ------------------------------------ Resolution: Done master: https://github.com/Teiid-Designer/teiid-designer/compare/251ef76a7a30...3... > Name in source not included when doing preview > ---------------------------------------------- > > Key: TEIIDDES-3026 > URL: https://issues.jboss.org/browse/TEIIDDES-3026 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 11.0.1 > Reporter: Matus Makovy > Assignee: Barry LaFond > Priority: Blocker > Fix For: 11.0.1 > > Attachments: project.zip > > > Prieview VDB doesn't include name in source for column. When you try to do a preview for SHIP_VIA table from partsSourceSQLServer model that is in attached project, the generated dynamic VDB looks like this: > {code:xml} > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <vdb name="PREVIEW-21b09376-8753-42ac-a874-34d47820fc30" version="1"> > <description>Importer VDB</description> > <property name="UseConnectorMetadata" value="true" /> > <property name="deployment-name" value="PREVIEW-21b09376-8753-42ac-a874-34d47820fc30-vdb.xml" /> > <model name="partsSourceSQLServer" type="PHYSICAL" visible="true"> > <source name="partsSourceSQLServer" translator-name="sqlserver" connection-jndi-name="java:/partsSourceSQLServer" /> > <metadata type="DDL"><![CDATA[ > CREATE FOREIGN TABLE SHIP_VIA ( > SHIPPER_ID bigdecimal NOT NULL OPTIONS(FIXED_LENGTH 'TRUE'), > SHIPPER_NAME string(30), > AVERAGE_TIME_DELIVERY bigdecimal OPTIONS(FIXED_LENGTH 'TRUE'), > CONSTRAINT PK_SHIP_VIA PRIMARY KEY(SHIPPER_ID) > ) OPTIONS(UPDATABLE 'TRUE'); > ]]></metadata> > </model> > </vdb> > {code} > It is missing name in source for AVERAGE_TIME_DELIVERY (which is "AVERAGE TIME DELIVERY" at it is defined in the XMI model). Preview cannot be done. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2973) When creating View model by transforming should set nameInSource to blank

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2973?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2973. ------------------------------------ Resolution: Done master: https://github.com/Teiid-Designer/teiid-designer/compare/251ef76a7a30...3... > When creating View model by transforming should set nameInSource to blank > ------------------------------------------------------------------------- > > Key: TEIIDDES-2973 > URL: https://issues.jboss.org/browse/TEIIDDES-2973 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 10.0.2 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 11.0.1 > > > When a view model is being created by transforming from a source model is assigning the NameInSource to what the source model had and that is incorrect and cause incorrect references. The NIS for the view model should be set to blank, so that it delegates to the source model as to what the underlying nameinSource to use. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3027) Duplicate Source Model in created VDB

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3027?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-3027. ------------------------------------ Resolution: Done master: https://github.com/Teiid-Designer/teiid-designer/compare/251ef76a7a30...3... > Duplicate Source Model in created VDB > ------------------------------------- > > Key: TEIIDDES-3027 > URL: https://issues.jboss.org/browse/TEIIDDES-3027 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs, Editors > Affects Versions: 11.0.1 > Reporter: stanislav kaleta > Assignee: Barry LaFond > Fix For: 11.0.1 > > > If you select both View Model and related Source Model in _New VDB_ dialog, created VDB has pending changes and is unable to save due to error: > {code:java} > java.lang.Exception: java.util.zip.ZipException: duplicate entry: <SourceModelName> > {code} > Related Source Models are automatically added during creation of VDB. The Problem occurs when you also manually add Source Model in _New VDB_ dialog. The creation process doesn't recognize that it's the same model which is related to View Model. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3010) High-level event handling

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3010?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-3010: ---------------------------------------- After today's discussions, we have an option to attach the after-trigger SQL/DDL properties to either the source table or the view table. The desire is to be able to provide SQL validation as part of the UI feature as well as track dependencies (model imports). This can most effectively be done using a the virtual metamodel. > High-level event handling > ------------------------- > > Key: TEIIDDES-3010 > URL: https://issues.jboss.org/browse/TEIIDDES-3010 > Project: Teiid Designer > Issue Type: Enhancement > Reporter: Steven Hawkins > Assignee: Barry LaFond > Priority: Blocker > Fix For: 12.0 > > > TEIID-4627 adds support for source level triggers to be called after CDC events. > The triggers are similar to what is supported by views, but "INSTEAD OF" is not supported - just AFTER. > CREATE TRIGGER name ON table AFTER (INSERT|UPDATE|DELETE) FOR EACH ROW statement > Just like view triggers new/old/changing values can be referenced. Note that unlike view triggers, these must be named as an arbitrary number of them are supported per table (like other of our constructs they are scoped to the table, not to the schema). > We may eventually want to support multiple event types for a single trigger and may need to support internal events as well. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3010) High-level event handling

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3010?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-3010: -------------------------------------- Assignee: Barry LaFond > High-level event handling > ------------------------- > > Key: TEIIDDES-3010 > URL: https://issues.jboss.org/browse/TEIIDDES-3010 > Project: Teiid Designer > Issue Type: Enhancement > Reporter: Steven Hawkins > Assignee: Barry LaFond > Priority: Blocker > Fix For: 12.0 > > > TEIID-4627 adds support for source level triggers to be called after CDC events. > The triggers are similar to what is supported by views, but "INSTEAD OF" is not supported - just AFTER. > CREATE TRIGGER name ON table AFTER (INSERT|UPDATE|DELETE) FOR EACH ROW statement > Just like view triggers new/old/changing values can be referenced. Note that unlike view triggers, these must be named as an arbitrary number of them are supported per table (like other of our constructs they are scoped to the table, not to the schema). > We may eventually want to support multiple event types for a single trigger and may need to support internal events as well. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3010) High-level event handling

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3010?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-3010: ----------------------------------- Priority: Blocker (was: Major) > High-level event handling > ------------------------- > > Key: TEIIDDES-3010 > URL: https://issues.jboss.org/browse/TEIIDDES-3010 > Project: Teiid Designer > Issue Type: Enhancement > Reporter: Steven Hawkins > Priority: Blocker > Fix For: 12.0 > > > TEIID-4627 adds support for source level triggers to be called after CDC events. > The triggers are similar to what is supported by views, but "INSTEAD OF" is not supported - just AFTER. > CREATE TRIGGER name ON table AFTER (INSERT|UPDATE|DELETE) FOR EACH ROW statement > Just like view triggers new/old/changing values can be referenced. Note that unlike view triggers, these must be named as an arbitrary number of them are supported per table (like other of our constructs they are scoped to the table, not to the schema). > We may eventually want to support multiple event types for a single trigger and may need to support internal events as well. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3026) Name in source not included when doing preview

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3026?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-3026: ----------------------------------- Fix Version/s: 11.0.1 > Name in source not included when doing preview > ---------------------------------------------- > > Key: TEIIDDES-3026 > URL: https://issues.jboss.org/browse/TEIIDDES-3026 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 11.0.1 > Reporter: Matus Makovy > Assignee: Barry LaFond > Priority: Blocker > Fix For: 11.0.1 > > Attachments: project.zip > > > Prieview VDB doesn't include name in source for column. When you try to do a preview for SHIP_VIA table from partsSourceSQLServer model that is in attached project, the generated dynamic VDB looks like this: > {code:xml} > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <vdb name="PREVIEW-21b09376-8753-42ac-a874-34d47820fc30" version="1"> > <description>Importer VDB</description> > <property name="UseConnectorMetadata" value="true" /> > <property name="deployment-name" value="PREVIEW-21b09376-8753-42ac-a874-34d47820fc30-vdb.xml" /> > <model name="partsSourceSQLServer" type="PHYSICAL" visible="true"> > <source name="partsSourceSQLServer" translator-name="sqlserver" connection-jndi-name="java:/partsSourceSQLServer" /> > <metadata type="DDL"><![CDATA[ > CREATE FOREIGN TABLE SHIP_VIA ( > SHIPPER_ID bigdecimal NOT NULL OPTIONS(FIXED_LENGTH 'TRUE'), > SHIPPER_NAME string(30), > AVERAGE_TIME_DELIVERY bigdecimal OPTIONS(FIXED_LENGTH 'TRUE'), > CONSTRAINT PK_SHIP_VIA PRIMARY KEY(SHIPPER_ID) > ) OPTIONS(UPDATABLE 'TRUE'); > ]]></metadata> > </model> > </vdb> > {code} > It is missing name in source for AVERAGE_TIME_DELIVERY (which is "AVERAGE TIME DELIVERY" at it is defined in the XMI model). Preview cannot be done. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues February 2017