[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15406231#comment-15406231 ]
Chen Li commented on ASTERIXDB-1556: ------------------------------------ Understood. For (2), how does this spilling complicate the algorithm, since some data structures are now on the disk? For (3) choice 1) seems to be the ideal one, but I am open to other choices. Do you have any idea about how much time is needed to make these changes? We want to unblock the "fuzzy work" soon. Let's do a discussion when you are available. > 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)