[ARROW-11845] [Rust] Debug implementation of Date32Array panics if array contains negative values

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.0.0, 4.0.0
• Fix Version/s: 4.0.0
• Component/s: Rust
• Labels: newbie pull-request-available
• External issue URL: https://github.com/apache/arrow/issues/27692
• Assignee: Eric Burden
• Reporter: Eric Burden
• Created: 02/Mar/21 22:16
• Updated: 11/Jan/23 08:22
• Resolved: 05/Mar/21 21:55

Description

Attempting to print `Date32Array`s (and probably all Date/Time/Timestamp array types) using Rust's debug print format macro (`println!("{:?}", date_32_array")`) causes a panic, as shown in the minimum reproducible example below:

 

Invocation:

 

fn date32_print_panic() {        
    let mut date_32_builder = Date32Builder::new(1);
    date_32_builder.append_value(-50).unwrap();
    let date_32_array = date_32_builder.finish();
    println!("{:?}", date_32_array);
}

 

Result:

PrimitiveArray<Date32>
[
thread 'demo::tests::date32_print_panic' panicked at 'called `Option::unwrap()` on a `None` value', /home/.../rust/arrow/src/array/array_primitive.rs:226:54
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Issue Links

• links to: GitHub Pull Request #9624