Uh oh!
There was an error while loading. Please reload this page.
Change default SQL mapping for VARCAHR from Utf8 to Utf8View - #16142
Conversation
zhuqi-lucas
commented
May 22, 2025
Interesting, sqllogic testing successfully for my local mac but CI failed... |
6ee857a to
0780263Comparezhuqi-lucas
commented
May 26, 2025
Resolved all problems now including the slt testing. I think the PR is ready for benchmark progress to see if switching to Utf8View by default slows some queries down. cc @alamb Thanks a lot. |
alamb
commented
May 27, 2025
🤖 |
alamb
commented
May 27, 2025
THanks @zhuqi-lucas -- I have started it up |
alamb
commented
May 27, 2025
🤖: Benchmark completed Details |
zhuqi-lucas
commented
May 27, 2025
Thank you @alamb , it seems no regression from the benchmark result! |
5d9c537 to
e54e432Compare
alamb
left a comment
There was a problem hiding this comment.
Thank you @zhuqi-lucas -- this is great
FYI @jayzhan211 , @timsaucer@xudong963 and @comphead
I have a few suggestions on how to simplify the examples which would be nice to get in prior to merge but I don't think it is needed
| // Assuming the input columns are | ||
| // column[0]: customer_id / UTF8 | ||
| // column[0]: customer_id / UTF8 or UTF8View |
There was a problem hiding this comment.
I feel like the example would be simpler if it just used Utf8View. Could we do that and avoid adding the logic to handle both types?
There was a problem hiding this comment.
Good suggestion! Thank you @alamb , addressed in latest PR.
| # specific language governing permissions and limitations | ||
| # under the License. | ||
| # Currently, the avro not support Utf8View type, so we disable the map_varchar_to_utf8view |
There was a problem hiding this comment.
There appears to be an update of parquet-testing with unrelated content, but I think it is ok to update it too
| // Ensure the column names and types match the target table | ||
| df = df.with_column_renamed("column1", "tablecol1").unwrap(); | ||
| df = df |
There was a problem hiding this comment.
I think it would be better if we could change the example to maybe just use a StringViewArray in the first place (rather than have to cast it here)
There was a problem hiding this comment.
Good suggestion! Thank you @alamb , addressed in latest PR.
VARCAHR from Utf8 to Utf8Viewzhuqi-lucas
commented
May 28, 2025
Thank you @alamb for review, i also addressed the suggestions about example in latest PR. |
alamb
commented
May 28, 2025
I'll plan to merge this tomorrow unless I hear anything different |
e7243d4 to
9195b6aComparexudong963
commented
May 29, 2025
I'm reviewing |
zhuqi-lucas
commented
May 29, 2025
Thank you @xudong963 for review! |
xudong963
commented
May 30, 2025
Let's go, thank you all |
alamb
commented
May 30, 2025
Thanks again @zhuqi-lucas and @xudong963 I have also made a PR to add a mention of this change to the upgrade guide: |
Which issue does this PR close?
Rationale for this change
Setting Varchar default mapping to utf8view, and change testing result.
What changes are included in this PR?
Setting Varchar default mapping to utf8view, and change testing result.
Are these changes tested?
Yes, new testing/slt testing result generated.
Are there any user-facing changes?
No, the internal datatype will change to utf8view.