[
https://issues.jboss.org/browse/TEIID-2365?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-2365.
-----------------------------------
Fix Version/s: 8.5
Resolution: Done
Gave this a second look. We had already been using the string pool when setting output
names, so that is why there didn't seem to be much difference with not setting the
values altogether. However ultimately the change ended up being straight-forward by using
the QueryMetadataInterface as the stateful mechanism to control whether output names are
used. Also moved the resolver switch to find short names to be on the QMI rather than a
static/threadlocal construct.
Reduce the usage of output names on the server side
---------------------------------------------------
Key: TEIID-2365
URL:
https://issues.jboss.org/browse/TEIID-2365
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Minor
Fix For: 8.5
Parsed objects retain much of the original parse string, which is generally unnecessary
on the server side. The use of output names should reduced to unnecessary memory
consumption.
--
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