Skip to content

Why is the default value of write.metadata.delete-after-commit.enabled set to false? #13330

Open
@lintingbin

Description

@lintingbin

Query engine

Flink,Spark,Trino

Question

What are the benefits of the default value of write.metadata.delete-after-commit.enabled being false? Setting it to false will leave many useless files on the object storage, so why not set its default value to true?
Why is write.metadata.previous-versions-max configured as 100? It feels like keeping 10 files would be enough.
Is there any special meaning behind the configuration of these two parameters?

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions