binary_to_string_coercion in binary.rs does not support utf8view

[Omega359]

Describe the bug

The coercion rules defined in binary_to_string_coercion do not account for utf8view

To Reproduce

No response

Expected behavior

binary coercion rules support utf8view

Additional context

No response

[alamb]

i double checked and binary_to_string_coercion already suports Utf8View so closing this issue

datafusion/datafusion/expr-common/src/type_coercion/binary.rs

Lines 1232 to 1247 in 11435de

	use arrow::datatypes::DataType::*;
	match (lhs_type, rhs_type) {
	(Binary, Utf8) => Some(Utf8),
	(Binary, LargeUtf8) => Some(LargeUtf8),
	(BinaryView, Utf8) => Some(Utf8View),
	(BinaryView, LargeUtf8) => Some(LargeUtf8),
	(LargeBinary, Utf8) => Some(LargeUtf8),
	(LargeBinary, LargeUtf8) => Some(LargeUtf8),
	(Utf8, Binary) => Some(Utf8),
	(Utf8, LargeBinary) => Some(LargeUtf8),
	(Utf8, BinaryView) => Some(Utf8View),
	(LargeUtf8, Binary) => Some(LargeUtf8),
	(LargeUtf8, LargeBinary) => Some(LargeUtf8),
	(LargeUtf8, BinaryView) => Some(LargeUtf8),
	_ => None,
	}

[alamb]

I see now that @jonathanc-n proposes some additions in

• feat: Support Utf8View for get_wider_type + binary_to_string_coercion functions #13370 (comment)

However I am not sure how important those cases are to cover (how common they are in practice). So I propose closing this ticket as "good enough" unless someone hits them for real.

Funnily enough while verifying the tests I found one small corner case;

• Fully support LIKE/ILIKE with Utf8View #14379

[alamb]

Let's reopen this ticket if we find any additional work to do -- I think it is closed enough in #14379