- 
                Notifications
    
You must be signed in to change notification settings  - Fork 0
 
fix for fix #1
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
fix for fix #1
Conversation
| }), | ||
| Some(3), | ||
| vec![None, None, Some(2)], | ||
| vec![None, Some(2), Some(0)], | 
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.
I think the checked in answers are incorrect -- namely the first three items in the input are None, 0 and 2 and yet the output has two nulls in it.
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.
Is this passing? This looks wrong to me, the unoptimized order (ie /wo limit) would look like None, None, 2, 0, 0, -1, applying the limit: None, None, 2.
| if let Some(limit) = limit { | ||
| len = limit.min(len); | ||
| // count how many nulls are present in the limit | ||
| nulls_len = nulls.iter().filter(|&idx| *idx as usize <= limit).count(); | 
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.
Everything else in this function doesn't need to dig into the actual index values so something smells here to me. I thought the limit is applied to the sorted result so I don't know that comparing the limit to the indices is correct here.
| }), | ||
| Some(3), | ||
| vec![None, None, Some(2)], | ||
| vec![None, Some(2), Some(0)], | 
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.
Is this passing? This looks wrong to me, the unoptimized order (ie /wo limit) would look like None, None, 2, 0, 0, -1, applying the limit: None, None, 2.
| 
           I misunderstood the expected behavior. Sorry about that  | 
    
* Add ported Rust release verification script * Minor simplifications. (#1) Co-authored-by: Jorge Leitao <[email protected]>
* add parquet-fromcsv (#1) add command line tool for convert csv to parquet. * add `text` for non-rust documentation text * Update parquet/src/bin/parquet-fromcsv.rs Co-authored-by: Raphael Taylor-Davies <[email protected]> * Update parquet/src/bin/parquet-fromcsv.rs Co-authored-by: Raphael Taylor-Davies <[email protected]> * Update parquet/src/bin/parquet-fromcsv.rs Co-authored-by: Raphael Taylor-Davies <[email protected]> * Update parquet/src/bin/parquet-fromcsv.rs Co-authored-by: Raphael Taylor-Davies <[email protected]> * automate update help text * remove anyhow * add rat_exclude_files * update test_command_help * fix clippy warnings * add writer-version, max-row-group-size arg * fix cargo fmt lint Co-authored-by: Raphael Taylor-Davies <[email protected]>
Proposed modification for apache#236