[
https://issues.apache.org/jira/browse/TAJO-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14643906#comment-14643906
]
ASF GitHub Bot commented on TAJO-1715:
--------------------------------------
GitHub user jihoonson opened a pull request:
https://github.com/apache/tajo/pull/658
TAJO-1715: Precompute the hash value of various kinds of ids
Changes are:
* Statically maintaining the hash value in TaskId and TaskAttemptId
* This is because, unlike QueryId and ExecutionBlockId, it is expected
there are many tasks and their attempts.
* Improving TupleMap.put()
* Copying tuple is expensive, so I implemented the clone() method for
KeyTuple.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jihoonson/tajo-2 TAJO-1715
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/658.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 #658
----
commit 6c44a72990c2177f669c76472dbde87fe81366ba
Author: Jihoon Son <[email protected]>
Date: 2015-07-28T06:08:15Z
TAJO-1715
----
> Precompute the hash value of various kinds of ids
> -------------------------------------------------
>
> Key: TAJO-1715
> URL: https://issues.apache.org/jira/browse/TAJO-1715
> Project: Tajo
> Issue Type: Improvement
> Reporter: Jihoon Son
> Assignee: Jihoon Son
> Priority: Minor
> Fix For: 0.11.0
>
>
> QueryId, ExecutionBlockId, TaskId, and TaskAttemptId are used for key of
> HashMap. Statically maintaining hash value will improve the performance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
