/** The key of the configuration. e.g. url */
    String INDEX_FIELD_URL = "index.field.url";

    /** The key of the configuration. e.g. doc_id */
    String INDEX_FIELD_doc_id = "index.field.doc_id";

    /** The key of the configuration. e.g. _id */
    String INDEX_FIELD_ID = "index.field.id";

    /** The key of the configuration. e.g. _version */

labels.userInfo=Informações do usuário
labels.webApiJson=Resposta JSON
labels.webConfigName=Nome da configuração de rastreamento da web
labels.allLanguages=Todos os idiomas
labels.dictId=ID do dicionário
labels.docId=ID do documento
labels.endTime=Hora de término
labels.hq=hq
labels.inputs=Entradas
labels.jobLogging=Logging
labels.jobName=Nome
labels.jobStatus=Estado
labels.labelTypeIds=Rótulos
labels.lang=Idioma

labels.threadName=スレッド名
labels.url=URL
labels.userFavorite=お気に入りログ
labels.userInfo=利用者情報
labels.webApiJson=JSONレスポンス
labels.webConfigName=ウェブクロール設定名
labels.allLanguages=すべての言語
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=品詞

         * element anymore. Otherwise, when we remove from the old iterator, we may be invalidating
         * the new one. The result is a ConcurrentModificationException or other bad behavior.
         *
         * (If we decide that we really, really hate allocating two Iterators per cycle instead of
         * one, we can optimistically store the new Iterator and then be willing to throw it out if
         * the user calls remove().)
         */

 * by it and by its input steps.
 *
 * <h3>Ending a pipeline</h3>
 *
 * Each {@code ClosingFuture} pipeline must be ended. To end a pipeline, decide whether you want to
 * close the captured objects automatically or manually.
 *
 * <h4>Automatically closing</h4>
 *
 * You can extract a {@link Future} that represents the result of the last step in the pipeline by

from being positioned outside the boundary.\n   *\n   * A scenario exists where the reference itself is not within the boundaries.<br />\n   * We can say it has \"escaped the boundaries\" — or just \"escaped\".<br />\n   * In this case we need to decide whether the popper should either:\n   *\n   * - detach from the reference and remain \"trapped\" in the boundaries, or\n   * - if it should ignore the boundary and \"escape with its reference\"\n   *\n   * When `escapeWithReference` is set to`true`...

 * by it and by its input steps.
 *
 * <h3>Ending a pipeline</h3>
 *
 * Each {@code ClosingFuture} pipeline must be ended. To end a pipeline, decide whether you want to
 * close the captured objects automatically or manually.
 *
 * <h4>Automatically closing</h4>
 *
 * You can extract a {@link Future} that represents the result of the last step in the pipeline by

    /** The key of the message: Dictionary ID */
    public static final String LABELS_DICT_ID = "{labels.dictId}";

    /** The key of the message: Document ID */
    public static final String LABELS_DOC_ID = "{labels.docId}";

    /** The key of the message: End Time */
    public static final String LABELS_END_TIME = "{labels.endTime}";

    /** The key of the message: hq */
    public static final String LABELS_HQ = "{labels.hq}";

* PodDisruptionBudget now uses ControllerRef to decide which controller owns a given Pod, so it doesn't get confused by controllers with overlapping selectors. ([#45003](https://github.com/kubernetes/kubernetes/pull/45003), [@krmayankk](https://github.com/krmayankk))

Before this change, the default `admin.conf` was bound to `system:masters` Group, which was undesired. Executing `kubeadm init phase kubeconfig all` or just `kubeadm init` will now generate the new `super-admin.conf` file. The cluster admin can then decide to keep the file present on a node host or move it to a safe location. `kubadm certs renew` will renew the certificate in `super-admin.conf` to one year if the file exists; if it does not exist a "MISSING" note will be printed. `kubeadm upgrade apply`...