- **Elasticsearch / OpenSearch** - Direct data migration via bulk APIs
- **Apache Solr** - Document import via REST API
- **Database Systems** - Direct connection via DataStore plugins
- **File Systems** - SMB, FTP, local file crawling
- **Custom Systems** - REST API for bulk document indexing

---

## Pre-Migration Planning

### 1. Assessment Phase

   * of the same class. For example, if sublists of {@code MyList} instances were serializable,
   * those sublists might implement a private {@code MySubList} type but serialize as a plain {@code
   * MyList} to save space. So long as {@code MyList} has all the public supertypes of {@code
   * MySubList}, this is safe. For these cases, for which {@code reserializeAndAssert} is too
   * strict, use {@link #reserialize}.

									</li>
								</c:when>
								<c:when test="${ pageLoginLink }">
									<li class="nav-item"><la:link href="/login" styleClass="nav-link" role="button" aria-haspopup="true"
											aria-expanded="false"
										>
											<i class="fa fa-fw fa-sign-in" aria-hidden="true"></i>
											<la:message key="labels.login" />
										</la:link></li>
								</c:when>
							</c:choose>

labels.check_url=URLを確認してください。
labels.busy_title=一時的に利用できません
labels.busy_message=サーバーが混雑しています。しばらくしてから再度お試しください。
labels.user_name=ユーザー名
labels.login=ログイン
labels.login.placeholder_username=ユーザー名
labels.login.placeholder_password=パスワード
labels.login.title=ログイン
labels.index_label=ラベル
labels.index_lang=優先する言語
labels.index_sort=ソート
labels.index_num=表示件数
labels.logout_title=ログアウト
labels.logout=ログアウト

`users` 및 `items`에 대한 태그 예시로 시도해 보겠습니다.

태그에 대한 메타데이터를 생성하고 이를 `openapi_tags` 매개변수로 전달하세요:

{* ../../docs_src/metadata/tutorial004_py310.py hl[3:16,18] *}

설명 안에 마크다운을 사용할 수 있다는 점에 유의하세요. 예를 들어 "login"은 굵게(**login**) 표시되고, "fancy"는 기울임꼴(_fancy_)로 표시됩니다.

/// tip | 팁

사용 중인 모든 태그에 메타데이터를 추가할 필요는 없습니다.

///

### 태그 사용 { #use-your-tags }

`tags` 매개변수를 *경로 처리* (및 `APIRouter`)와 함께 사용하여 이를 서로 다른 태그에 할당하세요:

## Context

[Gradle properties](https://docs.gradle.org/current/userguide/build_environment.html#sec:gradle_configuration_properties)
are flags that allow build engineers to opt into and out of features of Gradle Runtime or Core Plugins.
Practically every Gradle feature is behind a flag, and additional sub-flags or options provide further control.

The number of existing Gradle properties is already in the double digits. More properties will be added in the future.

* ressources
* fournisseurs
* services
* injectables
* composants

## Plug-ins **FastAPI** { #fastapi-plug-ins }

    win_def_file = ":tensorflow_filtered_def_file",
)

# To avoid duplication, check that the C++ or python library does not depend on
# the stream executor cuda plugins. Targets that want to use cuda APIs should
# instead depend on the dummy plugins in //tensorflow/compiler/xla/tsl/platform/default/build_config
# and use header only targets.
# TODO(ddunleavy): This seems completely broken. :tensorflow_cc depends on

    return delegate().get(key, valueLoader);
  }

  /**
   * @since 11.0
   */
  @Override
  /*
   * <? extends Object> is mostly the same as <?> to plain Java. But to nullness checkers, they
   * differ: <? extends Object> means "non-null types," while <?> means "all types."
   */
  public ImmutableMap<K, V> getAllPresent(Iterable<? extends Object> keys) {

		config.Net.SASL.SCRAMClientGeneratorFunc = func() sarama.SCRAMClient { return &XDGSCRAMClient{HashGeneratorFcn: KafkaSHA256} }
		config.Net.SASL.Mechanism = sarama.SASLMechanism(sarama.SASLTypeSCRAMSHA256)
	default:
		// default to PLAIN
		config.Net.SASL.Mechanism = sarama.SASLMechanism(sarama.SASLTypePlaintext)
	}
}

// KafkaSHA256 is a function that returns a crypto/sha256 hasher and should be used