[JBoss JIRA] (TEIIDDES-2213) JDBC Importer with PostgreSQL function that returns table imports parameters incorrectly
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2213?page=com.atlassian.jira.plu... ]
Mark Drilling resolved TEIIDDES-2213.
-------------------------------------
Release Notes Docs Status: Documented as Known Issue
Release Notes Text:
Known Issue:
- For PostgreSQL drivers prior to 9.3, a bug exists for import of the described procedures. For pre-9.3 drivers, the resultset params are erroneously all returned as IN parameters. The workaround is to manually edit the imported procedure for pre-9.3 driver import
Resolution: Done
- Adds code fix to account for PostgreSQL 9.3 driver bug. For certain procedure types described above, the 9.3 driver will return multiple return parameters. The code change in the importer will detect if multiple return params exist and if so will put them in a resultSet.
https://github.com/Teiid-Designer/teiid-designer/pull/421
Known Issue:
- For PostgreSQL drivers prior to 9.3, a bug also exists for same type of procedures. For pre-9.3 drivers, the params are erroneously all returned as IN parameters. We should have a known issue for that.
> JDBC Importer with PostgreSQL function that returns table imports parameters incorrectly
> ----------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2213
> URL: https://issues.jboss.org/browse/TEIIDDES-2213
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.3.2
> Reporter: Debbie Steigner
> Assignee: Mark Drilling
> Fix For: 8.6.1, 9.0.1, 9.0
>
>
> Using the JDBC Importer on a PostgreSQL Function that RETURNS TABLE the columns that are returned when running the function are imported as input parameters not as resultset.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (TEIIDDES-2385) Error when generating SOAP WAR with WS-Security
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2385?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2385.
------------------------------------
Resolution: Done
Resolved issue by replaceing the wws4j 1.0.0 version with 1.6.17 which provided the classes with the correct methods in them.
Fixed in 8.6.x, 9.0.x and master
> Error when generating SOAP WAR with WS-Security
> ------------------------------------------------
>
> Key: TEIIDDES-2385
> URL: https://issues.jboss.org/browse/TEIIDDES-2385
> Project: Teiid Designer
> Issue Type: Bug
> Components: Web Services Support
> Affects Versions: 9.0.1
> Environment: JBDS 8.0.0 GA
> Teiid Designer 9.0.1.Beta1-v20141021-1225-B183
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Fix For: 8.6.1, 9.0.1, 9.0
>
> Attachments: i18n.properties, SourceModel_invokeHttp.java, TeiidWSProvider.java, UsernamePasswordCallback.java
>
>
> When creating a SOAP WAR in designer with the WS-Security option selected, the following error is shown:
> bq. An error occurred while creating WAR file, check log for detail
> The error message in log is
> {quote}
> !ENTRY org.teiid.designer.webservice 4 5 2014-11-07 12:19:28.256
> !MESSAGE An error occurred while creating WAR file, check log for detail
> !STACK 0
> java.lang.Exception: cannot find symbol
> symbol: method getIdentifier()
> location: variable pc of type org.apache.ws.security.WSPasswordCallback
> at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.createProviderJavaClasses(DefaultWebArchiveBuilderImpl.java:612)
> at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.createWebArchive(DefaultWebArchiveBuilderImpl.java:259)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.execute(WarDeploymentInfoDialog.java:195)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog$1.run(WarDeploymentInfoDialog.java:150)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:466)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:374)
> at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:527)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.okPressed(WarDeploymentInfoDialog.java:159)
> at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:466)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4353)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:832)
> at org.eclipse.jface.window.Window.open(Window.java:808)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.open(WarDeploymentInfoDialog.java:171)
> at org.teiid.designer.runtime.ui.actions.GenerateWarAction.run(GenerateWarAction.java:115)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:519)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4353)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (TEIIDDES-2383) Transformation editor removes cache hint in SQL
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2383?page=com.atlassian.jira.plu... ]
Van Halbert edited comment on TEIIDDES-2383 at 11/13/14 9:45 AM:
-----------------------------------------------------------------
Maybe designer could support comments that are prepended or appended with /** ... **/ (or use the -- sql standard) and strip that out before validation and reapply before representing validated syntax.
was (Author: van.halbert):
Maybe designer could support comments that are prepended or appended with /** ... **/ and strip that out before validation and reapply before representing validated syntax.
> Transformation editor removes cache hint in SQL
> -----------------------------------------------
>
> Key: TEIIDDES-2383
> URL: https://issues.jboss.org/browse/TEIIDDES-2383
> Project: Teiid Designer
> Issue Type: Bug
> Components: Transformations
> Affects Versions: 8.6, 9.0
> Reporter: Jan Stastny
>
> When adding a comment in transformation editor, the comment disappears after saving its content. It happens with any comment. This disables usage of cache hints.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (TEIIDDES-2213) JDBC Importer with PostgreSQL function that returns table imports parameters incorrectly
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2213?page=com.atlassian.jira.plu... ]
Mark Drilling edited comment on TEIIDDES-2213 at 11/12/14 6:52 PM:
-------------------------------------------------------------------
On debugging designer code, I could see the column types all coming in as 'IN Parmeters' for the extended_foo procedure. Investigating further, I came across this -
http://stackoverflow.com/questions/21541745/postgresql-9-jdbc-driver-retu...
Here is a summary of parameter types for postgres 8.3 and 9.3 drivers for the 2 procs
{noformat}
procedure extended_foo
coltype coltype
name (8.3 driver) (9.3 driver)
------------------ ------- -----
pfooid 1 1
fooid 1 5
foosubid 1 5
fooname 1 5
procedure foo
name (8.3 driver) (9.3 driver)
------------------ ------- -----
pfooid 1 1
fooid 3 3
foosubid 3 3
fooname 3 3
{noformat}
coltype 1 = in parameter
coltype 3 = procedure col result
coltype 5 = procedure col return
was (Author: mdrillin):
On debugging designer code, I could see the column types all coming in as 'IN Parmeters' for the extended_foo procedure. Investigating further, I came across this -
http://stackoverflow.com/questions/21541745/postgresql-9-jdbc-driver-retu...
Here is a summary of parameter types for postgres 8.3 and 9.3 drivers for the 2 procs
procedure extended_foo
coltype coltype
name (8.3 driver) (9.3 driver)
------------------ ------- -----
pfooid 1 1
fooid 1 5
foosubid 1 5
fooname 1 5
procedure foo
name (8.3 driver) (9.3 driver)
------------------ ------- -----
pfooid 1 1
fooid 3 3
foosubid 3 3
fooname 3 3
coltype 1 = in parameter
coltype 3 = procedure col result
coltype 5 = procedure col return
> JDBC Importer with PostgreSQL function that returns table imports parameters incorrectly
> ----------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2213
> URL: https://issues.jboss.org/browse/TEIIDDES-2213
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.3.2
> Reporter: Debbie Steigner
> Assignee: Mark Drilling
> Fix For: 8.6.1, 9.0.1, 9.0
>
>
> Using the JDBC Importer on a PostgreSQL Function that RETURNS TABLE the columns that are returned when running the function are imported as input parameters not as resultset.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (TEIIDDES-2213) JDBC Importer with PostgreSQL function that returns table imports parameters incorrectly
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2213?page=com.atlassian.jira.plu... ]
Mark Drilling edited comment on TEIIDDES-2213 at 11/12/14 6:50 PM:
-------------------------------------------------------------------
On debugging designer code, I could see the column types all coming in as 'IN Parmeters' for the extended_foo procedure. Investigating further, I came across this -
http://stackoverflow.com/questions/21541745/postgresql-9-jdbc-driver-retu...
Here is a summary of parameter types for postgres 8.3 and 9.3 drivers for the 2 procs
procedure extended_foo
coltype coltype
name (8.3 driver) (9.3 driver)
------------------ ------- -----
pfooid 1 1
fooid 1 5
foosubid 1 5
fooname 1 5
procedure foo
name (8.3 driver) (9.3 driver)
------------------ ------- -----
pfooid 1 1
fooid 3 3
foosubid 3 3
fooname 3 3
coltype 1 = in parameter
coltype 3 = procedure col result
coltype 5 = procedure col return
was (Author: mdrillin):
On debugging designer code, I could see the column types all coming in as 'IN Parmeters' for the extended_foo procedure. Investigating further, I came across this -
http://stackoverflow.com/questions/21541745/postgresql-9-jdbc-driver-retu...
It appears to be a bug with some postgres driver versions, but I have not yet verified this.
> JDBC Importer with PostgreSQL function that returns table imports parameters incorrectly
> ----------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2213
> URL: https://issues.jboss.org/browse/TEIIDDES-2213
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.3.2
> Reporter: Debbie Steigner
> Assignee: Mark Drilling
> Fix For: 8.6.1, 9.0.1, 9.0
>
>
> Using the JDBC Importer on a PostgreSQL Function that RETURNS TABLE the columns that are returned when running the function are imported as input parameters not as resultset.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (TEIIDDES-2329) WS translator Procedure definition defined in correctly
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2329?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2329:
-----------------------------------
Fix Version/s: 9.1
(was: 9.0)
> WS translator Procedure definition defined in correctly
> -------------------------------------------------------
>
> Key: TEIIDDES-2329
> URL: https://issues.jboss.org/browse/TEIIDDES-2329
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Reporter: Ramesh Reddy
> Assignee: Ted Jones
> Fix For: 9.1
>
>
> TEIID-3016 added new headers argument, when by default it is not used in the invokeHTTP procedure the following exception is seen. I also tried named parameters to avoid the issue but no change in situation.
> {code}
> java.lang.NullPointerException
> at org.teiid.translator.ws.BinaryWSProcedureExecution.execute(BinaryWSProcedureExecution.java:138)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:326) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:298) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:110) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:107) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_65]
> at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:58) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:274) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.9.0.Alpha3-SNAPSHOT.jar:8.9.0.Alpha3-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_65]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_65]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months
[JBoss JIRA] (TEIIDDES-2388) Add SAP HANA Driver Type
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2388?page=com.atlassian.jira.plu... ]
Ramesh Reddy commented on TEIIDDES-2388:
----------------------------------------
It does't. Every database vendor specifies their connection URL in their documents. Teiid provides samples of those in the documents. When you creating the DataSouce in EAP, the user needs to know the URL pattern.
DataTools in eclipse, goes little further and defines them in the configuration profiles for the drivers, thus you are seeing it for the SQL Server.
> Add SAP HANA Driver Type
> ------------------------
>
> Key: TEIIDDES-2388
> URL: https://issues.jboss.org/browse/TEIIDDES-2388
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling
> Affects Versions: 8.6.1
> Reporter: Ted Jones
> Fix For: 8.6.1, 9.0.1, 9.0
>
>
> Need to add the SAP HANA driver to our list of drivers. The URL should be "jdbc:sap://{host:port}"
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
11 years, 5 months