[
https://issues.apache.org/jira/browse/TRAFODION-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16473314#comment-16473314
]
ASF GitHub Bot commented on TRAFODION-2821:
-------------------------------------------
Github user xiaozhongwang commented on a diff in the pull request:
https://github.com/apache/trafodion/pull/1562#discussion_r187754295
--- Diff: core/sqf/src/tm/tmtransaction.cpp ---
@@ -797,7 +797,7 @@ short TM_Transaction::status(short *pp_status)
return iv_last_error;
}
- if (!gv_tmlib.is_initialized())
+ if (!gv_tmlib_initialized)
--- End diff --
as same as before.
I understand this code, dirty read before lock, but this is initializing
step, performance is not important, it's hard to maintain.
> Trafodion core code base needs to be thread safe
> -------------------------------------------------
>
> Key: TRAFODION-2821
> URL: https://issues.apache.org/jira/browse/TRAFODION-2821
> Project: Apache Trafodion
> Issue Type: Improvement
> Components: sql-general
> Affects Versions: any
> Reporter: Selvaganesan Govindarajan
> Assignee: Selvaganesan Govindarajan
> Priority: Major
> Fix For: 2.3
>
>
> This is the covering trafodion jira to make trafodion core code base to be
> thread safe. It is needed to ensure that type T2 JDBC driver hosted on
> platform can be enabled to support multi-threaded JDBC applications.
> [TRAFODION-2783] is one such case.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
