Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Add a Tip to LOOKUP JOIN about rhs memory limits

Description

Would be nice to include something about LOOKUP JOIN to ephasize that the rhs must fit into memory on every node.

for example:

If your job is spilling to disk or if you get
“error: 1301: Pool memory exhausted: pool id 4194667 exhausted, requested 1 heap(1216/4294967295) global(1216/1216) (in Lookup Join”

It means the RHS is too big and lookup join should not be used…

Conclusion

None

Activity

Show:
Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Components

Assignee

Reporter

Priority

Fix versions

Pull Request URL

Created June 27, 2017 at 3:55 PM
Updated July 12, 2017 at 3:15 PM
Resolved July 12, 2017 at 3:15 PM