January 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1558) VdbEditor 'Add Model' dialog shows a 'Server' folder

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1558?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1558. ------------------------------------- Resolution: Done Changed the filter for the 'Add Models' action in the VDBEditor. It now shows only the models within the same project as the VDB. Pull request: https://github.com/Teiid-Designer/teiid-designer/pull/75 > VdbEditor 'Add Model' dialog shows a 'Server' folder > ---------------------------------------------------- > > Key: TEIIDDES-1558 > URL: https://issues.jboss.org/browse/TEIIDDES-1558 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 8.0 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.1 > > > The 'Add Model' dialog in the VDB Editor shows a 'Server' folder in addition to the workspace projects... It should be filtered out. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1508) Add ability to Build a EDS VDB via APIe

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1508?page=com.atlassian.jira.plu... ] Steven Hawkins updated TEIIDDES-1508: ------------------------------------- Description: Ability to build a VDB pro-grammatically via an API The need is to build the VDB during their build process, so would like to pull XMI's into the build process, then bind them together into a VDB for release. This way the build process can choose which version of the XMI files to bundle together into the VDB. Also an addition to this, it would be (almost necessary) great to be able to define what goes into the VDB (roles, translators to use, translator overrides etc) in a file that we can provide to the API, and also that we can check in to our source control. was: Ability to build a VDB pro-grammatically via an API The need is to build the VDB during their build process, so would like to pull XMI's into the build process, then bind them together into a VDB for release. This way the build process can choose which version of the XMI files to bundle together into the VDB. Also an addition to this, it would be (almost necessary) great to be able to define what goes into the VDB (roles, translators to use, translator overrides etc) in a file that we can provide to the API, and also that we can check in to our source control. Assignee: (was: Steven Hawkins) > Add ability to Build a EDS VDB via APIe > --------------------------------------- > > Key: TEIIDDES-1508 > URL: https://issues.jboss.org/browse/TEIIDDES-1508 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Debbie Steigner > > Ability to build a VDB pro-grammatically via an API > The need is to build the VDB during their build process, so would like to pull XMI's into the build process, then bind them together into a VDB for release. This way the build process can choose which version of the XMI files to bundle together into the VDB. Also an addition to this, it would be (almost necessary) great to be able to define what goes into the VDB (roles, translators to use, translator overrides etc) in a file that we can provide to the API, and also that we can check in to our source control. -- 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

12 years

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-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-parameters.png, new-procedure-wizard-properties.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

12 years

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-parameters.png new-procedure-wizard-properties.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 > > > 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

12 years

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-properties.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 > > > 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

12 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1540) Non-UTF-8 Multi-byte characters imported from csv file are garbled

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1540?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-1540: ---------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=893583 > Non-UTF-8 Multi-byte characters imported from csv file are garbled > ------------------------------------------------------------------ > > Key: TEIIDDES-1540 > URL: https://issues.jboss.org/browse/TEIIDDES-1540 > Project: Teiid Designer > Issue Type: Bug > Components: Dialogs > Affects Versions: 7.7 > Reporter: Hisanobu Okuda > Assignee: Mark Drilling > Fix For: 8.1 > > > Non-UTF-8 Multi-byte characters imported from csv file are garbled. -- 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

12 years

1
0
0 / 0

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

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1255?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-1255: ---------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=893581 > 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.7, 7.4.4, 8.1 > > 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

12 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1558) VdbEditor 'Add Model' dialog shows a 'Server' folder

by Mark Drilling (JIRA)

Mark Drilling created TEIIDDES-1558: --------------------------------------- Summary: VdbEditor 'Add Model' dialog shows a 'Server' folder Key: TEIIDDES-1558 URL: https://issues.jboss.org/browse/TEIIDDES-1558 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 8.0 Reporter: Mark Drilling Assignee: Mark Drilling Fix For: 8.1 The 'Add Model' dialog in the VDB Editor shows a 'Server' folder in addition to the workspace projects... It should be filtered out. -- 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

12 years

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 commented on TEIIDDES-1255: ----------------------------------------- Pull request for master branch: https://github.com/Teiid-Designer/teiid-designer/pull/73 If it is decided to include this in a product patch, would need to pull back to the appropriate branch. > 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.7, 7.4.4, 8.1 > > 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

12 years

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 updated TEIIDDES-1255: ------------------------------------ Fix Version/s: 8.1 Affects Version/s: 7.7 > 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.7, 7.4.4, 8.1 > > 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

12 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues January 2013