[ 
https://issues.apache.org/jira/browse/TAJO-691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hyunsik Choi updated TAJO-691:
------------------------------

    Attachment: TAJO-691.patch

+1 for latest patch.

Thank you for your contribution. The patch looks good to me.

After hashCode of both VTuple and LazyTuple are changed, some non-determined 
query statements seem to result in different results. From your patch, I'll try 
to find more unit tests which potentially can cause the same problem. This 
patch contains more fixes of the cases that I found.

> HashJoin or HashAggregation is too slow if there is many unique keys
> --------------------------------------------------------------------
>
>                 Key: TAJO-691
>                 URL: https://issues.apache.org/jira/browse/TAJO-691
>             Project: Tajo
>          Issue Type: Improvement
>            Reporter: hyoungjunkim
>            Assignee: hyoungjunkim
>         Attachments: TAJO-691.patch, TAJO-691_2.patch
>
>
> HashJoin or HashAggregation is too slow if there is many unique keys.
> Java's native Map is inefficient  to handle many items. In case more than 1 
> million items in HashMap, Adding 10000 items takes more than 7 ~ 10 seconds.  
>  
> This should be improved.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to