November 2017 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2659) Preview data will have deployed the driver to the server only after first error.

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2659?page=com.atlassian.jira.plu... ] Matej Kralik closed TEIIDDES-2659. ---------------------------------- > Preview data will have deployed the driver to the server only after first error. > -------------------------------------------------------------------------------- > > Key: TEIIDDES-2659 > URL: https://issues.jboss.org/browse/TEIIDDES-2659 > Project: Teiid Designer > Issue Type: Bug > Components: Data Preview, Patch Release > Affects Versions: 9.0.3 > Reporter: Matej Kralik > Assignee: Dan Florian > Priority: Minor > Fix For: 11.1 > > > I removed a driver from the server,then clicked to refresh teiid instance connection in the Jboss developer studio. (once or more) but preview data doesn't deploy the driver on the server and shows error (TEIID30498 Capabilities for [source model] were not avaialable. The command could not be planned properly.). And from now when I click to refresh teiid instance connection and I click to preview data, data will be show correctly. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3144) Warning dialog for udf function in vdb appears every time

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3144?page=com.atlassian.jira.plu... ] Matej Kralik resolved TEIIDDES-3144. ------------------------------------ Resolution: Done PR: https://github.com/Teiid-Designer/teiid-designer/pull/583 > Warning dialog for udf function in vdb appears every time > --------------------------------------------------------- > > Key: TEIIDDES-3144 > URL: https://issues.jboss.org/browse/TEIIDDES-3144 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 11.1.1 > Reporter: Matej Kralik > Assignee: Matej Kralik > Priority: Critical > > Warning dialog which shows a warning when VDB contains udf appears every time when VDB is generated as XML. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3144) Warning dialog for udf function in vdb appears every time

by Matej Kralik (JIRA)

Matej Kralik created TEIIDDES-3144: -------------------------------------- Summary: Warning dialog for udf function in vdb appears every time Key: TEIIDDES-3144 URL: https://issues.jboss.org/browse/TEIIDDES-3144 Project: Teiid Designer Issue Type: Bug Affects Versions: 11.1.1 Reporter: Matej Kralik Assignee: Matej Kralik Priority: Critical Warning dialog which shows a warning when VDB contains udf appears every time when VDB is generated as XML. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3097) Create common JNDI entry workflow requiring "java:/" prefix

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3097?page=com.atlassian.jira.plu... ] Matej Kralik updated TEIIDDES-3097: ----------------------------------- Attachment: jdgConnectionProfile.png > Create common JNDI entry workflow requiring "java:/" prefix > ----------------------------------------------------------- > > Key: TEIIDDES-3097 > URL: https://issues.jboss.org/browse/TEIIDDES-3097 > Project: Teiid Designer > Issue Type: Enhancement > Components: Datatools Integration, Editors, Teiid Integration > Affects Versions: 11.0.1 > Reporter: Barry LaFond > Fix For: 11.1 > > Attachments: jdgConnectionProfile.png > > > Change all JNDI name entry fields to validate using common validator to require proper "java:/" prefix and verify valid characters only after that. > This should collapse all possible JNDI text fields to operate with the same validation logic and make the "java:/" prefix a requirement rather than confusing the user in allowing a name without it yet adding it behind the scenes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3097) Create common JNDI entry workflow requiring "java:/" prefix

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3097?page=com.atlassian.jira.plu... ] Matej Kralik reopened TEIIDDES-3097: ------------------------------------ JDG 6.x connection profile still doesn't have this validator. > Create common JNDI entry workflow requiring "java:/" prefix > ----------------------------------------------------------- > > Key: TEIIDDES-3097 > URL: https://issues.jboss.org/browse/TEIIDDES-3097 > Project: Teiid Designer > Issue Type: Enhancement > Components: Datatools Integration, Editors, Teiid Integration > Affects Versions: 11.0.1 > Reporter: Barry LaFond > Fix For: 11.1 > > Attachments: jdgConnectionProfile.png > > > Change all JNDI name entry fields to validate using common validator to require proper "java:/" prefix and verify valid characters only after that. > This should collapse all possible JNDI text fields to operate with the same validation logic and make the "java:/" prefix a requirement rather than confusing the user in allowing a name without it yet adding it behind the scenes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3143) NPE after click on Create POJO

by Matej Kralik (JIRA)

Matej Kralik created TEIIDDES-3143: -------------------------------------- Summary: NPE after click on Create POJO Key: TEIIDDES-3143 URL: https://issues.jboss.org/browse/TEIIDDES-3143 Project: Teiid Designer Issue Type: Bug Affects Versions: 11.1.1 Environment: Windows 10 Reporter: Matej Kralik Priority: Critical NPE when I want to create POJO for view table. {code:java} java.lang.NullPointerException at org.teiid.designer.transformation.ui.wizards.jdg.MaterializationWizardPage_2.createControl(MaterializationWizardPage_2.java:131) 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.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:688) at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:580) at org.eclipse.jface.window.Window.create(Window.java:426) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096) at org.eclipse.jface.window.Window.open(Window.java:783) at org.teiid.designer.transformation.ui.actions.CreatePojoAction.run(CreatePojoAction.java:102) at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565) at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4428) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4238) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3817) 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.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2683) Importing Excel file using Teiid Connection does not import extension properties

by Michael Echevarria (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2683?page=com.atlassian.jira.plu... ] Michael Echevarria commented on TEIIDDES-2683: ---------------------------------------------- Is this fix currently available? I am using Teiid Designer 11.1.0.V20170905-2106 in JBDS 11.1 and this issue is still present. The DDL import wizard shows the CELL_NUMBER options, but they are not in the generated model > Importing Excel file using Teiid Connection does not import extension properties > -------------------------------------------------------------------------------- > > Key: TEIIDDES-2683 > URL: https://issues.jboss.org/browse/TEIIDDES-2683 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 9.0.4 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Fix For: 11.1 > > > When importing an excel file using Teiid Connection, the extension properties are silently discarded. This results in invalid model, which, when deployed and queried, causes the following error in the server log: > bq. Connector worker process failed for atomic-request=AVU37BnZoOUS.0.0.0: org.teiid.translator.TranslatorException: TEIID23007 OPTIONS property CELL_NUMBER is required and it not defined on column ROW_ID > The DDL obtained from the server is > {code:sql} > SET NAMESPACE 'http://www.teiid.org/translator/excel/2014' AS teiid_excel; > CREATE FOREIGN TABLE Sheet1 ( > ROW_ID integer OPTIONS (SEARCHABLE 'All_Except_Like', "teiid_excel:CELL_NUMBER" 'ROW_ID'), > StringNum string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '1'), > CharValue string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '2'), > DoubleNum double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '3'), > BigIntegerValue double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '4'), > ShortValue double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '5'), > FloatNum double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '6'), > ObjectValue string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '7'), > IntNum double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '8'), > BigDecimalValue double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '9'), > LongNum double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '10'), > BooleanValue boolean OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '11'), > TimestampValue double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '12'), > ByteNum double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '13'), > IntKey double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '14'), > StringKey string OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '15'), > TimeValue double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '16'), > DateValue double OPTIONS (SEARCHABLE 'Unsearchable', "teiid_excel:CELL_NUMBER" '17'), > CONSTRAINT PK0 PRIMARY KEY(ROW_ID) > ) OPTIONS ("teiid_excel:FILE" 'smalla.xlsx', "teiid_excel:FIRST_DATA_ROW_NUMBER" '2'); > {code} > When trying to import the same DDL using the DDL import wizard, a warning dialog is shown stating that the extension properties could not be processed and the Model Extension Definition should be registered -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3132) After hitting cancel in Set Data Source JNDI name dialogue alert with empty message is displayed

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3132?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-3132. ---------------------------------- > After hitting cancel in Set Data Source JNDI name dialogue alert with empty message is displayed > ------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-3132 > URL: https://issues.jboss.org/browse/TEIIDDES-3132 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 11.1.1 > Reporter: Matus Makovy > Assignee: Barry LaFond > Fix For: 11.1.1 > > Attachments: Screen Shot 2017-11-08 at 12.34.53.png > > > I discovered this while verifying TEIIDDES-3098. > After you click cancel in Set Data Source JNDI name dialogue alert is displayed, but this alert has no message set. See screenshot. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2868) texttable parsing error

by Tom Johnston (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2868?page=com.atlassian.jira.plu... ] Tom Johnston commented on TEIIDDES-2868: ---------------------------------------- If this helps... I've learned that I can do a regex search/replace. Search for \r\n and replace with 3 spaces > texttable parsing error > ----------------------- > > Key: TEIIDDES-2868 > URL: https://issues.jboss.org/browse/TEIIDDES-2868 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 10.0 > Environment: Teiid Designer 10.0.0.Final-v20160413-1817-B4094 org.teiid.designer.feature.feature.group JBoss by Red Hat > Reporter: Tom Johnston > Attachments: QuickStartSource.xmi, QuickStartViewModel.xmi, TeiiDDes2868.txt, TeiiDDes2868.zip, marketdata-price.txt, screenshot-1.png, screenshot-2.png, screenshot-3.png > > > I successfully created a physical table and view using texttable. > I can query it. > I then manually created another view to a different file and it kept failing with a very ambiguous error when I tried validating. > ERROR: Error in parsing of sql - null > I then created another view with a diff name of the 1st view using the same copy/pasted transformation.. it too resulting with the same error: > The auto-generated view verbiage that was created and that I re-used was: > SELECT > A.OldWAC, A.NewWAC > FROM > (EXEC SourceModel.getTextFiles('wac.txt')) AS f, TEXTTABLE(f.file COLUMNS OldWAC string, NewWAC string DELIMITER '|') AS A > You can also clone the automatically created object, copy the transformation, clear the transformation, paste back the transformation and it too fails with the same error. > ALSO if I deploy the 1st physical and view models to a vdb I can execute the view transformation that fails in designer fine from squirrel getting data returned. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-3142) Missing native metadata tag with overriding infinispan translator

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-3142?page=com.atlassian.jira.plu... ] Matej Kralik resolved TEIIDDES-3142. ------------------------------------ Resolution: Done PR: https://github.com/Teiid-Designer/teiid-designer/pull/581 > Missing native metadata tag with overriding infinispan translator > ----------------------------------------------------------------- > > Key: TEIIDDES-3142 > URL: https://issues.jboss.org/browse/TEIIDDES-3142 > Project: Teiid Designer > Issue Type: Bug > Components: Dynamic VDBs > Affects Versions: 11.1.1 > Environment: Fedora 26 > Reporter: Matej Kralik > Assignee: Matej Kralik > Priority: Critical > Fix For: 11.1.1 > > > When I set up JDG materialization, the teiid designer automatic creates overriding infinispan translator for JDG source model but when I generate -vdb.xml, the model with overriding translator doesn't have *NATIVE* metadata tag because has another name than "infinispan-hotrod" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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 November 2017