You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2014/09/03 09:47:51 UTC
[jira] [Commented] (TAJO-1017) TajoConf misuses read & write locks
in some functions
[ https://issues.apache.org/jira/browse/TAJO-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119510#comment-14119510 ]
ASF GitHub Bot commented on TAJO-1017:
--------------------------------------
GitHub user mhthanh opened a pull request:
https://github.com/apache/tajo/pull/130
TAJO-1017: TajoConf misuses read & write locks in some functions
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mhthanh/tajo Tajo-1017
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/130.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 #130
----
commit 919812d4fe6debdcdcb45860635f89e73a758d4b
Author: mhthanh <ma...@gmail.com>
Date: 2014-09-03T07:40:50Z
Fixed misused locks in TajoConf
----
> TajoConf misuses read & write locks in some functions
> -----------------------------------------------------
>
> Key: TAJO-1017
> URL: https://issues.apache.org/jira/browse/TAJO-1017
> Project: Tajo
> Issue Type: Bug
> Reporter: Mai Hai Thanh
> Priority: Trivial
>
> In TajoConf, {{setCurrentTimeZone}} and {{setDateOrder}} are using {{readLock}} for concurrency control although {{writeLock}} should be used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)