[JBoss JIRA] (TEIIDDES-2550) parseTimestamp function in Transformation Editor gives StringIndexOutOfBounds Exception
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2550?page=com.atlassian.jira.plu... ]
Matej Kralik updated TEIIDDES-2550:
-----------------------------------
Labels: verified_jbdsis-9.0.0.Beta (was: )
> parseTimestamp function in Transformation Editor gives StringIndexOutOfBounds Exception
> ---------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2550
> URL: https://issues.jboss.org/browse/TEIIDDES-2550
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling, Patch Release, Transformations
> Affects Versions: 9.1
> Environment: Teiid 8.7.1.redhat-8 and Teiid Designer 9.1.0.Beta1
> Reporter: Daan Creemers
> Assignee: Paul Richardson
> Labels: verified_jbdsis-9.0.0.Beta
> Fix For: 10.0.1, 9.2.1
>
> Attachments: ParseTimestamp-Project.png, TestParseTimestamp.tar.gz
>
>
> When using the parseTimestamp function in the transformation editor while creating a relational view model, a StringIndexOutOfBoundsException is thrown. The query SELECT parseTimestamp('18:10:20', 'HH:mm:ss') is used in the transformation editor which gives 'String index out of range: 1'. I want to use the function with a column of my table but produces the same error.
> When deploying a virtual database and executing exactly the same query on the database, the query finishes successfully and gives the result.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 2 months
[JBoss JIRA] (TEIIDDES-2493) Check for spaces in the parent directory Flat File connection importer
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2493?page=com.atlassian.jira.plu... ]
Matej Kralik closed TEIIDDES-2493.
----------------------------------
> Check for spaces in the parent directory Flat File connection importer
> ----------------------------------------------------------------------
>
> Key: TEIIDDES-2493
> URL: https://issues.jboss.org/browse/TEIIDDES-2493
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Patch Release
> Reporter: Ramesh Reddy
> Assignee: Mark Drilling
> Labels: release_notes, verified_jbdsis-9.0.0.Beta
> Fix For: 10.0.1, 9.2.1
>
>
> Add a check to make sure there are no spaces in the ParentDirectory or root directory path when Flat File Connection Profile is chosen.
> ====================
> The problem is manifested on the server when attempting to query the datasource. On datasource creation, the resource adapter is written to the standalone.xml like this.
> {code:java}
> <config-property name="ParentDirectory">
> /home/mdrilling/My Dir/data
> </config-property>
> {code}
> The embedded space in the ParentDirectory property value is problematic.
> Need to determine whether to (1) disallow a path with spaces or (2) allow it, replacing the space with the appropriate control code ie {code:java} {code} - like this
> {code:java}
> <config-property name="ParentDirectory">
> /home/mdrilling/My Dir/data
> </config-property>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 2 months
[JBoss JIRA] (TEIIDDES-2493) Check for spaces in the parent directory Flat File connection importer
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2493?page=com.atlassian.jira.plu... ]
Matej Kralik updated TEIIDDES-2493:
-----------------------------------
Labels: release_notes verified_jbdsis-9.0.0.Beta (was: )
> Check for spaces in the parent directory Flat File connection importer
> ----------------------------------------------------------------------
>
> Key: TEIIDDES-2493
> URL: https://issues.jboss.org/browse/TEIIDDES-2493
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Patch Release
> Reporter: Ramesh Reddy
> Assignee: Mark Drilling
> Labels: release_notes, verified_jbdsis-9.0.0.Beta
> Fix For: 10.0.1, 9.2.1
>
>
> Add a check to make sure there are no spaces in the ParentDirectory or root directory path when Flat File Connection Profile is chosen.
> ====================
> The problem is manifested on the server when attempting to query the datasource. On datasource creation, the resource adapter is written to the standalone.xml like this.
> {code:java}
> <config-property name="ParentDirectory">
> /home/mdrilling/My Dir/data
> </config-property>
> {code}
> The embedded space in the ParentDirectory property value is problematic.
> Need to determine whether to (1) disallow a path with spaces or (2) allow it, replacing the space with the appropriate control code ie {code:java} {code} - like this
> {code:java}
> <config-property name="ParentDirectory">
> /home/mdrilling/My Dir/data
> </config-property>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 2 months
[JBoss JIRA] (TEIIDDES-2795) Check if URL contains empty spaces
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2795?page=com.atlassian.jira.plu... ]
Matej Kralik updated TEIIDDES-2795:
-----------------------------------
Steps to Reproduce:
# create new connection profile (flat file URL source)
# set URL to you local file (for example "file:///home/mkralik/Downloads/folder with space/productdata_data.csv")
# import source and view model (Flat file via remote URL)
# create data source from source model
# check standalone.xml
was:
* create new connection profile (flat file URL source)
* set URL to you local file (for example "file:///home/mkralik/Downloads/folder with space/productdata_data.csv")
* import source and view model (Flat file via remote URL)
* create data source from source model
* check standalone.xml
> Check if URL contains empty spaces
> ----------------------------------
>
> Key: TEIIDDES-2795
> URL: https://issues.jboss.org/browse/TEIIDDES-2795
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 10.0.1
> Environment: Fedora 23
> Reporter: Matej Kralik
> Attachments: Screenshot from 2016-02-25 15-08-51.png
>
>
> When I tried to reproduce this bug ([TEIIDDES-2493|https://issues.jboss.org/browse/TEIIDDES-2493])
> I've found a way how set file whose path contains empty string. I set the file path as a URL and use import from remote flat file. Problem is same as ([TEIIDDES-2493|https://issues.jboss.org/browse/TEIIDDES-2493]).
> When i created datasource, file path is written to the standalone.xml with empty space.
> {code:java}
> <config-property name="EndPoint">
> file:/home/mkralik/Downloads/folder with space/productdata_data.csv
> </config-property>
> {code}
> I think user
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 2 months
[JBoss JIRA] (TEIIDDES-2794) Connecting to remote server and refreshing produces an exception
by Matus Makovy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2794?page=com.atlassian.jira.plu... ]
Matus Makovy commented on TEIIDDES-2794:
----------------------------------------
I forgot to mention that I encountered this only with clean / new workspace
> Connecting to remote server and refreshing produces an exception
> ----------------------------------------------------------------
>
> Key: TEIIDDES-2794
> URL: https://issues.jboss.org/browse/TEIIDDES-2794
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0
> Reporter: Matus Makovy
> Attachments: Screen Shot 2016-02-25 at 11.31.43.png, Screen Shot 2016-02-25 at 11.41.58.png
>
>
> When I create new remote server in teiid designer, try to connect to it and refresh the connection an exception occurs. After clicking OK in the alert dialogue connection to server works.
> When I hit refresh once more, there is no exception/error.
> Screenshots attached
> Exception:
> {code:java}
> org.teiid.adminapi.AdminComponentException: java.io.IOException: java.lang.IllegalStateException: JBAS010641: ModelControllerClient is closed
> at org.teiid.runtime.client.admin.v8.Admin8Factory$AdminImpl.getVDBs(Admin8Factory.java:1761)
> at org.teiid.runtime.client.admin.v8.Admin8Factory$AdminImpl.getVDBs(Admin8Factory.java:1)
> at org.teiid.runtime.client.admin.ExecutionAdmin.refreshVDBs(ExecutionAdmin.java:796)
> at org.teiid.runtime.client.admin.ExecutionAdmin.refresh(ExecutionAdmin.java:722)
> at org.teiid.runtime.client.admin.ExecutionAdmin.connect(ExecutionAdmin.java:682)
> at org.teiid.designer.runtime.TeiidServer.connect(TeiidServer.java:253)
> at org.teiid.designer.runtime.TeiidServer.reconnect(TeiidServer.java:293)
> at org.teiid.designer.runtime.ui.server.RefreshServerAction$1.run(RefreshServerAction.java:89)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator$2$1.run(UiBusyIndicator.java:206)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.executeRunnable(UiBusyIndicator.java:227)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.showWhileInternal(UiBusyIndicator.java:159)
> at org.teiid.designer.ui.common.viewsupport.UiBusyIndicator.showWhile(UiBusyIndicator.java:116)
> at org.teiid.designer.runtime.ui.server.RefreshServerAction.run(RefreshServerAction.java:80)
> at org.teiid.designer.runtime.ui.server.RefreshServerAction.execute(RefreshServerAction.java:132)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> 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:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:799)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:675)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:659)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:592)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299)
> at org.jboss.reddeer.core.handler.WidgetHandler$5.run(WidgetHandler.java:382)
> at org.jboss.reddeer.core.util.Display$VoidResultRunnable.run(Display.java:194)
> at org.jboss.reddeer.core.util.Display$VoidResultRunnable.run(Display.java:1)
> at org.jboss.reddeer.core.util.Display$ErrorHandlingRunnable.run(Display.java:160)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700)
> 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.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:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> 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)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> Caused by: java.io.IOException: java.lang.IllegalStateException: JBAS010641: ModelControllerClient is closed
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75)
> at org.teiid.runtime.client.admin.v8.Admin8Factory$AdminImpl.getVDBs(Admin8Factory.java:1756)
> ... 72 more
> Caused by: java.lang.IllegalStateException: JBAS010641: ModelControllerClient is closed
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:115)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:65)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:123)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:98)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147)
> ... 74 more
> {code}
> TD 10.0.0.Beta3
> DV 6.2
> remote connection using ssh
> the connection uses management operations
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 2 months
[JBoss JIRA] (TEIIDDES-2784) Not open the xml mapping diagram through the model explorer
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2784?page=com.atlassian.jira.plu... ]
Matej Kralik updated TEIIDDES-2784:
-----------------------------------
Labels: verified_jbdsis-9.0.0.Beta (was: release_notes verified_jbdsis-9.0.0.Beta)
> Not open the xml mapping diagram through the model explorer
> -----------------------------------------------------------
>
> Key: TEIIDDES-2784
> URL: https://issues.jboss.org/browse/TEIIDDES-2784
> Project: Teiid Designer
> Issue Type: Bug
> Components: Editors
> Affects Versions: 10.0.1
> Environment: Windows 10 Pro N
> Fedora 23
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Priority: Minor
> Labels: verified_jbdsis-9.0.0.Beta
> Fix For: 10.0.1
>
> Attachments: Recursive.zip
>
>
> When I try open XML document through model explorer, it shows me the mapping diagram for a few seconds but then show me back the package diagram.
> When I open XML document through package diagram, the mapping diagram shows correct.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 2 months
[JBoss JIRA] (TEIIDDES-2784) Not open the xml mapping diagram through the model explorer
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2784?page=com.atlassian.jira.plu... ]
Matej Kralik closed TEIIDDES-2784.
----------------------------------
> Not open the xml mapping diagram through the model explorer
> -----------------------------------------------------------
>
> Key: TEIIDDES-2784
> URL: https://issues.jboss.org/browse/TEIIDDES-2784
> Project: Teiid Designer
> Issue Type: Bug
> Components: Editors
> Affects Versions: 10.0.1
> Environment: Windows 10 Pro N
> Fedora 23
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Priority: Minor
> Labels: verified_jbdsis-9.0.0.Beta
> Fix For: 10.0.1
>
> Attachments: Recursive.zip
>
>
> When I try open XML document through model explorer, it shows me the mapping diagram for a few seconds but then show me back the package diagram.
> When I open XML document through package diagram, the mapping diagram shows correct.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 2 months