}

    /**
     * Gets the message ID.
     *
     * @return the message ID
     */
    public String getId() {
        return id;
    }

    /**
     * Sets the message ID.
     *
     * @param id the message ID
     */
    public void setId(final String id) {
        this.id = id;
    }

    /**
     * Gets the message role.
     *

            existingIds.add(execution.getId());
        }

        String base = "default-" + goal;
        String id = base;

        for (int index = 1; existingIds.contains(id); index++) {
            id = base + '-' + index;
        }

        return id;
    }

    static class GoalSpec {

        String groupId;

        String artifactId;

        String version;

```

...那是因為用戶端產生器對每個 *路徑操作* 都使用 OpenAPI 內部的**操作 ID（operation ID）**。

OpenAPI 要求每個操作 ID 在所有 *路徑操作* 之間必須唯一，因此 FastAPI 會用**函式名稱**、**路徑**與 **HTTP 方法/操作**來產生該操作 ID，如此便能確保操作 ID 的唯一性。

接下來我會示範如何把它變得更好看。🤓

## 自訂 Operation ID 與更好的方法名稱 { #custom-operation-ids-and-better-method-names }

你可以**修改**這些操作 ID 的**產生方式**，讓它們更簡潔，並在用戶端中得到**更簡潔的方法名稱**。

在這種情況下，你需要用其他方式確保每個操作 ID 都是**唯一**的。

         <vendor>sun</vendor>
         <!-- no id, so it's considered 'default' -->
     </provides>
     <configuration>
        <jdkHome>${env.JAVA_HOME}</jdkHome>
     </configuration>
  </toolchain>
  <toolchain>
     <type>jdk</type>
     <provides>
         <version>1.7</version>
         <vendor>ibm</vendor>
         <id>ibm_17</id>
     </provides>
     <configuration>

  <version>1.0.0-SNAPSHOT</version>

  <repositories>
    <repository>
      <id>repo</id>
      <url>file://${basedir}/target/remote-repo</url>
    </repository>
    <repository>
      <id>repo-project-basedir</id>
      <url>file://${project.basedir}/sdk/maven/repo</url>
    </repository>
    <repository>
      <id>repo-project-baseUri</id>
      <url>${project.baseUri}/sdk/maven/repo</url>
    </repository>
  </repositories>

<?xml version="1.0"?>
<assembly>
	<id>targz</id>
	<formats>
		<format>tar.gz</format>
	</formats>

	<includeBaseDirectory>false</includeBaseDirectory>

	<componentDescriptors>
		<componentDescriptor>src/main/assemblies/common-bin.xml
		</componentDescriptor>
	</componentDescriptors>

  }

  private static final class ThrowingTearDown implements TearDown {

    private final String id;
    boolean ran = false;

    ThrowingTearDown(String id) {
      this.id = id;
    }

    @Override
    public void tearDown() throws Exception {
      ran = true;
      throw new RuntimeException(id);
    }
  }

  private static final class SimpleTearDown implements TearDown {

        assertObjectNotNull("id", id);
        return newConditionBean().acceptPK(id);
    }

    protected <ENTITY extends FileConfig> OptionalEntity<ENTITY> doSelectOptionalByPK(String id, Class<? extends ENTITY> tp) {
        return createOptionalEntity(doSelectByPK(id, tp), id);
    }

    @Override
    protected Class<? extends FileConfig> typeOfSelectedEntity() {
        return FileConfig.class;
    }

	echo "BUG: ILM expiry rules tags not replicated to 'siteb'"
	exit 1
fi

## Check edit of ILM expiry rule and its replication
id=$(./mc ilm rule list sitea/bucket --json | jq '.config.Rules[] | select(.Expiration.Days==3) | .ID' | sed 's/"//g')
./mc ilm edit --id "${id}" --expire-days "100" sitea/bucket
sleep 30s

count1=$(./mc ilm rule list sitea/bucket --json | jq '.config.Rules[0].Expiration.Days')

// This function currently supports
// - SIPMOD
func sipHashMod(key string, cardinality int, id [16]byte) int {
	if cardinality <= 0 {
		return -1
	}
	// use the faster version as per siphash docs
	// https://github.com/dchest/siphash#usage
	k0, k1 := binary.LittleEndian.Uint64(id[0:8]), binary.LittleEndian.Uint64(id[8:16])
	sum64 := siphash.Hash(k0, k1, []byte(key))
	return int(sum64 % uint64(cardinality))
}