Possible Arrow Float64 <=> DuckDB FLOAT mapping bug

[ctsk]

As far as I understand....

I believe Arrow's DataType::Float64 should be mapped to DuckDB's DOUBLE -- and DataType::Float32 is DuckDB's FLOAT.

duckdb-rs/crates/duckdb/src/types/mod.rs

Lines 119 to 121 in 1096461

	// DataType::Float16 => Self::Float16,
	// DataType::Float32 => Self::Float32,
	DataType::Float64 => Self::Float,

Is it a bug that this snippet is mapping DataType::Float64 to FLOAT?

[ctsk]

How I got here:

• I wanted to store embeddings in a duckdb database -- These embeddings are a Vec<f32>, and represented as FLOAT[<DIM>] in the database
• Storing a Value::Array(Vec<f32>) in the database failed due to an unimplemented! code path here
  

  duckdb-rs/crates/duckdb/src/types/value_ref.rs

  Lines 354 to 356 in 1096461

  	Value::List(..) | Value::Struct(..) | Value::Map(..) | Value::Array(..) | Value::Union(..) => {
  	unimplemented!()
  	}

• I then converted my representation into a FixedSizeListArray, aiming to pass ValueRef::Array(&FixedSizeListArray, usize) as a parameter to execute and hit the unimplemented! code path for DataType::Float32 in the issue above...