[JBoss JIRA] (TEIIDDES-1914) Recursive element - mismatch column names between mapping classes
by Lucie Fabrikova (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1914?page=com.atlassian.jira.plu... ]
Lucie Fabrikova commented on TEIIDDES-1914:
-------------------------------------------
It is in tab "Problems", as error, with description "Column type mismatch between recursion root mapping class Employee and recursion child mapping class Supervisor", location "Mapping Class Set Container/Mapping Classes/Supervisor", in EmpDoc.xmi.
> Recursive element - mismatch column names between mapping classes
> -----------------------------------------------------------------
>
> Key: TEIIDDES-1914
> URL: https://issues.jboss.org/browse/TEIIDDES-1914
> Project: Teiid Designer
> Issue Type: Feature Request
> Affects Versions: 8.2
> Environment: JBDS 7.0.1.GA, Teiid Designer 8.2Final
> Reporter: Lucie Fabrikova
> Assignee: Mark Drilling
> Fix For: 8.3
>
>
> I run the E2eRecursiveXmlTextSourceTestScript; the XML view model from XSD contains mapping classes Employee and Supervisor. Next I copy the attributes from Employee to Supervisor. If the order of columns in Supervisor isn't the same as in Employee, I get
> "Mismatch column name between mapping class Employee and Supervisor"
> I am not sure if this is bug or if the message error is considered self-explanatory.
--
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
12 years, 5 months
[JBoss JIRA] (TEIIDDES-1920) Cannot create relational source with Sybase jconn4.jar
by Lucie Fabrikova (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1920?page=com.atlassian.jira.plu... ]
Lucie Fabrikova edited comment on TEIIDDES-1920 at 11/20/13 4:01 AM:
---------------------------------------------------------------------
I reproduced the import described in Barry's previous comment;
- the preview of data gives the same error message in log as described in TEIID-2730.
@Van Halbert: My original setup was Sybase ASE 15.x, jconn4-25602 and I couldn't complete the import wizard from the bqt2 database (but from a different database, with different structure, I could). The model can be imported with jconn4-25602 and Sybase ASA 10.x.
was (Author: lfabriko):
I reproduced the import described in Barry's previous comment;
- the preview of data gives the same error message in log as described in TEIID-2730.
@Van Halbert: My original setup was Sybase ASE 15.x, jconn4-25602 and I couldn't complete the import wizard from the bqt2 database (but from a different database, with different structure, I could).
> Cannot create relational source with Sybase jconn4.jar
> ------------------------------------------------------
>
> Key: TEIIDDES-1920
> URL: https://issues.jboss.org/browse/TEIIDDES-1920
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.3
> Environment: java oracle 1.7, Teiid 8.4.1-redhat4 in DV 6.0.0.ER3, Teiid Designer 8.3.beta3
> Reporter: Lucie Fabrikova
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 8.3
>
> Attachments: jconn4-26502.jar, jconn4-26666.jar
>
>
> Creating a relational source model from jdbc connection profile to Sybase database (1st page of wizard, connecting to database of given profile) which uses jconn4.jar results in error message :
> java.sql.SQLException: JZ0SJ: Metadata accessor information was not found on this database. Please install the required tables as mentioned in the jConnect documentation.
> at com.sybase.jdbc4.jdbc.SybConnection.getAllExceptions(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.handleSQLE(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.checkMDA(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.getMDA(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybLob.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybCharClientLob.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.resetNullLobs(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.init(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.tryLogin(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.handleHAFailover(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybDriver.connect(Unknown Source)
> at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.createConnection(JDBCConnection.java:298)
> at org.eclipse.datatools.connectivity.DriverConnectionBase.internalCreateConnection(DriverConnectionBase.java:105)
> at org.eclipse.datatools.connectivity.DriverConnectionBase.open(DriverConnectionBase.java:54)
> at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.open(JDBCConnection.java:81)
> at org.eclipse.datatools.enablement.sybase.ase.internal.connection.JDBCASEConnectionFactory.createConnection(JDBCASEConnectionFactory.java:32)
> at org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(ConnectionFactoryProvider.java:83)
> at org.eclipse.datatools.connectivity.internal.ConnectionProfile.createConnection(ConnectionProfile.java:359)
> at org.eclipse.datatools.connectivity.ui.PingJob.createTestConnection(PingJob.java:76)
> at org.eclipse.datatools.connectivity.ui.PingJob.run(PingJob.java:59)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Errors log:
> Modeler Core Exception: Status ERROR: org.teiid.core.designer code=0 JZ0SJ: Metadata accessor information was not found on this database. Please install the required tables as mentioned in the jConnect documentation. null
> at org.teiid.designer.jdbc.JdbcManagerImpl.createConnection(JdbcManagerImpl.java:202)
> at org.teiid.designer.jdbc.JdbcManagerImpl.createConnection(JdbcManagerImpl.java:211)
> at org.teiid.designer.jdbc.ui.util.JdbcUiUtil$1.run(JdbcUiUtil.java:80)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
--
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
12 years, 5 months
[JBoss JIRA] (TEIIDDES-1920) Cannot create relational source with Sybase jconn4.jar
by Lucie Fabrikova (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1920?page=com.atlassian.jira.plu... ]
Lucie Fabrikova edited comment on TEIIDDES-1920 at 11/20/13 3:59 AM:
---------------------------------------------------------------------
I reproduced the import described in Barry's previous comment;
- the preview of data gives the same error message in log as described in TEIID-2730.
@Van Halbert: My original setup was Sybase ASE 15.x, jconn4-25602 and I couldn't complete the import wizard from the bqt2 database (but from a different database, with different structure, I could).
was (Author: lfabriko):
I reproduced the import described in Barry's previous comment;
- the preview of data gives the same error message in log as described in TEIID-2730.
@Van Halbert: My original setup was Sybase ASE 15.x, jconn4-25602 and I couldn't complete the import wizard from the bqt2 database (but from a different one, with different structure, I could).
> Cannot create relational source with Sybase jconn4.jar
> ------------------------------------------------------
>
> Key: TEIIDDES-1920
> URL: https://issues.jboss.org/browse/TEIIDDES-1920
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.3
> Environment: java oracle 1.7, Teiid 8.4.1-redhat4 in DV 6.0.0.ER3, Teiid Designer 8.3.beta3
> Reporter: Lucie Fabrikova
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 8.3
>
> Attachments: jconn4-26502.jar, jconn4-26666.jar
>
>
> Creating a relational source model from jdbc connection profile to Sybase database (1st page of wizard, connecting to database of given profile) which uses jconn4.jar results in error message :
> java.sql.SQLException: JZ0SJ: Metadata accessor information was not found on this database. Please install the required tables as mentioned in the jConnect documentation.
> at com.sybase.jdbc4.jdbc.SybConnection.getAllExceptions(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.handleSQLE(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.checkMDA(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.getMDA(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybLob.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybCharClientLob.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.resetNullLobs(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.init(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.tryLogin(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.handleHAFailover(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybDriver.connect(Unknown Source)
> at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.createConnection(JDBCConnection.java:298)
> at org.eclipse.datatools.connectivity.DriverConnectionBase.internalCreateConnection(DriverConnectionBase.java:105)
> at org.eclipse.datatools.connectivity.DriverConnectionBase.open(DriverConnectionBase.java:54)
> at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.open(JDBCConnection.java:81)
> at org.eclipse.datatools.enablement.sybase.ase.internal.connection.JDBCASEConnectionFactory.createConnection(JDBCASEConnectionFactory.java:32)
> at org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(ConnectionFactoryProvider.java:83)
> at org.eclipse.datatools.connectivity.internal.ConnectionProfile.createConnection(ConnectionProfile.java:359)
> at org.eclipse.datatools.connectivity.ui.PingJob.createTestConnection(PingJob.java:76)
> at org.eclipse.datatools.connectivity.ui.PingJob.run(PingJob.java:59)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Errors log:
> Modeler Core Exception: Status ERROR: org.teiid.core.designer code=0 JZ0SJ: Metadata accessor information was not found on this database. Please install the required tables as mentioned in the jConnect documentation. null
> at org.teiid.designer.jdbc.JdbcManagerImpl.createConnection(JdbcManagerImpl.java:202)
> at org.teiid.designer.jdbc.JdbcManagerImpl.createConnection(JdbcManagerImpl.java:211)
> at org.teiid.designer.jdbc.ui.util.JdbcUiUtil$1.run(JdbcUiUtil.java:80)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
--
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
12 years, 5 months
[JBoss JIRA] (TEIIDDES-1920) Cannot create relational source with Sybase jconn4.jar
by Lucie Fabrikova (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1920?page=com.atlassian.jira.plu... ]
Lucie Fabrikova commented on TEIIDDES-1920:
-------------------------------------------
I reproduced the import described in Barry's previous comment;
- the preview of data gives the same error message in log as described in TEIID-2730.
@Van Halbert: My original setup was Sybase ASE 15.x, jconn4-25602 and I couldn't complete the import wizard from the bqt2 database (but from a different one, with different structure, I could).
> Cannot create relational source with Sybase jconn4.jar
> ------------------------------------------------------
>
> Key: TEIIDDES-1920
> URL: https://issues.jboss.org/browse/TEIIDDES-1920
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.3
> Environment: java oracle 1.7, Teiid 8.4.1-redhat4 in DV 6.0.0.ER3, Teiid Designer 8.3.beta3
> Reporter: Lucie Fabrikova
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 8.3
>
> Attachments: jconn4-26502.jar, jconn4-26666.jar
>
>
> Creating a relational source model from jdbc connection profile to Sybase database (1st page of wizard, connecting to database of given profile) which uses jconn4.jar results in error message :
> java.sql.SQLException: JZ0SJ: Metadata accessor information was not found on this database. Please install the required tables as mentioned in the jConnect documentation.
> at com.sybase.jdbc4.jdbc.SybConnection.getAllExceptions(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.handleSQLE(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.checkMDA(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.getMDA(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybLob.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybCharClientLob.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.resetNullLobs(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.init(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.tryLogin(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.handleHAFailover(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybConnection.<init>(Unknown Source)
> at com.sybase.jdbc4.jdbc.SybDriver.connect(Unknown Source)
> at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.createConnection(JDBCConnection.java:298)
> at org.eclipse.datatools.connectivity.DriverConnectionBase.internalCreateConnection(DriverConnectionBase.java:105)
> at org.eclipse.datatools.connectivity.DriverConnectionBase.open(DriverConnectionBase.java:54)
> at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.open(JDBCConnection.java:81)
> at org.eclipse.datatools.enablement.sybase.ase.internal.connection.JDBCASEConnectionFactory.createConnection(JDBCASEConnectionFactory.java:32)
> at org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(ConnectionFactoryProvider.java:83)
> at org.eclipse.datatools.connectivity.internal.ConnectionProfile.createConnection(ConnectionProfile.java:359)
> at org.eclipse.datatools.connectivity.ui.PingJob.createTestConnection(PingJob.java:76)
> at org.eclipse.datatools.connectivity.ui.PingJob.run(PingJob.java:59)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Errors log:
> Modeler Core Exception: Status ERROR: org.teiid.core.designer code=0 JZ0SJ: Metadata accessor information was not found on this database. Please install the required tables as mentioned in the jConnect documentation. null
> at org.teiid.designer.jdbc.JdbcManagerImpl.createConnection(JdbcManagerImpl.java:202)
> at org.teiid.designer.jdbc.JdbcManagerImpl.createConnection(JdbcManagerImpl.java:211)
> at org.teiid.designer.jdbc.ui.util.JdbcUiUtil$1.run(JdbcUiUtil.java:80)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
--
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
12 years, 5 months
[JBoss JIRA] (TEIIDDES-1118) Add/Remove operations on a VDB should block other operations on the VDB
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1118?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-1118:
---------------------------------------------------
belong(a)redhat.com made a comment on [bug 781035|https://bugzilla.redhat.com/show_bug.cgi?id=781035]
Fixed before GA - setting to requires_doc_text- accordingly
> Add/Remove operations on a VDB should block other operations on the VDB
> -----------------------------------------------------------------------
>
> Key: TEIIDDES-1118
> URL: https://issues.jboss.org/browse/TEIIDDES-1118
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 7.4.2
> Reporter: Marc Shirley
> Assignee: Mark Drilling
> Fix For: 7.7.2, 8.0
>
>
> As adding/removing objects from a VDB results in filesystem operations of adding/removing indexes, this should result in a blocking of additional operations against the VDB. If latency with the filesystem is large enough (for example, on a network filesystem) and no blocking is performed, multiple operations can be performed on the VDB resulting in the below exception:
> !MESSAGE Unhandled event loop exception
> !STACK 0
> java.lang.ArrayIndexOutOfBoundsException: 0
> at org.teiid.designer.vdb.VdbModelEntry.synchronizeModelEntry(VdbModelEntry.java:435)
> at org.teiid.designer.vdb.Vdb.addModelEntry(Vdb.java:244)
> at com.metamatrix.modeler.internal.vdb.ui.editor.VdbEditor$25.selected(VdbEditor.java:1709)
> at com.metamatrix.ui.table.TableAndToolBar$2.run(TableAndToolBar.java:79)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:498)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
> at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:452)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
> at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:620)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:575)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1408)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1384)
--
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
12 years, 5 months
[JBoss JIRA] (TEIIDDES-1871) NPE While using DDL based importer
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1871?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-1871:
---------------------------------------------------
belong(a)redhat.com made a comment on [bug 1012634|https://bugzilla.redhat.com/show_bug.cgi?id=1012634]
Fixed before GA - setting to requires_doc_text- accordingly
> NPE While using DDL based importer
> ----------------------------------
>
> Key: TEIIDDES-1871
> URL: https://issues.jboss.org/browse/TEIIDDES-1871
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.2
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 8.3
>
> Attachments: sap-flight.ddl, working_sap_flight.ddl
>
>
> While importing the OData translator based DDL, encountered the below NPE.
> {code}
> Caused by: java.lang.NullPointerException
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.getColumnNode(CreateTableParser.java:117)
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.parseReferenceList(CreateTableParser.java:330)
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.parseTableBodyConstraint(CreateTableParser.java:453)
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.parseTableBody(CreateTableParser.java:362)
> at org.modeshape.sequencer.ddl.dialect.teiid.CreateTableParser.parse(CreateTableParser.java:195)
> at org.modeshape.sequencer.ddl.dialect.teiid.TeiidDdlParser.parseNextStatement(TeiidDdlParser.java:150)
> at org.modeshape.sequencer.ddl.StandardDdlParser.parse(StandardDdlParser.java:209)
> at org.modeshape.sequencer.ddl.DdlParsers.parseUsing(DdlParsers.java:152)
> at org.teiid.designer.ddl.importer.DdlImporter.importDdl(DdlImporter.java:134)
> at org.teiid.designer.ddl.importer.DdlImporter$1.tryToDo(DdlImporter.java:106)
> at org.teiid.core.designer.util.OperationUtil.perform(OperationUtil.java:40)
> at org.teiid.designer.ddl.importer.DdlImporter.importDdl(DdlImporter.java:90)
> at org.teiid.designer.ddl.importer.ui.DdlImportDifferencesPage$1.run(DdlImportDifferencesPage.java:222)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
> {code}
--
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
12 years, 5 months
[JBoss JIRA] (TEIIDDES-1870) OData Importing issues
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1870?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-1870:
---------------------------------------------------
belong(a)redhat.com made a comment on [bug 1012634|https://bugzilla.redhat.com/show_bug.cgi?id=1012634]
Fixed before GA - setting to requires_doc_text- accordingly
> OData Importing issues
> ----------------------
>
> Key: TEIIDDES-1870
> URL: https://issues.jboss.org/browse/TEIIDDES-1870
> Project: Teiid Designer
> Issue Type: Bug
> Components: Extension Framework, Import/Export
> Affects Versions: 8.2
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Fix For: 8.3
>
>
> After fixing the TEIID-2673, I have failed to import the OData metadata correctly. Upon some investigation here are some issues that needs to be fixed on the Designer
> 1) MED specified for OData properties are incomplete. Please add following properties
> Namespace URI:http://www.jboss.org/teiiddesigner/ext/odata/2012
> Namespace: teiid_odata
> # LinkTables - String/optional
> # HttpMethod - String/optional
> # JoinColumn - String/optional
> # EntityType - String/optional
> # ComplexType - String/optional
> # ColumnGroup - String/optional
> 2) When the "name space" based properties are returned in the DDL from Teiid, none of the properties are correctly being resolved. Bigger issue is they are being ignored, Designer should fail here with error message saying that "extension property match not found" and force users to define or select a MED that matches with all the properties
> 3) Mark the OData not built-in, so that it allows the user to edit the allowed properties list until we have the feature fully worked as expected.
--
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
12 years, 5 months