February 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1523) Source Function And Procedure Modeling And Terminology Is Confusing

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1523?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1523: ----------------------------------- Attachment: (was: new-procedure-wizard-parameters.png) > Source Function And Procedure Modeling And Terminology Is Confusing > ------------------------------------------------------------------- > > Key: TEIIDDES-1523 > URL: https://issues.jboss.org/browse/TEIIDDES-1523 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 7.8 > Reporter: Dan Florian > Assignee: Barry LaFond > Fix For: 8.1 > > Attachments: new-procedure-wizard-procedure-option.png, new-procedure-wizard-source-function-option.png, new-procedure-wizard-udf-option.png, select-procedure-type-dialog.png > > > It is very confusing that creating a "Source Function" and creating a "Procedure" both end up with model objects of type "Procedure." The source function wizard sets a procedure's "function" property to "true" and requires the user to create one or more inputs and one output. However, after finishing the wizard, the user is free to delete the inputs, delete the output, and set the "function" property to "false" if they so choose (in essence making it just a procedure). Alternatively, the user could start by creating a procedure, then set the "function" property to "true," add one or more inputs, add an output, and end up creating a "source function." Maybe the source function wizard could be adapted and used when creating procedures. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1523) Source Function And Procedure Modeling And Terminology Is Confusing

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1523?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1523: ----------------------------------- Attachment: (was: new-procedure-wizard-resultset.png) > Source Function And Procedure Modeling And Terminology Is Confusing > ------------------------------------------------------------------- > > Key: TEIIDDES-1523 > URL: https://issues.jboss.org/browse/TEIIDDES-1523 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 7.8 > Reporter: Dan Florian > Assignee: Barry LaFond > Fix For: 8.1 > > Attachments: new-procedure-wizard-procedure-option.png, new-procedure-wizard-source-function-option.png, new-procedure-wizard-udf-option.png, select-procedure-type-dialog.png > > > It is very confusing that creating a "Source Function" and creating a "Procedure" both end up with model objects of type "Procedure." The source function wizard sets a procedure's "function" property to "true" and requires the user to create one or more inputs and one output. However, after finishing the wizard, the user is free to delete the inputs, delete the output, and set the "function" property to "false" if they so choose (in essence making it just a procedure). Alternatively, the user could start by creating a procedure, then set the "function" property to "true," add one or more inputs, add an output, and end up creating a "source function." Maybe the source function wizard could be adapted and used when creating procedures. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1523) Source Function And Procedure Modeling And Terminology Is Confusing

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1523?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1523: ----------------------------------- Attachment: new-procedure-wizard-procedure-option.png new-procedure-wizard-source-function-option.png new-procedure-wizard-udf-option.png > Source Function And Procedure Modeling And Terminology Is Confusing > ------------------------------------------------------------------- > > Key: TEIIDDES-1523 > URL: https://issues.jboss.org/browse/TEIIDDES-1523 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 7.8 > Reporter: Dan Florian > Assignee: Barry LaFond > Fix For: 8.1 > > Attachments: new-procedure-wizard-procedure-option.png, new-procedure-wizard-source-function-option.png, new-procedure-wizard-udf-option.png, select-procedure-type-dialog.png > > > It is very confusing that creating a "Source Function" and creating a "Procedure" both end up with model objects of type "Procedure." The source function wizard sets a procedure's "function" property to "true" and requires the user to create one or more inputs and one output. However, after finishing the wizard, the user is free to delete the inputs, delete the output, and set the "function" property to "false" if they so choose (in essence making it just a procedure). Alternatively, the user could start by creating a procedure, then set the "function" property to "true," add one or more inputs, add an output, and end up creating a "source function." Maybe the source function wizard could be adapted and used when creating procedures. -- 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

11 years, 11 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 resolved TEIIDDES-1576. -------------------------------------- Resolution: Rejected Marking as rejected since this applies to server concerns and is not considered valid as per the last two comments. > 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1255) Execution plan without executing the query

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1255?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1255. ------------------------------------- Resolution: Done > Execution plan without executing the query > ------------------------------------------ > > Key: TEIIDDES-1255 > URL: https://issues.jboss.org/browse/TEIIDDES-1255 > Project: Teiid Designer > Issue Type: Bug > Components: Data Preview, Transformations > Affects Versions: 7.6, 7.7 > Reporter: Ramesh Reddy > Assignee: Mark Drilling > Fix For: 7.4.4, 8.1, 7.7 > > Attachments: patch-TeiidAdHocScriptRunnable.txt > > > DTP execution panel, when user right clicks on the query and ask for execution plan then no execution plan is returned. Only if the user executes the query then the execution plan, then user requests for plan it is returned. A query plan can be retrived by excuting > SET NOEXEC ON > <query> > SET NOEXEC OFF > Also, when I tried to manually do the above steps in the DTP SQL Scrap Book, then it seemed like it is using a separate connection for each of the abouve commands. so to check that we did > SET NOEXEC OFF > SHOW NOEXEC -> result was -> NULL (should have been ON) -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1580) During JDBC import it the ability to multiselect tables for import is critical

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1580?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1580: ---------------------------------------- Tom... please add description. The title is insufficient to describe this issue > During JDBC import it the ability to multiselect tables for import is critical > ------------------------------------------------------------------------------ > > Key: TEIIDDES-1580 > URL: https://issues.jboss.org/browse/TEIIDDES-1580 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Reporter: Tom Johnston > -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1580) During JDBC import it the ability to multiselect tables for import is critical

by Tom Johnston (JIRA)

Tom Johnston created TEIIDDES-1580: -------------------------------------- Summary: During JDBC import it the ability to multiselect tables for import is critical Key: TEIIDDES-1580 URL: https://issues.jboss.org/browse/TEIIDDES-1580 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export Reporter: Tom Johnston -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1523) Source Function And Procedure Modeling And Terminology Is Confusing

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1523?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1523: ----------------------------------- Attachment: select-procedure-type-dialog.png > Source Function And Procedure Modeling And Terminology Is Confusing > ------------------------------------------------------------------- > > Key: TEIIDDES-1523 > URL: https://issues.jboss.org/browse/TEIIDDES-1523 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 7.8 > Reporter: Dan Florian > Assignee: Barry LaFond > Fix For: 8.1 > > Attachments: new-procedure-wizard-parameters.png, new-procedure-wizard-properties.png, new-procedure-wizard-resultset.png, select-procedure-type-dialog.png > > > It is very confusing that creating a "Source Function" and creating a "Procedure" both end up with model objects of type "Procedure." The source function wizard sets a procedure's "function" property to "true" and requires the user to create one or more inputs and one output. However, after finishing the wizard, the user is free to delete the inputs, delete the output, and set the "function" property to "false" if they so choose (in essence making it just a procedure). Alternatively, the user could start by creating a procedure, then set the "function" property to "true," add one or more inputs, add an output, and end up creating a "source function." Maybe the source function wizard could be adapted and used when creating procedures. -- 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

11 years, 11 months

1
0
0 / 0

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

by Dan Florian (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1579?page=com.atlassian.jira.plu... ] Dan Florian closed TEIIDDES-1579. --------------------------------- Resolution: Done Pull request merged into komodo branch. > 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

11 years, 11 months

1
0
0 / 0

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

by Dan Florian (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1579?page=com.atlassian.jira.plu... ] Dan Florian updated TEIIDDES-1579: ---------------------------------- Git Pull Request: https://github.com/Teiid-Designer/teiid-designer/pull/93 > 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

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