Hello All,
Any pointer on how to update/set a specific attribute value in a DynamoDB versioned table using aws-sdk-java-v2?
Also how one can use enhanced client with timed-series DynamoDB tables (eg. TestResultsOCT2020, TestResultsNOV2020 etc. Here the associated java entity class would be "TestResults" without time-series and not "TestResultsOCT2020" )
Hello All,
Any Idea how I can get GSI (global secondary indexes) associated with @DynamoDbSecondaryPartitionKey using sdkV2 enhanced DynamoDB client?
TableSchema.fromBean(clazz).tableMetadata().indices() does provide IndexMetadata (name, primary & sortkey), but does not reveal any association with @DynamoDbSecondaryPartitionKey or @DynamoDbSecondarySortKey, either.
1 reply
Caused by: java.util.concurrent.CompletionException: java.io.IOException: Server failed to send complete response
at java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:292)
at java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:308)
at java.util.concurrent.CompletableFuture.uniCompose(CompletableFuture.java:943)
at java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:926)
at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)
at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1977)
at software.amazon.awssdk.core.internal.http.async.CombinedResponseAsyncHttpResponseHandler.onError(CombinedResponseAsyncHttpResponseHandler.java:67)
at software.amazon.awssdk.core.internal.http.async.AsyncAfterTransmissionInterceptorCallingResponseHandler.onError(AsyncAfterTransmissionInterceptorCallingResponseHandler.java:72)
at software.amazon.awssdk.core.internal.http.pipeline.stages.MakeAsyncHttpRequestStage$WrappedErrorForwardingResponseHandler.onError(MakeAsyncHttpRequestStage.java:159)
at software.amazon.awssdk.http.nio.netty.internal.ResponseHandler.lambda$notifyIfResponseNotCompleted$2(ResponseHandler.java:401)
at software.amazon.awssdk.http.nio.netty.internal.ResponseHandler.runAndLogError(ResponseHandler.java:180)
at software.amazon.awssdk.http.nio.netty.internal.ResponseHandler.notifyIfResponseNotCompleted(ResponseHandler.java:401)
at software.amazon.awssdk.http.nio.netty.internal.ResponseHandler.channelInactive(ResponseHandler.java:152)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:262)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:248)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:241)
at io.netty.handler.logging.LoggingHandler.channelInactive(LoggingHandler.java:197)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:262)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:248)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:241)
at io.netty.channel.ChannelInboundHandlerAdapter.channelInactive(ChannelInboundHandlerAdapter.java:81)
at io.netty.handler.timeout.IdleStateHandler.channelInactive(IdleStateHandler.java:277)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:262)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:248)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:241)
at io.netty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandlerContext.fireChannelInactive(CombinedChannelDuplexHandler.java:418)
at io.netty.handler.codec.ByteToMessageDecoder.channelInputClosed(ByteToMessageDecoder.java:386)
at io.netty.handler.codec.ByteToMessageDecoder.channelInactive(ByteToMessageDecoder.java:351)
at io.netty.handler.codec.http.HttpClientCodec$Decoder.channelInactive(HttpClientCodec.java:288)
at io.netty.channel.CombinedChannelDuplexHandler.channelInactive(CombinedChannelDuplexHandler.java:221)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:262)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:248)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:241)
at io.netty.handler.codec.ByteToMessageDecoder.channelInputClosed(ByteToMessageDecoder.java:386)
at io.netty.handler.codec.ByteToMessageDecoder.channelInactive(ByteToMessageDecoder.java:351)
at io.netty.handler.ssl.SslHandler.channelInactive(SslHandler.java:1084)
at io.netty.channel.AbstractChannelHandlerCon
final SdkEventLoopGroup sdkEventLoopGroup;
if (Epoll.isAvailable()) {
sdkEventLoopGroup = SdkEventLoopGroup.create(new EpollEventLoopGroup(eventLoopGroupThreads), HttpClientConfiguration::createEpollSocketChannel);
} else {
sdkEventLoopGroup = SdkEventLoopGroup.create(new NioEventLoopGroup(eventLoopGroupThreads), HttpClientConfiguration::createNioSocketChannel);
}
final NettyNioAsyncHttpClient.Builder nettyNioAsyncHttpClientBuilder = NettyNioAsyncHttpClient.builder()
.connectionMaxIdleTime(connectionMaxIdleTime)
.connectionAcquisitionTimeout(connectionAcquisitionTimeout)
.connectionTimeout(connectionTimeout)
.readTimeout(readTimeout)
.maxConcurrency(maxConnections)
.maxPendingConnectionAcquires(maxPendingConnectionAcquires)
.eventLoopGroup(sdkEventLoopGroup)
.sslProvider(OpenSsl.isAvailable() ? SslProvider.OPENSSL : SslProvider.JDK);
log.info("Netty async http client - openssl: {} - epoll: {}", OpenSsl.isAvailable(), Epoll.isAvailable());
if (!OpenSsl.isAvailable()) {
log.info("OpenSSL reason: {}", OpenSsl.unavailabilityCause().getMessage(), OpenSsl.unavailabilityCause());
}
if (!Epoll.isAvailable()) {
log.info("Epoll reason: {}", NestedExceptionUtils.getMostSpecificCause(Epoll.unavailabilityCause()).getMessage());
}
return nettyNioAsyncHttpClientBuilder.build();final S3AsyncClientBuilder clientBuilder = S3AsyncClient.builder()
.httpClient(asyncHttpClient)
.region(region);
I searched for some online Javadoc and found 2 sources that both claim to be latest, for 2.15.68. For example for StsAssumeRoleCredentialsProvider.Builder:
https://sdk.amazonaws.com/java/api/latest/software/amazon/awssdk/services/sts/auth/StsAssumeRoleCredentialsProvider.Builder.html
and
https://javadoc.io/doc/software.amazon.awssdk/sts/latest/software/amazon/awssdk/services/sts/auth/StsAssumeRoleCredentialsProvider.Builder.html
The first shows it extends Object. The second extends BaseBuilder and obviously supplies more methods.
Why are they different? What is the correct source?
2 replies
I am trying to update a single attribute using UpdateItemEnhancedRequest (using the Dynamodb Enhanced Client. - JAVA SDK 2). I am able to build the condition for updating the attribute but it updates the entire item and not just the attribute. Can somebody please guide on how to update a single attribute using DynamoDb Enhanced Client? just like we do using the update expression
7 replies
Hi
I'm developping a SpringBoot application in java with Intellij and I need to list files from a S3.
I'm behind a proxy
I'm using the AWS java sdk V2 and I can't set a proxy for the s3Client to access files on S3
Does anyone use AWS java sdk (v1 or v2) and may help me configure the proxy (in code or in Intelij configuration) ?
Thanks
SdkHttpClient httpClient = ApacheHttpClient.builder()
.proxyConfiguration(proxyConfiguration)
.build();
but I got
java.lang.IllegalArgumentException: Proxy endpoint path is not supported.
Hey y'all I'm running into a dead end when trying to used the dynamodb-enhanced client to update only specific fields on an object without doing an extra read.
Lets say I only have the partition/sort key for an item, and I want to unset one attribute on that item. If I use the enhanced client updateItem, I need to use ignoreNulls(false) so my null attribute gets propagated, but without the rest of the item data, this will unset all the attributes, not just the one in question. The only solution I've found is to first getItem to get all the item data, set the specific field to null, and pass that whole object back into updateItem. It feels wrong to do an entire database read just to satisfy the sdk. Is there a way to blacklist or whitelist certain attributes relating to ignoreNulls?
updateExpression
2 replies
Hoping someone might be able to provide some clarity as I'm not 100% sure based off of reading the code...
Does does the S3Client.putObject method stream requests (reading a bit of a file at time and uploading it before grabbing more), or do it all at once (Up to the max file size, which is where multipart uploads would be used)?
1 reply
I have completed the changes I wish to make, however I don't have permission to create a branch. How can I get permission to push my code?
aws s3 ls
1 reply
com.amazonaws:aws-xray-recorder-sdk-* with the aws-xray-recorder-sdk-aws-sdk-v2 module for v2 services integrations, but this library is still itself build on top of com.amazonaws:aws-java-sdk-xray (i.e. v1). Or is there already an alternative to that recorder library that I'm not finding?
2 replies
Exception in thread "main" java.lang.ExceptionInInitializerError
at com.oracle.svm.core.classinitialization.ClassInitializationInfo.initialize(ClassInitializationInfo.java:315)
Caused by: java.lang.IllegalArgumentException: Failed to generate method handle.
at software.amazon.awssdk.enhanced.dynamodb.internal.mapper.LambdaToMethodBridgeBuilder.build(LambdaToMethodBridgeBuilder.java:92)
at software.amazon.awssdk.enhanced.dynamodb.internal.mapper.ObjectConstructor.create(ObjectConstructor.java:37)
at software.amazon.awssdk.enhanced.dynamodb.mapper.BeanTableSchema.newObjectSupplierForClass(BeanTableSchema.java:361)
at software.amazon.awssdk.enhanced.dynamodb.mapper.BeanTableSchema.createStaticTableSchema(BeanTableSchema.java:172)
at software.amazon.awssdk.enhanced.dynamodb.mapper.BeanTableSchema.create(BeanTableSchema.java:129)
at software.amazon.awssdk.enhanced.dynamodb.mapper.BeanTableSchema.create(BeanTableSchema.java:121)
at software.amazon.awssdk.enhanced.dynamodb.TableSchema.fromBean(TableSchema.java:81)
2.11.4to 2.16.56 we get Caused by: java.lang.NullPointerException
at software.amazon.awssdk.core.internal.handler.BaseClientHandler.finalizeSdkHttpFullRequest(BaseClientHandler.java:81)
at software.amazon.awssdk.core.internal.handler.BaseAsyncClientHandler.doExecute(BaseAsyncClientHandler.java:196)
... 92 moreNull metrics collector
Dear AWS Team!
Please help me to confirm a feature I found by trying. A static execution of "handler" method.
I'm trying to figure out a feature which I couldn't find documented anywhere, as well as when looking on Github into source code.
Would you please help me to find a documentation or source code regarding to the following behavior I observed?
A feature is very helpful, but I would like to double check that I will not rely on some experimental or deprecated functionality.
According to documentation (https://docs.aws.amazon.com/lambda/latest/dg/java-handler.html) there are two handler formats.
If we define in template.yml the following...
MyFeatureLambda
Type: AWS::Serverless::Function
Properties:
...
Handler: com.acme.some.MyFeatureLambda
......then a new instance of MyFeatureLambda class is created and a method executed on it.
Next, something like below is happening on AWS side, under the hood:
MyFeatureLambda handler = new MyFeatureLambda;
handler.handleRequest(input, output, context);If we define Handler: com.acme.some.MyFeatureLambda::handleRequest it works in a similar way.
Now, an interesting (undocumented?) feature. When we define handler as following (using apply):
Handler: com.acme.some.MyFeatureLambda::applyFrom my observation, I'm guessing that under the hood it is happening something like this:
MyFeatureLambda.apply(input, output, context);Here, it calls an apply directly in a static way without instantiating the class. I tested the functionality by implementing a lambda class without no-arg constructor, so instantiating of a class is not possible, but lambda is correctly executed. Now, I'm able to implement the apply method according to needs and call handleRequest from there myself, what I do. It works well. But... I couldn't find it documented that apply is executed in a static way.
This is what I need. Please help me make sure about this functionality by pointing to a place in the documentation or code on Github.
Thanks!
https://github.com/aws/aws-lambda-java-libs/blob/311f97cc47b414633c62ee96d9df3e8404e14d69/aws-lambda-java-runtime-interface-client/src/main/java/com/amazonaws/services/lambda/runtime/api/client/EventHandlerLoader.java#L331
In the case when in template.yml it was defined in a way:
Handler: com.acme.some.MyFeatureLambda::handleRequest but a method was not static, this didn't work.Now, if my
apply method is static, all works fine. So I answered my own question ;-)
2 replies
2 replies
Hi, does anyone have any idea what could be the reason I am having this exception?
Exception encountered when invoking run on a nested suite - software.amazon.awssdk.core.exception.SdkClientException: Unable to execute HTTP request: Acquire operation took longer than the configured maximum time. This indicates that a request cannot get a connection from the pool within the specified maximum time. This can be due to high request rate.
Consider taking any of the following actions to mitigate the issue: increase max connections, increase acquire timeout, or slowing the request rate.
Increasing the max connections can increase client throughput (unless the network interface is already fully utilized), but can eventually start to hit operation system limitations on the number of file descriptors used by the process. If you already are fully utilizing your network interface or cannot further increase your connection count, increasing the acquire timeout gives extra time for requests to acquire a connection before timing out. If the connections doesn't free up, the subsequent requests will still timeout.
If the above mechanisms are not able to fix the issue, try smoothing out your requests so that large traffic bursts cannot overload the client, being more efficient with the number of times you need to call AWS, or by increasing the number of hosts sending requests.
java.util.concurrent.CompletionException: software.amazon.awssdk.core.exception.SdkClientException: Unable to execute HTTP request: Acquire operation took longer than the configured maximum time. This indicates that a request cannot get a connection from the pool within the specified maximum time. This can be due to high request rate.
Consider taking any of the following actions to mitigate the issue: increase max connections, increase acquire timeout, or slowing the request rate.
Increasing the max connections can increase client throughput (unless the network interface is already fully utilized), but can eventually start to hit operation system limitations on the number of file descriptors used by the process. If you already are fully utilizing your network interface or cannot further increase your connection count, increasing the acquire timeout gives extra time for requests to acquire a connection before timing out. If the connections doesn't free up, the subsequent requests will still timeout.
If the above mechanisms are not able to fix the issue, try smoothing out your requests so that large traffic bursts cannot overload the client, being more efficient with the number of times you need to call AWS, or by increasing the number of hosts sending requests.