就和宣告查詢參數時一樣，當模型屬性有預設值時，它就不是必填；否則就是必填。使用 `None` 可使其成為選填。

例如，上述模型對應的 JSON「`object`」（或 Python `dict`）如下：

```JSON
{
    "name": "Foo",
    "description": "An optional description",
    "price": 45.2,
    "tax": 3.5
}
```

...由於 `description` 與 `tax` 是選填（預設為 `None`），以下這個 JSON「`object`」也有效：

```JSON
{
    "name": "Foo",
    "price": 45.2
}
```

## 將它宣告為參數 { #declare-it-as-a-parameter }

 * based on these entries.
 * <p>
 * To fully understand the information exposed by this class a description
 * of the access check algorithm used by Windows is required. The following
 * is a basic description of the algorithm. For a more complete description
 * we recommend reading the section on Access Control in Keith Brown's
 * "The .NET Developer's Guide to Windows Security" (which is also

レスポンスの content type は `application/jsonl`（`application/json` の代わり）となり、ボディは次のようになります:

```json
{"name": "Plumbus", "description": "A multi-purpose household device."}
{"name": "Portal Gun", "description": "A portal opening device."}
{"name": "Meeseeks Box", "description": "A box that summons a Meeseeks."}
```

 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

plugins {
    `kotlin-dsl`
}

description = "Provides plugin for configuring default settings plugins"

group = "gradlebuild"

dependencies {
    implementation(buildLibs.develocityPlugin)
    implementation(buildLibs.develocityConventions)

---
- job:
    name: elastic+elasticsearch+%BRANCH%+periodic+platform-support
    display-name: "elastic / elasticsearch # %BRANCH% - platform support"
    description: "Testing of the Elasticsearch %BRANCH% branch platform support tests.\n"
    project-type: multijob
    node: master
    vault: []
    scm:
      - git:
          wipe-workspace: false
    builders:
      - multijob:
          name: Packaging tests
          projects:

import model.Stage

class CompileAll(
    model: CIBuildModel,
    stage: Stage,
) : OsAwareBaseGradleBuildType(os = Os.LINUX, stage = stage, init = {
        id(buildTypeId(model))
        name = "Compile All"
        description = "Compiles all production/test source code and warms up the build cache"

        features {
            publishBuildStatusToGithub(model)
        }

        applyDefaults(
            model,
            this,

                                        <label for="attributes.description" class="col-sm-3 text-sm-right col-form-label"><la:message
                                                key="labels.user_description"/></label>
                                        <div class="col-sm-9">
                                            <la:errors property="attributes.description"/>

```Python hl_lines="3  5"
{
    "name": "Bar",
    "description": "The bartenders",
    "price": 62,
    "tax": 20.2
}
```

这些值将包含在响应中。

#### 具有与默认值相同值的数据 { #data-with-the-same-values-as-the-defaults }

如果数据具有与默认值相同的值，例如 ID 为 `baz` 的项：

```Python hl_lines="3  5-6"
{
    "name": "Baz",
    "description": None,
    "price": 50.2,
    "tax": 10.5,
    "tags": []
}

---
- job:
    name: elastic+elasticsearch+%BRANCH%+multijob+platform-support-unix
    display-name: "elastic / elasticsearch # %BRANCH% - unix compatibility"
    description: "Elasticsearch %BRANCH% unix compatibility testing.\n"
    project-type: matrix
    node: master
    scm:
      - git:
          wipe-workspace: false
    axes:
      - axis:
          type: label-expression
          name: os
          values:

Upcoming Jobs

- Copy objects from NAS to MinIO
- Copy objects from HDFS to MinIO

## Replication Job
To perform replication via batch jobs, you create a job. The job consists of a job description YAML that describes

- Source location from where the objects must be copied from
- Target location from where the objects must be copied to