scylladb / scylladb/alternator-client-java
CRT clients are incompatible with documented AWS SDK 2.20 minimum
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 0
- Forks
- 7
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 9
Description
The README states that AWS SDK for Java v2 2.20 or newer is supported, but the CRT client paths directly use APIs unavailable in SDK 2.20.
- The synchronous path references
AwsCrtHttpClient, which is unavailable in SDK 2.20. Selecting sync CRT fails withNoClassDefFoundError. - The asynchronous path calls
AwsCrtAsyncHttpClient.Builder.connectionAcquisitionTimeout(Duration), which is unavailable before SDK 2.30.15. With the default positive acquisition timeout, selecting async CRT on SDK 2.20 fails withNoSuchMethodError.
The SDK dependencies are provided, so applications using the documented minimum can encounter these failures at runtime.
Relevant locations:
README.md:22src/main/java/com/scylladb/alternator/internal/CrtSyncClientFactory.javasrc/main/java/com/scylladb/alternator/internal/CrtAsyncClientFactory.java:59
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with README.md:22 and inspect CrtSyncClientFactory.java and CrtAsyncClientFactory.java:59 to trace the SDK APIs used by each CRT path. Reproduce both failures with SDK 2.20, then compare behavior with the version where the async API is available. Done means the documented minimum no longer causes runtime failures when selecting either CRT client.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100