[
https://issues.apache.org/jira/browse/TAJO-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14357991#comment-14357991
]
ASF GitHub Bot commented on TAJO-1383:
--------------------------------------
Github user jihoonson commented on the pull request:
https://github.com/apache/tajo/pull/404#issuecomment-78411489
@jinossy thanks for your comment. It is very helpful.
I left some comments for descriptions on classes and a variable.
If a table is broadcasted, it seems that all tasks in a node share the same
cache. It would be great if you can give detailed descriptions on this cache
mechanism.
Thanks!
> 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
> Labels: performance
> 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)
