delta-io/delta

[Kernel][Testing] Run more write test suites using the V2 builders

Open

#5,092 opened on Aug 16, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Scala (8,807 stars) (2,100 forks)batch import
enhancementgood first issuekernel

Description

Feature request

Which Delta project/connector is this regarding?

  • Spark
  • Standalone
  • Flink
  • Kernel
  • Other (fill in here)

Overview

Currently we run DeltaTableWritesSuite and TablePropertiesSuite with both the V1 and V2 builders. We should run more test suites (all?) that use WriteUtils with the V2 builders as well.

Potentially blocked by #5090

Willingness to contribute

The Delta Lake Community encourages new feature contributions. Would you or another member of your organization be willing to contribute an implementation of this feature?

  • Yes. I can contribute this feature independently.
  • Yes. I would be willing to contribute this feature with guidance from the Delta Lake community.
  • No. I cannot contribute this feature at this time.

Contributor guide

Tech stack
scala
Domain
testingbackend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Familiarity with Delta Kernel testingBasic knowledge of Scala and Spark
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
The issue asks to run additional write test suites (like DeltaTableWritesSuite and TablePropertiesSuite) with V2 builders. Start by examining the existing tests that use WriteUtils and identify which are currently only run with V1 builders. Look at the references in the issue body and check if issue #5090 is resolved. Then, modify the test configurations to include V2 builders for those suites, potentially following the pattern of the already updated suites. Ensure that the new tests pass without regressions.