Users/tanmayapanda/address review comments

[tanmaya-panda1]

This pull request introduces significant changes to the ingestion client and uploader logic to simplify and clarify multi-source ingestion, enforce stricter type safety, and improve concurrency handling. The main focus is to restrict multi-source ingestion to only support blob sources, remove internal logic for uploading local sources within multi-ingest, and enhance the uploader's parallelism and load distribution.

Multi-source ingestion API and logic changes:

• Restricts multi-source ingestion (ingestAsync) to only accept BlobSource objects, both in the interface and implementation, and updates all related documentation to clarify that local sources must be uploaded separately before ingestion. This prevents partial failure scenarios and enforces a clearer, safer workflow. [1] [2] [3] [4]
• Removes the internal method for uploading local sources (uploadLocalSourcesAsync) from QueuedIngestClient, making it the caller's responsibility to upload local files/streams before calling multi-ingest. [1] [2]

Error handling and messaging improvements:

• Updates error messages in IngestClientException to use the message parameter for clarity and consistency. [1] [2]

Uploader concurrency and load balancing enhancements:

• Switches the container selection logic in ContainerUploaderBase from random to round-robin using an atomic counter, ensuring more even load distribution across containers during uploads and retries. [1] [2] [3]
• Improves parallel upload logic to use a semaphore for true streaming parallelism, allowing new uploads to start as soon as slots are available, rather than processing in fixed-size chunks.

Java interop and API usability:

• Adds overloaded static factory methods to DefaultConfigurationCache for easier creation from Java, supporting both minimal and full-parameter configurations.
• Adds @JvmOverloads constructors to FileSource and StreamSource for better Java interoperability and sensible defaults. [1] [2]

These changes collectively make the ingestion API safer, simpler, and more robust, especially in multi-source scenarios.### Added

Changed

Fixed

[github-actions]

Test Results

530 tests  ±0   521 ✅ ±0   7m 58s ⏱️ -12s
 31 suites ±0     9 💤 ±0 
 31 files   ±0     0 ❌ ±0 

Results for commit 428eb23. ± Comparison against base commit ce36f64.

♻️ This comment has been updated with latest results.

[ag-ramachandran]

AtomicLong perhaps ?

[tanmaya-panda1]

I thought of so but AtomicLong seems to be an overkill perhaps, since AtomicInteger has already around 2.1 billion positive values. Added Math.floorMod to handle the negative values incase overflow occurs.