QATOOLS-2 [DynamoDB] Upgraded to AWS SDK for Java v2

[m-szymon]

Based on #3 work by Arjan Schaaf schaafas@amazon.nl

I split original commit into 2 parts - this PR only updates SDK.
Due to previous changes in the code it required some adaptations.
Tests (which didn't exists in original commit) were also updated to use new SDK.

It removes option dynamodb.awsCredentialsFile switching to the "Default Credential Provider" chain.

Fixes #10

[Copilot]

Pull Request Overview

This PR upgrades the DynamoDB client from AWS SDK for Java v1 to v2, removing the deprecated credentials file configuration in favor of the Default Credential Provider chain.

Key changes:

• Migration from AWS SDK v1 (1.12.565) to v2 (2.27.21)
• Removal of dynamodb.awsCredentialsFile property and related credentials file handling
• Updated all DynamoDB API calls to use v2 builder patterns and method names

Reviewed Changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
dynamodb/pom.xml	Updates SDK dependencies from v1 to v2, including apache-client and dynamodb modules
dynamodb/src/main/java/site/ycsb/db/DynamoDBClient.java	Migrates client initialization and all API operations to SDK v2 patterns
dynamodb/src/test/java/site/ycsb/db/dynamodb/DynamoDBClientTest.java	Updates test setup and assertions to use SDK v2 API
dynamodb/conf/dynamodb.properties	Removes credentials file references and unused connection parameters
dynamodb/conf/AWSCredentials.properties	Removes deprecated credentials template file
dynamodb/README.md	Updates documentation for new credential provider approach

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[soyacz]

@m-szymon it broke some tests testExclusiveScan(site.ycsb.db.dynamodb.DynamoDBClientTest): Scan did not return expected number of rows

[m-szymon]

@m-szymon it broke some tests testExclusiveScan(site.ycsb.db.dynamodb.DynamoDBClientTest): Scan did not return expected number of rows

Yes, I'm taking care of it. But first I am trying to figure out why the test is not running locally (probably after Fedora upgrade):

256  [main] ERROR org.testcontainers.dockerclient.DockerClientProviderStrategy  -Could not find a valid Docker environment. Please check configuration. Attempted configurations were:
        UnixSocketClientProviderStrategy: failed with exception BadRequestException (Status 400: {"message":"client version 1.32 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer version"}
)
        DockerDesktopClientProviderStrategy: failed with exception NullPointerException (Cannot invoke "java.nio.file.Path.toString()" because the return value of "org.testcontainers.dockerclient.DockerDesktopClientProviderStrategy.getSocketPath()" is null)As no valid configuration was found, execution cannot continue.
See https://java.testcontainers.org/on_failure.html for more details.

[m-szymon]

it broke some tests

It was a problem with credentials - basically all tests failed. And locally it used my system configuration.
It is fixed, but the credential setting changes in this PR may brake things.
I followed the original PR #3, but now I think that maybe I should keep the backward compatibility with dynamodb.awsCredentialsFile.

[fruch]

@soyacz @CodeLieutenant what's blocking this one ?

unit-tests seems to be working now

[soyacz]

@CodeLieutenant can you take a look? Merge if LGTY.