April 2016 - teiid-designer-issues

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

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2811?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2811: ---------------------------------------- I do know the DataTools metamodel does not destinguish between a procedure and a UDF. The common construct is UDF, so not sure how or if we can make changes to affect how Teiid schema shows up in Data Source explorer. Thinking this just needs to be a known issue. As far as executing a procedure, steve's correct, the proper SQL is an EXEC statement because it's hitting the Teiid JDBC client. > 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)

10 years

1
0
0 / 0

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

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2815?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2815: ----------------------------------- Fix Version/s: 11.0 > 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 > Fix For: 11.0 > > 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)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2812) Add ability to reverse engineer into a Pojo object from a table or view

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2812?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2812: ----------------------------------- Fix Version/s: 10.0.2 > Add ability to reverse engineer into a Pojo object from a table or view > ----------------------------------------------------------------------- > > Key: TEIIDDES-2812 > URL: https://issues.jboss.org/browse/TEIIDDES-2812 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling, Usability > Affects Versions: 9.0.6 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 10.0.2 > > > The scenario is: select table/view, right mouse click select Create Pojo, present dialog, need a file chooser to select location to save output. > Label of action: Create Pojo (or something to indicates the process) > Dialog title: Create Pojo from Table [tableName] > Message: This will create a Pojo class, and packaged in a jar, that is meant to be used when JDG will be used in materialization or accessed as a data source. > Options: > - file chooser option to select folder to save pojo jar > - drop-down: <select option> > Access JDG in Library Mode > Access JDG via Hot Rod Client > - pojo package name (default = org.teiid.pojo) > - pojo jar name (default = pojo.jar) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2823) "Generate Dynamic VDB" utility should use correct property names

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2823?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2823: ----------------------------------- Fix Version/s: 10.0.1 > "Generate Dynamic VDB" utility should use correct property names > ---------------------------------------------------------------- > > Key: TEIIDDES-2823 > URL: https://issues.jboss.org/browse/TEIIDDES-2823 > Project: Teiid Designer > Issue Type: Bug > Components: Dynamic VDBs > Affects Versions: 9.2 > Reporter: Colin Mondesir > Fix For: 10.0.1 > > > When we generate a Dynamic VDB from a Multisource VDB the output contains: > <property name="supports-multi-source-bindings" value="true"/> > As far as I can see this is the old property name, I believe the designer to use the new "multisource" property name instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2823) "Generate Dynamic VDB" utility should use correct property names

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2823?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-2823: -------------------------------------- Assignee: Barry LaFond > "Generate Dynamic VDB" utility should use correct property names > ---------------------------------------------------------------- > > Key: TEIIDDES-2823 > URL: https://issues.jboss.org/browse/TEIIDDES-2823 > Project: Teiid Designer > Issue Type: Bug > Components: Dynamic VDBs > Affects Versions: 9.2 > Reporter: Colin Mondesir > Assignee: Barry LaFond > Fix For: 10.0.1 > > > When we generate a Dynamic VDB from a Multisource VDB the output contains: > <property name="supports-multi-source-bindings" value="true"/> > As far as I can see this is the old property name, I believe the designer to use the new "multisource" property name instead. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2830) The SOAP schema processor is not handling the ANY type element

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2830?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2830: ----------------------------------- Attachment: project-asmx.wsdl.zip > The SOAP schema processor is not handling the ANY type element > -------------------------------------------------------------- > > Key: TEIIDDES-2830 > URL: https://issues.jboss.org/browse/TEIIDDES-2830 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Environment: Windows 7 Pro > Eclipse Mars.2 > Java 8 x64 > Teiid Designer 10.0.0.Final-V20160413-1817-B4094 > Reporter: Jesse Shaffer > Attachments: project-asmx.wsdl.zip > > > As requested on the forum, I am raising an issue where the SOAP import tool is not giving me options to automatically add columns when trying to consume a Project Server 2010 WSDL. > For more information, see the forum thread here: https://developer.jboss.org/thread/269374 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2830) The SOAP schema processor is not handling the ANY type element

by Jesse Shaffer (JIRA)

Jesse Shaffer created TEIIDDES-2830: --------------------------------------- Summary: The SOAP schema processor is not handling the ANY type element Key: TEIIDDES-2830 URL: https://issues.jboss.org/browse/TEIIDDES-2830 Project: Teiid Designer Issue Type: Bug Components: Import/Export Environment: Windows 7 Pro Eclipse Mars.2 Java 8 x64 Teiid Designer 10.0.0.Final-V20160413-1817-B4094 Reporter: Jesse Shaffer As requested on the forum, I am raising an issue where the SOAP import tool is not giving me options to automatically add columns when trying to consume a Project Server 2010 WSDL. For more information, see the forum thread here: https://developer.jboss.org/thread/269374 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2829) Issues with generated dynamic VDB for preview

by Mark Drilling (JIRA)

Mark Drilling created TEIIDDES-2829: --------------------------------------- Summary: Issues with generated dynamic VDB for preview Key: TEIIDDES-2829 URL: https://issues.jboss.org/browse/TEIIDDES-2829 Project: Teiid Designer Issue Type: Bug Components: Dynamic VDBs Affects Versions: 10.0.1 Reporter: Mark Drilling Assignee: Barry LaFond Fix For: 10.0.1 Imported from SF then tried to preview the Accounts table. The generated dynamic VDB (attached) will not deploy. 1) 'Default value' property = Generated upon completion Results in following deployment error TEIID50036 VDB PREVIEW_SFModel_Account.1 model "SFModel" metadata failed to load. Reason:TEIID30386 org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered "NOT NULL DEFAULT [*]Generated[*] upon completion" at line 3, column 40. 2) includes FK defns which result in this: [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 3) TEIID31092 Foreign Key definition on view SFModel.Account points to non-existent table User_ on schema SFModel. Fully qualify the Reference Table name including the schema name. [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 3) TEIID31092 Foreign Key definition on view SFModel.Account points to non-existent table User_ on schema SFModel. Fully qualify the Reference Table name including the schema name. [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 3) TEIID31092 Foreign Key definition on view SFModel.Account points to non-existent table User_ on schema SFModel. Fully qualify the Reference Table name including the schema name. [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID40073 The metadata for the VDB PREVIEW_SFModel_Account.1 is loaded, however it is not valid. Check models for errors. Correct the metadata and re-deploy. [org.teiid.RUNTIME] (teiid-async-threads - 3) TEIID40003 VDB PREVIEW_SFModel_Account.1 is set to FAILED -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

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

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2800?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2800. ------------------------------------ Fix Version/s: (was: 10.0.2) (was: 9.0.7) Resolution: Rejected The Teiid Runtime defines source and view metadata. There are some legacy metamodel definitions in Teiid Designer (TABLE and VIEW) in source models that when deployed to the server, are treated as TABLES. So in Designer, the difference is just at design-time. New Teiid Tooling is now adapting to the DDL and VDB.XML metadata formats and CREATE VIEW only represents a virtual construct, where CREATE FOREIGN TABLE/PROCEDURE/FUNCTION are the only source-related schema objects. Adding this feature would complicate the current Teiid Designer and make it more difficult to transition to the simpler Teiid metadata structure and nomenclature. > 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)

10 years

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2825) After import DDL which contains GLOBAL TEMPORARY TABLE shows error

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2825?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2825. ------------------------------------ Resolution: Done 10.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/50ab31585903da937... > After import DDL which contains GLOBAL TEMPORARY TABLE shows error > ------------------------------------------------------------------ > > Key: TEIIDDES-2825 > URL: https://issues.jboss.org/browse/TEIIDDES-2825 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Patch Release, Transformations > Affects Versions: 10.0 > Environment: Fedora 23 > Reporter: Matej Kralik > Assignee: Barry LaFond > Fix For: 10.0.1 > > Attachments: viewModel.ddl > > > After I imported DLL file which contains GLOBAL TEMPORARY TABLE the designer shows me errors "The virtual table 'temp Table' does not have any associated transformation.". > I think that global temporary table doesn't have any sql transformation. > But when I open generated model and save it, the problem is resolved. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 April 2016