[JBoss JIRA] (TEIIDDES-3217) Error reading Foreign Keys from Mysql 8.0
by Christoph John (Jira)
[ https://issues.jboss.org/browse/TEIIDDES-3217?page=com.atlassian.jira.plu... ]
Christoph John edited comment on TEIIDDES-3217 at 11/18/18 8:05 PM:
--------------------------------------------------------------------
Hello Steven,
sorry for the late reply. I could now solve the issue. I had no primary key in the table. Therefore the foreign key was probably not correctly imported. Now the import is working with mysql8
was (Author: cjohn001):
Hello Steven,
sorry for the late reply. I could …
[View More]now solve the issue. I had no primary key in the table. Therefore the foreign key was probably not correctly imported. No the import is working with mysql8
> Error reading Foreign Keys from Mysql 8.0
> -----------------------------------------
>
> Key: TEIIDDES-3217
> URL: https://issues.jboss.org/browse/TEIIDDES-3217
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration
> Affects Versions: 11.1.3
> Reporter: Christoph John
> Priority: Major
>
> I am currently trying to use TEIID designer together with a mysql 8.0 database to import a source model. Unfortunately, foreign keys cannot be read correctly. I assume it has to do with the VISIBLE flag on the index. Is there a known workaround available for mysql 8.0?
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[View Less]
6 years, 4 months
[JBoss JIRA] (TEIIDDES-3197) Run SQL query first time causes exceptions
by Barry LaFond (Jira)
[ https://issues.jboss.org/browse/TEIIDDES-3197?page=com.atlassian.jira.plu... ]
Barry LaFond closed TEIIDDES-3197.
----------------------------------
Resolution: Won't Fix
this exception is partly due to OS and Eclipse start-up config. Depending on what other applications (Eclipse plugins) are running may reduce the amount of handles for Designer. Closing
> Run SQL query first time causes exceptions
> ------------------------------------------
>
> Key: …
[View More]TEIIDDES-3197
> URL: https://issues.jboss.org/browse/TEIIDDES-3197
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 11.1.3
> Environment: Fedora
> Reporter: Matej Kralik
> Priority: Critical
> Attachments: runSQLcausesException.mkv
>
>
> When I run SQL in the SQL Scrapbook first time, the exception ("No more handles") is thrown. After that, JBDS shows me that SWT error has occurred. I choose not to restart JBDS. After that, I am able to run next SQL queries without exception but when I restart JBDS, the exception is thrown the first time again. I have uploaded the video with this behavior to the attachments.
> Exceptions:
> org.teiid.datatools.connectivity.ui
> {code:java}
> org.eclipse.swt.SWTError: No more handles
> at org.eclipse.swt.SWT.error(SWT.java:4559)
> at org.eclipse.swt.SWT.error(SWT.java:4448)
> at org.eclipse.swt.SWT.error(SWT.java:4419)
> at org.eclipse.swt.browser.Browser.<init>(Browser.java:103)
> at org.teiid.datatools.views.ExecutionPlanView.createHTMLViewerPanel(ExecutionPlanView.java:295)
> at org.teiid.datatools.views.ExecutionPlanView.createPlanHTMLTab(ExecutionPlanView.java:256)
> at org.teiid.datatools.views.ExecutionPlanView.createPlanViewerGroup(ExecutionPlanView.java:247)
> at org.teiid.datatools.views.ExecutionPlanView.createPanel(ExecutionPlanView.java:191)
> at org.teiid.datatools.views.ExecutionPlanView.createPartControl(ExecutionPlanView.java:94)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:151)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityView.createPartControl(CompatibilityView.java:147)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:355)
> 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:498)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:990)
> at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:955)
> at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:124)
> at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:399)
> at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:318)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:105)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:74)
> at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:56)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:129)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:992)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:661)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$1.run(PartRenderingEngine.java:546)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:530)
> at org.eclipse.e4.ui.workbench.renderers.swt.ElementReferenceRenderer.createWidget(ElementReferenceRenderer.java:70)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:992)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:661)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:767)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:738)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:732)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:716)
> at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.showTab(StackRenderer.java:1293)
> at org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer.lambda$0(LazyStackRenderer.java:68)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:233)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:144)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:5535)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:212)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36)
> at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:201)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135)
> at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78)
> at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39)
> at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:52)
> at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:60)
> at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374)
> at org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:173)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:620)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:584)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:769)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:743)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:681)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:676)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1179)
> at org.eclipse.ui.internal.WorkbenchPage.showPart(WorkbenchPage.java:1287)
> at org.eclipse.ui.internal.WorkbenchPage.busyShowView(WorkbenchPage.java:1278)
> at org.eclipse.ui.internal.WorkbenchPage$12.run(WorkbenchPage.java:4329)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage.java:4325)
> at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage.java:4305)
> at org.teiid.datatools.connectivity.ui.TeiidAdHocScriptRunnable.handleShowExecutionPlan(TeiidAdHocScriptRunnable.java:301)
> at org.teiid.datatools.connectivity.ui.TeiidAdHocScriptRunnable.access$1(TeiidAdHocScriptRunnable.java:295)
> at org.teiid.datatools.connectivity.ui.TeiidAdHocScriptRunnable$UpdatePlanViewRunnable.run(TeiidAdHocScriptRunnable.java:338)
> at org.eclipse.ui.internal.PendingSyncExec.run(PendingSyncExec.java:58)
> at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:168)
> at org.eclipse.ui.internal.UISynchronizer.lambda$0(UISynchronizer.java:150)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:37)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4577)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4186)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
> 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:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> 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:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1472)
> {code}
> The command ("org.eclipse.datatools.sqltools.sqleditor.ExplainSQLAction") is undefined
> {code:java}
> java.lang.Exception
> at org.eclipse.jface.action.ExternalActionManager$CommandCallback.isActive(ExternalActionManager.java:364)
> at org.eclipse.jface.action.ActionContributionItem.isCommandActive(ActionContributionItem.java:626)
> at org.eclipse.jface.action.ActionContributionItem.isVisible(ActionContributionItem.java:682)
> at org.eclipse.jface.action.MenuManager.isChildVisible(MenuManager.java:982)
> at org.eclipse.jface.action.MenuManager.isVisible(MenuManager.java:563)
> at org.eclipse.jface.action.MenuManager.isChildVisible(MenuManager.java:982)
> at org.eclipse.jface.action.MenuManager.update(MenuManager.java:752)
> at org.eclipse.jface.action.MenuManager.update(MenuManager.java:669)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer.scheduleManagerUpdate(MenuManagerRenderer.java:1214)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer.processContents(MenuManagerRenderer.java:649)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer.subscribeTopicChildAdded(MenuManagerRenderer.java:324)
> at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
> at org.eclipse.e4.ui.internal.di.UIEventObjectSupplier$UIEventHandler$1.run(UIEventObjectSupplier.java:64)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:233)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:144)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:5535)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:212)
> at org.eclipse.e4.ui.internal.di.UIEventObjectSupplier$UIEventHandler.handleEvent(UIEventObjectSupplier.java:61)
> at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:201)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135)
> at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78)
> at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39)
> at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:52)
> at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:60)
> at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374)
> at org.eclipse.emf.ecore.util.EcoreEList.dispatchNotification(EcoreEList.java:249)
> at org.eclipse.emf.common.notify.impl.NotifyingListImpl.addUnique(NotifyingListImpl.java:294)
> at org.eclipse.emf.common.util.AbstractEList.add(AbstractEList.java:305)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer.reconcileManagerToModel(MenuManagerRenderer.java:1041)
> at org.eclipse.ui.internal.PopupMenuExtender.addMenuContributions(PopupMenuExtender.java:409)
> at org.eclipse.ui.internal.PopupMenuExtender.menuAboutToShow(PopupMenuExtender.java:382)
> at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:339)
> at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:470)
> at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:465)
> at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:497)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:256)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5348)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1348)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1374)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1353)
> at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:198)
> at org.eclipse.swt.widgets.Display.runPopups(Display.java:4644)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4173)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
> 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:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> 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:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1472)
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[View Less]
6 years, 4 months
[JBoss JIRA] (TEIIDDES-3010) Add feature to provide adding After Triggers to materialized views/tables
by Barry LaFond (Jira)
[ https://issues.jboss.org/browse/TEIIDDES-3010?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-3010:
-----------------------------------
Fix Version/s: 12.0
(was: 11.2.2)
> Add feature to provide adding After Triggers to materialized views/tables
> -------------------------------------------------------------------------
>
> Key: TEIIDDES-3010
> URL: https://issues.jboss.org/browse/TEIIDDES-3010
> …
[View More] Project: Teiid Designer
> Issue Type: Enhancement
> Reporter: Steven Hawkins
> Assignee: Barry LaFond
> Priority: Blocker
> Fix For: 12.0
>
> Attachments: Sample Materialization Editor Page.bmml, Sample Materialization Editor Page.png, teditor-toolbar.png
>
>
> TEIID-4627 adds support for source level triggers to be called after CDC events.
> The triggers are similar to what is supported by views, but "INSTEAD OF" is not supported - just AFTER.
> CREATE TRIGGER name ON table AFTER (INSERT|UPDATE|DELETE) FOR EACH ROW statement
> Just like view triggers new/old/changing values can be referenced. Note that unlike view triggers, these must be named as an arbitrary number of them are supported per table (like other of our constructs they are scoped to the table, not to the schema).
> We may eventually want to support multiple event types for a single trigger and may need to support internal events as well.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[View Less]
6 years, 4 months
[JBoss JIRA] (TEIIDDES-2390) Transformation SQL formatting inserts extra characters
by Barry LaFond (Jira)
[ https://issues.jboss.org/browse/TEIIDDES-2390?page=com.atlassian.jira.plu... ]
Barry LaFond closed TEIIDDES-2390.
----------------------------------
Resolution: Won't Fix
> Transformation SQL formatting inserts extra characters
> ------------------------------------------------------
>
> Key: TEIIDDES-2390
> URL: https://issues.jboss.org/browse/TEIIDDES-2390
> Project: Teiid Designer
> Issue Type: Bug
> …
[View More] Components: Patch Release, Transformations
> Affects Versions: 8.3.4, 9.0.1
> Reporter: Andrej Šmigala
> Assignee: Paul Richardson
> Priority: Minor
> Fix For: Future
>
>
> Typing more than two newlines after a keyword in the transformation editor causes part of that keyword to be inserted into the transformation.
> e. g. typing
> {code:sql}
> select <enter><enter><enter>
> {code}
> produces
> {code:sql}
> SEL
> SELECT
>
> {code}
> and
> {code:sql}
> select * from <enter><enter><enter><enter>
> {code}
> produces
> {code:sql}
> SELECT
> *
> FRO
> FRO
> FROM
>
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[View Less]
6 years, 4 months
[JBoss JIRA] (TEIIDDES-2689) LDAP dialogue too slow - loads a lot of data?
by Barry LaFond (Jira)
[ https://issues.jboss.org/browse/TEIIDDES-2689?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-2689:
--------------------------------------
Assignee: (was: Paul Richardson)
> LDAP dialogue too slow - loads a lot of data?
> ---------------------------------------------
>
> Key: TEIIDDES-2689
> URL: https://issues.jboss.org/browse/TEIIDDES-2689
> Project: Teiid Designer
> Issue Type: Bug
> …
[View More] Components: Import/Export, Patch Release
> Affects Versions: 9.0.4
> Environment: MAC OS
> Reporter: Matus Makovy
> Priority: Critical
> Fix For: Future
>
> Attachments: Screen Shot 2015-10-14 at 14.17.46.png
>
>
> I came across this when trying to verify TEIIDDES-2478.
> When you have a LDAP instance with big amount of entries (in the screenshot you can see that are 931 entries) in some part, it takes long to load all attributes. After clicking Next> on the page shown in screenshot (see attachment) JBDS freezes and doesn't respond for about 3 minutes. At least we should have some message that says, that TD is loading data from LDAP.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[View Less]
6 years, 4 months
[JBoss JIRA] (TEIIDDES-2689) LDAP dialogue too slow - loads a lot of data?
by Barry LaFond (Jira)
[ https://issues.jboss.org/browse/TEIIDDES-2689?page=com.atlassian.jira.plu... ]
Barry LaFond closed TEIIDDES-2689.
----------------------------------
Resolution: Done
> LDAP dialogue too slow - loads a lot of data?
> ---------------------------------------------
>
> Key: TEIIDDES-2689
> URL: https://issues.jboss.org/browse/TEIIDDES-2689
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/…
[View More]Export, Patch Release
> Affects Versions: 9.0.4
> Environment: MAC OS
> Reporter: Matus Makovy
> Priority: Critical
> Fix For: Future
>
> Attachments: Screen Shot 2015-10-14 at 14.17.46.png
>
>
> I came across this when trying to verify TEIIDDES-2478.
> When you have a LDAP instance with big amount of entries (in the screenshot you can see that are 931 entries) in some part, it takes long to load all attributes. After clicking Next> on the page shown in screenshot (see attachment) JBDS freezes and doesn't respond for about 3 minutes. At least we should have some message that says, that TD is loading data from LDAP.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[View Less]
6 years, 4 months
[JBoss JIRA] (TEIIDDES-1809) WAR File (REST, SOAP) Creation usability enhancements
by Barry LaFond (Jira)
[ https://issues.jboss.org/browse/TEIIDDES-1809?page=com.atlassian.jira.plu... ]
Barry LaFond closed TEIIDDES-1809.
----------------------------------
Resolution: Done
> WAR File (REST, SOAP) Creation usability enhancements
> ------------------------------------------------------
>
> Key: TEIIDDES-1809
> URL: https://issues.jboss.org/browse/TEIIDDES-1809
> Project: Teiid Designer
> Issue Type: Enhancement
> …
[View More] Components: Patch Release, Web Services Support
> Reporter: Ramesh Reddy
> Assignee: Ted Jones
> Priority: Major
> Fix For: Future
>
>
> I have seen so many time in the community, where users are confused in asking them to create JNDI file to VDB and deploy the VDB and WAR file. I have two suggestions in this regard to help improve the situation
> 1) Instead of (or in addition) asking to enter {REPLACE_WITH_VDB_JNDI_NAME}, offer to create data source to the VDB. If the server is attached, you have all details, or pop up create datasource dialog to create.
> 2) Instead of (or in addition) to saving the WAR file, offer to deploy directly to the server, that will save time and would seem seamless operation we can provide.
> 3) I often find myself struck in figuring out what is WSDL Endpoint or what are REST endpoints exposed by the WAR deployed, it there is any help we can show at the end of this dialog box (if they choose to deploy) that would save time in them figuring out (going to documentation etc).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
[View Less]
6 years, 4 months