December 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1996) Add Problems tab in VDB editor to view warnings and errors if present in VDB

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1996: -------------------------------------- Summary: Add Problems tab in VDB editor to view warnings and errors if present in VDB Key: TEIIDDES-1996 URL: https://issues.jboss.org/browse/TEIIDDES-1996 Project: Teiid Designer Issue Type: Enhancement Components: Editors, VDB & Execution Affects Versions: 8.3 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Critical Fix For: 8.3.x If a VDB has errors and can't be deployed, there's no way to view those error messages in the VDB editor. Add a Problems tab next to the Source Binding Definition tab and display problems in table for selected model. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1995) Add templates for OBJECTTABLE, TEXTABLE, etc

by Van Halbert (JIRA)

Van Halbert created TEIIDDES-1995: ------------------------------------- Summary: Add templates for OBJECTTABLE, TEXTABLE, etc Key: TEIIDDES-1995 URL: https://issues.jboss.org/browse/TEIIDDES-1995 Project: Teiid Designer Issue Type: Enhancement Components: Transformations Affects Versions: 8.4 Reporter: Van Halbert Assignee: Barry LaFond Priority: Minor Add templates for using OBJECTTABLE, TEXTTABLE, etc. to the the list of templates to apply to the transformation. Example: SELECT o.{colname}, o.{colname} FROM {ObjectTableName} as T, OBJECTTABLE('x' PASSING T.{ObjectColumnName}Object as x COLUMNS {colname} type 'teiid_row.{colname}', ….) as o -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1993) Issues with allowing '.' character in object name without d-quoting the name

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1993?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1993. ------------------------------------ Assignee: Barry LaFond Resolution: Done * Added validation rule * Fixed JDBC Importer to automatically generate double-quoted names if names are fully qualified. > Issues with allowing '.' character in object name without d-quoting the name > ---------------------------------------------------------------------------- > > Key: TEIIDDES-1993 > URL: https://issues.jboss.org/browse/TEIIDDES-1993 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling, Validation > Affects Versions: 8.3 > Reporter: Barry LaFond > Assignee: Barry LaFond > Priority: Critical > Fix For: 8.3.x > > > Designer allows object names to contain "." character but does not force wrapping the name in double quotes. > The JDBC importer, for instance, allows creating with fully qualified names like: PARTSSUPPLIER.SUPPLIER for a table name. > The VDB Permission "resource-name" string value assumes that this name would be wrapped in d-quotes to prevent wrong interpretation of path. > * Need to auto-wrap name in JDBC Importer processor > * Create a validation rule (ERROR) to check for non-double-quoted names -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1994) Quick Fix for names requiring double-quote problem marker

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1994: -------------------------------------- Summary: Quick Fix for names requiring double-quote problem marker Key: TEIIDDES-1994 URL: https://issues.jboss.org/browse/TEIIDDES-1994 Project: Teiid Designer Issue Type: Feature Request Components: Validation Affects Versions: 8.3.x Reporter: Barry LaFond Fix For: 8.4 TEIIDDES-1993 introducted a new validation rule that checks to see if object names require double-quoting to be valid as Teiid runtime metadata. Designer's JDBC Importer allows using fully qualified names for table names (schema.table). Example: PARTSSUPPLIER.SUPPLIER will fail. Add a Quick Fix to turn hjelp turn this problem marker type into a simple fix of the name. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1993) Issues with allowing '.' character in object name without d-quoting the name

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1993?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1993: ---------------------------------------- Validation rules will check for Double-quoted name (can contain '.' character, but only other current valid characters (i.e. number, _, etc..) VALID NAME = "dbo.SUPPLIER" INVALID NAME = dbo.Supplier Resulting validation error message will state: *The name (Table.Name) contains the '.' delimiter. This name is required to be wrapped in double-quotes.* If the name contains an invalid character, it will still show a "info" message like: *The character '(' (at position 3) is not allowed; only alphabetic ([a-z]|[A-Z]), digit ([0-9])) or '_' are allowed* > Issues with allowing '.' character in object name without d-quoting the name > ---------------------------------------------------------------------------- > > Key: TEIIDDES-1993 > URL: https://issues.jboss.org/browse/TEIIDDES-1993 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling, Validation > Affects Versions: 8.3 > Reporter: Barry LaFond > Priority: Critical > Fix For: 8.3.x > > > Designer allows object names to contain "." character but does not force wrapping the name in double quotes. > The JDBC importer, for instance, allows creating with fully qualified names like: PARTSSUPPLIER.SUPPLIER for a table name. > The VDB Permission "resource-name" string value assumes that this name would be wrapped in d-quotes to prevent wrong interpretation of path. > * Need to auto-wrap name in JDBC Importer processor > * Create a validation rule (ERROR) to check for non-double-quoted names -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1861) Designer deletes data role "condition" information

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1861?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1861: ---------------------------------------- The issue arises because of the use of the fully-qualified table name referenced in the permission. This name contains the delimiter character '.' The permission's "resource-name" string value, (path-based name of the table) assumes the '.' is a path delimiter. Designer also assumes this when it tries to resolve that resource-name, and in this instance removes the permission because it couldn't find the table. The fix will require forcing double-quotes around all object names containing the '.' character, creating a validation rule (ERROR) to warn the user if they name it by hand, changing the JDBC Importer to wrap these names in d-quotes (if '.' present) and tweaking the DataRoleResolver.getTargetName() method to check for d-quotes when converting the resource-name to a IPath string (i.e. replacing '.' with a '/' character) > Designer deletes data role "condition" information > -------------------------------------------------- > > Key: TEIIDDES-1861 > URL: https://issues.jboss.org/browse/TEIIDDES-1861 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration, VDB & Execution > Affects Versions: 8.2 > Environment: Windows 7, Eclipse kepler. > Reporter: Pablo Navascues > Assignee: Barry LaFond > Fix For: 8.3.x > > Attachments: Teiiddes-1861-screencapture.m4v > > > Create a VDB > Create a source model by importing from JDBC > Add model to VDB > Define data role with a table wide condition like "USERNAME=substring(user(), 1, locate('@', user()) - 1)" > Synchronize, save VBD. > Condition is applied to queries, can be seen in the designer, can be seen in the VBD internal xml. > Keep working and after another save (not necessarily de second one) condition field value is empty in designer and gone from teh XML as well. > This has happened more than once and to more than one developer in the team. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1993) Issues with allowing '.' character in object name without d-quoting the name

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1993: -------------------------------------- Summary: Issues with allowing '.' character in object name without d-quoting the name Key: TEIIDDES-1993 URL: https://issues.jboss.org/browse/TEIIDDES-1993 Project: Teiid Designer Issue Type: Bug Components: Modeling, Validation Affects Versions: 8.3 Reporter: Barry LaFond Priority: Critical Fix For: 8.3.x Designer allows object names to contain "." character but does not force wrapping the name in double quotes. The JDBC importer, for instance, allows creating with fully qualified names like: PARTSSUPPLIER.SUPPLIER for a table name. The VDB Permission "resource-name" string value assumes that this name would be wrapped in d-quotes to prevent wrong interpretation of path. * Need to auto-wrap name in JDBC Importer processor * Create a validation rule (ERROR) to check for non-double-quoted names -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1989) Unable to deploy VDB because use Source Name didn't match datasource Pool Name

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1989?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1989: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1042914|https://bugzilla.redhat.com/show_bug.cgi?id=1042914] from NEW to ASSIGNED > Unable to deploy VDB because use Source Name didn't match datasource Pool Name > ------------------------------------------------------------------------------ > > Key: TEIIDDES-1989 > URL: https://issues.jboss.org/browse/TEIIDDES-1989 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 8.3 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 8.3.x > > > Created a VDB and used the defaults for the Source Name for the model when creating the bindings. However, unable to deploy the VDB until the Source Name was changed to match the Pool Name for the JNDI data source that is being used. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1989) Unable to deploy VDB because use Source Name didn't match datasource Pool Name

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1989?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-1989: ---------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1042914 > Unable to deploy VDB because use Source Name didn't match datasource Pool Name > ------------------------------------------------------------------------------ > > Key: TEIIDDES-1989 > URL: https://issues.jboss.org/browse/TEIIDDES-1989 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 8.3 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 8.3.x > > > Created a VDB and used the defaults for the Source Name for the model when creating the bindings. However, unable to deploy the VDB until the Source Name was changed to match the Pool Name for the JNDI data source that is being used. -- 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

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1986) When pasting a role condition it always is pasted twice

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1986?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-1986: ---------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1042910 > When pasting a role condition it always is pasted twice > ------------------------------------------------------- > > Key: TEIIDDES-1986 > URL: https://issues.jboss.org/browse/TEIIDDES-1986 > Project: Teiid Designer > Issue Type: Bug > Components: VDB & Execution > Affects Versions: 8.3 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 8.3.x > > > On the new role conditions functionality if you paste a value into the text box it is always pasted twice. -- 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

10 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues December 2013