@Rocky does starrocks 4.1.7 support iceberg v3 deletion vectors

StarRocks 4.1.7 does not support Iceberg v3 deletion vectors. While StarRocks 4.1.x introduced significant Iceberg v3 features, the support for deletion vectors is currently limited. Key details regarding this support in version 4.1.7 include: * Unsupported Feature: According to recent release notes and technical documentation (as of late 2026), Iceberg v3 tables that utilize deletion vectors are explicitly rejected. Starting from version 4.1.1, queries against such tables will fail with an error message indicating the feature is unsupported, rather than ignoring the deletions and returning incorrect data. * Alternative Delete Mechanism: StarRocks 4.1.x supports native Iceberg

DELETE

operations, but it does so by producing standard v2 position delete files rather than v3 deletion vectors. * Other Iceberg v3 Support: Although deletion vectors are not supported, StarRocks 4.1.7 does support other Iceberg v3 capabilities, such as: * The

VARIANT

data type for semi-structured data. * Row Lineage (including the

_row_id

and

_last_updated_sequence_number

metadata columns). * Default column values. * Global late materialization for v3 tables. For production workloads requiring row-level deletes, StarRocks continues to rely on the Iceberg v2 position delete format. If you are using a tool that produces Iceberg data for StarRocks, it is recommended to configure it to write positional deletes instead of deletion vectors for compatibility. References • data_source/catalog/iceberg/DML.md • data_source/catalog/iceberg/iceberg_catalog.md • data_source/feature-support-data-lake-analytics.md • administration/management/monitoring/metrics.md • data_source/catalog/iceberg/DDL.md • data_source/catalog/iceberg/procedures.md

@Rocky give a starrocks query to get the number and size of deletion files for my iceberg table

To get the number and size of deletion files for an Iceberg table in StarRocks, you can query the Iceberg metadata tables using the

$files

or

$partitions

suffixes. Option 1: Detailed summary using the

$files

table This query provides a breakdown of the number of files and their total size for both position and equality deletes.

sql
SELECT 
    CASE content 
        WHEN 1 THEN 'Position Delete' 
        WHEN 2 THEN 'Equality Delete' 
    END AS delete_type,
    COUNT(*) AS file_count,
    SUM(file_size_in_bytes) AS total_size_bytes,
    ROUND(SUM(file_size_in_bytes) / 1024 / 1024, 2) AS total_size_mb
FROM <catalog_name>.<database_name>.<table_name>$files
WHERE content IN (1, 2)
GROUP BY content;

Option 2: Partition-level breakdown using the

$partitions

table If you want to see how many delete files exist per partition, use the

$partitions

metadata table.

sql
SELECT 
    partition_value,
    position_delete_file_count,
    equality_delete_file_count,
    record_count AS total_records_in_partition
FROM <catalog_name>.<database_name>.<table_name>$partitions;

Key to Metadata Fields: *

$files

table: * `content = 1`: Position Delete files. * `content = 2`: Equality Delete files. * `file_size_in_bytes`: The actual physical size of the delete file. *

$partitions

table: * `position_delete_file_count`: Number of position delete files in that partition. * `equality_delete_file_count`: Number of equality delete files in that partition. References • data_source/catalog/iceberg/iceberg_meta_table.md meta_table) References • data_source/catalog/iceberg/iceberg_meta_table.md • administration/management/monitoring/metrics.md • data_source/feature-support-data-lake-analytics.md • data_source/catalog/iceberg/DML.md