Skip to content

Conversation

@zanmato1984
Copy link
Contributor

@zanmato1984 zanmato1984 commented Dec 31, 2024

Rationale for this change

See #45135

What changes are included in this PR?

Remove the useless states.

Are these changes tested?

Existing tests suffice.

Are there any user-facing changes?

None.

@zanmato1984
Copy link
Contributor Author

Pretty straightforward cleanup. cc @pitrou @kou @westonpace @mapleFU

if (!local_states_[thread_index].hash_table_ready) {
local_states_[thread_index].hash_table_ready = hash_table_ready_.load();
}
ARROW_DCHECK(local_states_[thread_index].hash_table_ready);
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Upper level logic

bool hash_table_ready_ = false;
guarantees the readiness of the hash table by calling the interfaces (impl_->BuildHashTable and impl_->ProbeSingleBatch) in sequence so we don't actually have to do it all over.

@github-actions github-actions bot added awaiting committer review Awaiting committer review and removed awaiting review Awaiting review labels Dec 31, 2024
Copy link
Member

@kou kou left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

They were introduced by GH-13493 and GH-13332. They might not know that both of them have the "hash table ready" state.

@github-actions github-actions bot added awaiting merge Awaiting merge and removed awaiting committer review Awaiting committer review labels Dec 31, 2024
@zanmato1984 zanmato1984 merged commit 1df4889 into apache:main Dec 31, 2024
35 of 39 checks passed
@zanmato1984 zanmato1984 removed the awaiting merge Awaiting merge label Dec 31, 2024
@zanmato1984 zanmato1984 deleted the remove-hash-table-ready branch December 31, 2024 14:38
@conbench-apache-arrow
Copy link

After merging your PR, Conbench analyzed the 4 benchmarking runs that have been run so far on merge-commit 1df4889.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 2 possible false positives for unstable benchmarks that are known to sometimes produce them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants