August 2014 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2259) Edit VDB Data Role dialogue doesn't check off checkboxes properly

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2259?page=com.atlassian.jira.plu... ] Van Halbert reassigned TEIIDDES-2259: ------------------------------------- Assignee: Van Halbert > Edit VDB Data Role dialogue doesn't check off checkboxes properly > ----------------------------------------------------------------- > > Key: TEIIDDES-2259 > URL: https://issues.jboss.org/browse/TEIIDDES-2259 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: VDB & Execution > Affects Versions: 8.3.3 > Reporter: Matus Makovy > Assignee: Van Halbert > Attachments: screen.png, screen1.png > > > When I tick, for example, "Create" on one column and "Read" on the same column and then check off "Create", the gray checkboxes stay the same. Only after I check off "Read" on this column all disappear... screenshot attached > JBDS 7.1.1.GA + Teiid Designer 8.3.3 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2259) Edit VDB Data Role dialogue doesn't check off checkboxes properly

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2259?page=com.atlassian.jira.plu... ] Van Halbert updated TEIIDDES-2259: ---------------------------------- Assignee: Barry LaFond (was: Van Halbert) > Edit VDB Data Role dialogue doesn't check off checkboxes properly > ----------------------------------------------------------------- > > Key: TEIIDDES-2259 > URL: https://issues.jboss.org/browse/TEIIDDES-2259 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: VDB & Execution > Affects Versions: 8.3.3 > Reporter: Matus Makovy > Assignee: Barry LaFond > Attachments: screen.png, screen1.png > > > When I tick, for example, "Create" on one column and "Read" on the same column and then check off "Create", the gray checkboxes stay the same. Only after I check off "Read" on this column all disappear... screenshot attached > JBDS 7.1.1.GA + Teiid Designer 8.3.3 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2292) Add SOLR data source type to Teiid Connection importer's Built-In DS types

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2292?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2292: ---------------------------------------- There is *no* reason to make the distinction. If Teiid does not return any metadata from getSchema() call just build a empty source model. That way user has head start in building a source model manually (if needed) and data source is created and Teiid connection import wizard does not end up in error. > Add SOLR data source type to Teiid Connection importer's Built-In DS types > -------------------------------------------------------------------------- > > Key: TEIIDDES-2292 > URL: https://issues.jboss.org/browse/TEIIDDES-2292 > Project: Teiid Designer > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Import/Export > Affects Versions: 8.6 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 8.6 > > > Teiid 8.8 supports SOLR data source/translator. > Need to add *solr* to the list of *BUILTIN_TYPES* in *SelectDataSourcePage* so it can recognize it as a supported non-JDBC translator type. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2292) Add SOLR data source type to Teiid Connection importer's Built-In DS types

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2292?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2292: ---------------------------------------- I understand that we can make the getSchema() call with any *type*, however, some translators return nothing, while *file* and *webservice* translators return procedures that are pretty much just Teiid functions. I think the expectation of the Teiid Connection Importer is that you end up with DDL defining Tables and Columns for a source. So, without a means for Designer to determine if getSchema() is really supported for a given translator type through the Teiid Admin API, Designer needs to contain some business logic to make the user experience a little better. If you can add that functionality, we can then start removing this business logic/dependency > Add SOLR data source type to Teiid Connection importer's Built-In DS types > -------------------------------------------------------------------------- > > Key: TEIIDDES-2292 > URL: https://issues.jboss.org/browse/TEIIDDES-2292 > Project: Teiid Designer > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Import/Export > Affects Versions: 8.6 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 8.6 > > > Teiid 8.8 supports SOLR data source/translator. > Need to add *solr* to the list of *BUILTIN_TYPES* in *SelectDataSourcePage* so it can recognize it as a supported non-JDBC translator type. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2292) Add SOLR data source type to Teiid Connection importer's Built-In DS types

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2292?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2292: ---------------------------------------- we really need to remove this dependency, this goes against the custom translator development > Add SOLR data source type to Teiid Connection importer's Built-In DS types > -------------------------------------------------------------------------- > > Key: TEIIDDES-2292 > URL: https://issues.jboss.org/browse/TEIIDDES-2292 > Project: Teiid Designer > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Import/Export > Affects Versions: 8.6 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 8.6 > > > Teiid 8.8 supports SOLR data source/translator. > Need to add *solr* to the list of *BUILTIN_TYPES* in *SelectDataSourcePage* so it can recognize it as a supported non-JDBC translator type. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2292) Add SOLR data source type to Teiid Connection importer's Built-In DS types

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2292?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2292. ------------------------------------ Resolution: Done Done > Add SOLR data source type to Teiid Connection importer's Built-In DS types > -------------------------------------------------------------------------- > > Key: TEIIDDES-2292 > URL: https://issues.jboss.org/browse/TEIIDDES-2292 > Project: Teiid Designer > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Import/Export > Affects Versions: 8.6 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 8.6 > > > Teiid 8.8 supports SOLR data source/translator. > Need to add *solr* to the list of *BUILTIN_TYPES* in *SelectDataSourcePage* so it can recognize it as a supported non-JDBC translator type. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2292) Add SOLR data source type to Teiid Connection importer's Built-In DS types

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-2292: -------------------------------------- Summary: Add SOLR data source type to Teiid Connection importer's Built-In DS types Key: TEIIDDES-2292 URL: https://issues.jboss.org/browse/TEIIDDES-2292 Project: Teiid Designer Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Import/Export Affects Versions: 8.6 Reporter: Barry LaFond Assignee: Barry LaFond Fix For: 8.6 Teiid 8.8 supports SOLR data source/translator. Need to add *solr* to the list of *BUILTIN_TYPES* in *SelectDataSourcePage* so it can recognize it as a supported non-JDBC translator type. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2275) Invalid Model Name, when trying to use Teiid Connection Importer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2275?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2275: ----------------------------------- Fix Version/s: 8.3.4 8.6 8.5.1 Assignee: Barry LaFond > Invalid Model Name, when trying to use Teiid Connection Importer > ---------------------------------------------------------------- > > Key: TEIIDDES-2275 > URL: https://issues.jboss.org/browse/TEIIDDES-2275 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Import/Export > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Fix For: 8.3.4, 8.6, 8.5.1 > > Attachments: Invalid Model Name.png > > > When trying to use Teiid Connection Importer with SOLR source, the wizard says "Invalid model name", there is no model name to enter. The data source was created in the server and was available for selection. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2276) Windows only - XML File Importer will not let you add elements as columns

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2276?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2276: ----------------------------------- Fix Version/s: 8.3.4 8.6 8.5.1 Assignee: Mark Drilling > Windows only - XML File Importer will not let you add elements as columns > ------------------------------------------------------------------------- > > Key: TEIIDDES-2276 > URL: https://issues.jboss.org/browse/TEIIDDES-2276 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Import/Export > Affects Versions: 8.4, 8.3.3 > Environment: Windows > Reporter: Debbie Steigner > Assignee: Mark Drilling > Fix For: 8.3.4, 8.6, 8.5.1 > > > This only happens in Window the Linux JBDS works fine. Using the attached xml file, trying importing it as a File source. At the XML File Data Import options, try to select the rss > channel > item > tns:StoreId and click Add to move it to the columns box. It won't do it and gives the below error in the log > !ENTRY org.eclipse.ui 4 0 2014-08-07 10:24:35.234 > !MESSAGE Unhandled event loop exception > !STACK 0 > java.lang.NullPointerException > at org.teiid.designer.transformation.ui.wizards.xmlfile.TeiidXmlColumnInfo.getName(TeiidXmlColumnInfo.java:212) > at org.teiid.designer.transformation.ui.wizards.xmlfile.TeiidXmlColumnInfo.validate(TeiidXmlColumnInfo.java:466) > at org.teiid.designer.transformation.ui.wizards.xmlfile.TeiidXmlColumnInfo.setRelativePath(TeiidXmlColumnInfo.java:290) > at org.teiid.designer.transformation.ui.wizards.xmlfile.TeiidXmlColumnInfo.setRelativePathInternal(TeiidXmlColumnInfo.java:300) > at org.teiid.designer.transformation.ui.wizards.xmlfile.TeiidXmlColumnInfo.<init>(TeiidXmlColumnInfo.java:141) > at org.teiid.designer.transformation.ui.wizards.xmlfile.TeiidXmlColumnInfo.<init>(TeiidXmlColumnInfo.java:95) > at org.teiid.designer.transformation.ui.wizards.xmlfile.TeiidXmlFileInfo.addNewColumn(TeiidXmlFileInfo.java:277) > at org.teiid.designer.transformation.ui.wizards.xmlfile.panels.XmlFileContentsGroup.createColumn(XmlFileContentsGroup.java:174) > at org.teiid.designer.transformation.ui.wizards.xmlfile.TeiidXmlImportXmlConfigurationPage.createColumn(TeiidXmlImportXmlConfigurationPage.java:233) > at org.teiid.designer.transformation.ui.wizards.xmlfile.panels.ColumnsInfoPanel$2.widgetSelected(ColumnsInfoPanel.java:112) > 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.Widget.sendEvent(Widget.java:1057) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4170) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:826) > at org.eclipse.jface.window.Window.open(Window.java:802) > at org.eclipse.ui.internal.handlers.WizardHandler$Import.executeHandler(WizardHandler.java:152) > at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:279) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290) > 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:601) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167) > 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:213) > at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:420) > at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157) > at org.eclipse.ui.internal.actions.CommandAction.run(CommandAction.java:171) > at org.eclipse.ui.actions.ImportResourcesAction.run(ImportResourcesAction.java:97) > at org.eclipse.ui.actions.BaseSelectionListenerAction.runWithEvent(BaseSelectionListenerAction.java:168) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) > at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1057) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4170) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:140) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:611) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) > 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:354) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) > 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:601) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591) > at org.eclipse.equinox.launcher.Main.run(Main.java:1450) > at org.eclipse.equinox.launcher.Main.main(Main.java:1426) > !ENTRY org.eclipse.ui 4 0 2014-08-07 10:25:54.277 > !MESSAGE Unhandled event loop exception > !STACK 0 > java.lang.NullPointerException > at org.teiid.designer.transformation.ui.wizards.xmlfile.TeiidXmlColumnInfo.getName(TeiidXmlColumnInfo.java:212) > at org.teiid.designer.transformation.ui.wizards.xmlfile.TeiidXmlColumnInfo.validate(TeiidXmlColumnInfo.java:466) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2286) Creating procedure and assigning results works different depending on steps taken

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2286?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2286: ----------------------------------- Fix Version/s: 8.6 Assignee: Barry LaFond > Creating procedure and assigning results works different depending on steps taken > --------------------------------------------------------------------------------- > > Key: TEIIDDES-2286 > URL: https://issues.jboss.org/browse/TEIIDDES-2286 > Project: Teiid Designer > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Dialogs > Affects Versions: 8.5.1 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 8.6 > > > Trying to create a relational view procedure. And in the wizard, if I do NOT enter a result set, and click OK, and then proceed to right click on procedure to add result set (but add no column), the result set ends up taking on the datatype that the procedure returns. However, if in the wizard, I add the name of the result set (same name used if right mouse clicking above) and do not add a column, it doesn't work the same. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 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-designer-issues August 2014