diff --git a/deploy-manage/security/httprest-clients-security.md b/deploy-manage/security/httprest-clients-security.md index 5cd346bff..9164f7e6d 100644 --- a/deploy-manage/security/httprest-clients-security.md +++ b/deploy-manage/security/httprest-clients-security.md @@ -83,7 +83,7 @@ es-secondary-authorization: ApiKey <1> For more information about using {{security-features}} with the language specific clients, refer to: -* [Java](elasticsearch-java://reference/_basic_authentication.md) +* [Java](elasticsearch-java://reference/setup/connecting.md) * [JavaScript](elasticsearch-js://reference/connecting.md) * [.NET](elasticsearch-net://reference/configuration.md) * [Perl](https://metacpan.org/pod/Search::{{es}}::Cxn::HTTPTiny#CONFIGURATION) diff --git a/manage-data/ingest/ingesting-data-from-applications/ingest-data-with-nodejs-on-elasticsearch-service.md b/manage-data/ingest/ingesting-data-from-applications/ingest-data-with-nodejs-on-elasticsearch-service.md index 798c80ae9..14aa1273c 100644 --- a/manage-data/ingest/ingesting-data-from-applications/ingest-data-with-nodejs-on-elasticsearch-service.md +++ b/manage-data/ingest/ingesting-data-from-applications/ingest-data-with-nodejs-on-elasticsearch-service.md @@ -304,7 +304,7 @@ Security Connections ({{ech}} only) -: If your application connecting to {{ech}} runs under the Java security manager, you should at least disable the caching of positive hostname resolutions. To learn more, check the [Java API Client documentation](elasticsearch-java://reference/_others.md). +: If your application connecting to {{ech}} runs under the Java security manager, you should at least disable the caching of positive hostname resolutions. To learn more, check the [Java API Client documentation](elasticsearch-java://reference/transport/rest5-client/config/others.md). Schema : When the example code was run an index mapping was created automatically. The field types were selected by {{es}} based on the content seen when the first record was ingested, and updated as new fields appeared in the data. It would be more efficient to specify the fields and field types in advance to optimize performance. Refer to the Elastic Common Schema documentation and Field Type documentation when you are designing the schema for your production use cases. diff --git a/troubleshoot/elasticsearch/elasticsearch-client-java-api-client/error-no-such-method.md b/troubleshoot/elasticsearch/elasticsearch-client-java-api-client/error-no-such-method.md index 9962665f3..94858824d 100644 --- a/troubleshoot/elasticsearch/elasticsearch-client-java-api-client/error-no-such-method.md +++ b/troubleshoot/elasticsearch/elasticsearch-client-java-api-client/error-no-such-method.md @@ -15,7 +15,7 @@ This method was introduced in `elasticsearch-rest-client` version 7.16.0. The er This happens in particular when the project is using the [Spring Boot Maven Plugin](https://docs.spring.io/spring-boot/docs/current/maven-plugin/reference/htmlsingle/), as this plugin [defines versions for commonly used libraries](https://github.com/spring-projects/spring-boot/blob/main/spring-boot-project/spring-boot-dependencies/build.gradle), including `elasticsearch-rest-client`. Depending on the version of Spring Boot used in the project, that version may be outdated. -To solve this issue, you have to add the `elasticsearch-rest-client` dependency explicitly in your project, with the same version as `elasticsearch-java` (see also [Installation](elasticsearch-java://reference/installation.md)). +To solve this issue, you have to add the `elasticsearch-rest-client` dependency explicitly in your project, with the same version as `elasticsearch-java` (see also [Installation](elasticsearch-java://reference/setup/installation.md)). Using Gradle: