May 2009 - teiid-designer-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIIDDES-196) Change default for UDF property *deterministic* from false to true to improve usability

by Jerry Helbling (JIRA)

Change default for UDF property *deterministic* from false to true to improve usability --------------------------------------------------------------------------------------- Key: TEIIDDES-196 URL: https://jira.jboss.org/jira/browse/TEIIDDES-196 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 6.1.0 Reporter: Jerry Helbling Priority: Minor [related to internal case IT281239] Change the default value for the 'deterministic' property of User Defined Functions to true, so UDFs will be specified as 'deterministic' by default. Currently the default value for the 'deterministic' property of User Defined Functions is false. It is probably false because that is the usual default for a boolean property. This is a usability issue because a user who creates a new UDF without paying attention to, and explicitly setting this property will wind up creating a non-deterministic UDF, by default. That is a bad outcome for several reasons. First, most Functions, including User Defined Functions, are deterministic, not non-deterministic. So in most cases the current default makes it more likely that this property will be specified incorrectly. Secondly, specifying that a UDF is non-deterministic when it is really deterministic may create unnecessary performance issues. For example, the planner has the ability to optimize the placement of a deterministic function so that it can be called the fewest number of times. It is unable to do that with non-deterministic functions. More critically, a change was made to all versions in Feb 2009 (see Jira TEIID-16) that prevents the merging of queries if one of them contains a non-deterministic function. This can have a dramatically negative effect on performance (see internal case IT281239). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-136) VDB's configuration.def contains more info than needed/desired

by Paul Nittel (JIRA)

VDB's configuration.def contains more info than needed/desired -------------------------------------------------------------- Key: TEIIDDES-136 URL: https://jira.jboss.org/jira/browse/TEIIDDES-136 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 6.0.0 Environment: fedora 10, Teiid 6.0.0, Teiid Designer 040709 Reporter: Paul Nittel I exported the PartsSupplier_VDB and used that with Teiid Embedded. I was unable to connect to the data sources (Oracle and SQL Server). Ramesh determined we could either copy in the Designer's configuration.xml file or edit the VDBs configuration.def and change the encrypted password to plain text. Ramesh will fill in the technical details. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

4
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-197) Update Designer To Use Teiid Embedded 6.1.0

by Dan Florian (JIRA)

Update Designer To Use Teiid Embedded 6.1.0 ------------------------------------------- Key: TEIIDDES-197 URL: https://jira.jboss.org/jira/browse/TEIIDDES-197 Project: Teiid Designer Issue Type: Task Affects Versions: 6.1.0 Reporter: Dan Florian Assignee: Dan Florian Priority: Blocker Fix For: 6.1.0 Need to integrate with the latest Teiid Embedded 6.1.0 Snapshot. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-195) Missing icon in query.ui plugin

by Barry LaFond (JIRA)

Missing icon in query.ui plugin ------------------------------- Key: TEIIDDES-195 URL: https://jira.jboss.org/jira/browse/TEIIDDES-195 Project: Teiid Designer Issue Type: Bug Components: Views Affects Versions: 6.0.0 Reporter: Barry LaFond Assignee: Barry LaFond Fix For: 6.1.0 While testing adding sources to Union queries I got an exception in the QueryTreeContentProvider... org.eclipse.jface.resource.DeviceResourceException: Unable to create resource URLImageDescriptor(bundleentry://457/icons/full/obj16/join.gif) at org.eclipse.jface.resource.ImageDescriptor.createResource(ImageDescriptor.java:167) at org.eclipse.jface.resource.DeviceResourceManager.allocate(DeviceResourceManager.java:56) at org.eclipse.jface.resource.AbstractResourceManager.create(AbstractResourceManager.java:88) There is no join.gif and apparently there never has been. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-90) No auto rename when adding elements to XML document

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-90?page=com.atlassian.jira.pl... ] Barry LaFond resolved TEIIDDES-90. ---------------------------------- Resolution: Duplicate Issue Same symptom as TEIIDDES-88 which was fixed today. Marking as Duplicate. > No auto rename when adding elements to XML document > --------------------------------------------------- > > Key: TEIIDDES-90 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-90 > Project: Teiid Designer > Issue Type: Task > Components: Views > Affects Versions: 6.0.0 > Environment: Linux > Reporter: Paul Nittel > Assignee: Barry LaFond > Fix For: 6.1.0 > > > I'm following the E2E XML Schemaless BookListing test script which calls for manually adding a number of elements to a document model. As I add each one, the name "NewXmlElement" is displayed. To change that name, I have to right-click > Rename. > Should be auto-renaming for me. (And the model is open in the editor.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIIDDES-90) No auto rename when adding elements to XML document

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-90?page=com.atlassian.jira.pl... ] Barry LaFond reassigned TEIIDDES-90: ------------------------------------ Assignee: Barry LaFond > No auto rename when adding elements to XML document > --------------------------------------------------- > > Key: TEIIDDES-90 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-90 > Project: Teiid Designer > Issue Type: Task > Components: Views > Affects Versions: 6.0.0 > Environment: Linux > Reporter: Paul Nittel > Assignee: Barry LaFond > Fix For: 6.1.0 > > > I'm following the E2E XML Schemaless BookListing test script which calls for manually adding a number of elements to a document model. As I add each one, the name "NewXmlElement" is displayed. To change that name, I have to right-click > Rename. > Should be auto-renaming for me. (And the model is open in the editor.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Assigned: (TEIIDDES-88) Creating base table in view model doesn't use auto-naming feature

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-88?page=com.atlassian.jira.pl... ] Barry LaFond reassigned TEIIDDES-88: ------------------------------------ Assignee: Barry LaFond > Creating base table in view model doesn't use auto-naming feature > ----------------------------------------------------------------- > > Key: TEIIDDES-88 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-88 > Project: Teiid Designer > Issue Type: Task > Components: Views > Affects Versions: 6.0.0 > Environment: Linux > Reporter: Paul Nittel > Assignee: Barry LaFond > Fix For: 6.1.0 > > > When adding a base table to a relational view model, it names it NewBaseTable and requires the user to manually rename the table. It should be coming up in rename mode. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-88) Creating base table in view model doesn't use auto-naming feature

by Barry LaFond (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-88?page=com.atlassian.jira.pl... ] Barry LaFond resolved TEIIDDES-88. ---------------------------------- Resolution: Done Fixes auto-renaming problems. Delays the open-in-editor to the action's postRun() method. Removed redundant Operations Editor selection logic to minimize impact of selection during rename. Reviewed by John V. Removed update of Operations editor tree view with workspace selection. Removed focus problems with in-line rename in Model Explorer. > Creating base table in view model doesn't use auto-naming feature > ----------------------------------------------------------------- > > Key: TEIIDDES-88 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-88 > Project: Teiid Designer > Issue Type: Task > Components: Views > Affects Versions: 6.0.0 > Environment: Linux > Reporter: Paul Nittel > Fix For: 6.1.0 > > > When adding a base table to a relational view model, it names it NewBaseTable and requires the user to manually rename the table. It should be coming up in rename mode. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-182) Salesforce Importer should retrieve the Distinct Value Count for each column when creating the models, in order to improve cost-based query optimization

by John Doyle (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-182?page=com.atlassian.jira.p... ] John Doyle resolved TEIIDDES-182. --------------------------------- Resolution: Done Revision 258 I implemented this for the initial import. > Salesforce Importer should retrieve the Distinct Value Count for each column when creating the models, in order to improve cost-based query optimization > -------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-182 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-182 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 6.0.0 > Environment: SFDC connector tech preview, windows 2003 server, MMX 5.5 > Reporter: Michael Walker > Assignee: John Doyle > Fix For: 6.1.0 > > > The importer brings in table cardinality, but for even better query optimization, we should also bring in distinct value count, or provide an option to do so. > This may be a larger one-time cost during import, but it's well worth it, and definitely is faster than doing it by hand for every column in every object in SFDC. It greatly impacts performance, especially for dependent join scenarios, since many SFDC columns/fields happen to have very low distinct value counts. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-187) Renaming Simple Datatype in SDE does not update name in datatypes list box

by Barry LaFond (JIRA)

Renaming Simple Datatype in SDE does not update name in datatypes list box -------------------------------------------------------------------------- Key: TEIIDDES-187 URL: https://jira.jboss.org/jira/browse/TEIIDDES-187 Project: Teiid Designer Issue Type: Bug Components: Editors Affects Versions: 6.0.0 Reporter: Barry LaFond Fix For: Future 1) Opened BooksDatatypes.xsd in Simple Datatypes Editor (SDE) 2) Selected PublisherYear in SDE upper left datatypes list box 3) Selected "change" link and renamed to "Temporary" 4) Saved ALL 5) Name in SDE upper left datatypes list box did not change 6) Closing editor and re-opening refreshes name correctly. List box label provider needs to get notified of the change so it can update. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues May 2009