-
Notifications
You must be signed in to change notification settings - Fork 1k
Refactor key remapping #21041
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Refactor key remapping #21041
Conversation
- Rename key_remapping class to join_factorizer for clarity - Update all file names from key_remapping to join_factorizer - Rename enum compute_metrics to factorizer_metrics (YES/NO → ENABLE/DISABLE) - Update sentinel constants: KEY_REMAP_* to FACTORIZE_* - Rename methods: remap_*_keys() to factorize_*_keys() - Update Java classes: KeyRemapping to JoinFactorizer - Update all CMakeLists.txt and build files - Apply clang-format
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
| // for the join type selection heuristic, either way) | ||
| cudf::key_remapping remap( | ||
| cudf::join_factorizer remap( | ||
| build_keys, NullEquality, cudf::compute_metrics::NO, cudf::get_default_stream()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do you want to change build_keys here to right_keys as well?
| } | ||
|
|
||
| // Left with values 0-99 (all exist) and 100-104 (don't exist) | ||
| std::vector<int32_t> probe_data; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should this with left_data?
| // Build with struct{INT32, STRING} | ||
| column_wrapper<int32_t> build_child1{1, 2, 3}; | ||
| strcol_wrapper build_child2{"a", "b", "c"}; | ||
| auto build_struct = cudf::test::structs_column_wrapper{{build_child1, build_child2}}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same type of comment here, not sure if the idea to make these build/probe names all consistent.
Description
Checklist