You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Type coercion for binary operators forces UTF8View to Utf8 #13348
This is a cleanup ticket for #12212 which had introduced logic for regexp forcing coercion to Utf8 if any side had utf8View. This looks to have been done before #12180 landed which to my understanding should negate the need for this.
However, I think fixing regexp_match to support utf8View should likely land before the special handling code and tests introduced in #12212 is removed.
I think we have completed this issue now -- let's close it (and if it is not closed, perhaps we can file a ticket that explains the end user effect / reproducer so we can get it fixed)
Activity
jayzhan211 commentedon Nov 11, 2024
I think change the signature to TypeSignature::String can solve this issue. See #13301
jayzhan211 commentedon Nov 11, 2024
?regex_comparison_string_coercionis the same asstring_coercion, can we remove it and usestring_coercioninsteadI saw the comment 👍
alamb commentedon Mar 8, 2025
I think we have completed this issue now -- let's close it (and if it is not closed, perhaps we can file a ticket that explains the end user effect / reproducer so we can get it fixed)