November 2017 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-3142) Missing native metadata tag with overriding infinispan translator

by Matej Kralik (JIRA)

Matej Kralik created TEIIDDES-3142: -------------------------------------- Summary: Missing native metadata tag with overriding infinispan translator Key: TEIIDDES-3142 URL: https://issues.jboss.org/browse/TEIIDDES-3142 Project: Teiid Designer Issue Type: Bug Components: Dynamic VDBs Affects Versions: 11.1.1 Environment: Fedora 26 Reporter: Matej Kralik Assignee: Matej Kralik Priority: Critical Fix For: 11.1.1 When I set up JDG materialization, the teiid designer automatic creates overriding infinispan translator for JDG source model but when I generate -vdb.xml, the model with overriding translator doesn't have *NATIVE* metadata tag because has another name than "infinispan-hotrod" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3141) ADD Create View from Model With Criteria.

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3141?page=com.atlassian.jira.plu... ] Van Halbert commented on TEIIDDES-3141: --------------------------------------- Why hardcode the value, in this example '201711'? Why not try one of the following: - use ENV('KEY') in the criteria, where KEY references system property - use internal materialized table that contains name=value pairs for dynamic environment setting. Using the join to the internal table to derive the yyyymm value. This way your VDB doesn't have to be changed with every date change. However, that doesn't change the core aspect of this feature request, which still would be useful. > ADD Create View from Model With Criteria. > ----------------------------------------- > > Key: TEIIDDES-3141 > URL: https://issues.jboss.org/browse/TEIIDDES-3141 > Project: Teiid Designer > Issue Type: Enhancement > Reporter: Tom Johnston > > In some environments (Data Lakes etc) it is likely that one would have a time-metric to query from.. (i.e. snapshot_year_month) where one might want to create a custom view model for the latest dataset. As such, a query such as Select * from Table where snapshot_year_month = '201711' might be used OR (as in my case)...Regardless on how its used.. the ability to add a FIXED Criteria to ALL objects for a model would be immensely useful. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3141) ADD Create View from Model With Criteria.

by Tom Johnston (JIRA)

Tom Johnston created TEIIDDES-3141: -------------------------------------- Summary: ADD Create View from Model With Criteria. Key: TEIIDDES-3141 URL: https://issues.jboss.org/browse/TEIIDDES-3141 Project: Teiid Designer Issue Type: Enhancement Reporter: Tom Johnston In some environments (Data Lakes etc) it is likely that one would have a time-metric to query from.. (i.e. snapshot_year_month) where one might want to create a custom view model for the latest dataset. As such, a query such as Select * from Table where snapshot_year_month = '201711' might be used OR (as in my case)...Regardless on how its used.. the ability to add a FIXED Criteria to ALL objects for a model would be immensely useful. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3138) Designer is putting the return parameter in the wrong position on a REST invokeHttp procedure

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3138?page=com.atlassian.jira.plu... ] Barry LaFond edited comment on TEIIDDES-3138 at 11/14/17 3:46 PM: ------------------------------------------------------------------ master: https://github.com/Teiid-Designer/teiid-designer/commit/4b893c75b2f851669... and https://github.com/Teiid-Designer/teiid-designer/commit/2a0838f9a3fdd0d18... was (Author: blafond): master: https://github.com/Teiid-Designer/teiid-designer/commit/4b893c75b2f851669... > Designer is putting the return parameter in the wrong position on a REST invokeHttp procedure > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-3138 > URL: https://issues.jboss.org/browse/TEIIDDES-3138 > Project: Teiid Designer > Issue Type: Bug > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 11.1.1 > > > Designer is putting the return parameter in the wrong position on a REST invokeHttp procedure. See https://developer.jboss.org/message/977532 and https://issues.jboss.org/browse/TEIID-5130 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3138) Designer is putting the return parameter in the wrong position on a REST invokeHttp procedure

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3138?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-3138. ------------------------------------ Resolution: Done master: https://github.com/Teiid-Designer/teiid-designer/commit/4b893c75b2f851669... > Designer is putting the return parameter in the wrong position on a REST invokeHttp procedure > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-3138 > URL: https://issues.jboss.org/browse/TEIIDDES-3138 > Project: Teiid Designer > Issue Type: Bug > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 11.1.1 > > > Designer is putting the return parameter in the wrong position on a REST invokeHttp procedure. See https://developer.jboss.org/message/977532 and https://issues.jboss.org/browse/TEIID-5130 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3138) Designer is putting the return parameter in the wrong position on a REST invokeHttp procedure

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3138?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-3138: ----------------------------------- Fix Version/s: 11.1.1 > Designer is putting the return parameter in the wrong position on a REST invokeHttp procedure > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-3138 > URL: https://issues.jboss.org/browse/TEIIDDES-3138 > Project: Teiid Designer > Issue Type: Bug > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 11.1.1 > > > Designer is putting the return parameter in the wrong position on a REST invokeHttp procedure. See https://developer.jboss.org/message/977532 and https://issues.jboss.org/browse/TEIID-5130 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3138) Designer is putting the return parameter in the wrong position on a REST invokeHttp procedure

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3138?page=com.atlassian.jira.plu... ] Steven Hawkins commented on TEIIDDES-3138: ------------------------------------------ invokeHttp( action IN STRING, request IN OBJECT, endpoint IN STRING, stream IN BOOLEAN, result OUT BLOB, contentType OUT STRING, headers IN CLOB) should be: invokeHttp( result OUT BLOB result, action IN STRING, request IN OBJECT, endpoint IN STRING, stream IN BOOLEAN, contentType OUT STRING, headers IN CLOB) > is expecting the result OUT BLOB to be the result set, so it's not included as a parameter in the SQL? OUT and result values do not need explicit parameters. Only if you are trying to capture the OUT value to use a parameter, and it must be a variable. For result values you use "var = call..." > Can I also assume that the EMF version of an invokeHttp() in a *.vdb is ignored? You mean the metadata declaration in the .xmi, yes. Only the index metadata is looked at. > Designer is putting the return parameter in the wrong position on a REST invokeHttp procedure > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-3138 > URL: https://issues.jboss.org/browse/TEIIDDES-3138 > Project: Teiid Designer > Issue Type: Bug > Reporter: Debbie Steigner > Assignee: Barry LaFond > > Designer is putting the return parameter in the wrong position on a REST invokeHttp procedure. See https://developer.jboss.org/message/977532 and https://issues.jboss.org/browse/TEIID-5130 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3138) Designer is putting the return parameter in the wrong position on a REST invokeHttp procedure

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3138?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-3138: ---------------------------------------- [~shawkins] It looks like our generated SourceModel.invokeHttp('GET', null, 'file:///home/blafond/Testing/Test Data/data/employees/file/EMPLOYEEDATA.txt', 'TRUE')) is expecting the *result OUT BLOB* to be the result set, so it's not included as a parameter in the SQL? Can I also assume that the EMF version of an invokeHttp() in a *.vdb is ignored? > Designer is putting the return parameter in the wrong position on a REST invokeHttp procedure > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-3138 > URL: https://issues.jboss.org/browse/TEIIDDES-3138 > Project: Teiid Designer > Issue Type: Bug > Reporter: Debbie Steigner > Assignee: Barry LaFond > > Designer is putting the return parameter in the wrong position on a REST invokeHttp procedure. See https://developer.jboss.org/message/977532 and https://issues.jboss.org/browse/TEIID-5130 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3138) Designer is putting the return parameter in the wrong position on a REST invokeHttp procedure

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3138?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-3138: ---------------------------------------- Here's the generated source procedure: invokeHttp( action IN STRING, request IN OBJECT, endpoint IN STRING, stream IN BOOLEAN, *result* *OUT* BLOB, contentType *OUT* STRING, headers IN CLOB) I think the remote file wizards generate: SourceModel.invokeHttp('GET', null, 'file:///home/blafond/Testing/Test Data/data/employees/file/EMPLOYEEDATA.txt', 'TRUE')) > Designer is putting the return parameter in the wrong position on a REST invokeHttp procedure > ---------------------------------------------------------------------------------------------- > > Key: TEIIDDES-3138 > URL: https://issues.jboss.org/browse/TEIIDDES-3138 > Project: Teiid Designer > Issue Type: Bug > Reporter: Debbie Steigner > Assignee: Barry LaFond > > Designer is putting the return parameter in the wrong position on a REST invokeHttp procedure. See https://developer.jboss.org/message/977532 and https://issues.jboss.org/browse/TEIID-5130 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3140) Missing message for unsupported connection profile

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3140?page=com.atlassian.jira.plu... ] Matej Kralik resolved TEIIDDES-3140. ------------------------------------ Resolution: Done PR: https://github.com/Teiid-Designer/teiid-designer/pull/580 > Missing message for unsupported connection profile > -------------------------------------------------- > > Key: TEIIDDES-3140 > URL: https://issues.jboss.org/browse/TEIIDDES-3140 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 11.1.1 > Reporter: Matej Kralik > Assignee: Matej Kralik > Fix For: 11.1.1 > > Attachments: missingMessage.png > > > When I want to set connection profile which is not supported, shows error without message. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

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 November 2017