-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Minor: Encapsulate LeftJoinData
into a struct (rather than anonymous enum) and add comments
#8153
Conversation
LeftJoinData
into a struct (rather than anonymous enum)
LeftJoinData
into a struct (rather than anonymous enum)LeftJoinData
into a struct (rather than anonymous enum) and add comments
@Dandandan or @metesynnada I wonder if you might have time to review this (I am in the process of working on #8130 and am trying to encode my findings in comments) |
@@ -73,7 +73,47 @@ use datafusion_physical_expr::EquivalenceProperties; | |||
use ahash::RandomState; | |||
use futures::{ready, Stream, StreamExt, TryStreamExt}; | |||
|
|||
type JoinLeftData = (JoinHashMap, RecordBatch, MemoryReservation); | |||
/// HashTable and input data for the left (build side) of a join | |||
struct JoinLeftData { |
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.
The idea is just to document the fields better by using names rather than .0
, .1
, etc
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.
lgtm, thanks @alamb
Thank you @alamb |
Which issue does this PR close?
Related to #8130
Rationale for this change
I am going through this code to understand what is happening, and one thing I think would help would be to use names to refer to fields rather than
data.0
,data.1
, and that could be commentedWhat changes are included in this PR?
JoinData
non pubLeftJoinData
a struct with named fields and accessorsAre these changes tested?
Existing tests
Are there any user-facing changes?
No, this is entirely internal code refactoring