[JBoss JIRA] (TEIIDDES-2833) Select all when assigning object permissions
by Steve Tran (JIRA)
Steve Tran created TEIIDDES-2833:
------------------------------------
Summary: Select all when assigning object permissions
Key: TEIIDDES-2833
URL: https://issues.jboss.org/browse/TEIIDDES-2833
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
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)
8 years
[JBoss JIRA] (TEIIDDES-2832) Unable to preview - connection-jndi-name is null in dynamic vdb
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2832?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2832:
----------------------------------------
The SF import wizard needs to add the same "Edit JNDI Name" panel on one of it's pages. (see JDBC, File .. etc. Import wizards).
This wizard should set the JNDI name on the model.
YOu could also work-around it by using the "Set JBoss JNDI Name" action on the model and re-try preview
> Unable to preview - connection-jndi-name is null in dynamic vdb
> ---------------------------------------------------------------
>
> Key: TEIIDDES-2832
> URL: https://issues.jboss.org/browse/TEIIDDES-2832
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs
> Affects Versions: 10.0.2
> Reporter: Mark Drilling
> Assignee: Barry LaFond
> Attachments: server.log
>
>
> Import from salesforce using SF importer, then attempt to preview Account table, results in the attached server.log exception.
> The dynamic VDB content:
> <vdb name="PREVIEW-f118338c-1837-4973-ae81-61092ac55eb9" version="1">
> <description>Importer VDB</description>
> <property name="UseConnectorMetadata" value="true" />
> <property name="deployment-name" value="PREVIEW-f118338c-1837-4973-ae81-61092ac55eb9-vdb.xml" />
> <model name="SFModel" type="PHYSICAL" visible="true">
> <source name="SFModel" translator-name="salesforce" connection-jndi-name="null" />
> <metadata type="DDL"><![CDATA[
> CREATE FOREIGN TABLE Account (
> Id string(18) NOT NULL OPTIONS(NAMEINSOURCE 'Id', NATIVE_TYPE 'id', "teiid_sf:Defaulted on Create" 'TRUE'),
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years
[JBoss JIRA] (TEIIDDES-2832) Unable to preview - connection-jndi-name is null in dynamic vdb
by Mark Drilling (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2832?page=com.atlassian.jira.plu... ]
Mark Drilling updated TEIIDDES-2832:
------------------------------------
Attachment: server.log
> Unable to preview - connection-jndi-name is null in dynamic vdb
> ---------------------------------------------------------------
>
> Key: TEIIDDES-2832
> URL: https://issues.jboss.org/browse/TEIIDDES-2832
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs
> Affects Versions: 10.0.2
> Reporter: Mark Drilling
> Assignee: Barry LaFond
> Attachments: server.log
>
>
> Import from salesforce using SF importer, then attempt to preview Account table, results in the attached server.log exception.
> The dynamic VDB content:
> <vdb name="PREVIEW-f118338c-1837-4973-ae81-61092ac55eb9" version="1">
> <description>Importer VDB</description>
> <property name="UseConnectorMetadata" value="true" />
> <property name="deployment-name" value="PREVIEW-f118338c-1837-4973-ae81-61092ac55eb9-vdb.xml" />
> <model name="SFModel" type="PHYSICAL" visible="true">
> <source name="SFModel" translator-name="salesforce" connection-jndi-name="null" />
> <metadata type="DDL"><![CDATA[
> CREATE FOREIGN TABLE Account (
> Id string(18) NOT NULL OPTIONS(NAMEINSOURCE 'Id', NATIVE_TYPE 'id', "teiid_sf:Defaulted on Create" 'TRUE'),
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years
[JBoss JIRA] (TEIIDDES-2832) Unable to preview - connection-jndi-name is null in dynamic vdb
by Mark Drilling (JIRA)
Mark Drilling created TEIIDDES-2832:
---------------------------------------
Summary: Unable to preview - connection-jndi-name is null in dynamic vdb
Key: TEIIDDES-2832
URL: https://issues.jboss.org/browse/TEIIDDES-2832
Project: Teiid Designer
Issue Type: Bug
Components: Dynamic VDBs
Affects Versions: 10.0.2
Reporter: Mark Drilling
Assignee: Barry LaFond
Import from salesforce using SF importer, then attempt to preview Account table, results in the attached server.log exception.
The dynamic VDB content:
<vdb name="PREVIEW-f118338c-1837-4973-ae81-61092ac55eb9" version="1">
<description>Importer VDB</description>
<property name="UseConnectorMetadata" value="true" />
<property name="deployment-name" value="PREVIEW-f118338c-1837-4973-ae81-61092ac55eb9-vdb.xml" />
<model name="SFModel" type="PHYSICAL" visible="true">
<source name="SFModel" translator-name="salesforce" connection-jndi-name="null" />
<metadata type="DDL"><![CDATA[
CREATE FOREIGN TABLE Account (
Id string(18) NOT NULL OPTIONS(NAMEINSOURCE 'Id', NATIVE_TYPE 'id', "teiid_sf:Defaulted on Create" 'TRUE'),
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years
[JBoss JIRA] (TEIIDDES-2831) Vdb conversion should exclude model 'checksum' and 'index' properties
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2831?page=com.atlassian.jira.plu... ]
Paul Richardson reassigned TEIIDDES-2831:
-----------------------------------------
Assignee: Paul Richardson
> Vdb conversion should exclude model 'checksum' and 'index' properties
> ---------------------------------------------------------------------
>
> Key: TEIIDDES-2831
> URL: https://issues.jboss.org/browse/TEIIDDES-2831
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 10.0
> Reporter: Paul Richardson
> Assignee: Paul Richardson
> Fix For: 10.0
>
>
> Conversion of an xmi vdb to a dynamic vdb simply copies all properties contained in models. However, this includes both the 'checksum' and 'indexName' properties which are not applicable to dynamic vdbs. Worse still this is counter-productive since the Dynamic Vdb Sequencers in Komodo actually use the 'indexName' property to determine if the model is Declarative or not, excluding those models with the property present.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years
[JBoss JIRA] (TEIIDDES-2831) Vdb conversion should exclude model 'checksum' and 'index' properties
by Paul Richardson (JIRA)
Paul Richardson created TEIIDDES-2831:
-----------------------------------------
Summary: Vdb conversion should exclude model 'checksum' and 'index' properties
Key: TEIIDDES-2831
URL: https://issues.jboss.org/browse/TEIIDDES-2831
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 10.0
Reporter: Paul Richardson
Fix For: 10.0
Conversion of an xmi vdb to a dynamic vdb simply copies all properties contained in models. However, this includes both the 'checksum' and 'indexName' properties which are not applicable to dynamic vdbs. Worse still this is counter-productive since the Dynamic Vdb Sequencers in Komodo actually use the 'indexName' property to determine if the model is Declarative or not, excluding those models with the property present.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years
[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 commented on TEIIDDES-2823:
----------------------------------------
This was changed appears to have been made back in June 2013 for the Teiid 8.4 release
> "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)
8 years
[JBoss JIRA] (TEIIDDES-2829) Issues with generated dynamic VDB for preview
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2829?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2829.
------------------------------------
Resolution: Done
10.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/75627899f86660843...
fixed default value and FK issues
> 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)
8 years
[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 resolved TEIIDDES-2811.
------------------------------------
Resolution: Won't Do
> 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)
8 years