new String[] { SuggestConstants.DEFAULT_ROLE }, null, SuggestItem.Kind.DOCUMENT);

        // First write without update
        writer.write(runner.client(), suggester.settings(), suggester.getIndex(), new SuggestItem[] { item }, false);
        runner.refresh();

        // Second write with update=true
        SuggestItem updatedItem = new SuggestItem(new String[] { "テスト" }, readings, new String[] { "content" }, 3, 0, -1,

import org.dbflute.optional.OptionalEntity;

import jakarta.annotation.Resource;

/**
 * Service class for managing job logs in the Fess application.
 * Provides functionality to create, read, update, and delete job log entries,
 * as well as manage job status and perform cleanup operations.
 */
public class JobLogService {

    /**
     * Behavior class for job log database operations.
     */
    @Resource

     * configured update policy.
     *
     * @return {@code true} if remote repositories should be re-checked for updated artifacts/metadata, {@code false}
     *         otherwise.
     */
    boolean isForceUpdate();

    /**
     * Enables/disabled forced checks for updated artifacts/metadata on remote repositories.
     *

                <details>
                  <summary>
                    If change was made on the `release` branch but hasn't yet been published to the baseline version, update the baseline version:
                    <span class="btn btn-info" role="button">Update baseline</span>
                  </summary>
                  <div class="well">

        echo "### You can start fess service by executing"
        echo " sudo service fess start"

    elif command -v update-rc.d >/dev/null; then
        echo "### NOT starting on installation, please execute the following statements to configure fess service to start automatically using chkconfig"
        echo " sudo update-rc.d fess defaults 95 10"
        echo "### You can start fess service by executing"
        echo " sudo /etc/init.d/fess start"

        doInsert(entity, null);
    }

    public void update(WebConfig entity) {
        doUpdate(entity, null);
    }

    public void update(WebConfig entity, RequestOptionCall<IndexRequestBuilder> opLambda) {
        entity.asDocMeta().indexOption(opLambda);
        doUpdate(entity, null);
    }

    public void insertOrUpdate(WebConfig entity) {

        doInsert(entity, null);
    }

    public void update(FileAuthentication entity) {
        doUpdate(entity, null);
    }

    public void update(FileAuthentication entity, RequestOptionCall<IndexRequestBuilder> opLambda) {
        entity.asDocMeta().indexOption(opLambda);
        doUpdate(entity, null);
    }

    public void insertOrUpdate(FileAuthentication entity) {

```

### Upgrading the Chart

You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values using the command:

```bash
helm get values my-release > old_values.yaml
```

Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using

```bash
helm upgrade -f old_values.yaml my-release minio/minio

        String childName = "file1.txt";

        // Initial update - should mark as changed
        entry.updateChild(childName, 1024L, 1000L, false, 0x20, 500L, 800L);
        assertTrue(entry.hasChanges());

        // Clear changes to test next scenario
        entry.markComplete();
        assertFalse(entry.hasChanges());

        // Update with same values - should not mark as changed (no actual change)

    }

    /**
     * Update the port in sitemaps files after the server has started.
     * This is needed when using port 0 (random port) because the actual port
     * is not known until the server starts.
     */
    public void updateSitemapsPort() {
        final int actualPort = getPort();
        try {
            // Update sitemaps.xml