August 2012 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1458) Import of DDL with Foreign Keys Fails.

by Steve Darnowsky (JIRA)

Steve Darnowsky created TEIIDDES-1458: ----------------------------------------- Summary: Import of DDL with Foreign Keys Fails. Key: TEIIDDES-1458 URL: https://issues.jboss.org/browse/TEIIDDES-1458 Project: Teiid Designer Issue Type: Bug Reporter: Steve Darnowsky -- 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, 4 months

3
4
0 / 0

[JBoss JIRA] (TEIIDDES-1348) Investigate Adding Additional VDB Properties

by Ted Jones (JIRA)

Ted Jones created TEIIDDES-1348: ----------------------------------- Summary: Investigate Adding Additional VDB Properties Key: TEIIDDES-1348 URL: https://issues.jboss.org/browse/TEIIDDES-1348 Project: Teiid Designer Issue Type: Enhancement Components: VDB & Execution Affects Versions: 7.7 Reporter: Ted Jones Fix For: 8.0 We currently allow the user to set the query timeout on the VDB. We had a request from the field to see if there were other properties we could set at that level and add to the tab. -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] (TEIIDDES-1476) Create readme for github repo

by Ted Jones (JIRA)

Ted Jones created TEIIDDES-1476: ----------------------------------- Summary: Create readme for github repo Key: TEIIDDES-1476 URL: https://issues.jboss.org/browse/TEIIDDES-1476 Project: Teiid Designer Issue Type: Task Components: Documentation Affects Versions: 8.0 Reporter: Ted Jones Fix For: 8.0 We need a readme.md file for our github repo that explains the project, development process, build process, etc. ModeShape's readme is a good example: https://github.com/ModeShape/modeshape -- 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, 4 months

2
1
0 / 0

[JBoss JIRA] (TEIIDDES-1452) Unable to install

by Steve Darnowsky (JIRA)

Steve Darnowsky created TEIIDDES-1452: ----------------------------------------- Summary: Unable to install Key: TEIIDDES-1452 URL: https://issues.jboss.org/browse/TEIIDDES-1452 Project: Teiid Designer Issue Type: Bug Components: Teiid Integration Affects Versions: 7.7 Environment: teiid designer 7.7, eclipse 3.7.2 Reporter: Steve Darnowsky Using Teiid designer 7.7 plug in in Eclipse 3.7.2. Created soruce model and then imported DDL. Selected import wsdl into source model procedure. Created connection profile that points to url for WSDL.Changed Source Model created in previous step. Status - "Existing model xxxx.xmi has connection profile for different wsdl. Continued to to next dialog. In the Procedure Defintion dialog added element name in Schema Contents window. Invalid Name error displayed - "The character "-" is not allowed...." Is there a workaround for the name restrictions? Also why is this status message displayed when I select an existing model in soruce definition dialog? If I select the radio button to generate legacy create and extract functions, the import completes successfully. -- 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, 4 months

4
6
0 / 0

[JBoss JIRA] (TEIIDDES-1326) Use findbugs to identify code bugs and potential problems

by Paul Richardson (JIRA)

Paul Richardson created TEIIDDES-1326: ----------------------------------------- Summary: Use findbugs to identify code bugs and potential problems Key: TEIIDDES-1326 URL: https://issues.jboss.org/browse/TEIIDDES-1326 Project: Teiid Designer Issue Type: Task Reporter: Paul Richardson Fix For: 8.0, Future Use the findbugs eclipse plugin to identify and fix potential coding problems and bugs. At creation of this issue, findbugs reports ~200 potential problems with the codebase, ranging from troubling - scariest. Some are false-positives but some do point to potential problems. Consider each one and fix if required. -- 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, 4 months

4
5
0 / 0

[JBoss JIRA] (TEIIDDES-1229) CLONE - Add support for a comparable binary type

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1229?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1229. ------------------------------------ Resolution: Done Done > CLONE - Add support for a comparable binary type > ------------------------------------------------ > > Key: TEIIDDES-1229 > URL: https://issues.jboss.org/browse/TEIIDDES-1229 > Project: Teiid Designer > Issue Type: Feature Request > Components: Teiid Integration > Reporter: Steven Hawkins > Assignee: Barry LaFond > Fix For: 8.0 > > > Teiid currently lacks a binary/varbinary type. Since we have both blob/clob, it would be natural to also introduce a varbinary analog to string. It would be a comparable type and need an escape syntax for entering literals. Translators would need to be modified to account for binary literals. > See the forum post for current workarounds. We also as a one off have previously allowed clob types to be comparable, see also TEIID-1248. Another approach would by to allow clob/blob to comparable in Teiid, but possibly not at the source as per the searchability metadata. We would still need to support an escape syntax and modify translators to use native type information and the appropriate literal format. The advantage of this latter approach is that there is nothing more that designer must do to support this case. The most practical benefit from introducing a varbinary type would be in having a better size estimate (it would be limited to 8000 bytes) for buffering. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1229) CLONE - Add support for a comparable binary type

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1229?page=com.atlassian.jira.plu... ] Steven Hawkins commented on TEIIDDES-1229: ------------------------------------------ we're using base64Binary on the Teiid side. Also, the type info for teiid is now in engine/src/manin/resources/org/teiid/metadata/types.dat > CLONE - Add support for a comparable binary type > ------------------------------------------------ > > Key: TEIIDDES-1229 > URL: https://issues.jboss.org/browse/TEIIDDES-1229 > Project: Teiid Designer > Issue Type: Feature Request > Components: Teiid Integration > Reporter: Steven Hawkins > Assignee: Barry LaFond > Fix For: 8.0 > > > Teiid currently lacks a binary/varbinary type. Since we have both blob/clob, it would be natural to also introduce a varbinary analog to string. It would be a comparable type and need an escape syntax for entering literals. Translators would need to be modified to account for binary literals. > See the forum post for current workarounds. We also as a one off have previously allowed clob types to be comparable, see also TEIID-1248. Another approach would by to allow clob/blob to comparable in Teiid, but possibly not at the source as per the searchability metadata. We would still need to support an escape syntax and modify translators to use native type information and the appropriate literal format. The advantage of this latter approach is that there is nothing more that designer must do to support this case. The most practical benefit from introducing a varbinary type would be in having a better size estimate (it would be limited to 8000 bytes) for buffering. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1229) CLONE - Add support for a comparable binary type

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1229?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1229: ---------------------------------------- For 8.0 it'd be the simplest solution to add varbinary to our built-in datatypes xsd. I need a base-type for varbinary and not sure which one. (i.e. open Desginer's Datatype Hiearchy View) Would it be anySimpleType? or would I use the existing base64Binary as the base type? > CLONE - Add support for a comparable binary type > ------------------------------------------------ > > Key: TEIIDDES-1229 > URL: https://issues.jboss.org/browse/TEIIDDES-1229 > Project: Teiid Designer > Issue Type: Feature Request > Components: Teiid Integration > Reporter: Steven Hawkins > Assignee: Barry LaFond > Fix For: 8.0 > > > Teiid currently lacks a binary/varbinary type. Since we have both blob/clob, it would be natural to also introduce a varbinary analog to string. It would be a comparable type and need an escape syntax for entering literals. Translators would need to be modified to account for binary literals. > See the forum post for current workarounds. We also as a one off have previously allowed clob types to be comparable, see also TEIID-1248. Another approach would by to allow clob/blob to comparable in Teiid, but possibly not at the source as per the searchability metadata. We would still need to support an escape syntax and modify translators to use native type information and the appropriate literal format. The advantage of this latter approach is that there is nothing more that designer must do to support this case. The most practical benefit from introducing a varbinary type would be in having a better size estimate (it would be limited to 8000 bytes) for buffering. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1474) Preview Data on certain models causes JBDS to go into unrecoverable loop

by Blaine Mincey (JIRA)

Blaine Mincey created TEIIDDES-1474: --------------------------------------- Summary: Preview Data on certain models causes JBDS to go into unrecoverable loop Key: TEIIDDES-1474 URL: https://issues.jboss.org/browse/TEIIDDES-1474 Project: Teiid Designer Issue Type: Bug Components: Data Preview Affects Versions: 7.1.1 Environment: Have attempted on both RHEL 6.3 and Mac OSX. Used JBDS 5.0 with latest plugins and EDS 5.3. Reporter: Blaine Mincey When using the FinancialsDemo, our internal demo project (https://docspace.corp.redhat.com/docs/DOC-56653), previewing data from the CustomerHoldings/BrokerageModel (models AccountHoldings, AccountValue, and HighNetWorthCustomers) causes JBDS/Teiid to go into an unrecoverable loop where you must abruptly "force quit" the IDE to regain control. I have also seen this behavior when attempting to preview data from one of the included Web Services in the project. The following snippet is repeated multiple times in the EDS server log at the time that the process seems to get stuck in a loop: 2012-08-15 15:10:29,866 INFO [org.teiid.RUNTIME] (New I/O server worker #2-1) org.teiid.query.tempdata.GlobalTableStoreImpl@644ec403 first member or timeout exceeded 2012-08-15 15:10:29,881 INFO [org.teiid.PROCESSOR] (New I/O server worker #2-1) Clearing prepared plan cache for vdb PREVIEW_70a7a0cb-5c46-4589-aa1c-9018517e0c0f_FinancialsDemo_project.1 2012-08-15 15:10:29,882 INFO [org.teiid.PROCESSOR] (New I/O server worker #2-1) Clearing the resultset cache for vdb PREVIEW_70a7a0cb-5c46-4589-aa1c-9018517e0c0f_FinancialsDemo_project.1 2012-08-15 15:10:29,896 INFO [STDOUT] (New I/O server worker #2-1) -- 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, 4 months

1
0
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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues August 2012