February 2011 - teiid-issues - Jboss List Archives

[JBoss JIRA] Moved: (TEIID-1469) CLONE - EDS Teiid Plugin uses Invalid Datatype Mask for SessionID Parameter to Terminate Session Operation

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIID-1469?page=com.atlassian.jira.plugin... ] Ted Jones moved SOA-2905 to TEIID-1469: --------------------------------------- Project: Teiid (was: JBoss Enterprise SOA Platform) Key: TEIID-1469 (was: SOA-2905) Affects Version/s: 7.3 (was: 5.1.0.ER9) Component/s: Jopr Plugin (was: EDS) Security: (was: Public) > CLONE - EDS Teiid Plugin uses Invalid Datatype Mask for SessionID Parameter to Terminate Session Operation > ---------------------------------------------------------------------------------------------------------- > > Key: TEIID-1469 > URL: https://issues.jboss.org/browse/TEIID-1469 > Project: Teiid > Issue Type: Bug > Components: Jopr Plugin > Affects Versions: 7.3 > Reporter: Ted Jones > > The Terminate Session operation validates the session id parameter as an integer when it is actually alpha-numeric, making it impossible to execute the operation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-1469) EDS Teiid Plugin uses Invalid Datatype Mask for SessionID Parameter to Terminate Session Operation

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIID-1469?page=com.atlassian.jira.plugin... ] Ted Jones updated TEIID-1469: ----------------------------- Summary: EDS Teiid Plugin uses Invalid Datatype Mask for SessionID Parameter to Terminate Session Operation (was: CLONE - EDS Teiid Plugin uses Invalid Datatype Mask for SessionID Parameter to Terminate Session Operation) Assignee: Ted Jones Workaround Description: Sessions can be terminated using the Adminshell or AdminAPI (was: Sessions can be terminated using the Admin Shell or AdminAPI) > EDS Teiid Plugin uses Invalid Datatype Mask for SessionID Parameter to Terminate Session Operation > -------------------------------------------------------------------------------------------------- > > Key: TEIID-1469 > URL: https://issues.jboss.org/browse/TEIID-1469 > Project: Teiid > Issue Type: Bug > Components: Jopr Plugin > Affects Versions: 7.3 > Reporter: Ted Jones > Assignee: Ted Jones > > The Terminate Session operation validates the session id parameter as an integer when it is actually alpha-numeric, making it impossible to execute the operation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIID-1468) Cannot Print Metadata Model Diagram under Linix

by Denis Golovin (JIRA)

Cannot Print Metadata Model Diagram under Linix ----------------------------------------------- Key: TEIID-1468 URL: https://issues.jboss.org/browse/TEIID-1468 Project: Teiid Issue Type: Bug Components: Tools Affects Versions: 7.1 Environment: Arch: Linux,GTK,x86 Distr: Ubuntu 10.10 Reporter: Denis Golovin Assignee: Steven Hawkins After creating diagram Select File->Print from bar menu. Then select printer and press Print button. It shows error dialog and reports exception in Error Log View: {noformat}org.eclipse.swt.SWTError: No more handles at org.eclipse.swt.SWT.error(SWT.java:4109) at org.eclipse.swt.SWT.error(SWT.java:3998) at org.eclipse.swt.SWT.error(SWT.java:3969) at org.eclipse.swt.printing.Printer.internal_new_GC(Printer.java:393) at org.eclipse.swt.graphics.GC.<init>(GC.java:159) at org.eclipse.swt.graphics.GC.<init>(GC.java:125) at com.metamatrix.modeler.diagram.ui.printing.DiagramPrintingAnalyzer.getPrinterGC(DiagramPrintingAnalyzer.java:228) at com.metamatrix.modeler.diagram.ui.printing.DiagramPrintingAnalyzer.getFreshPrinterGraphics(DiagramPrintingAnalyzer.java:220) at com.metamatrix.modeler.diagram.ui.printing.DiagramPrintingOperation.printLandscape_PrinterIsPortrait(DiagramPrintingOperation.java:690) at com.metamatrix.modeler.diagram.ui.printing.DiagramPrintingOperation.printPages(DiagramPrintingOperation.java:403) at com.metamatrix.modeler.diagram.ui.printing.DiagramPrintingAnalyzer.countPages(DiagramPrintingAnalyzer.java:170) at com.metamatrix.modeler.diagram.ui.printing.DiagramPrintingAnalyzer.setPageSize(DiagramPrintingAnalyzer.java:68) at com.metamatrix.modeler.diagram.ui.printing.DiagramPrintingAnalyzer.<init>(DiagramPrintingAnalyzer.java:44) at com.metamatrix.modeler.diagram.ui.actions.PrintWrapper.doRun(PrintWrapper.java:100) at com.metamatrix.ui.actions.AbstractAction$1.run(AbstractAction.java:537) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at com.metamatrix.ui.actions.AbstractAction.run(AbstractAction.java:540) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.commands.ActionHandler.execute(ActionHandler.java:119) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:241) at org.eclipse.ui.menus.CommandContributionItem.handleWidgetSelection(CommandContributionItem.java:820) at org.eclipse.ui.menus.CommandContributionItem.access$19(CommandContributionItem.java:806) at org.eclipse.ui.menus.CommandContributionItem$5.handleEvent(CommandContributionItem.java:796) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3161) 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:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407){noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
1
0 / 0

[JBoss JIRA] Moved: (TEIID-1467) Procedures in Teiid are not Resolvable if Their Models are Marked as Not Visible

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-1467?page=com.atlassian.jira.plugin... ] Van Halbert moved SOA-2897 to TEIID-1467: ----------------------------------------- Project: Teiid (was: JBoss Enterprise SOA Platform) Key: TEIID-1467 (was: SOA-2897) Affects Version/s: 7.1.1 (was: 5.1.0.ER9) Component/s: Query Engine (was: EDS) Security: (was: Public) > Procedures in Teiid are not Resolvable if Their Models are Marked as Not Visible > -------------------------------------------------------------------------------- > > Key: TEIID-1467 > URL: https://issues.jboss.org/browse/TEIID-1467 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.1.1 > Reporter: Ted Jones > > If a model containing procedures is marked as not visible, the queryplanner cannot resolve them. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (TEIID-247) Add support for array types

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-247?page=com.atlassian.jira.plugin.... ] Steven Hawkins commented on TEIID-247: -------------------------------------- Added array_get and array_length functions as well as the arraytable table function in 7.4. There is still no Teiid array type and specific pushdown support for the array functions was not yet added - although would be easy to the sources that support them. > Add support for array types > --------------------------- > > Key: TEIID-247 > URL: https://issues.jboss.org/browse/TEIID-247 > Project: Teiid > Issue Type: Feature Request > Components: Connector API, JDBC Driver, Query Engine > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 9.x > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Add language support for array types. Push down and client support should also be added. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-1437) It's not possible to deploy single file (*.xml) virtual database through web admin console

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIID-1437?page=com.atlassian.jira.plugin... ] Ted Jones updated TEIID-1437: ----------------------------- Fix Version/s: 7.4 > It's not possible to deploy single file (*.xml) virtual database through web admin console > ------------------------------------------------------------------------------------------ > > Key: TEIID-1437 > URL: https://issues.jboss.org/browse/TEIID-1437 > Project: Teiid > Issue Type: Feature Request > Components: Jopr Plugin > Affects Versions: 7.2 > Reporter: Robert Balent > Assignee: Ted Jones > Fix For: 7.4 > > > There are two ways how create virtual database. You can deploy *.vdb file which is basically zip archive with changed extension, or deploy just vdb.xml file. The second way doesn't work through soa admin console web interface. > Error message: > Failed to create Resource weather-vdb.xml - cause: Incorrect extension specified on filename > How to reproduce: > In soa web interface log in to Admin Console, than open "Virtual Database (VDB)s" link, than click "Add a new resource" button, and try to upload weather-vdb.xml which is attached. > Workaround: > Just copy weather-vdb.xml to the deploy folder. > weather-vdb.xml and weather-ds.xml which is required if you want to deploy vdb in active state are attached. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (TEIID-1430) FileNotFoundError Deploying VDB in JON

by Paul Nittel (JIRA)

[ https://issues.jboss.org/browse/TEIID-1430?page=com.atlassian.jira.plugin... ] Paul Nittel closed TEIID-1430. ------------------------------ Tested with ER9 and closed. > FileNotFoundError Deploying VDB in JON > -------------------------------------- > > Key: TEIID-1430 > URL: https://issues.jboss.org/browse/TEIID-1430 > Project: Teiid > Issue Type: Bug > Reporter: Ted Jones > Assignee: Ted Jones > > VDB deployment via Create causes a FileNotFound exception -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-98) Prepared/CallableStatement parameter indexes are not correct.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-98?page=com.atlassian.jira.plugin.s... ] Steven Hawkins resolved TEIID-98. --------------------------------- Fix Version/s: (was: 9.x) Resolution: Partially Completed retrieval indexes have been corrected based upon prior changes. Only the setXXX indexes are not strictly enforced. We could add client side validation that takes into account out parameter information to ensure consecutive indexes starting at 1. That may break older client code that for whatever reason is not registering out parameters. It seems best to just mark as resolved and reopen if it becomes an issue for a user. > Prepared/CallableStatement parameter indexes are not correct. > ------------------------------------------------------------- > > Key: TEIID-98 > URL: https://issues.jboss.org/browse/TEIID-98 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 9.x > Reporter: Steven Hawkins > Priority: Minor > Original Estimate: 2 days > Remaining Estimate: 2 days > > All parameter indexes are treated as relative rather than absolute. We should not accept values less than 1 and should ensure that the values specified are continuous. > Also, return parameters should be considered index 1 regardless of where they are in the procedure metadata. For example in defer_testDefect24952 in TestMMStoredProcedure ?=call sp.sp_count_rows_between(?, ?) should have a return value at index 1 from the driver perspective, but instead it has index 3. > see also defect 24952 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (TEIID-86) registering of CallableStatement out parameters should be used

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-86?page=com.atlassian.jira.plugin.s... ] Steven Hawkins resolved TEIID-86. --------------------------------- Fix Version/s: (was: 9.x) Resolution: Partially Completed Changes to stored procedure handling largely account for this issue. If a user has a query with both return and out parameters we will appropriately omit the return parameter if it is not asked for. There are two remaining reasons we should consider using out parameter information: 1. to have better parameter indexing logic TEIID-98 2. to enforce what getters can be used. Neither of these is particularly high priority. > registering of CallableStatement out parameters should be used > -------------------------------------------------------------- > > Key: TEIID-86 > URL: https://issues.jboss.org/browse/TEIID-86 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 9.x > Reporter: Steven Hawkins > Priority: Minor > Original Estimate: 3 days > Remaining Estimate: 3 days > > The registering of CallableStatement out (out, inout, return) parameters should be used to > 1. help resolve the procedure - if there is a type mismatch or a parameter requested that doesn't exist an exception should be thrown. > 2. determine what out parameters the driver should know about. currently the driver is supplied with all out values regardless of how many are registered. this means that the user may not get the right value if the statement does not fully specifier all out parameters. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (TEIID-65) Precision of BigInteger and BigDecimal need to be limited

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-65?page=com.atlassian.jira.plugin.s... ] Steven Hawkins updated TEIID-65: -------------------------------- Fix Version/s: 9.0 (was: 8.0) Pushing to Teiid 9 > Precision of BigInteger and BigDecimal need to be limited > --------------------------------------------------------- > > Key: TEIID-65 > URL: https://issues.jboss.org/browse/TEIID-65 > Project: Teiid > Issue Type: Sub-task > Components: Common > Affects Versions: 9.x > Reporter: Steven Hawkins > Fix For: 9.0 > > > To ensure database and string conversion compatibility BigInteger and BigDecimal should be limited to 1000 digits of precision (taken from PostGres). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2011