[
https://issues.apache.org/jira/browse/ASTERIXDB-2800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17243508#comment-17243508
]
ASF subversion and git services commented on ASTERIXDB-2800:
------------------------------------------------------------
Commit 92c0a1633958ff35877490dba1b9d747903a8c70 in asterixdb's branch
refs/heads/master from Shiva
[ https://gitbox.apache.org/repos/asf?p=asterixdb.git;h=92c0a16 ]
[ASTERIXDB-2800] Added exception for in-mem join
- user model changes: no
- storage format changes: no
- interface changes: no
Details:
- Exception is thrown if the record insertion in
hash table of the in-memory hash join fails after
compacting it.
Change-Id: I37e4b7209b5e9e31b9082f0ad04fbe611354da5f
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/9045
Integration-Tests: Jenkins <[email protected]>
Reviewed-by: Michael Blow <[email protected]>
Tested-by: Michael Blow <[email protected]>
> Hash join should deal/check if re-inserting a tuple in hash table fails
> -----------------------------------------------------------------------
>
> Key: ASTERIXDB-2800
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2800
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: RT - Runtime
> Affects Versions: 0.9.3
> Reporter: Ali Alsuliman
> Priority: Major
> Fix For: 0.9.7
>
>
> During the build phase of InMemoryHashJoin, we insert the incoming tuples in
> the hash table (in build()). If at one point, we could not insert a tuple,
> then we compact the hash table and try inserting the tuple again. However, we
> don't check if this second try succeeded or not.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
