Merge pull request #265326 from seesharprun/cosmos-archive-java-spark-v2

Cosmos DB | Retire `articles/cosmos-db/sdk-java-spark-v2.md`

Author: v-shils

articles/cosmos-db/includes/cosmos-db-sdk-list.md

@@ -15,7 +15,6 @@ ms.date: 09/28/2022
 > * [Node.js](../nosql/sdk-nodejs.md)
 > * [Java SDK v4](../nosql/sdk-java-v4.md)
 > * [Async Java SDK v2](../nosql/sdk-java-async-v2.md)
-> * [Sync Java SDK v2](../nosql/sdk-java-v2.md)
 > * [Spring Data v2](../nosql/sdk-java-spring-data-v2.md)
 > * [Spring Data v3](../nosql/sdk-java-spring-data-v3.md)
 > * [Spring Data v5](../nosql/sdk-java-spring-data-v5.md)

articles/cosmos-db/nosql/TOC.yml

@@ -938,8 +938,6 @@
           href: sdk-java-v4.md
         - name: Async Java SDK v2 (legacy)
           href: sdk-java-async-v2.md
-        - name: Sync Java SDK v2 (legacy)
-          href: sdk-java-v2.md
         - name: Spring Data Connector v2 (legacy)
           href: sdk-java-spring-data-v2.md
         - name: Spring Data Connector v3

articles/cosmos-db/nosql/how-to-manage-conflicts.md

@@ -89,7 +89,7 @@ DocumentCollection createdCollection = client.createCollection(databaseUri, coll
 
 # [Sync Java V2 SDK](#tab/sync)
 
-[Sync Java V2 SDK](sdk-java-v2.md) (Maven [com.microsoft.azure::azure-documentdb](https://mvnrepository.com/artifact/com.microsoft.azure/azure-documentdb))
+(Maven [com.microsoft.azure::azure-documentdb](https://mvnrepository.com/artifact/com.microsoft.azure/azure-documentdb))
 
 ```java
 DocumentCollection lwwCollection = new DocumentCollection();
@@ -274,7 +274,7 @@ DocumentCollection createdCollection = client.createCollection(databaseUri, coll
 
 # [Sync Java V2 SDK](#tab/sync)
 
-[Sync Java V2 SDK](sdk-java-v2.md) (Maven [com.microsoft.azure::azure-documentdb](https://mvnrepository.com/artifact/com.microsoft.azure/azure-documentdb))
+(Maven [com.microsoft.azure::azure-documentdb](https://mvnrepository.com/artifact/com.microsoft.azure/azure-documentdb))
 
 ```java
 DocumentCollection udpCollection = new DocumentCollection();
@@ -384,7 +384,7 @@ DocumentCollection createdCollection = client.createCollection(databaseUri, coll
 
 # [Sync Java V2 SDK](#tab/sync)
 
-[Sync Java V2 SDK](sdk-java-v2.md) (Maven [com.microsoft.azure::azure-documentdb](https://mvnrepository.com/artifact/com.microsoft.azure/azure-documentdb))
+(Maven [com.microsoft.azure::azure-documentdb](https://mvnrepository.com/artifact/com.microsoft.azure/azure-documentdb))
 
 ```java
 DocumentCollection manualCollection = new DocumentCollection();
@@ -478,7 +478,7 @@ for (Conflict conflict : response.getResults()) {
 ```
 # [Sync Java V2 SDK](#tab/v2sync)
 
-[Sync Java V2 SDK](sdk-java-v2.md) (Maven [com.microsoft.azure::azure-documentdb](https://mvnrepository.com/artifact/com.microsoft.azure/azure-documentdb))
+(Maven [com.microsoft.azure::azure-documentdb](https://mvnrepository.com/artifact/com.microsoft.azure/azure-documentdb))
 
 ```java
 Iterator<Conflict> conflictsIterator = client.readConflicts(this.collectionLink, null).getQueryIterator();

articles/cosmos-db/nosql/how-to-use-stored-procedures-triggers-udfs.md

@@ -20,7 +20,7 @@ ms.custom: devx-track-csharp
 
 The API for NoSQL in Azure Cosmos DB supports registering and invoking stored procedures, triggers, and user-defined functions (UDFs) written in JavaScript. After you define one or more stored procedures, triggers, or user-defined functions, you can load and view them in the [Azure portal](https://portal.azure.com/) by using Data Explorer.
 
-You can use the API for NoSQL SDK across multiple platforms including [.NET v2 (legacy)](sdk-dotnet-v2.md), [.NET v3](sdk-dotnet-v3.md), [Java](sdk-java-v2.md), [JavaScript](sdk-nodejs.md), or [Python](sdk-python.md) SDKs to do these tasks. If you haven't worked with one of these SDKs before, see the quickstart article for the appropriate SDK:
+You can use the API for NoSQL SDK across multiple platforms including [.NET v2 (legacy)](sdk-dotnet-v2.md), [.NET v3](sdk-dotnet-v3.md), [Java](/java/api/overview/azure/cosmos-readme), [JavaScript](sdk-nodejs.md), or [Python](sdk-python.md) SDKs to do these tasks. If you haven't worked with one of these SDKs before, see the quickstart article for the appropriate SDK:
 
 | SDK | Getting started |
 | :--- | :--- |

articles/cosmos-db/nosql/migrate-java-v4-sdk.md

@@ -36,7 +36,7 @@ The following table lists different Azure Cosmos DB Java SDKs, the package name
 | Java SDK| Release Date | Bundled APIs   | Maven Jar  | Java package name  |API Reference   | Release Notes  | Retire date |
 |-------|------|-----------|-----------|--------------|-------------|---------------------------|--------|
 | Async 2.x.x  | June 2018    | Async(RxJava)  | `com.microsoft.azure::azure-cosmosdb` | `com.microsoft.azure.cosmosdb.rx` | [API](https://azure.github.io/azure-cosmosdb-java/2.0.0/) | [Release Notes](sdk-java-async-v2.md) | August 31, 2024 |
-| Sync 2.x.x     | Sept 2018    | Sync   | `com.microsoft.azure::azure-documentdb` | `com.microsoft.azure.cosmosdb` | [API](https://azure.github.io/azure-cosmosdb-java/2.0.0/) | [Release Notes](sdk-java-v2.md)  | February 29, 2024 |
+| Sync 2.x.x     | Sept 2018    | Sync   | `com.microsoft.azure::azure-documentdb` | `com.microsoft.azure.cosmosdb` | [API](https://azure.github.io/azure-cosmosdb-java/2.0.0/) | | February 29, 2024 |
 | 3.x.x    | July 2019    | Async(Reactor)/Sync  | `com.microsoft.azure::azure-cosmos`  | `com.azure.data.cosmos` | [API](https://azure.github.io/azure-cosmosdb-java/3.0.0/) | - | August 31, 2024 |
 | 4.0   | June 2020   | Async(Reactor)/Sync  | `com.azure::azure-cosmos` | `com.azure.cosmos`   | [API](/java/api/overview/azure/cosmosdb) | - | - |
 

articles/cosmos-db/nosql/performance-tips-java.md

@@ -26,7 +26,7 @@ ms.custom: devx-track-java, devx-track-extended-java
 > [!IMPORTANT]  
 > This is *not* the latest Java SDK for Azure Cosmos DB! You should upgrade your project to [Azure Cosmos DB Java SDK v4](sdk-java-v4.md) and then read the Azure Cosmos DB Java SDK v4 [performance tips guide](performance-tips-java-sdk-v4.md). Follow the instructions in the [Migrate to Azure Cosmos DB Java SDK v4](migrate-java-v4-sdk.md) guide and [Reactor vs RxJava](https://github.com/Azure-Samples/azure-cosmos-java-sql-api-samples/blob/main/reactor-rxjava-guide.md) guide to upgrade. 
 > 
-> These performance tips are for Azure Cosmos DB Sync Java SDK v2 only. Please view the Azure Cosmos DB Sync Java SDK v2 [Release notes](sdk-java-v2.md) and [Maven repository](https://mvnrepository.com/artifact/com.microsoft.azure/azure-documentdb) for more information.
+> These performance tips are for Azure Cosmos DB Sync Java SDK v2 only. Please view the [Maven repository](https://mvnrepository.com/artifact/com.microsoft.azure/azure-documentdb) for more information.
 >
 
 > [!IMPORTANT]  
@@ -38,7 +38,7 @@ ms.custom: devx-track-java, devx-track-extended-java
 > Azure Cosmos DB Java SDK v4.
 >
 
-Azure Cosmos DB is a fast and flexible distributed database that scales seamlessly with guaranteed latency and throughput. You do not have to make major architecture changes or write complex code to scale your database with Azure Cosmos DB. Scaling up and down is as easy as making a single API call. To learn more, see [how to provision container throughput](how-to-provision-container-throughput.md) or [how to provision database throughput](how-to-provision-database-throughput.md). However, because Azure Cosmos DB is accessed via network calls there are client-side optimizations you can make to achieve peak performance when using [Azure Cosmos DB Sync Java SDK v2](./sdk-java-v2.md).
+Azure Cosmos DB is a fast and flexible distributed database that scales seamlessly with guaranteed latency and throughput. You do not have to make major architecture changes or write complex code to scale your database with Azure Cosmos DB. Scaling up and down is as easy as making a single API call. To learn more, see [how to provision container throughput](how-to-provision-container-throughput.md) or [how to provision database throughput](how-to-provision-database-throughput.md). However, because Azure Cosmos DB is accessed via network calls there are client-side optimizations you can make to achieve peak performance when using Azure Cosmos DB Sync Java SDK v2.
 
 So if you're asking "How can I improve my database performance?" consider the following options:
 
@@ -84,7 +84,7 @@ So if you're asking "How can I improve my database performance?" consider the fo
 ## SDK Usage
 1. **Install the most recent SDK**
 
-    The Azure Cosmos DB SDKs are constantly being improved to provide the best performance. See the [Azure Cosmos DB SDK](./sdk-java-v2.md) pages to determine the most recent SDK and review improvements.
+    The Azure Cosmos DB SDKs are constantly being improved to provide the best performance. See the [Azure Cosmos DB SDK](/java/api/overview/azure/cosmos-readme) pages to determine the most recent SDK and review improvements.
 2. **Use a singleton Azure Cosmos DB client for the lifetime of your application**
 
     Each [DocumentClient](/java/api/com.microsoft.azure.documentdb.documentclient) instance is thread-safe and performs efficient connection management and address caching when operating in Direct Mode. To allow efficient connection management and better performance by DocumentClient, it is recommended to use a single instance of DocumentClient per AppDomain for the lifetime of the application.
@@ -110,7 +110,7 @@ So if you're asking "How can I improve my database performance?" consider the fo
 
 5. **Implement backoff at getRetryAfterInMilliseconds intervals**
 
-    During performance testing, you should increase load until a small rate of requests get throttled. If throttled, the client application should backoff on throttle for the server-specified retry interval. Respecting the backoff ensures that you spend minimal amount of time waiting between retries. Retry policy support is included in Version 1.8.0 and above of the [Azure Cosmos DB Sync Java SDK](./sdk-java-v2.md). For more information, see [getRetryAfterInMilliseconds](/java/api/com.microsoft.azure.documentdb.documentclientexception.getretryafterinmilliseconds).
+    During performance testing, you should increase load until a small rate of requests get throttled. If throttled, the client application should backoff on throttle for the server-specified retry interval. Respecting the backoff ensures that you spend minimal amount of time waiting between retries. Retry policy support is included in Version 1.8.0 and above of the [Azure Cosmos DB Sync Java SDK](/java/api/overview/azure/cosmos-readme). For more information, see [getRetryAfterInMilliseconds](/java/api/com.microsoft.azure.documentdb.documentclientexception.getretryafterinmilliseconds).
 
 6. **Scale out your client-workload**
 

articles/cosmos-db/nosql/performance-tips.md

@@ -181,7 +181,7 @@ Azure Cosmos DB requests are made over HTTPS/REST when you use gateway mode. The
 During performance testing, you should increase load until a small rate of requests are throttled. If requests are throttled, the client application should back off on throttle for the server-specified retry interval. Respecting the backoff ensures you spend a minimal amount of time waiting between retries. 
 
 Retry policy support is included in these SDKs:
-- Version 1.8.0 and later of the [.NET SDK for SQL](sdk-dotnet-v2.md) and the [Java SDK for SQL](sdk-java-v2.md)
+* Version 1.8.0 and later of the [.NET SDK for SQL](sdk-dotnet-v2.md) and the [Java SDK for SQL](/java/api/overview/azure/cosmos-readme)
 - Version 1.9.0 and later of the [Node.js SDK for SQL](sdk-nodejs.md) and the [Python SDK for SQL](sdk-python.md)
 - All supported versions of the [.NET Core](sdk-dotnet-core-v2.md) SDKs 
 

articles/cosmos-db/nosql/sdk-java-async-v2.md

@@ -17,7 +17,7 @@ ms.custom: devx-track-java, devx-track-extended-java
 
 [!INCLUDE[SDK selector](../includes/cosmos-db-sdk-list.md)]
 
-The API for NoSQL Async Java SDK differs from the API for NoSQL Java SDK by providing asynchronous operations with support of the [Netty library](https://netty.io/). The pre-existing [API for NoSQL Java SDK](sdk-java-v2.md) does not support asynchronous operations. 
+The API for NoSQL Async Java SDK differs from the API for NoSQL Java SDK by providing asynchronous operations with support of the [Netty library](https://netty.io/). The pre-existing [API for NoSQL Java SDK](/java/api/overview/azure/cosmos-readme) does not support asynchronous operations.
 
 > [!IMPORTANT]  
 > This is *not* the latest Java SDK for Azure Cosmos DB! We **strongly recommend** using [Azure Cosmos DB Java SDK v4](sdk-java-v4.md) for your project. To upgrade, follow the instructions in the [Migrate to Azure Cosmos DB Java SDK v4](migrate-java-v4-sdk.md) guide and the [Reactor vs RxJava](https://github.com/Azure-Samples/azure-cosmos-java-sql-api-samples/blob/main/reactor-rxjava-guide.md) guide. 

articles/cosmos-db/nosql/sdk-java-spark-v2.md

@@ -17,7 +17,7 @@ ms.custom: devx-track-java, devx-track-extended-java
 
 [!INCLUDE[SDK selector](../includes/cosmos-db-sdk-list.md)]
 
-The Azure Cosmos DB Java SDK v4 for NoSQL combines an Async API and a Sync API into one Maven artifact. The v4 SDK brings enhanced performance, new API features, and Async support based on Project Reactor and the [Netty library](https://netty.io/). Users can expect improved performance with Azure Cosmos DB Java SDK v4 versus the [Azure Cosmos DB Async Java SDK v2](sdk-java-async-v2.md) and the [Azure Cosmos DB Sync Java SDK v2](sdk-java-v2.md).
+The Azure Cosmos DB Java SDK v4 for NoSQL combines an Async API and a Sync API into one Maven artifact. The v4 SDK brings enhanced performance, new API features, and Async support based on Project Reactor and the [Netty library](https://netty.io/). Users can expect improved performance with Azure Cosmos DB Java SDK v4 versus the [Azure Cosmos DB Async Java SDK v2](sdk-java-async-v2.md) and the [Azure Cosmos DB Sync Java SDK v2](/java/api/overview/azure/cosmos-readme).
 
 > [!IMPORTANT]  
 > These Release Notes are for Azure Cosmos DB Java SDK v4 only. If you are currently using an older version than v4, see the [Migrate to Azure Cosmos DB Java SDK v4](migrate-java-v4-sdk.md) guide for help upgrading to v4.