asterixdb-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Taewoo Kim (JIRA)" <j...@apache.org>
Subject [jira] [Created] (ASTERIXDB-1910) "Can't allocate one more frame. Assign more memory to InMemoryHashJoin. [HyracksDataException]" during a similarity join
Date Fri, 12 May 2017 00:28:04 GMT
Taewoo Kim created ASTERIXDB-1910:
-------------------------------------

             Summary: "Can't allocate one more frame. Assign more memory to InMemoryHashJoin.
[HyracksDataException]" during a similarity join
                 Key: ASTERIXDB-1910
                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1910
             Project: Apache AsterixDB
          Issue Type: Bug
            Reporter: Taewoo Kim


This happens on the fuzzy-join branch.

Currently, "inmem x, y" hint tells the system that x is the maximum number of output frames
and y is the maximum number of tuples that it will generate. This hint can be put on order
by (sort) operator. 

This information will be propagated via Project, Exchange, Running Aggregate operators as
the logical properties. When conducting a fuzzy-join, we have a "inmem" hint on the order
operator and this logical property generates the above exception since a "left outer join"
logical operator in the plan becomes a physical in-memory hash join operator because of this
logical property propagation. 

And during the actual in-memory hash join, it complains that it can't allocate more frames
because the data size is large.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message