But when using `Item` for output, for a response body, `tags` is always
                available because it has a default value, even if it's just an empty
                list. So, the client should be able to always expect it.

                In this case, there would be two different schemas, one for input and
                another one for output.

                Read more about it in the

labels.docId=Dokument-ID
labels.endTime=Endzeit
labels.hq=hq
labels.inputs=Eingaben
labels.jobLogging=Protokollierung
labels.jobName=Name
labels.jobStatus=Status
labels.labelTypeIds=Labels
labels.lang=Sprache
labels.outputs=Ausgaben
labels.pos=Wortart
labels.purgeJobLogDay=Alte Jobprotokolle löschen
labels.purgeUserInfoDay=Alte Benutzerprotokolle löschen
labels.reading=Lesen
labels.roleTypeIds=Rollen-IDs
labels.scriptData=Skript

labels.docId=ID dokumentu
labels.endTime=Godzina zakończenia
labels.hq=hq
labels.inputs=Wejścia
labels.jobLogging=Logowanie
labels.jobName=Nazwa
labels.jobStatus=Status
labels.labelTypeIds=Etykiety
labels.lang=Język
labels.outputs=Wyjścia
labels.pos=Część mowy
labels.purgeJobLogDay=Usuń poprzednie dzienniki zadań
labels.purgeUserInfoDay=Usuń poprzednie dzienniki użytkowników
labels.reading=Odczyt
labels.roleTypeIds=ID roli

labels.docId=Belge ID
labels.endTime=Bitiş Zamanı
labels.hq=hq
labels.inputs=Girdiler
labels.jobLogging=Günlükleme
labels.jobName=Ad
labels.jobStatus=Durum
labels.labelTypeIds=Etiketler
labels.lang=Dil
labels.outputs=Çıktılar
labels.pos=Sözcük Türü
labels.purgeJobLogDay=Eski iş günlüklerini sil
labels.purgeUserInfoDay=Eski kullanıcı günlüklerini sil
labels.reading=Okuma
labels.roleTypeIds=Rol ID'leri
labels.scriptData=Betik

}

// OutputLocation specifies bucket where object needs to be restored
type OutputLocation struct {
	S3 S3Location `xml:"S3,omitempty"`
}

// IsEmpty returns true if output location not specified.
func (o *OutputLocation) IsEmpty() bool {
	return o.S3.BucketName == ""
}

// SelectParameters specifies sql select parameters
type SelectParameters struct {
	s3select.S3Select
}

			wantColumns:     []string{"header1", "header2", "header3"},
			wantFields:      "ok1,ok2,ok3\n" + `"a""""b",c` + "\n",
			wantErr:         io.EOF,
		},
		{
			// This works since LazyQuotes is true, but output is very weird.
			file:            "invalid-oddquote.csv",
			recordDelimiter: "\n",
			fieldDelimiter:  ",",
			sendErr:         nil,
			header:          true,

labels.dictId=字典ID
labels.docId=文檔ID
labels.endTime=結束時間
labels.hq=hq
labels.inputs=輸入
labels.jobLogging=日誌記錄
labels.jobName=名稱
labels.jobStatus=狀態
labels.labelTypeIds=標籤
labels.lang=語言
labels.outputs=輸出
labels.pos=詞性
labels.purgeJobLogDay=刪除以前的作業日誌
labels.purgeUserInfoDay=刪除以前的使用者日誌
labels.reading=讀音
labels.roleTypeIds=角色ID
labels.scriptData=腳本
labels.scriptResult=結果
labels.scriptType=執行方法

   *
   * <p>If the mapped elements contain duplicates (according to {@code comparator}), the first
   * occurrence in encounter order appears in the resulting multiset, with count equal to the sum of
   * the outputs of {@code countFunction.applyAsInt(t)} for each {@code t} mapped to that element.
   *
   * @since 33.2.0 (available since 22.0 in guava-jre)
   */

- Fix a panic when using invalid output format in kubectl create secret command ([#107346](https://github.com/kubernetes/kubernetes/pull/107346), [@rikatz](https://github.com/rikatz)) [SIG CLI]

- `kubectl auth reconcile` now outputs details about what changes are being made ([#71564](https://github.com/kubernetes/kubernetes/pull/71564), [@liggitt](https://github.com/liggitt))