February 2012 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1126) Add Wizard to Build "XML to Scalar" and "Scalar to XML" Procedures

by Ted Jones (Created) (JIRA)

Add Wizard to Build "XML to Scalar" and "Scalar to XML" Procedures ------------------------------------------------------------------- Key: TEIIDDES-1126 URL: https://issues.jboss.org/browse/TEIIDDES-1126 Project: Teiid Designer Issue Type: Enhancement Components: Transformations Affects Versions: 7.5 Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.6 Need a wizard to select model, procedure name, and schema elements to build procedures for "XML to Scalar" and "Scalar to XML" -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

6
6
0 / 0

[JBoss JIRA] (TEIIDDES-1209) Upgrade to use Teiid 8.0 Admin API

by Ramesh Reddy (Created) (JIRA)

Upgrade to use Teiid 8.0 Admin API ---------------------------------- Key: TEIIDDES-1209 URL: https://issues.jboss.org/browse/TEIIDDES-1209 Project: Teiid Designer Issue Type: Task Components: VDB & Execution Reporter: Ramesh Reddy Priority: Blocker Fix For: 8.0 Teiid 8.0 has more or less has the same Admin API as it's 7.x releases. However the Admin connection ownership no longer held with the Teiid. i.e Teiid does not control which port the Admin connection nor the security that goes along, these are now core features from AS itself. However, usage for the purposes of the Teiid Designer is not changed. Teiid Designer needs to be upgraded to use the 8.0 API and validate all the operations it provides. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-216) Designer removes parentheses around criteria in ansi join when using compound ON

by Marc Shirley (JIRA)

Designer removes parentheses around criteria in ansi join when using compound ON -------------------------------------------------------------------------------- Key: TEIIDDES-216 URL: https://jira.jboss.org/jira/browse/TEIIDDES-216 Project: Teiid Designer Issue Type: Bug Affects Versions: 6.1.0 Reporter: Marc Shirley In Designer, when validating a transformation that has compound criteria in an ansi join statement's ON, the parentheses are removed and the order of operations is modified as a result. This does not appear to occur when using the same parentheses structure in WHERE criteria. Before validation: SELECT * FROM bqt.SMALLA AS a INNER JOIN bqt.SMALLB AS b ON (a.INTKEY = b.INTKEY) AND (a.INTNUM IS NULL OR a.INTNUM = 11) After validation: SELECT * FROM bqt.SMALLA AS a INNER JOIN bqt.SMALLB AS b ON a.INTKEY = b.INTKEY AND (a.INTNUM IS NULL) OR (a.INTNUM = 11) After validating a second time: SELECT * FROM bqt.SMALLA AS a INNER JOIN bqt.SMALLB AS b ON ((a.INTKEY = b.INTKEY) AND (a.INTNUM IS NULL)) OR (a.INTNUM = 11) -- 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

12 years, 1 month

5
9
0 / 0

[JBoss JIRA] Created: (TEIIDDES-813) Fix Test Fragments That Are Calling Protected And Package Private Methods In Classes Found In Other Plugins

by Dan Florian (JIRA)

Fix Test Fragments That Are Calling Protected And Package Private Methods In Classes Found In Other Plugins ----------------------------------------------------------------------------------------------------------- Key: TEIIDDES-813 URL: https://issues.jboss.org/browse/TEIIDDES-813 Project: Teiid Designer Issue Type: Task Components: Build Affects Versions: 7.2 Reporter: Dan Florian Fix For: Future The org.teiid.designer.jdbc.test and org.teiid.designer.jdbc.relational.test fragments are calling protected and package private methods in classes that our not found in their host plugins. This is not allowed in OSGi and their tests fail during the nightly build. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

3
2
0 / 0

[JBoss JIRA] (TEIIDDES-1207) Merge the relational and function metamodels

by Steven Hawkins (Created) (JIRA)

Merge the relational and function metamodels -------------------------------------------- Key: TEIIDDES-1207 URL: https://issues.jboss.org/browse/TEIIDDES-1207 Project: Teiid Designer Issue Type: Quality Risk Components: Modeling Affects Versions: 8.0 Reporter: Steven Hawkins Having the function and relational models is no longer necessary. We can add the needed function metadata (including TEIIDDES-152 vararg support, null-on-null, etc.) through either extension properties or a metamodel change. This is in the vain of PostgreSQL which uses the create function syntax to add what would be procedures in other dbmses. Virtual functions (procedures marked as functions in a view layer) could also still specify transformation sql if pushdown is not required - rather than forcing the use of a java class. We could deprecate the old function model support of the Teiid side then. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

5
6
0 / 0

[JBoss JIRA] (TEIIDDES-1217) Create single built-in Relational MED

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1217: -------------------------------------- Summary: Create single built-in Relational MED Key: TEIIDDES-1217 URL: https://issues.jboss.org/browse/TEIIDDES-1217 Project: Teiid Designer Issue Type: Task Components: Extension Framework Affects Versions: 8.0 Reporter: Barry LaFond Priority: Blocker Fix For: 8.0 The plan to replace the existing Function metamodel by extending the Relational metamodel "procedure" object requires the definition of initial built-in MED targeted at the relational metamodel. This MED would contain properties required by TEIID (See FunctionMethod class for details) that will include a "category", function Class etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-963) Add jboss tools runtime detector for Teid Servers

by Max Rydahl Andersen (JIRA)

Add jboss tools runtime detector for Teid Servers ------------------------------------------------- Key: TEIIDDES-963 URL: https://issues.jboss.org/browse/TEIIDDES-963 Project: Teiid Designer Issue Type: Bug Reporter: Max Rydahl Andersen Priority: Critical Add teid runtime detection so users don't have to setup teiid servers when already installed into EAP. extension point is: org.jboss.tools.runtime.core.runtimeDetectors -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

6
16
0 / 0

[JBoss JIRA] Created: (TEIIDDES-220) New Model Wizard prefs for XML Doc Model not getting picked up.

by Mark Drilling (JIRA)

New Model Wizard prefs for XML Doc Model not getting picked up. --------------------------------------------------------------- Key: TEIIDDES-220 URL: https://jira.jboss.org/jira/browse/TEIIDDES-220 Project: Teiid Designer Issue Type: Bug Components: Dialogs Affects Versions: 6.0.0, 6.1.0, 6.2.0, Future Reporter: Mark Drilling Assignee: Mark Drilling Priority: Minor The mapping class generation preference is being saved, but is not being picked up correctly on relaunch of the New Model wizard. This results in the xml doc model potentially being generated with the incorrect mapping class generator preference. -- 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

12 years, 3 months

2
13
0 / 0

[JBoss JIRA] (TEIIDDES-1222) Convert Function Metamodel to built-in relational model MED

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1222: -------------------------------------- Summary: Convert Function Metamodel to built-in relational model MED Key: TEIIDDES-1222 URL: https://issues.jboss.org/browse/TEIIDDES-1222 Project: Teiid Designer Issue Type: Sub-task Reporter: Barry LaFond In order to retire the Function metamodel we need to replace it with extension properties on the relational metamodel via the new MED framework. in 7.5/7.6 the "Source Function" property (deterministic) is the only current built-in "relational" extended property. Probably could convert to use only 1 built-in MED that extends "Relational" metamodel. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-595) ModelAnnotations Are Created When Models Are Deleted

by Dan Florian (JIRA)

ModelAnnotations Are Created When Models Are Deleted ---------------------------------------------------- Key: TEIIDDES-595 URL: https://jira.jboss.org/browse/TEIIDDES-595 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.1 Reporter: Dan Florian Just selected a model in the Model Explorer and deleted it. I noticed that the ModelAnnotationImpl constructor was being called when the model was being deleted. This doesn't seem right but doesn't seem to affect anything. Here is the stack trace: Daemon Thread [Thread-0] (Suspended (breakpoint at line 389 in ModelAnnotationImpl)) ModelAnnotationImpl.<init>() line: 389 CoreFactoryImpl.createModelAnnotation() line: 127 CoreFactoryImpl.create(EClass) line: 53 MtkXmiHelper(XMLHelperImpl).createObject(EFactory, EClassifier) line: 891 MtkXmiHandler.createObjectFromFactory(EFactory, String) line: 161 MtkXmiHandler.createTopObject(String, String) line: 192 MtkXmiHandler(XMLHandler).processElement(String, String, String) line: 1019 MtkXmiHandler(XMIHandler).processElement(String, String, String) line: 87 MtkXmiHandler(XMLHandler).startElement(String, String, String) line: 1001 MtkXmiHandler.startElement(String, String, String) line: 769 MtkXmiHandler(XMLHandler).startElement(String, String, String, Attributes) line: 712 MtkXmiHandler(XMIHandler).startElement(String, String, String, Attributes) line: 169 SAXParserImpl$JAXPSAXParser(AbstractSAXParser).startElement(QName, XMLAttributes, Augmentations) line: 501 XMLDocumentScannerImpl(XMLDocumentFragmentScannerImpl).scanStartElement() line: 1363 XMLDocumentScannerImpl$ContentDriver(XMLDocumentFragmentScannerImpl$FragmentContentDriver).next() line: 2755 XMLDocumentScannerImpl.next() line: 648 XMLDocumentScannerImpl(XMLDocumentFragmentScannerImpl).scanDocument(boolean) line: 511 XIncludeAwareParserConfiguration(XML11Configuration).parse(boolean) line: 808 XIncludeAwareParserConfiguration(XML11Configuration).parse(XMLInputSource) line: 737 SAXParserImpl$JAXPSAXParser(XMLParser).parse(XMLInputSource) line: 119 SAXParserImpl$JAXPSAXParser(AbstractSAXParser).parse(InputSource) line: 1205 SAXParserImpl$JAXPSAXParser.parse(InputSource) line: 522 SAXParserImpl(SAXParser).parse(InputSource, DefaultHandler) line: 395 MtkXmiResourceLoader(XMLLoadImpl).load(XMLResource, InputStream, Map<?,?>) line: 181 MtkXmiResourceImpl.doLoad(InputStream, Map) line: 282 MtkXmiResourceImpl(ResourceImpl).load(InputStream, Map<?,?>) line: 1494 MtkXmiResourceImpl(ResourceImpl).load(Map<?,?>) line: 1282 MtkXmiResourceImpl.load(Map) line: 222 ModelBufferImpl.open(IProgressMonitor) line: 236 ModelResourceImpl.openBuffer(IProgressMonitor) line: 434 ModelResourceImpl(OpenableImpl).getBuffer() line: 381 ModelResourceImpl.refreshIndexType() line: 247 ModelWorkspaceManager$NotificationProcessor.refreshResourceIndexType(Object) line: 1162 ModelWorkspaceManager$NotificationProcessor.checkResourceForIndexing(Notification) line: 1137 ModelWorkspaceManager$NotificationProcessor.notifyChanged(Notification) line: 1151 ChangeNotifier.fireNotifyChanged(Notification) line: 51 UnitOfWorkImpl.commit() line: 251 ModelerCore.commitTxn() line: 356 DeleteResourceAction.closeResources(List) line: 324 DeleteResourceAction.doRun() line: 381 AbstractAction$1.run() line: 537 BusyIndicator.showWhile(Display, Runnable) line: 70 DeleteResourceAction(AbstractAction).run() line: 540 DeleteResourceAction(Action).runWithEvent(Event) line: 498 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues February 2012