DynamoDB Local conflicts with Kotlin

[vgiguere]

Describe the bug

DynamoDBLocal-1.X and 2.0 come compiled with overrides of kotlin classes defined in kotlin core libs. It creates conflicts and prevents DynamoDBLocal from being used in Kotlin applications.

Similar issues have been opened on this in the past, it was decided not to fix it.

I am kindly asking to reconsider this decision because it is blocking kotlin users, which is a fast growing community, from using DynamoDBLocal in their kotlin apps for integration tests etc. I work for a major client of AWS and it is impacting us.

The error we get is:

`
An attempt was made to call a method that does not exist. The attempt was made from the following location:

aws.smithy.kotlin.runtime.http.operation.SerializeHandler.call(SdkOperationExecution.kt:396)

The following method did not exist:

'long kotlin.time.TimeSource$Monotonic.markNow-z9LOYto()'

The calling method's class, aws.smithy.kotlin.runtime.http.operation.SerializeHandler, was loaded from the following location:

jar:file:/xxx/.m2/repository/aws/smithy/kotlin/http-client-jvm/0.22.1/http-client-jvm-0.22.1.jar!/aws/smithy/kotlin/runtime/http/operation/SerializeHandler.class

The called method's class, kotlin.time.TimeSource$Monotonic, is available from the following locations:

jar:file:/xxx/.m2/repository/com/amazonaws/DynamoDBLocal/2.0.0/DynamoDBLocal-2.0.0.jar!/kotlin/time/TimeSource$Monotonic.class
jar:file:/xxx/.m2/repository/org/jetbrains/kotlin/kotlin-stdlib/1.8.21/kotlin-stdlib-1.8.21.jar!/kotlin/time/TimeSource$Monotonic.class

`

Can you simply do as suggested by @rafalwrzeszcz in this now defunct thread: #2487 and create 2 distributions of DynamoDBLocal.jar

• One uber jar with the embedded kotlin class overrides
• One smaller without the kotlin classes

That would be very much appreciated ;)

Expected Behavior

I expect to be able to use DynamoDBLocal-2.X in a kotlin application that packages the kotlin-stdlib-X.jar in its class path for integration tests without running into this unrecoverable error:

Current Behavior

`
An attempt was made to call a method that does not exist. The attempt was made from the following location:

aws.smithy.kotlin.runtime.http.operation.SerializeHandler.call(SdkOperationExecution.kt:396)

The following method did not exist:

'long kotlin.time.TimeSource$Monotonic.markNow-z9LOYto()'

The calling method's class, aws.smithy.kotlin.runtime.http.operation.SerializeHandler, was loaded from the following location:

jar:file:/xxx/.m2/repository/aws/smithy/kotlin/http-client-jvm/0.22.1/http-client-jvm-0.22.1.jar!/aws/smithy/kotlin/runtime/http/operation/SerializeHandler.class

The called method's class, kotlin.time.TimeSource$Monotonic, is available from the following locations:

jar:file:/xxx/.m2/repository/com/amazonaws/DynamoDBLocal/2.0.0/DynamoDBLocal-2.0.0.jar!/kotlin/time/TimeSource$Monotonic.class
jar:file:/xxx/.m2/repository/org/jetbrains/kotlin/kotlin-stdlib/1.8.21/kotlin-stdlib-1.8.21.jar!/kotlin/time/TimeSource$Monotonic.class

`

Reproduction Steps

Build integration tests on a kotlin application that is dependant on kotlin-stdlib and on DynamoDBLocal

Possible Solution

As suggested by use @rafalwrzeszcz in this now defunct thread: #2487 :

Create 2 distributions of DynamoDBLocal.jar

• One uber jar with the embedded kotlin class overrides
• One smaller without the kotlin classes

Additional Information/Context

No response

AWS Java SDK version used

latest

JDK version used

java 17, Kotlin 1.8

Operating System and version

Mac OS 13.4

[debora-ito]

@vgiguere I'll reach out to the DynamoDB Local team.

But will close this issue, as there's no pending actions from the Java SDK team.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

[vgiguere]

That's not a nice way to treat customers if you ask me.

Why close the issue instead of keeping me in the loop using this ticket?

There is no way to reach out to DynamoDBLocal team except through this repo and then you close the issue.
How am I, as a client, to get the attention of the DynamoDBLocal team?

[debora-ito]

@vgiguere reopening.

I understand there's no channel of communication with the DynamoDB Local team. Every time we get a Github issue that is service related, we reach out to the service team.

I closed this issue because it's not a feature request for the Java SDK itself, so the decision to accept it does not depend on the Java SDK team. Getting a decision from the service teams can take time and we can't control it, so closing this issue means the Java SDK team doesn't have to monitor this indefinitely.

I'm ok with keeping this open until we get a response from the DynamoDB Local team saying if they will support it or not - but will not keep it open until the change is released, if they decide to support it. What do you think?

[vgiguere]

Thanks.

I appreciate your help @debora-ito .

To answer your question, I am perfectly fine with your idea of allowing the conversation but not tracking the work.
I don't want to clog up your ticket system ;)

Since you work at AWS, maybe you can submit to DynamoDBLocal team the idea of creating a forum/ticket system for their clients? It's an important tool for any company that is serious about testing DynamoDB access control/queries/repos etc. etc..

[debora-ito]

Just a reminder that you can talk to the service team if you have access to a Premium Support plan -
https://aws.amazon.com/premiumsupport/plans/developers/

With a Premium Support plan you'll work with a support engineer that is dedicated to your case, talk to the service team directly and have a faster turnaround between questions. But you probably know that.