Skip to content

Commit a167f4b

Browse files
committed
[test](regression) Define bucket key for Paimon metadata fixture
### What problem does this PR solve? Issue Number: close apache#66816 Related PR: apache#67207 Problem Summary: The Paimon file metadata regression fixture configured one bucket without a bucket key. The external regression environment rejects bucketed append tables without a bucket key before the metadata assertions run. Define the id column as the bucket key while preserving the two-append, cross-file row-location scenario. ### Release note None ### Check List (For Author) - Test: Regression test - External Regression build 1035528 reproduced the fixture failure; git diff --check passed - Behavior changed: No - Does this need documentation: No
1 parent 2cf14a4 commit a167f4b

1 file changed

Lines changed: 5 additions & 1 deletion

File tree

‎regression-test/suites/external_table_p0/paimon/test_paimon_file_metadata_columns.groovy‎

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,11 @@ suite("test_paimon_file_metadata_columns", "p0,external") {
7979
create database if not exists paimon.db1;
8080
drop table if exists paimon.db1.${crossFileTable};
8181
create table paimon.db1.${crossFileTable} (id int, payload string)
82-
using paimon tblproperties ('bucket'='1', 'file.format'='parquet');
82+
using paimon tblproperties (
83+
'bucket'='1',
84+
'bucket-key'='id',
85+
'file.format'='parquet'
86+
);
8387
insert into paimon.db1.${crossFileTable} values
8488
(1, 'first-1'), (2, 'first-2'), (3, 'first-3');
8589
insert into paimon.db1.${crossFileTable} values

0 commit comments

Comments
 (0)