[JBoss JIRA] (TEIIDDES-2712) Support GET & POST methods together on REST procedures
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2712?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2712:
-----------------------------------
Fix Version/s: 10.0.2
(was: 9.2.2)
> Support GET & POST methods together on REST procedures
> ------------------------------------------------------
>
> Key: TEIIDDES-2712
> URL: https://issues.jboss.org/browse/TEIIDDES-2712
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Patch Release, Web Services Support
> Reporter: Matus Makovy
> Assignee: Ted Jones
> Fix For: 10.0.2
>
>
> Copied from BZ:
> Description of request:
> We can choose only one HTTP Request type for REST virtual procedures. Is it possible to combine GET & POST as one type ?
> Rationale:
> POST requests are more easy to create for client programmers.On the other hand GET method simplifies testing. Since it's easy to handle both request types on the server side, supporting both method at the same time may help to improve usability of services.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (TEIIDDES-1810) Support larger statistic values
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1810?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1810:
----------------------------------------
I think we're saying the same thing. EMF would store the calculated string value... annotation would store the *original* value.
Second part was the need to make sure the 21232533451.INDEX file contains the *original* value because the property is being set from the EMF version right now.
> Support larger statistic values
> -------------------------------
>
> Key: TEIIDDES-1810
> URL: https://issues.jboss.org/browse/TEIIDDES-1810
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Patch Release, Teiid Integration
> Reporter: Steven Hawkins
> Assignee: Dan Florian
> Fix For: 10.0.1, 9.2.1
>
>
> The table/column stats are currently limited to max int (2^31 -1) values.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (TEIIDDES-1810) Support larger statistic values
by Dan Florian (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1810?page=com.atlassian.jira.plu... ]
Dan Florian commented on TEIIDDES-1810:
---------------------------------------
No [~blafond]. The real value is the one that will be stored in the EObject property (so it will have the precision loss). The displayed value, coming from the EMF annotation property is strictly for the user to give them a warm and fuzzy feeling that the number they entered is _exactly_ the number we are using. Again, with numbers this large, the difference in the numbers is relatively extremely small and the user will not know the difference.
All values in the PropertiesView are shown as Strings [~mmakovy] regardless of their real type. The problem is that when we roundtrip the new value (obtaining the new long value, conversion from long to int, converting to String for PropertiesView) the value has changed. What I am proposing in #2 is that we save that original long value as an annotation. Then when displaying in the PropertiesView we would first look for that annotation, and if it exists, we would use that as the value instead of the actual value found in the object's property.
> Support larger statistic values
> -------------------------------
>
> Key: TEIIDDES-1810
> URL: https://issues.jboss.org/browse/TEIIDDES-1810
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Patch Release, Teiid Integration
> Reporter: Steven Hawkins
> Assignee: Dan Florian
> Fix For: 10.0.1, 9.2.1
>
>
> The table/column stats are currently limited to max int (2^31 -1) values.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (TEIIDDES-1810) Support larger statistic values
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1810?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1810:
----------------------------------------
The property value is stored in the XMI file in string form, of course, so the *2* solution would utilize an internal EMF property value that we'd have to specificially code to.. to store the *real* value, when that property is displayed, we can show the "real" string.
But... then we'd have to also grab the *real* string value when we are creating the model's *index*'d metadata so Teiid doesn't receive the *wrong* value.
> Support larger statistic values
> -------------------------------
>
> Key: TEIIDDES-1810
> URL: https://issues.jboss.org/browse/TEIIDDES-1810
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Patch Release, Teiid Integration
> Reporter: Steven Hawkins
> Assignee: Dan Florian
> Fix For: 10.0.1, 9.2.1
>
>
> The table/column stats are currently limited to max int (2^31 -1) values.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (TEIIDDES-1810) Support larger statistic values
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1810?page=com.atlassian.jira.plu... ]
Matus Makovy commented on TEIIDDES-1810:
----------------------------------------
[~elvisisking]
I have a suggestion for this, maybe it is the same as 2.
Would it be possible to show the value in the properties view as String, do the conversion in the background and save the value in whatever format / type the Teiid is able to understand (the value that results from conversion) ?
> Support larger statistic values
> -------------------------------
>
> Key: TEIIDDES-1810
> URL: https://issues.jboss.org/browse/TEIIDDES-1810
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Patch Release, Teiid Integration
> Reporter: Steven Hawkins
> Assignee: Dan Florian
> Fix For: 10.0.1, 9.2.1
>
>
> The table/column stats are currently limited to max int (2^31 -1) values.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (TEIIDDES-1810) Support larger statistic values
by Dan Florian (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1810?page=com.atlassian.jira.plu... ]
Dan Florian commented on TEIIDDES-1810:
---------------------------------------
When setting values, a conversion from a long to a negative float to an integer takes place. Doing this conversion a loss of precision is expected. However, the difference is *extremely* small relative to the original very large number. I talked to Steve Hawkins about this, and he said this is acceptable behavior. Agree that the user experience using the property editor is not that great (seeing a number they just entered change its value).
If we want to change the current behavior I can think of 2 possible solutions:
# We can make the user experience a bit nicer by displaying the value as a float. The float value will be displayed using scientific notation (which does not show all the digits.
# A bit harder solution would be to save the original value as an annotation and then display that to the user instead of the actual value that results from the conversions.
[~blafond] and [~mmakovy] what do you think?
> Support larger statistic values
> -------------------------------
>
> Key: TEIIDDES-1810
> URL: https://issues.jboss.org/browse/TEIIDDES-1810
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Patch Release, Teiid Integration
> Reporter: Steven Hawkins
> Assignee: Dan Florian
> Fix For: 10.0.1, 9.2.1
>
>
> The table/column stats are currently limited to max int (2^31 -1) values.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months
[JBoss JIRA] (TEIIDDES-2835) NullPointerException at org.teiid.designer.jdbc.ui.wizards.JdbcImportOptionsPage.createModelDefinitionPanel(JdbcImportOptionsPage.java:444) when "Create source model for JDBC Data Source" from the Guide UI
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2835?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2835.
------------------------------------
Resolution: Done
10.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/ce49ba7b0bed49726...
> NullPointerException at org.teiid.designer.jdbc.ui.wizards.JdbcImportOptionsPage.createModelDefinitionPanel(JdbcImportOptionsPage.java:444) when "Create source model for JDBC Data Source" from the Guide UI
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2835
> URL: https://issues.jboss.org/browse/TEIIDDES-2835
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Dialogs, Patch Release
> Affects Versions: 10.0
> Environment: Teiid Designed 10.0.0.Final.
> eclipse.buildId=4.5.2.M20160212-1500
> java.version=1.8.0_91
> java.vendor=Oracle Corporation
> BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
> Framework arguments: -product org.eclipse.epp.package.jee.product -product org.eclipse.epp.package.jee.product -product org.eclipse.epp.package.jee.product
> Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.jee.product -product org.eclipse.epp.package.jee.product -data file:/C:/Users/ggregory/workspaces/teiid-designer-mars/ -product org.eclipse.epp.package.jee.product
> Reporter: Gary Gregory
> Assignee: Barry LaFond
> Fix For: 10.0.1
>
> Attachments: npe.png, screenshot-1.png, teiid-mars-config.txt
>
>
> - Install stock plain Eclipse Mars (4.5.2)
> - Install Teiid Designer 10.0.0.Final per http://teiiddesigner.jboss.org/designer_summary/downloads
> - Following the guide http://docs.jboss.org/teiid/designer/10.0/user-guide/en-US/html/dive-righ...
> - Created MySQL 5.0 JDBC data source
> - Created Oracle 10g JDBC "thin" XE data source
> - On step 4 "Create source model for JDBC data source", launching the step from the guide causes an NPE:
> {{java.lang.NullPointerException
> at org.teiid.designer.jdbc.ui.wizards.JdbcImportOptionsPage.createModelDefinitionPanel(JdbcImportOptionsPage.java:444)
> at org.teiid.designer.jdbc.ui.wizards.JdbcImportOptionsPage.createModelDefinitionTab(JdbcImportOptionsPage.java:245)
> at org.teiid.designer.jdbc.ui.wizards.JdbcImportOptionsPage.createControl(JdbcImportOptionsPage.java:228)
> at org.teiid.designer.ui.common.wizard.AbstractWizard.createPageControls(AbstractWizard.java:153)
> at org.teiid.designer.ui.common.wizard.AbstractWizard.createPageControls(AbstractWizard.java:138)
> at org.teiid.designer.jdbc.ui.wizards.JdbcImportWizard.createPageControls(JdbcImportWizard.java:250)
> at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:705)
> at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:597)
> at org.eclipse.jface.window.Window.create(Window.java:430)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096)
> at org.teiid.designer.ui.viewsupport.ModelerUiViewUtils$7.run(ModelerUiViewUtils.java:250)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:186)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:4761)
> at org.teiid.designer.ui.viewsupport.ModelerUiViewUtils.launchWizard(ModelerUiViewUtils.java:240)
> at org.teiid.designer.ui.viewsupport.ModelerUiViewUtils$5.run(ModelerUiViewUtils.java:185)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:186)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:4761)
> at org.teiid.designer.ui.viewsupport.ModelerUiViewUtils.launchWizard(ModelerUiViewUtils.java:167)
> at org.teiid.designer.advisor.ui.actions.AdvisorActionFactory.launchWizard(AdvisorActionFactory.java:904)
> at org.teiid.designer.advisor.ui.actions.AdvisorActionFactory.executeAction(AdvisorActionFactory.java:437)
> at org.teiid.designer.advisor.ui.views.guides.TeiidGuidesSection.launchGuidesAction(TeiidGuidesSection.java:281)
> at org.teiid.designer.advisor.ui.views.guides.TeiidGuidesSection.access$1(TeiidGuidesSection.java:271)
> at org.teiid.designer.advisor.ui.views.guides.TeiidGuidesSection$4.doubleClick(TeiidGuidesSection.java:174)
> at org.eclipse.jface.viewers.StructuredViewer$1.run(StructuredViewer.java:832)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.viewers.StructuredViewer.fireDoubleClick(StructuredViewer.java:829)
> at org.eclipse.jface.viewers.AbstractTreeViewer.handleDoubleSelect(AbstractTreeViewer.java:1470)
> at org.eclipse.jface.viewers.StructuredViewer$4.widgetDefaultSelected(StructuredViewer.java:1263)
> at org.eclipse.jface.util.OpenStrategy.fireDefaultSelectionEvent(OpenStrategy.java:252)
> at org.eclipse.jface.util.OpenStrategy.access$0(OpenStrategy.java:249)
> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:311)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4362)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1113)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4180)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3769)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> 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(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> }}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 8 months