July 2015 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2447) Failed to import SalesForce Metadata

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2447?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2447: ----------------------------------- Fix Version/s: 9.1 > Failed to import SalesForce Metadata > ------------------------------------ > > Key: TEIIDDES-2447 > URL: https://issues.jboss.org/browse/TEIIDDES-2447 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Priority: Critical > Fix For: 9.1 > > Attachments: sfddl (1).ddl > > > Using the Teiid Connection import, the attached DDL has been retrived from salesforce instance. However Designer fails to import it, and gives NO clue as to what is wrong. > 1) The DDL should be successfully imported > 2) When there is something wrong that Designer does not understand it needs to give a meaningful error, as per the location of the file and context -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1846) Top Down modeling, when importing to create views, allow for default syntax to applied

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1846?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1846: ----------------------------------- Fix Version/s: Future (was: 9.2) > Top Down modeling, when importing to create views, allow for default syntax to applied > -------------------------------------------------------------------------------------- > > Key: TEIIDDES-1846 > URL: https://issues.jboss.org/browse/TEIIDDES-1846 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: Future > > > When a user is starting from a top-down approach (building the views) to design their data layers, and will be performing an import to create the view layer, it would speed up the iterative development of build / deploy / test (not preview) if when the view is built (on import), it can contain valid syntax so that the model will validate. Example of syntax could be, "Select '1'" or "Select 'view not defined'" or throw an exception. This would enable the modeler to implement the views at their pace and have it deployable, rather than having to go thru every view and add syntax before its valid. This is akin to JAVA and NOOP'ing the methods. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1898) Connection Profile requires a password for preview

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1898?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1898: ----------------------------------- Fix Version/s: 9.3 (was: 9.2) > Connection Profile requires a password for preview > -------------------------------------------------- > > Key: TEIIDDES-1898 > URL: https://issues.jboss.org/browse/TEIIDDES-1898 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.2 > Reporter: Ramesh Reddy > Assignee: Barry LaFond > Fix For: 9.3 > > > Some data sources can work without user name and/or password for connecting to the source. So, those properties are not mandatory and requiring them for preview is unnecessary if they are not defined. > In this example, Hive Connection profile was created with username but with out password, when the Teiid Connection importer used and them a connection profile is set on it to use the preview, it failed until a dummy password is provided -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2572) DDL Parser fails when table contains VARCHAR column with DEFAULT value

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2572?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2572: ---------------------------------------- This appears to be a MS Teiid Parsing issue. The work-around is to save the DDL to your filesystem/workspace, remove the offending quotes and re-import using the DDL Importer selecting the Teiid Dialect. Going to clone this and move to Modeshape JIRA > DDL Parser fails when table contains VARCHAR column with DEFAULT value > ---------------------------------------------------------------------- > > Key: TEIIDDES-2572 > URL: https://issues.jboss.org/browse/TEIIDDES-2572 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Teiid Integration > Affects Versions: 8.3.3 > Environment: Teiid Designer 8.3.3 > Teiid 8.4.1-redhat-7 > Reporter: Andrej Šmigala > Assignee: Barry LaFond > Fix For: 9.2 > > > Create a table with > {code:sql} > CREATE TABLE t1 ( c1 VARCHAR(10) DEFAULT 'c1' ) > {code} > When trying to import it through Teiid Connection Importer, the importer DDL is shown as > {code:sql} > CREATE FOREIGN TABLE "dballo00.dbo.t1" ( > c1 string(10) DEFAULT '(''c1'')' OPTIONS (NAMEINSOURCE '"c1"', NATIVE_TYPE 'varchar') > ) OPTIONS (NAMEINSOURCE '"dballo00"."dbo"."t1"', UPDATABLE TRUE, CARDINALITY 0); > {code} > but on the next page, the following error is shown (see screenshot): > The DDL failed to parse with message: "Unparsable table body". -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2572) DDL Parser fails when table contains VARCHAR column with DEFAULT value

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-2572: -------------------------------------- Summary: DDL Parser fails when table contains VARCHAR column with DEFAULT value Key: TEIIDDES-2572 URL: https://issues.jboss.org/browse/TEIIDDES-2572 Project: Teiid Designer Issue Type: Bug Components: Import/Export, Teiid Integration Affects Versions: 8.3.3 Environment: Teiid Designer 8.3.3 Teiid 8.4.1-redhat-7 Reporter: Andrej Šmigala Assignee: Barry LaFond Fix For: 9.2 Create a table with {code:sql} CREATE TABLE t1 ( c1 VARCHAR(10) DEFAULT 'c1' ) {code} When trying to import it through Teiid Connection Importer, the importer DDL is shown as {code:sql} CREATE FOREIGN TABLE "dballo00.dbo.t1" ( c1 string(10) DEFAULT '(''c1'')' OPTIONS (NAMEINSOURCE '"c1"', NATIVE_TYPE 'varchar') ) OPTIONS (NAMEINSOURCE '"dballo00"."dbo"."t1"', UPDATABLE TRUE, CARDINALITY 0); {code} but on the next page, the following error is shown (see screenshot): The DDL failed to parse with message: "Unparsable table body". -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2252) Add preference to importers to specify which characters should be substituted for

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2252?page=com.atlassian.jira.plu... ] Barry LaFond closed TEIIDDES-2252. ---------------------------------- Resolution: Out of Date > Add preference to importers to specify which characters should be substituted for > --------------------------------------------------------------------------------- > > Key: TEIIDDES-2252 > URL: https://issues.jboss.org/browse/TEIIDDES-2252 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Affects Versions: 8.5 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 9.2 > > > Add a preference that would allow the user to specify a set of characters that should be replaced by another character. > This enhancement will resolve the issue when ModeShape metadata is being imported using the Teiid Connection importer, and will allow the user to substitute the colon for an underscore. But would also be available for any other data source that would have need for this type of substitution. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2265) Allow MultiSelect Columns for creation of indexes

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2265?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2265: ----------------------------------- Fix Version/s: 9.3 (was: 9.2) > Allow MultiSelect Columns for creation of indexes > ------------------------------------------------- > > Key: TEIIDDES-2265 > URL: https://issues.jboss.org/browse/TEIIDDES-2265 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Reporter: Tom Johnston > Assignee: Barry LaFond > Fix For: 9.3 > > > I just realized a pain point. > I have a need to create a number of indexes on views (as they are going to be materialized) but there seems no easy way but one by one. > I envision the following: > Multi-select columns (in Model explorer OR Table editor ) and click Modeling and choose Create index (also UK and PK I would think) .. suggest a 'template' (i.e. tableName_ColumnName_IX (auto add 1...x if something or more than one exists) If I choose 2 cols from one table then a check to create one or multiple (default to multiple) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2270) Add capability to import a project for migrations.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2270?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2270: ----------------------------------- Fix Version/s: 9.3 (was: 9.2) > Add capability to import a project for migrations. > -------------------------------------------------- > > Key: TEIIDDES-2270 > URL: https://issues.jboss.org/browse/TEIIDDES-2270 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 8.5 > Reporter: Hisanobu Okuda > Assignee: Barry LaFond > Fix For: 9.3 > > > This capability would allow a user to easily upgrade their Designer version without losing anything. The workspace export/import would bring along projects, preferences, connector bindings, extension jars, etc. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2092) Consolidate Data Source connection management into a single view

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2092?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2092: ----------------------------------- Fix Version/s: 9.3 (was: 9.2) > Consolidate Data Source connection management into a single view > ---------------------------------------------------------------- > > Key: TEIIDDES-2092 > URL: https://issues.jboss.org/browse/TEIIDDES-2092 > Project: Teiid Designer > Issue Type: Feature Request > Components: Datatools Integration, Teiid Integration, Views > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 9.3 > > Attachments: data-sources-view-draft.png > > > Teiid Designer, and JBoss Tools in general, suffers from the lack of a centralized view of workspace datasource/connection information. > This feature may include: > * Data Sources view > ** Tree containing datasource category/type folders (i.e. JDBC, WS, File, Spreadsheet etc.... ) and instances of Datasource Definitions > ** Property table to show/edit properties for selected Datasource Definitions > ** Toolbar to allow creating DDs, creating/deploying datasources from selected DDs > ** Actions would include: Create Data Source, Import > JDBC or through Teiid Connection -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2121) Create a Connections editor dialog that can edit/manage a source model's connection profile and translator info

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2121?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2121: ----------------------------------- Fix Version/s: 9.3 (was: 9.2) > Create a Connections editor dialog that can edit/manage a source model's connection profile and translator info > --------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2121 > URL: https://issues.jboss.org/browse/TEIIDDES-2121 > Project: Teiid Designer > Issue Type: Feature Request > Components: Datatools Integration, Modeling > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 9.3 > > > Moved connection related actions to it's own sub-menu, *Connection* under *Modeling* action. > After further thought, it would simplify things even more if we created a dialog that can edit/manage all connection-related tasks for source models. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 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 July 2015