[JBoss JIRA] Commented: (TEIIDDES-907) In Designer, the default data type length could cause issues when accessing EDS via ODBC
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-907?page=com.atlassian.jira.plug... ]
Barry LaFond commented on TEIIDDES-907:
---------------------------------------
Not sure what "default data type length" is referred to here in Designer. Is it in the JDBC Importer? or somewhere in the Transformation Editor/Reconciler?
> In Designer, the default data type length could cause issues when accessing EDS via ODBC
> ----------------------------------------------------------------------------------------
>
> Key: TEIIDDES-907
> URL: https://issues.jboss.org/browse/TEIIDDES-907
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 7.1.1
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 7.5
>
>
> Customers that are building VDB's to be accessed via ODBC will be wrong when the MAX_INT default is used. The following exception will be seen in the server log when this occurs:
> 1 [FunctionExecutionException] ERR.015.001.0033: Error Code:ERR.015.001.0033 Message:Error converting [2,097,152] of type integer to type short
> 2 [TransformationException]The Integer value '2,097,152' is outside the of range for Short
> at org.teiid.query.function.FunctionDescriptor.invokeFunction(FunctionDescriptor.java:259)
> at org.teiid.query.eval.Evaluator.evaluate(Evaluator.java:969)
> at org.teiid.query.eval.Evaluator.internalEvaluate(Evaluator.java:633)
> at org.teiid.query.eval.Evaluator.evaluate(Evaluator.java:603)
> ... 39 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (TEIIDDES-715) Oracle metadata import using Designer takes long time for large schemas
by Ramesh Reddy (JIRA)
Oracle metadata import using Designer takes long time for large schemas
-----------------------------------------------------------------------
Key: TEIIDDES-715
URL: https://jira.jboss.org/browse/TEIIDDES-715
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 7.1
Reporter: Ramesh Reddy
Importing metadata from Oracle database seems to take longer than any other database, when the underlying the schema is large. This may be because the default settings with Oracle Driver tries to get lot more metadata then needed. Should explore ways to minimize the time to take import.
Teiid in the Dynamic VDB import uses "Table Types" and "schema" name to limit the number of tables it imports, may be we should adopt similar thing in Designer. It is possible that Designer is already doing such settings.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Moved: (TEIIDDES-996) Create Web Service fails if the model contains 2 schemas with the same tablenames underneath
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-996?page=com.atlassian.jira.plug... ]
Van Halbert moved SOA-3130 to TEIIDDES-996:
-------------------------------------------
Project: Teiid Designer (was: JBoss Enterprise SOA Platform)
Key: TEIIDDES-996 (was: SOA-3130)
Affects Version/s: 7.4
(was: 5.1.0 GA)
Component/s: Import/Export
(was: EDS)
Security: (was: Public)
> Create Web Service fails if the model contains 2 schemas with the same tablenames underneath
> --------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-996
> URL: https://issues.jboss.org/browse/TEIIDDES-996
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 7.4
> Reporter: Debbie Steigner
> Assignee: Van Halbert
> Labels: eds
>
> In Teiid Designer, if you import a Source Model that contains 2 schemas, each schema contains tables with the same name. Right-click > Modeling > Create Web Service fails:
> "The name table_a_OutputView is the same (ignoring case) as 1 other object(s) under the same parent."
> The default names for the table Output Views should also contain the schema/folder names, i.e. schemaA_tableA_OutputView.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (TEIIDDES-957) Exception Message blank
by Joel Tosi (JIRA)
Exception Message blank
-----------------------
Key: TEIIDDES-957
URL: https://issues.jboss.org/browse/TEIIDDES-957
Project: Teiid Designer
Issue Type: Bug
Components: Eclipse Integration
Affects Versions: 7.2
Environment: JBDS 4.0.0 GA
Reporter: Joel Tosi
I have an exception in my view and the error in the message log is blank. Double clicking on it, I can see a NullPointerException, but in the message log, it is blank. Here is the full exception (after double clicking on message)
java.lang.NullPointerException
at org.teiid.designer.runtime.preview.PreviewManager.needsToBeDeployed(PreviewManager.java:1086)
at org.teiid.designer.runtime.preview.PreviewManager.previewSetup(PreviewManager.java:1216)
at com.metamatrix.modeler.internal.dqp.ui.actions.PreviewTableDataContextAction$2.run(PreviewTableDataContextAction.java:444)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Updated: (TEIIDDES-323) Option to copy from an XSD model of the same model class throws NPE
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-323?page=com.atlassian.jira.plug... ]
Barry LaFond updated TEIIDDES-323:
----------------------------------
Summary: Option to copy from an XSD model of the same model class throws NPE (was: Option to copy from a model of the same model class has several defects)
Fix Version/s: 8.0
(was: 7.5)
Description:
Though there were other metamodels that had problems in 6.x release, the only one left is copying an XSD model
java.lang.NullPointerException
at com.metamatrix.core.util.PluginUtilImpl.log(PluginUtilImpl.java:238)
at com.metamatrix.modeler.internal.ui.wizards.StructuralCopyContributor.doFinish(StructuralCopyContributor.java:86)
at com.metamatrix.modeler.internal.ui.wizards.NewModelWizard$3.run(NewModelWizard.java:341)
Actual NPE is coming from:
org.eclipse.xsd.impl.XSDAttributeUseImpl.analyze() line: 790
and the rest of the stack is basically EMF based on giving the EMF CopyCommand a model to copy.
was:
If you choose to create a copy of a model of one of these model classes, the copy will be incorrect.
View Models - Found problems validating the transformation
XSD - Premature EOF (exception in Message Log)
Web Service - input is specified with an unknown group context
I found this using the Books Project. I'm attaching a model project set created after I made the copies.
Relational source models work, though :-)
> Option to copy from an XSD model of the same model class throws NPE
> -------------------------------------------------------------------
>
> Key: TEIIDDES-323
> URL: https://issues.jboss.org/browse/TEIIDDES-323
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 7.4
> Environment: fedora 10
> Reporter: Paul Nittel
> Assignee: Barry LaFond
> Fix For: 8.0
>
> Attachments: JBEDSP-979_MPS.zip
>
>
> Though there were other metamodels that had problems in 6.x release, the only one left is copying an XSD model
> java.lang.NullPointerException
> at com.metamatrix.core.util.PluginUtilImpl.log(PluginUtilImpl.java:238)
> at com.metamatrix.modeler.internal.ui.wizards.StructuralCopyContributor.doFinish(StructuralCopyContributor.java:86)
> at com.metamatrix.modeler.internal.ui.wizards.NewModelWizard$3.run(NewModelWizard.java:341)
> Actual NPE is coming from:
> org.eclipse.xsd.impl.XSDAttributeUseImpl.analyze() line: 790
> and the rest of the stack is basically EMF based on giving the EMF CopyCommand a model to copy.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (TEIIDDES-961) Dependency Diagram not responding to edit events
by Barry LaFond (JIRA)
Dependency Diagram not responding to edit events
------------------------------------------------
Key: TEIIDDES-961
URL: https://issues.jboss.org/browse/TEIIDDES-961
Project: Teiid Designer
Issue Type: Bug
Components: Diagrams
Affects Versions: 7.4
Reporter: Barry LaFond
Fix For: 7.5
1) Open Dependency Diagram for a virtual table
2) Delete the Virtual table
3) Diagram does nothing and still shows deleted table
4) Refresh Diagram and it turns white due to exception:
java.lang.IllegalArgumentException: TransformationHelper.getTransformationMappingRoot:null or invalid target.
at com.metamatrix.modeler.internal.transformation.util.TransformationHelper.getTransformationMappingRoot(TransformationHelper.java:2493)
at com.metamatrix.modeler.internal.transformation.util.TransformationHelper.getTransformationMappingRoot(TransformationHelper.java:2534)
at com.metamatrix.modeler.transformation.ui.model.TransformationDiagramModelFactory.getTransformationObject(TransformationDiagramModelFactory.java:356)
at com.metamatrix.modeler.transformation.ui.model.TransformationDiagramModelFactory.getTransformationDiagramContents(TransformationDiagramModelFactory.java:151)
at com.metamatrix.modeler.transformation.ui.model.TransformationDiagramModelFactory.createModel(TransformationDiagramModelFactory.java:107)
at com.metamatrix.modeler.diagram.ui.editor.DiagramEditor.createModel(DiagramEditor.java:391)
at com.metamatrix.modeler.diagram.ui.editor.DiagramEditor.setDiagram(DiagramEditor.java:1484)
at com.metamatrix.modeler.diagram.ui.editor.DiagramEditor$5.run(DiagramEditor.java:1180)
at com.metamatrix.ui.internal.viewsupport.UiBusyIndicator.showWhile(UiBusyIndicator.java:80)
at com.metamatrix.modeler.diagram.ui.editor.DiagramEditor.openContext(DiagramEditor.java:1178)
at com.metamatrix.modeler.diagram.ui.actions.RefreshAction.doRun(RefreshAction.java:50)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months