Currently our hash table support is scattered in several places:
-
compute/kernels/hash.cc
-
util/hash.h and util/hash.cc
-
builder.cc (in the DictionaryBuilder implementation)
Perhaps we should have something like a type-parametered hash table class (perhaps backed by non-owned memory) with several primitives:
-
decide allocation size for a given number of items
-
lookup an item
-
insert an item
-
decide whether resizing is needed
-
resize to a new memory area
-
...
Reporter: Antoine Pitrou / @pitrou
Assignee: Antoine Pitrou / @pitrou
Related issues:
PRs and other links:
Note: This issue was originally created as ARROW-2653. Please see the migration documentation for further details.
Currently our hash table support is scattered in several places:
compute/kernels/hash.ccutil/hash.handutil/hash.ccbuilder.cc(in the DictionaryBuilder implementation)Perhaps we should have something like a type-parametered hash table class (perhaps backed by non-owned memory) with several primitives:
decide allocation size for a given number of items
lookup an item
insert an item
decide whether resizing is needed
resize to a new memory area
...
Reporter: Antoine Pitrou / @pitrou
Assignee: Antoine Pitrou / @pitrou
Related issues:
PRs and other links:
Note: This issue was originally created as ARROW-2653. Please see the migration documentation for further details.