September 2016 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-2687) Dynamic VDB generation - Default value for string column problem (DDL)

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2687?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2687. ---------------------------------- Closing this one. Issue is also discussed in 2888. TD JIRA Clean up > Dynamic VDB generation - Default value for string column problem (DDL) > ---------------------------------------------------------------------- > > Key: TEIIDDES-2687 > URL: https://issues.jboss.org/browse/TEIIDDES-2687 > Project: Teiid Designer > Issue Type: Bug > Components: Dynamic VDBs, Patch Release, VDB & Execution > Affects Versions: 9.0.4 > Reporter: Matus Makovy > Assignee: Mark Drilling > Fix For: 10.0.2, 9.2.1 > > > I have a model with table that has String column with default value "Stock". > DDL generated by TD for dynamic VDB looks like this: > {quote} > ... > TYPE string(15) DEFAULT ('Stock') OPTIONS(NAMEINSOURCE '"TYPE"', NATIVE_TYPE 'VARCHAR2', UPDATABLE 'FALSE'), > ... > {quote} > *DEFAULT ('Stock')* is not correct, it should be: *DEFAULT '("Stock")'* -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2658) Designer forgets translator name after model synchronisation

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2658?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2658. ---------------------------------- Tested today with newest TD and translator name was persisted. Closing. TD JIRA Clean up > Designer forgets translator name after model synchronisation > ------------------------------------------------------------ > > Key: TEIIDDES-2658 > URL: https://issues.jboss.org/browse/TEIIDDES-2658 > Project: Teiid Designer > Issue Type: Enhancement > Affects Versions: 9.1 > Reporter: Bram Gadeyne > > Each time a model is updated the field translator name is reset to jdbc-simple. Could this be kept on the configured translator name prior to the synchronisation? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2705) Teiid designer does not take the overriden translator

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2705?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2705. ---------------------------------- Rejected by developers. I verified today with TD 10.0.0.Alpha2 that I am able to create translator override and add it as translator name to source model. Closing. TD JIRA Clean up > Teiid designer does not take the overriden translator > ----------------------------------------------------- > > Key: TEIIDDES-2705 > URL: https://issues.jboss.org/browse/TEIIDDES-2705 > Project: Teiid Designer > Issue Type: Feature Request > Components: VDB & Execution > Reporter: jie tao > Priority: Optional > > in the VDB editor, an overriden translator can be defined, but in vdb.xml the default one is still used. No way to tell Designer to take the overriden one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2726) Change of parameter type in dialogue for editing rest connection profile settings is not persisted

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2726?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2726. ---------------------------------- > Change of parameter type in dialogue for editing rest connection profile settings is not persisted > -------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-2726 > URL: https://issues.jboss.org/browse/TEIIDDES-2726 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 9.0.4 > Environment: MAC OS X > Reporter: Matus Makovy > Assignee: Barry LaFond > Fix For: 10.0.2 > > Attachments: bug.mov > > > Change of parameter type during editing of connection profile created for REST import is not remembered. > See attached video -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2815) Flat File Import - "Parse Selected Row" feature works incorrectly

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2815?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2815. ---------------------------------- Rejected by developers. Closing TD JIRA Clean up > Flat File Import - "Parse Selected Row" feature works incorrectly > ----------------------------------------------------------------- > > Key: TEIIDDES-2815 > URL: https://issues.jboss.org/browse/TEIIDDES-2815 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 9.0.6, 10.0.1 > Reporter: Matus Makovy > Assignee: Barry LaFond > Fix For: 10.0.2 > > Attachments: EmpData.csv, Screen Shot 2016-03-30 at 9.24.56.png > > > In Empdata.csv, there are data that include "annual salary". This value is entered as "$71,000.00" (for example). If you choose "character delimited" column format, click on some row in File Contents Preview and hit "Parse Selected Row" the values are parsed as: > ... AnnualSalary: $7, Title: 000.00" ... > Expected result is: > ... AnnualSalary: $71,000.00, Title: Associate, ... > Actually, when you finish the wizard and hit preview on the table (or create a VDB and query the table) the value is parsed correctly. Only the "Parse Selected Row" feature parses the row incorrectly. > Screenshot attached -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2861) Import DDL option is confusing

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2861?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2861. ---------------------------------- Rejected by developers. Closing. TD JIRA Clean up > Import DDL option is confusing > ------------------------------ > > Key: TEIIDDES-2861 > URL: https://issues.jboss.org/browse/TEIIDDES-2861 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 10.0.1 > Reporter: Van Halbert > Attachments: jdg-remote-cache-mat-vdb.xml, portfolio-vdb.xml > > > Have the following comments when trying to use the DDL importer to import a dynamic vdb: > - It refers to everything as DDL, when dynamic vdb is not > - the file chooser defaults to DDL, when maybe it should have an option for .xml > - on the importer, there's a Mode type. When importing dynamic VDB's, this shouldn't apply, because the dynamic vdb can have both virtual and source models. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2897) Vertica Translator - Missing Quotes on Reserved Words.

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2897?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2897. ---------------------------------- This was marked as duplicate of 2858. Closing TD JIRA Clean up > Vertica Translator - Missing Quotes on Reserved Words. > ------------------------------------------------------ > > Key: TEIIDDES-2897 > URL: https://issues.jboss.org/browse/TEIIDDES-2897 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Reporter: Ted Jones > Attachments: firstError.txt > > > During import, the example in question, returns a column in the DDL that is double-quoted. > Currently the DDL parsing (and/or Designer) is removing the double quotes. They need to be preserved. > Previewing a Vertica table results in the following error: > 10:46:53,873 WARN [org.teiid.RUNTIME] (teiid-async-threads - 1) TEIID50036 VDB PREVIEW-7288da00-a070-45c9-9762-671d641ed431.1 model "rhel_iot_data" metadata failed to load. Reason:TEIID30386 org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered "'Integer'), [*]date[*] date OPTIONS" at line 5, column 9. > Was expecting: "constraint" | "foreign" | "primary" | "unique" | id: org.teiid.metadata.ParseException: TEIID30386 org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered "'Integer'), [*]date[*] date OPTIONS" at line 5, column 9. > Was expecting: "constraint" | "foreign" | "primary" | "unique" | id > at org.teiid.query.parser.QueryParser.parseDDL(QueryParser.java:472) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.metadata.MetadataFactory.parse(MetadataFactory.java:768) [teiid-api-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.query.metadata.DDLMetadataRepository.loadMetadata(DDLMetadataRepository.java:40) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.runtime.AbstractVDBDeployer$MetadataRepositoryWrapper.loadMetadata(AbstractVDBDeployer.java:84) [teiid-runtime-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.jboss.VDBService$6.run(VDBService.java:395) [teiid-jboss-integration-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at org.teiid.jboss.VDBService$7.run(VDBService.java:446) [teiid-jboss-integration-8.12.5.redhat-8.jar:8.12.5.redhat-8] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_65] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_65] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_65] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > Caused by: org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered "'Integer'), [*]date[*] date OPTIONS" at line 5, column 9. > Was expecting: "constraint" | "foreign" | "primary" | "unique" | id > at org.teiid.query.parser.QueryParser.convertParserException(QueryParser.java:214) [teiid-engine-8.12.5.redhat-8.jar:8.12.5.redhat-8] > ... 11 more -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2811) Running a User-Defined uses the wrong syntax

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2811?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2811. ---------------------------------- This was marked as won't do and cloned to 2833. Closing TD JIRA Clean up > Running a User-Defined uses the wrong syntax > -------------------------------------------- > > Key: TEIIDDES-2811 > URL: https://issues.jboss.org/browse/TEIIDDES-2811 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 9.0.3 > Environment: Red Hat JBoss Data Virtualization 6.2.2 on EAP patched to version 6.4.5, > JBoss Developer Studio 8.1.0GA with Teiid Designer plugin 9.0.3.Final.v20150810-1438-B1157 > 64-bit Windows 7 environment > Reporter: Steve Tran > Assignee: Barry LaFond > Priority: Minor > Attachments: Capture.PNG, error.PNG > > > After deploying my VDB, and viewing it inside the Datasource Explorer inside of JBDS, running a User-Defined Function through the GUI does not work because it's executing the wrong query. > Here's what JDV is doing. > {code} > 17:17:29,178 INFO [org.teiid.PLANNER] (Worker0_QueryProcessorQueue46) > ============================================================================ > USER COMMAND: > EXEC datasource.PGT('XPO') > ---------------------------------------------------------------------------- > OPTIMIZE: > EXEC datasource.PGT('XPO') > ---------------------------------------------------------------------------- > GENERATE CANONICAL: > EXEC datasource.PGT('XPO') > CANONICAL PLAN: > Project(groups=[datasource.PGT], props={PROJECT_COLS=[datasource.PGT.AUDIT_CODE, datasource.PGT.CLIENT_NBR]}) > Source(groups=[datasource.PGT], props={VIRTUAL_COMMAND=EXEC datasource.PGT('XPO')}) > ============================================================================ > EXECUTING PlaceAccess > AFTER: > Project(groups=[datasource.PGT], props={PROJECT_COLS=[datasource.PGT.AUDIT_CODE, datasource.PGT.CLIENT_NBR]}) > Access(groups=[datasource.PGT], props={SOURCE_HINT=null, MODEL_ID=Schema name=datasource, nameInSource=null, uuid=mmuuid:a521401c-37c6-4d3c-909d-55599421a456}) > Source(groups=[datasource.PGT], props={VIRTUAL_COMMAND=EXEC datasource.PGT('XPO')}) > ============================================================================ > EXECUTING RaiseAccess > AFTER: > Project(groups=[datasource.PGT], props={PROJECT_COLS=[datasource.PGT.AUDIT_CODE, datasource.PGT.CLIENT_NBR]}) > Access(groups=[datasource.PGT], props={SOURCE_HINT=null, MODEL_ID=Schema name=datasource, nameInSource=null, uuid=mmuuid:a521401c-37c6-4d3c-909d-55599421a456}) > Source(groups=[datasource.PGT], props={VIRTUAL_COMMAND=EXEC datasource.PGT('XPO')}) > ============================================================================ > EXECUTING AssignOutputElements > AFTER: > Project(groups=[datasource.PGT], props={PROJECT_COLS=[datasource.PGT.AUDIT_CODE, datasource.PGT.CLIENT_NBR], OUTPUT_COLS=[datasource.PGT.AUDIT_CODE, datasource.PGT.CLIENT_NBR]}) > Access(groups=[datasource.PGT], props={SOURCE_HINT=null, MODEL_ID=Schema name=datasource, nameInSource=null, uuid=mmuuid:a521401c-37c6-4d3c-909d-55599421a456, OUTPUT_COLS=[datasource.PGT.AUDIT_CODE, datasource.PGT.CLIENT_NBR]}) > Source(groups=[datasource.PGT], props={VIRTUAL_COMMAND=EXEC datasource.PGT('XPO'), OUTPUT_COLS=[datasource.PGT.AUDIT_CODE, datasource.PGT.CLIENT_NBR]}) > ============================================================================ > EXECUTING CalculateCost > AFTER: > Project(groups=[datasource.PGT], props={PROJECT_COLS=[datasource.PGT.AUDIT_CODE, datasource.PGT.CLIENT_NBR], OUTPUT_COLS=[datasource.PGT.AUDIT_CODE, datasource.PGT.CLIENT_NBR], EST_CARDINALITY=-1.0}) > Access(groups=[datasource.PGT], props={SOURCE_HINT=null, MODEL_ID=Schema name=datasource, nameInSource=null, uuid=mmuuid:a521401c-37c6-4d3c-909d-55599421a456, OUTPUT_COLS=[datasource.PGT.AUDIT_CODE, datasource.PGT.CLIENT_NBR], EST_CARDINALITY=-1.0}) > Source(groups=[datasource.PGT], props={VIRTUAL_COMMAND=EXEC datasource.PGT('XPO'), OUTPUT_COLS=[datasource.PGT.AUDIT_CODE, datasource.PGT.CLIENT_NBR], EST_COL_STATS={datasource.PGT.AUDIT_CODE=[-1.0, -1.0], datasource.PGT.CLIENT_NBR=[-1.0, -1.0]}, EST_CARDINALITY=-1.0}) > ============================================================================ > EXECUTING PlanSorts > AFTER: > Project(groups=[datasource.PGT]) > Access(groups=[datasource.PGT]) > Source(groups=[datasource.PGT]) > ============================================================================ > EXECUTING CollapseSource > AFTER: > Project(groups=[datasource.PGT]) > Access(groups=[datasource.PGT], props={SOURCE_HINT=null, MODEL_ID=Schema name=datasource, nameInSource=null, uuid=mmuuid:a521401c-37c6-4d3c-909d-55599421a456, OUTPUT_COLS=[datasource.PGT.AUDIT_CODE, datasource.PGT.CLIENT_NBR], EST_CARDINALITY=-1.0, ATOMIC_REQUEST=EXEC datasource.PGT('XPO')}) > ============================================================================ > CONVERTING PLAN TREE TO PROCESS TREE > PROCESS PLAN = > ProjectNode(0) output=[datasource.PGT.AUDIT_CODE, datasource.PGT.CLIENT_NBR] [datasource.PGT.AUDIT_CODE, datasource.PGT.CLIENT_NBR] > AccessNode(1) output=[datasource.PGT.AUDIT_CODE, datasource.PGT.CLIENT_NBR] EXEC datasource.PGT('XPO') > ============================================================================ > ---------------------------------------------------------------------------- > OPTIMIZATION COMPLETE: > PROCESSOR PLAN: > ProjectNode(0) output=[datasource.PGT.AUDIT_CODE, datasource.PGT.CLIENT_NBR] [datasource.PGT.AUDIT_CODE, datasource.PGT.CLIENT_NBR] > AccessNode(1) output=[datasource.PGT.AUDIT_CODE, datasource.PGT.CLIENT_NBR] EXEC datasource.PGT('XPO') > ============================================================================ > {code} > And here's the query that actually gets run. > {code} > select ServiceTier.datasource.PGT ('ABC') > org.teiid.runtime.client.TeiidClientException: org.teiid.api.exception.query.QueryResolverException: TEIID30068 The function 'ServiceTier.datasource.PGT('ABC')' is an unknown form. Check that the function name and number of arguments is correct. > Elapsed Time: 0 hr, 0 min, 0 sec, 18 ms. > {code} > The problem is "select ServiceTier.datasource.PGT ('ABC')" should be "exec ServiceTier.datasource.PGT ('ABC')". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2800) Add back New Child >>View option to the View Model

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2800?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2800. ---------------------------------- This was rejected by developers. Closing the JIRA. TD JIRA Clean up > Add back New Child >>View option to the View Model > -------------------------------------------------- > > Key: TEIIDDES-2800 > URL: https://issues.jboss.org/browse/TEIIDDES-2800 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling, Patch Release > Affects Versions: 9.0.3, 9.2 > Reporter: Debbie Steigner > Assignee: Barry LaFond > > RFE https://issues.jboss.org/browse/TEIID-4010 has been entered to differentiate table and view, so would like to have New View and Table option under View Model > New Child. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2806) Generate Dynamic VDB: Columns with non-standard characters end up in the resulting xml without quotes, resulting in a an undeployable vdb

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2806?page=com.atlassian.jira.plu... ] Matus Makovy closed TEIIDDES-2806. ---------------------------------- Duplicate of 2858. Closing. TD JIRA Clean up > Generate Dynamic VDB: Columns with non-standard characters end up in the resulting xml without quotes, resulting in a an undeployable vdb > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-2806 > URL: https://issues.jboss.org/browse/TEIIDDES-2806 > Project: Teiid Designer > Issue Type: Feature Request > Components: Dynamic VDBs, Patch Release > Affects Versions: 9.0.3, 9.2 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Fix For: 10.0.2 > > > The Teiid vdb has column named e.g. PE$HOME. When I generate a dynamic vdb xml from this model, the xml document contains: > CREATE FOREIGN TABLE MYTABLE ( > ID string(40) NOT NULL, > NAME string(40), > PE$HOME string(19) NOT NULL, > CONSTRAINT FKI_MY_VIEW PRIMARY KEY(ID) > ) > When i deploy this, it fails because P$HOME is not allowed as column name. > I expect to see this name "quoted" in the xml vdb: > CREATE FOREIGN TABLE MYTABLE ( > "ID" string(40) NOT NULL, > "NAME" string(40), > "PE$HOME" string(19) NOT NULL, > CONSTRAINT FKI_MY_VIEW PRIMARY KEY(ID) > ) > Proposed solution: always use "quotes" in source and view xml vdb, both for the column names, and the mapping statement. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues September 2016