[JBoss JIRA] (TEIID-2476) Exclude hidden columns from metadata
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2476:
-------------------------------------
Summary: Exclude hidden columns from metadata
Key: TEIID-2476
URL: https://issues.jboss.org/browse/TEIID-2476
Project: Teiid
Issue Type: Enhancement
Components: JDBC Driver, Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
We should offer or possibly default to filtering columns that can not accessed out of the user metadata. This could be done on the server side - however given the reuse we have of the system tables for example for materialized pg catalog queries - it seems better to add filters to the DatabaseMetadata (and ideally pg) metadata queries. On the server side we may still want to have alternative handling for resolving select star.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (TEIID-2475) The RelationalNode.collectNodeStats is only subtracting out the last node
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2475?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-2475.
-----------------------------------
Resolution: Done
updated the logic always compute the the processing time as cumulative minus the child times
> The RelationalNode.collectNodeStats is only subtracting out the last node
> -------------------------------------------------------------------------
>
> Key: TEIID-2475
> URL: https://issues.jboss.org/browse/TEIID-2475
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 6.0.0
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
> Fix For: 8.4
>
> Attachments: Query_Plan.txt
>
>
> The "Node Cumulative Next Batch Process Time" Statistic
> If you have a look at the explain plan (attached). Following the definition,
> the JoinNode Node Cumulative Next Batch Process Time: 565471. So, it is the summation of AccessNode (Node Process Time: 892860) + DependentAccessNode (Node Process Time: 439) + JoinNode (Node Process Time: 2203120). The summation does not agree.
> The RelationalNode.collectNodeStats looks wrong (it's effectively only subtracting out the last node)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (TEIID-2475) The RelationalNode.collectNodeStats is only subtracting out the last node
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2475?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2475:
----------------------------------
Fix Version/s: 8.4
Affects Version/s: 6.0.0
(was: 7.7.5)
> The RelationalNode.collectNodeStats is only subtracting out the last node
> -------------------------------------------------------------------------
>
> Key: TEIID-2475
> URL: https://issues.jboss.org/browse/TEIID-2475
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 6.0.0
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
> Fix For: 8.4
>
> Attachments: Query_Plan.txt
>
>
> The "Node Cumulative Next Batch Process Time" Statistic
> If you have a look at the explain plan (attached). Following the definition,
> the JoinNode Node Cumulative Next Batch Process Time: 565471. So, it is the summation of AccessNode (Node Process Time: 892860) + DependentAccessNode (Node Process Time: 439) + JoinNode (Node Process Time: 2203120). The summation does not agree.
> The RelationalNode.collectNodeStats looks wrong (it's effectively only subtracting out the last node)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (TEIID-2475) The RelationalNode.collectNodeStats is only subtracting out the last node
by Debbie Steigner (JIRA)
Debbie Steigner created TEIID-2475:
--------------------------------------
Summary: The RelationalNode.collectNodeStats is only subtracting out the last node
Key: TEIID-2475
URL: https://issues.jboss.org/browse/TEIID-2475
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.7.5
Reporter: Debbie Steigner
Assignee: Steven Hawkins
Attachments: Query_Plan.txt
The "Node Cumulative Next Batch Process Time" Statistic
If you have a look at the explain plan (attached). Following the definition,
the JoinNode Node Cumulative Next Batch Process Time: 565471. So, it is the summation of AccessNode (Node Process Time: 892860) + DependentAccessNode (Node Process Time: 439) + JoinNode (Node Process Time: 2203120). The summation does not agree.
The RelationalNode.collectNodeStats looks wrong (it's effectively only subtracting out the last node)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (TEIID-2475) The RelationalNode.collectNodeStats is only subtracting out the last node
by Debbie Steigner (JIRA)
[ https://issues.jboss.org/browse/TEIID-2475?page=com.atlassian.jira.plugin... ]
Debbie Steigner updated TEIID-2475:
-----------------------------------
Attachment: Query_Plan.txt
> The RelationalNode.collectNodeStats is only subtracting out the last node
> -------------------------------------------------------------------------
>
> Key: TEIID-2475
> URL: https://issues.jboss.org/browse/TEIID-2475
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 7.7.5
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
> Attachments: Query_Plan.txt
>
>
> The "Node Cumulative Next Batch Process Time" Statistic
> If you have a look at the explain plan (attached). Following the definition,
> the JoinNode Node Cumulative Next Batch Process Time: 565471. So, it is the summation of AccessNode (Node Process Time: 892860) + DependentAccessNode (Node Process Time: 439) + JoinNode (Node Process Time: 2203120). The summation does not agree.
> The RelationalNode.collectNodeStats looks wrong (it's effectively only subtracting out the last node)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (TEIID-2474) Deploying dynamic VDB with invalid XML will cause incomprehensible error
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2474?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2474:
---------------------------------------
This should probably be moved over to AS as this is their message. Do you see any Teiid related logs, such as a parse error with line/column?
> Deploying dynamic VDB with invalid XML will cause incomprehensible error
> ------------------------------------------------------------------------
>
> Key: TEIID-2474
> URL: https://issues.jboss.org/browse/TEIID-2474
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.3
> Reporter: Filip Nguyen
> Assignee: Steven Hawkins
> Priority: Trivial
> Attachments: loop-vdb.xml
>
>
> Deploying VDB with invalid XML (closed translator tag). Causes following error:
> [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015009: Scan found incompletely copied file content for deployment standalone/deployments/loop-vdb.xml. Deployment changes will not be processed until all content is complete.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (TEIID-2474) Deploying dynamic VDB with invalid XML will cause incomprehensible error
by Filip Nguyen (JIRA)
Filip Nguyen created TEIID-2474:
-----------------------------------
Summary: Deploying dynamic VDB with invalid XML will cause incomprehensible error
Key: TEIID-2474
URL: https://issues.jboss.org/browse/TEIID-2474
Project: Teiid
Issue Type: Bug
Reporter: Filip Nguyen
Assignee: Steven Hawkins
Priority: Minor
Attachments: loop-vdb.xml
Deploying VDB with invalid XML (closed translator tag). Causes following error:
[org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015009: Scan found incompletely copied file content for deployment standalone/deployments/loop-vdb.xml. Deployment changes will not be processed until all content is complete.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months