[
https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15405183#comment-15405183
]
Taewoo Kim edited comment on ASTERIXDB-1556 at 8/3/16 2:17 AM:
---------------------------------------------------------------
At this moment, I'm wondered how [~javierjia] implemented "the memory-bounded
HashGroupby and HashJoin for BigObject". Specifically, how the memory-bounded
part is implemented. [~javierjia]: can you give me the big picture of the
following change? How do we allocate memory to the operators? I mean, how do we
make it memory-bounded?
https://asterix-gerrit.ics.uci.edu/#/c/398/
was (Author: wangsaeu):
At this moment, I'm wondered how [~javierjia] implemented "the memory-bounded
HashGroupby and HashJoin for BigObject". Specifically, how the memory-bounded
part is implemented. [~javierjia]: can you give me the big picture of the
following change? How do we allocate memory to the operators?
https://asterix-gerrit.ics.uci.edu/#/c/398/
> Prefix-based multi-way Fuzzy-join generates an exception.
> ---------------------------------------------------------
>
> Key: ASTERIXDB-1556
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1556
> Project: Apache AsterixDB
> Issue Type: Bug
> Reporter: Taewoo Kim
> Assignee: Taewoo Kim
> Attachments: 2wayjoin.pdf, 2wayjoin.rtf, 2wayjoinplan.rtf,
> 3wayjoin.pdf, 3wayjoin.rtf, 3wayjoinplan.rtf
>
>
> When we enable prefix-based fuzzy-join and apply the multi-way fuzzy-join ( >
> 2), the system generates an out-of-memory exception.
> Since a fuzzy-join is created using 30-40 lines of AQL codes and this AQL is
> translated into massive number of operators (more than 200 operators in the
> plan for a 3-way fuzzy join), it could generate out-of-memory exception.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
