- All versions, including delete-markers should be deleted before deleting a bucket.
- **Versioning feature is only available in erasure coded and distributed erasure coded setups**.

## How to configure versioning on a bucket

Each bucket created has a versioning configuration associated with it. By default bucket is unversioned as shown below

```

    private InetAddress witnessServer;
    private InetAddress serverAddress;

    @BeforeEach
    void setUp() throws Exception {
        witnessServer = InetAddress.getByName("192.168.1.200");
        serverAddress = InetAddress.getByName("192.168.1.100");

        // Setup mock configuration with lenient stubbing
        lenient().when(mockContext.getConfig()).thenReturn(mockConfig);

        for (int i = 0; i < expected.length; i++) {
            assertEquals("Array element at index " + i + " differs", expected[i], actual[i]);
        }
    }

    @Override
    public void setUp() throws Exception {
        super.setUp();
        crawlJob = new CrawlJob();
    }

    @Override
    public void tearDown() throws Exception {
        super.tearDown();
    }

    // Test constructor and field initialization

      - name: Configure JDK
        uses: actions/setup-java@v5
        with:
          distribution: 'zulu'
          java-version: 11

      - name: Configure JDK
        uses: actions/setup-java@v5
        with:
          distribution: 'zulu'
          java-version: 17

      - name: Setup Gradle
        uses: gradle/actions/setup-gradle@v4

      - name: Upload Artifacts

	chmod a+x "$FUNCTIONAL_TESTS"
}

function main() {
	echo "Testing in FS setup"
	if ! run_test_fs; then
		echo "FAILED"
		purge "$WORK_DIR"
		exit 1
	fi

	echo "Testing in Erasure setup"
	if ! run_test_erasure; then
		echo "FAILED"
		purge "$WORK_DIR"
		exit 1
	fi

	echo "Testing in Distributed Erasure setup"
	if ! run_test_dist_erasure; then
		echo "FAILED"
		purge "$WORK_DIR"

    private static final String TEST_SERVER = "server";
    private static final String TEST_ENDPOINT = "\\pipe\\test";

    @BeforeEach
    void setUp() throws IOException {
        // Setup mock behavior with lenient stubbing to avoid UnnecessaryStubbingException
        lenient().when(mockSmbNamedPipe.openPipe()).thenReturn(mockSmbPipeHandle);

public class ThumbnailGeneratorTest extends UnitFessTestCase {

    private ThumbnailGenerator thumbnailGenerator;

    @Override
    public void setUp() throws Exception {
        super.setUp();
        thumbnailGenerator = new ThumbnailGenerator();
    }

    @Override
    public void tearDown() throws Exception {
        super.tearDown();
    }

        env:
          GITHUB_CONTEXT: ${{ toJson(github) }}
        run: echo "$GITHUB_CONTEXT"
      - uses: actions/checkout@v5
      - uses: actions/setup-python@v5
        with:
          python-version: '3.9'
      - name: Setup uv
        uses: astral-sh/setup-uv@v6
        with:
          version: "0.4.15"
          enable-cache: true
          cache-dependency-glob: |
            requirements**.txt

            this.bytesRead = value;
        }

        public int getWordCount() {
            return wordCount;
        }
    }

    @BeforeEach
    void setUp() {
        MockitoAnnotations.openMocks(this);
        when(mockConfig.getPid()).thenReturn(12345);
    }

    @Nested
    @DisplayName("Constructor Tests")
    class ConstructorTests {

        @Test

Hay algunas diferencias:

* `table=True` le dice a SQLModel que este es un *modelo de tabla*, que debe representar una **tabla** en la base de datos SQL, no es solo un *modelo de datos* (como lo sería cualquier otra clase regular de Pydantic).

* `Field(primary_key=True)` le dice a SQLModel que `id` es la **clave primaria** en la base de datos SQL (puedes aprender más sobre claves primarias de SQL en la documentación de SQLModel).