[
https://issues.apache.org/jira/browse/TRAFODION-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16723854#comment-16723854
]
ASF GitHub Bot commented on TRAFODION-3250:
-------------------------------------------
GitHub user mashengchen opened a pull request:
https://github.com/apache/trafodion/pull/1764
[TRAFODION-3250] optimize get/set schema
push down setSchema() to server side, now it will be set in server side.
getSchema() will get value from outContext, and it will not do a tcp request
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mashengchen/trafodion TRAFODION-3250
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafodion/pull/1764.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1764
----
commit c212cdd61284b30d65ebe692e0f878417c918955
Author: Aven <shengchen.ma@...>
Date: 2018-12-18T09:19:21Z
[TRAFODION-3250] optimize get/set schema
----
> it's slow in using preparedstmt cache by jdbc
> ---------------------------------------------
>
> Key: TRAFODION-3250
> URL: https://issues.apache.org/jira/browse/TRAFODION-3250
> Project: Apache Trafodion
> Issue Type: Bug
> Components: client-jdbc-t4
> Affects Versions: 2.4
> Reporter: mashengchen
> Assignee: mashengchen
> Priority: Major
> Fix For: 2.4
>
>
> when set maxStatements_ > 0 , it will open preparedstmt cache function. then
> I open trafci 'using timing' function, and do prepare s from select * from
> tbl, it cost much time than i close preparedstmt cache.
> the reason is when get pstmt from cache, it will do a network connection to
> get current schema name, while it has already been cache in local.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
