October 2014 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2362) Column can be selected as Row Filter target

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2362?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2362: ----------------------------------- Fix Version/s: 8.7 8.6.1 Assignee: Barry LaFond Component/s: Patch Release VDB & Execution > Column can be selected as Row Filter target > ------------------------------------------- > > Key: TEIIDDES-2362 > URL: https://issues.jboss.org/browse/TEIIDDES-2362 > Project: Teiid Designer > Issue Type: Bug > Components: Patch Release, VDB & Execution > Affects Versions: 8.6.1 > Reporter: Matus Makovy > Assignee: Barry LaFond > Fix For: 8.7, 8.6.1 > > > Teiid Designer lets user select column as row-filter target. Row filter target can be only table, view or procedure. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1037) Data types inported from flat file partially implemented in wizard

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1037?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1037: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1093210|https://bugzilla.redhat.com/show_bug.cgi?id=1093210] from ASSIGNED to MODIFIED > Data types inported from flat file partially implemented in wizard > ------------------------------------------------------------------ > > Key: TEIIDDES-1037 > URL: https://issues.jboss.org/browse/TEIIDDES-1037 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Patch Release > Affects Versions: 7.5 > Reporter: Paul Nittel > Assignee: Barry LaFond > Fix For: 8.7, 8.6.1 > > Attachments: FlatFileDataTypes_NOT.png > > > The new Flat File metadata importer is great! Not having to write the TEXTTABLE function is a fine example of usability improvement. > I noticed, during import, a dialog option that indicated datatypes can be the second line in the data file (column names being the first). That, and its associated help, are the only reference to this possibility (see attached screenshot). Without the actual functionality, it's confusing. > Later in the wizardly process, the column names row number is captured. I suspect the types row--if present, and its use desired by the user--should also be determined at that point. > The ability of importing the datatypes from the flat file would, IMHO, really enhance what is already a superb importer! (Yeah, I _do_ like it!) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1037) Data types inported from flat file partially implemented in wizard

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1037?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1037: ----------------------------------- Component/s: Patch Release > Data types inported from flat file partially implemented in wizard > ------------------------------------------------------------------ > > Key: TEIIDDES-1037 > URL: https://issues.jboss.org/browse/TEIIDDES-1037 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Patch Release > Affects Versions: 7.5 > Reporter: Paul Nittel > Assignee: Barry LaFond > Fix For: 8.7, 8.6.1 > > Attachments: FlatFileDataTypes_NOT.png > > > The new Flat File metadata importer is great! Not having to write the TEXTTABLE function is a fine example of usability improvement. > I noticed, during import, a dialog option that indicated datatypes can be the second line in the data file (column names being the first). That, and its associated help, are the only reference to this possibility (see attached screenshot). Without the actual functionality, it's confusing. > Later in the wizardly process, the column names row number is captured. I suspect the types row--if present, and its use desired by the user--should also be determined at that point. > The ability of importing the datatypes from the flat file would, IMHO, really enhance what is already a superb importer! (Yeah, I _do_ like it!) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1037) Data types inported from flat file partially implemented in wizard

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1037?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1037. ------------------------------------ Resolution: Done > Data types inported from flat file partially implemented in wizard > ------------------------------------------------------------------ > > Key: TEIIDDES-1037 > URL: https://issues.jboss.org/browse/TEIIDDES-1037 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Patch Release > Affects Versions: 7.5 > Reporter: Paul Nittel > Assignee: Barry LaFond > Fix For: 8.7, 8.6.1 > > Attachments: FlatFileDataTypes_NOT.png > > > The new Flat File metadata importer is great! Not having to write the TEXTTABLE function is a fine example of usability improvement. > I noticed, during import, a dialog option that indicated datatypes can be the second line in the data file (column names being the first). That, and its associated help, are the only reference to this possibility (see attached screenshot). Without the actual functionality, it's confusing. > Later in the wizardly process, the column names row number is captured. I suspect the types row--if present, and its use desired by the user--should also be determined at that point. > The ability of importing the datatypes from the flat file would, IMHO, really enhance what is already a superb importer! (Yeah, I _do_ like it!) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1037) Data types inported from flat file partially implemented in wizard

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1037?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1037: ---------------------------------------- Committed to master for 8.7: https://github.com/Teiid-Designer/teiid-designer/commit/5e65200c9b214e8ca... > Data types inported from flat file partially implemented in wizard > ------------------------------------------------------------------ > > Key: TEIIDDES-1037 > URL: https://issues.jboss.org/browse/TEIIDDES-1037 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.5 > Reporter: Paul Nittel > Assignee: Barry LaFond > Fix For: 8.7, 8.6.1 > > Attachments: FlatFileDataTypes_NOT.png > > > The new Flat File metadata importer is great! Not having to write the TEXTTABLE function is a fine example of usability improvement. > I noticed, during import, a dialog option that indicated datatypes can be the second line in the data file (column names being the first). That, and its associated help, are the only reference to this possibility (see attached screenshot). Without the actual functionality, it's confusing. > Later in the wizardly process, the column names row number is captured. I suspect the types row--if present, and its use desired by the user--should also be determined at that point. > The ability of importing the datatypes from the flat file would, IMHO, really enhance what is already a superb importer! (Yeah, I _do_ like it!) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1037) Data types inported from flat file partially implemented in wizard

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1037?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1037: ---------------------------------------- Backed off a bit. Seems the TEXTTABLE() and XMLTABLE() functions are looking for Teiid RUNTIME Types and not Design-time Types. This clashes a bit with the creation of the COLUMN EMF objects. If INTEGER type is selected then the COLUMN will end up with INTEGER and a validation warning will result. This needs to get converted to INT during *FlatFileViewModelFactory.createColumns()* method. This will also apply to the XML File Import use-case. > Data types inported from flat file partially implemented in wizard > ------------------------------------------------------------------ > > Key: TEIIDDES-1037 > URL: https://issues.jboss.org/browse/TEIIDDES-1037 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.5 > Reporter: Paul Nittel > Assignee: Barry LaFond > Fix For: 8.7, 8.6.1 > > Attachments: FlatFileDataTypes_NOT.png > > > The new Flat File metadata importer is great! Not having to write the TEXTTABLE function is a fine example of usability improvement. > I noticed, during import, a dialog option that indicated datatypes can be the second line in the data file (column names being the first). That, and its associated help, are the only reference to this possibility (see attached screenshot). Without the actual functionality, it's confusing. > Later in the wizardly process, the column names row number is captured. I suspect the types row--if present, and its use desired by the user--should also be determined at that point. > The ability of importing the datatypes from the flat file would, IMHO, really enhance what is already a superb importer! (Yeah, I _do_ like it!) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2365) Validate the JDBC username and password in the default teiid instance.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2365?page=com.atlassian.jira.plu... ] Barry LaFond moved JBTIS-329 to TEIIDDES-2365: ---------------------------------------------- Project: Teiid Designer (was: JBoss Tools Integration Stack) Key: TEIIDDES-2365 (was: JBTIS-329) Issue Type: Bug (was: Feature Request) Workflow: classic default workflow (was: GIT Pull Request workflow ) Component/s: Data Preview VDB & Execution (was: teiid) > Validate the JDBC username and password in the default teiid instance. > ---------------------------------------------------------------------- > > Key: TEIIDDES-2365 > URL: https://issues.jboss.org/browse/TEIIDDES-2365 > Project: Teiid Designer > Issue Type: Bug > Components: Data Preview, VDB & Execution > Environment: jboss-eap-6.1, teiid-8.8.1-jboss-dist and teiid-8.4.1-redhat-7-jdbc.jar > Reporter: mohith sethia > Priority: Critical > Attachments: JDBC_connection.png, teiid_instance.png > > > 11:25:06,981 INFO [org.teiid.RUNTIME] (MSC service thread 1-3) TEIID50029 VDB PREVIEW_36d41ce6-4641-4fdd-9682-a1d24b5b9a73_parts_sources_SourceModel.1 model "SourceModel" metadata is currently being loaded. Start Time: 9/24/14 11:25 AM > 11:25:07,107 INFO [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50030 VDB PREVIEW_36d41ce6-4641-4fdd-9682-a1d24b5b9a73_parts_sources_SourceModel.1 model "SourceModel" metadata loaded. End Time: 9/24/14 11:25 AM > 11:25:07,146 INFO [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID40003 VDB PREVIEW_36d41ce6-4641-4fdd-9682-a1d24b5b9a73_parts_sources_SourceModel.1 is set to ACTIVE > 11:25:07,150 INFO [org.teiid.RUNTIME] (MSC service thread 1-3) TEIID40003 VDB PREVIEW_36d41ce6-4641-4fdd-9682-a1d24b5b9a73_parts_project.1 is set to ACTIVE > 11:25:07,181 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "PREVIEW_36d41ce6-4641-4fdd-9682-a1d24b5b9a73_parts_sources_SourceModel.vdb" (runtime-name : "PREVIEW_36d41ce6-4641-4fdd-9682-a1d24b5b9a73_parts_sources_SourceModel.vdb") > 11:25:07,735 INFO [org.teiid.RUNTIME] (MSC service thread 1-2) TEIID50026 VDB "PREVIEW_36d41ce6-4641-4fdd-9682-a1d24b5b9a73_parts_project.1[]" undeployed. > 11:25:07,740 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment PREVIEW_36d41ce6-4641-4fdd-9682-a1d24b5b9a73_parts_project.vdb (runtime-name: PREVIEW_36d41ce6-4641-4fdd-9682-a1d24b5b9a73_parts_project.vdb) in 6ms > 11:25:07,808 INFO [org.jboss.as.repository] (management-handler-thread - 3) JBAS014901: Content removed from location E:\jboss_teiid\jboss-eap-6.1\standalone\data\content\23\235c09797b9816d7b3b09ac12c1bd177f0eae0\content > 11:25:07,808 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018558: Undeployed "PREVIEW_36d41ce6-4641-4fdd-9682-a1d24b5b9a73_parts_project.vdb" (runtime-name: "PREVIEW_36d41ce6-4641-4fdd-9682-a1d24b5b9a73_parts_project.vdb") > 11:25:07,889 INFO [org.jboss.as.repository] (management-handler-thread - 4) JBAS014900: Content added at location E:\jboss_teiid\jboss-eap-6.1\standalone\data\content\73\50264a19b19e4d514258c1df73900c6e9d73af\content > 11:25:07,912 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "PREVIEW_36d41ce6-4641-4fdd-9682-a1d24b5b9a73_parts_project.vdb" (runtime-name: "PREVIEW_36d41ce6-4641-4fdd-9682-a1d24b5b9a73_parts_project.vdb") > 11:25:08,032 INFO [org.teiid.RUNTIME] (MSC service thread 1-1) TEIID40003 VDB PREVIEW_36d41ce6-4641-4fdd-9682-a1d24b5b9a73_parts_project.1 is set to ACTIVE > 11:25:08,193 INFO [org.jboss.as.server] (management-handler-thread - 4) JBAS018559: Deployed "PREVIEW_36d41ce6-4641-4fdd-9682-a1d24b5b9a73_parts_project.vdb" (runtime-name : "PREVIEW_36d41ce6-4641-4fdd-9682-a1d24b5b9a73_parts_project.vdb") > 11:25:09,499 WARN [org.teiid.SECURITY] (New I/O worker #1) TEIID40011 Processing exception 'TEIID50072 The username "user" and/or password and/or payload token could not be authenticated by any membership domain.' for session null. Exception type org.teiid.client.security.LogonException thrown from org.teiid.jboss.JBossSessionService.authenticate(JBossSessionService.java:74). Enable more detailed logging to see the entire stacktrace. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2361) Project indicates it needs a Quick Fix

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2361?page=com.atlassian.jira.plu... ] Van Halbert closed TEIIDDES-2361. --------------------------------- Resolution: Rejected User error, thanks barry. > Project indicates it needs a Quick Fix > -------------------------------------- > > Key: TEIIDDES-2361 > URL: https://issues.jboss.org/browse/TEIIDDES-2361 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.6.1 > Reporter: Van Halbert > Attachments: object_projectset.zip > > > Getting the following error message for the attached project set: > Model project definition for Object is out of date. Perform Quick Fix to update the project > <vhalbert> blafond, have an error in designer: > [08:19] <vhalbert> Model project definition for Object is out of date. Perform Quick Fix to update the project > [08:19] <vhalbert> where's the Quick Fix button? > [08:21] <blafond> vhalbert: you have a model project is out of date? 7.7.x (5.3) project? > [08:22] <vhalbert> blafond, not that i'm aware, this quickstart project wasn't done until 6.0, and it worked then > [08:23] <vhalbert> blafond, i started making changes and the error just started yesterday > [08:23] <blafond> vhalbert: log a JIRA, attach the project and I'll check it out > [08:23] <vhalbert> blafond, ok, tx -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2361) Project indicates it needs a Quick Fix

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2361?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2361: ---------------------------------------- The .project attached is from Designer 7.4.2 {code:xml} <?xml version="1.0" encoding="UTF-8"?> <projectDescription> <name>Object</name> <comment>No Product Application, version 7.4.2.v20111104-1235-H672-Final</comment> <projects> </projects> <buildSpec> <buildCommand> <name>org.teiid.designer.core.modelBuilder</name> <arguments> </arguments> </buildCommand> </buildSpec> <natures> <nature>org.teiid.designer.core.modelNature</nature> </natures> </projectDescription> {code} To be up-to-date it needs to include 2 new build spec entries: {code:xml} <?xml version="1.0" encoding="UTF-8"?> <projectDescription> <name>Object</name> <comment>No Product Application, version XXXXXXX</comment> <projects> </projects> <buildSpec> <buildCommand> <name>org.teiid.designer.vdb.ui.vdbBuilder</name> <arguments> </arguments> </buildCommand> <buildCommand> <name>org.teiid.designer.extension.ui.modelExtensionDefinitionBuilder</name> <arguments> </arguments> </buildCommand> <buildCommand> <name>org.teiid.designer.core.modelBuilder</name> <arguments> </arguments> </buildCommand> </buildSpec> <natures> <nature>org.teiid.designer.core.modelNature</nature> </natures> </projectDescription> {code} > Project indicates it needs a Quick Fix > -------------------------------------- > > Key: TEIIDDES-2361 > URL: https://issues.jboss.org/browse/TEIIDDES-2361 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 8.6.1 > Reporter: Van Halbert > Attachments: object_projectset.zip > > > Getting the following error message for the attached project set: > Model project definition for Object is out of date. Perform Quick Fix to update the project > <vhalbert> blafond, have an error in designer: > [08:19] <vhalbert> Model project definition for Object is out of date. Perform Quick Fix to update the project > [08:19] <vhalbert> where's the Quick Fix button? > [08:21] <blafond> vhalbert: you have a model project is out of date? 7.7.x (5.3) project? > [08:22] <vhalbert> blafond, not that i'm aware, this quickstart project wasn't done until 6.0, and it worked then > [08:23] <vhalbert> blafond, i started making changes and the error just started yesterday > [08:23] <blafond> vhalbert: log a JIRA, attach the project and I'll check it out > [08:23] <vhalbert> blafond, ok, tx -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2364) Remove .settings folder from Model Explorer

by Joao Viragine (JIRA)

Joao Viragine created TEIIDDES-2364: --------------------------------------- Summary: Remove .settings folder from Model Explorer Key: TEIIDDES-2364 URL: https://issues.jboss.org/browse/TEIIDDES-2364 Project: Teiid Designer Issue Type: Feature Request Reporter: Joao Viragine Model Explorer should filter (don't show) the .settings folder in the Teiid Project Tree -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 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 October 2014