[
https://issues.apache.org/jira/browse/TAJO-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14354171#comment-14354171
]
ASF GitHub Bot commented on TAJO-1383:
--------------------------------------
GitHub user jinossy opened a pull request:
https://github.com/apache/tajo/pull/404
TAJO-1383: Improve broadcast table cache
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jinossy/tajo TAJO-1383
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/404.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 #404
----
commit fabf69400df28e4badf283c1c3dd5f393fba2364
Author: jhkim <[email protected]>
Date: 2015-03-10T02:47:38Z
TAJO-1383: Improve broadcast table cache
----
> Improve broadcast table cache
> -----------------------------
>
> Key: TAJO-1383
> URL: https://issues.apache.org/jira/browse/TAJO-1383
> Project: Tajo
> Issue Type: Improvement
> Components: physical operator
> Affects Versions: 0.8.0, 0.9.0, 0.10
> Reporter: Jinho Kim
> Assignee: Jinho Kim
> Attachments: TAJO-1383.patch
>
>
> Currently, broadcast implementation keep a tuples on scan operator and It
> create a duplicated table cache in memory.
> We should improve it
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
