February 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1579) Remove S-RAMP Dependencies From The Repository Manager API

by Dan Florian (JIRA)

Dan Florian created TEIIDDES-1579: ------------------------------------- Summary: Remove S-RAMP Dependencies From The Repository Manager API Key: TEIIDDES-1579 URL: https://issues.jboss.org/browse/TEIIDDES-1579 Project: Teiid Designer Issue Type: Task Components: komodo-repository Affects Versions: Komodo Reporter: Dan Florian Assignee: Dan Florian Fix For: Komodo The repository manager interface layer should not have S-RAMP dependencies in its API. Since other komodo modules, and Design UI projects, do and may have dependencies on the komodo-repository module, create a layer of abstraction from the S-RAMP library. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1578) Extension Properties category keeps collapsing in Property View

by Mark Drilling (JIRA)

Mark Drilling created TEIIDDES-1578: --------------------------------------- Summary: Extension Properties category keeps collapsing in Property View Key: TEIIDDES-1578 URL: https://issues.jboss.org/browse/TEIIDDES-1578 Project: Teiid Designer Issue Type: Bug Components: Extension Framework Affects Versions: 8.0 Reporter: Mark Drilling Fix For: 8.1 The 'Extension' Category in the property view collapses whenever you edit one of the extension properties. This is very annoying when you want to edit several of the extension properties. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1208) Add ability to include the supporting UDF implementaion jar files to VDB

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1208?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1208. ------------------------------------- Resolution: Done Added ability to include the supporting udf jar. A new extension property is defined that allows the user to select the jar. Validation rules on FunctionModel scalarFunction were added as well as for relational procedures when function=true. VdbEditor was also modified to show the jars that are present in the VDB. pull request https://github.com/Teiid-Designer/teiid-designer/pull/90 > Add ability to include the supporting UDF implementaion jar files to VDB > ------------------------------------------------------------------------ > > Key: TEIIDDES-1208 > URL: https://issues.jboss.org/browse/TEIIDDES-1208 > Project: Teiid Designer > Issue Type: Feature Request > Components: VDB & Execution > Reporter: Ramesh Reddy > Assignee: Mark Drilling > Priority: Critical > Fix For: 8.1 > > > In Teiid 8.0 release the class loading mechanism is different, and supplying the UDF implementation jar files in a "lib" directory and restarting the server is not an option. So, it has introduced a new way to read the dependent JAR files in the VDB archive itself. > This needs to be supported by the Designer, where user can include a jar file in the "lib" directory in the VDB archive. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1556) In 8.0, the function metamodel has been deprecated, can the new model wizard drop down indicate as such

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1556?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1556. ------------------------------------- Resolution: Done Drop down now indicates that the FunctionModel is deprecated. Tutorials going forward will show how to define the UDF using relational procedure. > In 8.0, the function metamodel has been deprecated, can the new model wizard drop down indicate as such > ------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1556 > URL: https://issues.jboss.org/browse/TEIIDDES-1556 > Project: Teiid Designer > Issue Type: Enhancement > Components: Dialogs, Usability > Affects Versions: 8.0 > Reporter: Van Halbert > Assignee: Mark Drilling > Fix For: 8.1 > > > When selecting New Model Wizard, the Model Class drop down should indicate the Function Model is "Deprecated". -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1577) Changing connection URL for JDBC driver has no effect

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1577?page=com.atlassian.jira.plu... ] Van Halbert commented on TEIIDDES-1577: --------------------------------------- Each source model needs to have a Connection Profile associated with it. By selecting the model and right mouse click, then select "Modeling ==> Set Connection Profile". From there you can select an existing profile or create a new one. Once its assigned to the model, then you can select the model and right mouse click, select "Modeling ==> Create Data Source" to push your data connection changes to the server. > Changing connection URL for JDBC driver has no effect > ----------------------------------------------------- > > Key: TEIIDDES-1577 > URL: https://issues.jboss.org/browse/TEIIDDES-1577 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Tom Johnston > > Changing Connection URL under Properties Tab for Edit Driver Definitions does not have any impact when using the driver. > I.E. When specifying a new connection profile the Connection URL (shaded, unchangeable here) does NOT reflect the aforementioned property. > Use Case: I'm trying to create a new driver entry using Oracles OCI connectivity capability thus requiring a change in the connection url to (jdbc:oracle:oci:@<database_string> , for example) -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1577) Changing connection URL for JDBC driver has no effect

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1577?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-1577: ---------------------------------------- 1) From "Connection Profile" select "Oracle" 2) On "New Connection Profile", Click on "New Driver Definition" (little circle with +) 3) Select One driver, Now change the "Driver Name" 4) switch to JARList tab, point to the JDBC jar 5) Now go properties, type in your URL format for this DB and rest of the properties Now you can use the format of the URL you put in (PS: pls, if in question please ask in the community before creating the JIRA, JIRA for confirmed bugs/approved feature requests only) > Changing connection URL for JDBC driver has no effect > ----------------------------------------------------- > > Key: TEIIDDES-1577 > URL: https://issues.jboss.org/browse/TEIIDDES-1577 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Tom Johnston > > Changing Connection URL under Properties Tab for Edit Driver Definitions does not have any impact when using the driver. > I.E. When specifying a new connection profile the Connection URL (shaded, unchangeable here) does NOT reflect the aforementioned property. > Use Case: I'm trying to create a new driver entry using Oracles OCI connectivity capability thus requiring a change in the connection url to (jdbc:oracle:oci:@<database_string> , for example) -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1576) Unnecessary table aliasing causing in pushdown query

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1576?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-1576: ---------------------------------------- it is an expression not column name. Name in Source is available for source column name differences and abstract those from the Teiid models. If you need such an expression, create a view table and define that report column on that using above expression, and Teiid will do the right thing to push all that expression down to source. Yes, when you remove the g_0, it becomes a proper expression, not a column and that is why is works. This should be rejected. > Unnecessary table aliasing causing in pushdown query > ---------------------------------------------------- > > Key: TEIIDDES-1576 > URL: https://issues.jboss.org/browse/TEIIDDES-1576 > Project: Teiid Designer > Issue Type: Bug > Components: Data Preview > Reporter: Tom Johnston > > Create a Added a table manually to an existing physical model (generated from JDBC import). put source specific syntax as name in source for a column. > When previewed I get an error because the g0 predicate was added to the column thus resulting in an invalid query. > I proved the point by copy/paste the atomic query to the source directly (via Squirrel) it failed with the same error then removed the predicate references (both on column and table) and it succeeded. > The source is Sybase. > The Name in source entered for the column was: > convert(varchar(16384),report)+convert(varchar(16384),impression)+convert(varchar(16384),signature) > which resulted in the following push down > SELECT g_0.convert(varchar(16384),report)+convert(varchar(16384),impression)+convert(varchar(16384),signature) FROM "pinspr"."dbo"."cdr_rad_obs" g_0 > which when executed directly against sybase fails.. > if the g_0 is removed entirely the query succeeds in against Sybase using Squirrel. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1576) Unnecessary table aliasing causing in pushdown query

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1576?page=com.atlassian.jira.plu... ] Steven Hawkins commented on TEIIDDES-1576: ------------------------------------------ This is not a supported usage of a column name in source. This would not be generally valid as any usage in a join could cause the column references to be ambiguous and would likely not be worked as an enhancement given the workarounds of introducing a view layer to achieve the same effect (assuming that the functions are applicable to Teiid) or using the native-query feature effectively specify a source inline view. > Unnecessary table aliasing causing in pushdown query > ---------------------------------------------------- > > Key: TEIIDDES-1576 > URL: https://issues.jboss.org/browse/TEIIDDES-1576 > Project: Teiid Designer > Issue Type: Bug > Components: Data Preview > Reporter: Tom Johnston > > Create a Added a table manually to an existing physical model (generated from JDBC import). put source specific syntax as name in source for a column. > When previewed I get an error because the g0 predicate was added to the column thus resulting in an invalid query. > I proved the point by copy/paste the atomic query to the source directly (via Squirrel) it failed with the same error then removed the predicate references (both on column and table) and it succeeded. > The source is Sybase. > The Name in source entered for the column was: > convert(varchar(16384),report)+convert(varchar(16384),impression)+convert(varchar(16384),signature) > which resulted in the following push down > SELECT g_0.convert(varchar(16384),report)+convert(varchar(16384),impression)+convert(varchar(16384),signature) FROM "pinspr"."dbo"."cdr_rad_obs" g_0 > which when executed directly against sybase fails.. > if the g_0 is removed entirely the query succeeds in against Sybase using Squirrel. -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1577) Changing connection URL for JDBC driver has no effect

by Tom Johnston (JIRA)

Tom Johnston created TEIIDDES-1577: -------------------------------------- Summary: Changing connection URL for JDBC driver has no effect Key: TEIIDDES-1577 URL: https://issues.jboss.org/browse/TEIIDDES-1577 Project: Teiid Designer Issue Type: Bug Components: Import/Export Reporter: Tom Johnston Changing Connection URL under Properties Tab for Edit Driver Definitions does not have any impact when using the driver. I.E. When specifying a new connection profile the Connection URL (shaded, unchangeable here) does NOT reflect the aforementioned property. Use Case: I'm trying to create a new driver entry using Oracles OCI connectivity capability thus requiring a change in the connection url to (jdbc:oracle:oci:@<database_string> , for example) -- 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

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1576) Unnecessary table aliasing causing in pushdown query

by Tom Johnston (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1576?page=com.atlassian.jira.plu... ] Tom Johnston updated TEIIDDES-1576: ----------------------------------- Description: Create a Added a table manually to an existing physical model (generated from JDBC import). put source specific syntax as name in source for a column. When previewed I get an error because the g0 predicate was added to the column thus resulting in an invalid query. I proved the point by copy/paste the atomic query to the source directly (via Squirrel) it failed with the same error then removed the predicate references (both on column and table) and it succeeded. The source is Sybase. The Name in source entered for the column was: convert(varchar(16384),report)+convert(varchar(16384),impression)+convert(varchar(16384),signature) which resulted in the following push down SELECT g_0.convert(varchar(16384),report)+convert(varchar(16384),impression)+convert(varchar(16384),signature) FROM "pinspr"."dbo"."cdr_rad_obs" g_0 which when executed directly against sybase fails.. if the g_0 is removed entirely the query succeeds in against Sybase using Squirrel. was: Create a Added a table manually to an existing physical model (generated from JDBC import). put source specific syntax as name in source for a column. When previewed I get an error because the g0 predicate was added to the column thus resulting in an invalid query. I proved the point by copy/paste the atomic query to the source directly (via Squirrel) it failed with the same error then removed the predicate references (both on column and table) and it succeeded. > Unnecessary table aliasing causing in pushdown query > ---------------------------------------------------- > > Key: TEIIDDES-1576 > URL: https://issues.jboss.org/browse/TEIIDDES-1576 > Project: Teiid Designer > Issue Type: Bug > Components: Data Preview > Reporter: Tom Johnston > > Create a Added a table manually to an existing physical model (generated from JDBC import). put source specific syntax as name in source for a column. > When previewed I get an error because the g0 predicate was added to the column thus resulting in an invalid query. > I proved the point by copy/paste the atomic query to the source directly (via Squirrel) it failed with the same error then removed the predicate references (both on column and table) and it succeeded. > The source is Sybase. > The Name in source entered for the column was: > convert(varchar(16384),report)+convert(varchar(16384),impression)+convert(varchar(16384),signature) > which resulted in the following push down > SELECT g_0.convert(varchar(16384),report)+convert(varchar(16384),impression)+convert(varchar(16384),signature) FROM "pinspr"."dbo"."cdr_rad_obs" g_0 > which when executed directly against sybase fails.. > if the g_0 is removed entirely the query succeeds in against Sybase using Squirrel. -- 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

13 years, 3 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 February 2013