July 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4331) Use of st_geomfromText wrapped around a UDF fails.

by Tom Johnston (JIRA)

Tom Johnston created TEIID-4331: ----------------------------------- Summary: Use of st_geomfromText wrapped around a UDF fails. Key: TEIID-4331 URL: https://issues.jboss.org/browse/TEIID-4331 Project: Teiid Issue Type: Bug Reporter: Tom Johnston Assignee: Steven Hawkins Attachments: gis-1.0.0.jar -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4090) Issue with entitysets/properties ending in auth or token

by Lucie Fabrikova (JIRA)

[ https://issues.jboss.org/browse/TEIID-4090?page=com.atlassian.jira.plugin... ] Lucie Fabrikova commented on TEIID-4090: ---------------------------------------- Which URIs should be tested? 1. http://localhost:8080/odata4/myvdb/mymodel/auth 2. http://localhost:8080/odata4/myvdb/mymodel/token 3. http://localhost:8080/odata4/static/mymodel/token 4. http://localhost:8080/odata4/static.1/mymodel/token 5. http://localhost:8080/odata4/static/mymodel/auth 6. http://localhost:8080/odata4/static.1/mymodel/auth 7. 3.-6. with keycloak instead of static Where - in 1., 2. suppose myvdb is name of vdb, auth/token is name of table - in 3.-7. static/keycloak is name of vdb, auth/token is name of table thanks for info. > Issue with entitysets/properties ending in auth or token > -------------------------------------------------------- > > Key: TEIID-4090 > URL: https://issues.jboss.org/browse/TEIID-4090 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.12 > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Priority: Blocker > Labels: Final > Fix For: 9.0, 8.12.5 > > > To handle oauth, we are check for uri.endsWith("auth") || uri.endsWith("token") - however valid uris can end with those characters as well. An ioexception will be thrown instead of seeing the expected results - we also need to not simply throw an ioexception in ODataServlet as there is no server log of the exception and the client sees a 500 error. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3686) OData DELETE nonexisting row - wrong response code

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3686?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3686: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1266539|https://bugzilla.redhat.com/show_bug.cgi?id=1266539] from ASSIGNED to MODIFIED > OData DELETE nonexisting row - wrong response code > -------------------------------------------------- > > Key: TEIID-3686 > URL: https://issues.jboss.org/browse/TEIID-3686 > Project: Teiid > Issue Type: Bug > Components: OData > Affects Versions: 8.7.1.6_2 > Reporter: Michal Sanitrak > Assignee: Ramesh Reddy > Labels: CR1 > Fix For: 8.12, 8.7.2.6_2 > > > I deployed VDB that can be accessed with OData. When I perform DELETE request to remove row for first time response code is 200 OK (maybe it should be 204) but when I repeat the same DELETE request and tried to delete already deleted entry, response is again 200 OK, but it should be 404 Not Found. Same thing happens even I when tried to delete entry with id that doesn't exist at all. > Only indication of this problem is in the server log: > {code:plain}INFO [org.teiid.ODATA] (http-/127.0.0.1:8080-1) no entity to delete in = BooksMySQL.BOOKS with key= ('1') > {code} > I think that response code for deleting row that doesn't exist should be different than 200 OK. > For example the service at odata.org returns following content with response code 404 Not Found: > {code:xml} > <?xml version="1.0" encoding="utf-8" standalone="yes"?> > <error xmlns="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"> > <code></code> > <message xml:lang="en-US">Resource not found for the segment 'Products'.</message> > </error> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3629) Teiid DDL columns options for Salesforce column have wrong name for "Calculated" property

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3629?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3629: ------------------------------------------------ Andrej Smigala <asmigala(a)redhat.com> changed the Status of [bug 1253602|https://bugzilla.redhat.com/show_bug.cgi?id=1253602] from ON_QA to VERIFIED > Teiid DDL columns options for Salesforce column have wrong name for "Calculated" property > ----------------------------------------------------------------------------------------- > > Key: TEIID-3629 > URL: https://issues.jboss.org/browse/TEIID-3629 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Affects Versions: 8.8 > Reporter: Andrej Šmigala > Priority: Minor > Fix For: 8.12, 8.7.2.6_2 > > Attachments: sfDDL.ddl > > > Back in 2014, Teiid & Teiid Designer synched our Salesforce constants/extension properties to facilitate DDL import. However, it appears that the teiid_sf:calculated constant wasn't converted properly to *teiid_sf:Calculated*. https://github.com/teiid/teiid/commit/88781c220e1afc79c889cfc5d7c1c3e5d8e... > I'm able to import the attached DDL if I change *teiid_sf:calculated* to *teiid_sf:Calculated*. > The following is logged in the error log multiple times when importing Salesforce from Teiid Connection. The imported model appears to work ok (tried previewing a couple tables). > {quote} > java.lang.Exception: The property definition "salesforce:calculated" could not be found. > at org.teiid.designer.core.extension.EmfModelObjectExtensionAssistant.setPropertyValue(EmfModelObjectExtensionAssistant.java:485) > at org.teiid.designer.ddl.importer.node.EmfModelGenerator.setPropertyValue(EmfModelGenerator.java:1203) > at org.teiid.designer.ddl.importer.node.EmfModelGenerator.processExtensionProperties(EmfModelGenerator.java:1110) > at org.teiid.designer.ddl.importer.node.EmfModelGenerator.execute(EmfModelGenerator.java:219) > at org.teiid.designer.ddl.importer.DdlImporter.save(DdlImporter.java:324) > at org.teiid.designer.teiidimporter.ui.wizard.TeiidImportManager$2.run(TeiidImportManager.java:802) > 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.teiidimporter.ui.wizard.TeiidImportManager.saveUsingDdlDiffReport(TeiidImportManager.java:795) > at org.teiid.designer.teiidimporter.ui.wizard.TeiidImportWizard.finish(TeiidImportWizard.java:197) > at org.teiid.designer.ui.common.wizard.AbstractWizard.performFinish(AbstractWizard.java:356) > at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:853) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:438) > 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:4454) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1397) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1182) > at org.jboss.reddeer.swt.handler.WidgetHandler$4.run(WidgetHandler.java:333) > at org.jboss.reddeer.swt.util.Display$VoidResultRunnable.run(Display.java:184) > at org.jboss.reddeer.swt.util.Display$VoidResultRunnable.run(Display.java:1) > at org.jboss.reddeer.swt.util.Display$ErrorHandlingRunnable.run(Display.java:150) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3774) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3412) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:832) > at org.eclipse.jface.window.Window.open(Window.java:808) > at org.eclipse.ui.internal.handlers.WizardHandler$Import.executeHandler(WizardHandler.java:158) > at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:294) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > 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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:149) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343) > at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:159) > 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:4454) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1397) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1182) > at org.jboss.reddeer.swt.handler.MenuHandler$5.run(MenuHandler.java:116) > at org.jboss.reddeer.swt.util.Display$VoidResultRunnable.run(Display.java:184) > at org.jboss.reddeer.swt.util.Display$VoidResultRunnable.run(Display.java:1) > at org.jboss.reddeer.swt.util.Display$ErrorHandlingRunnable.run(Display.java:150) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3774) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3412) > 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.jboss.reddeer.eclipse.core.UITestApplication.start(UITestApplication.java:47) > 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.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4330) Better planning with chained makedep scenarios

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4330: ------------------------------------- Summary: Better planning with chained makedep scenarios Key: TEIID-4330 URL: https://issues.jboss.org/browse/TEIID-4330 Project: Teiid Issue Type: Bug Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.1 Plans with an implied series of make dep may not have the hint honored as intended. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4326) Swagger translator bugs and enhancement request

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4326?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-4326. --------------------------------- Fix Version/s: 9.1 Resolution: Done merged the pull request > Swagger translator bugs and enhancement request > ----------------------------------------------- > > Key: TEIID-4326 > URL: https://issues.jboss.org/browse/TEIID-4326 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 9.0, 9.0.1 > Environment: Windows 7 x64 > Java 8 > Reporter: Van Dillon > Assignee: Ramesh Reddy > Fix For: 9.1 > > > This JIRA is in response to instructions from Ramesh Reddy in the teiid-dev mailing list (http://lists.jboss.org/pipermail/teiid-dev/2016-July/000997.html) > Bugs > 1) JsonSerializer.deserialize with an unnamed array > If a Rest endpoint is called that returns an unnamed array such as: > [ > { > "scheduleId": 10007, > "timeStamp": 1468000572174, > "value": 2813018112 > }, > { > "scheduleId": 10007, > "timeStamp": 1468000602173, > "value": 2817523712 > } > ] > the JsonSerializer.deserialize method throws an EmptyStackException in the > END_ARRAY case because the 'fieldName' stack is empty. A check for empty > in the if clause fixes the problem: > if (arrayLevel > objectLevel && !fieldName.empty())... > 2) DDL generation > When the schema DDL is generated from the Swagger, all procedure parameters > have their NullType set to NullType.No_Nulls. Can this be set depending on > the Swagger parameter 'required' field? For instance: > boolean required = parameter.getRequired(); > pp.setNullType(required ? NullType.No_Nulls : NullType.Nullable); > Enhancement idea: > REST apis that are not Swagger based could be used with the Swagger > translator if a user could provide a swagger.json file they've created in > the Swagger Editor. I've added some changes to SwaggerMetadataProcessor > that allow a user to specify an importer property, swaggerFilePath, that's > used in the getSchema method to load the Swagger metadata from file. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4320) Costing calculation issues

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4320?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4320: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1354554 Bugzilla Update: Perform > Costing calculation issues > -------------------------- > > Key: TEIID-4320 > URL: https://issues.jboss.org/browse/TEIID-4320 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 9.1, 8.13.6, 9.0.1 > > > When determining if a dependent join should be used we'll rule out too many scenarios based upon requiring additional ndv info - when that can be determined from cardinality alone. Also we are inappropriately assuming key usage in predicate costing - as it does not consider the node which may not represent a single table. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4322) Add embedded quickstart using sockets

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4322?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4322: ---------------------------------- Fix Version/s: 9.1 (was: 9.2) > Add embedded quickstart using sockets > ------------------------------------- > > Key: TEIID-4322 > URL: https://issues.jboss.org/browse/TEIID-4322 > Project: Teiid > Issue Type: Task > Components: Embedded, Quick Starts > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Optional > Fix For: 9.1 > > > Add an embedded quick start that is using the socket feature. > Have the following parameter options: > - set the host and port > - which protocol to use > I would suggest duplicating the embedded-portfolio example. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4295) TEIID31150 when using date function with MSSQL

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4295?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4295: --------------------------------------- What type do you have DateField set to in Teiid - if imported by the Teiid importer is should be of type date. > TEIID31150 when using date function with MSSQL > ---------------------------------------------- > > Key: TEIID-4295 > URL: https://issues.jboss.org/browse/TEIID-4295 > Project: Teiid > Issue Type: Feature Request > Reporter: Mark Tawk > Assignee: Steven Hawkins > > I'm using teiid version 8.11.3 > I have a field of type date over mssql 2012, when applying a date function over it, i get directly the error : > org.teiid.jdbc.TeiidSQLException: TEIID31150 The function 'YEAR(testmark.mydate)' is ambiguous. Use schema qualification. > if I change the field type to datetime, the query executes successfully. > Here is the simplified query i'm testing with: > select YEAR("testmark"."mydate") as "testmark_mydate" from "implify_dataModel_at"."implify_data"."implify_red2"."testmark" "testmark" LIMIT 0 , 10 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4295) TEIID31150 when using date function with MSSQL

by Mark Tawk (JIRA)

[ https://issues.jboss.org/browse/TEIID-4295?page=com.atlassian.jira.plugin... ] Mark Tawk commented on TEIID-4295: ---------------------------------- I tried the case with teiid 9.0.0, now i'm getting a different exception: Error TEIID30070 The function 'month(DateTest.DateField)' is a valid function form, but the arguments do not match a known type signature and cannot be converted using implicit type conversions. here is the query i'm running on mssql: select month("DateTest"."DateField") as "DateTest_DateField" from "implify_dataModel_hX"."implify_data"."implify_red2"."DateTest" "DateTest" LIMIT 0 , 10 > TEIID31150 when using date function with MSSQL > ---------------------------------------------- > > Key: TEIID-4295 > URL: https://issues.jboss.org/browse/TEIID-4295 > Project: Teiid > Issue Type: Feature Request > Reporter: Mark Tawk > Assignee: Steven Hawkins > > I'm using teiid version 8.11.3 > I have a field of type date over mssql 2012, when applying a date function over it, i get directly the error : > org.teiid.jdbc.TeiidSQLException: TEIID31150 The function 'YEAR(testmark.mydate)' is ambiguous. Use schema qualification. > if I change the field type to datetime, the query executes successfully. > Here is the simplified query i'm testing with: > select YEAR("testmark"."mydate") as "testmark_mydate" from "implify_dataModel_at"."implify_data"."implify_red2"."testmark" "testmark" LIMIT 0 , 10 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues July 2016