How to update only a single field in DynamoDB using the AWS Go SDK
Hopefully someone can shed some light on this issue I've been struggling with.
I have this table in dynamo, let's call it people
, in this table, I have the attribute of id
as our partition key, name
, lastname
and status
.
I want to be able to update just a single property or save all properties of the id.
Now, this is how I do it. I created the following structure:
type personupdate struct { firstname string `json:"firstname,omitempty"` lastname string `json:"lastname,omitempty"` status string `json:"status,omitempty"` }
The request from the server simply updates the person's last name, so our request body will look like this:
{ "lastname": "bob" }
After binding the request to the structure, the object that will be sent to dynamo will look like this:
{ "firstname": "", "lastname": "bob", "status": "", }
Now, as you can see, when it is time to write to dynamo, only one property should be updated and the rest of the null/null properties should be ignored.
The code written to do this can be condensed into the following:
// marshal our object _, err := dynamodbattribute.marshalmap(person) if err != nil{ fmt.println("some error marshaling") } // create our update input input := &dynamodb.updateiteminput{ key: map[string]*dynamodb.attributevalue{ "id":{ s: aws.string("1234"), }, }, tablename: aws.string("people"), expressionattributevalues: map[string]*dynamodb.attributevalue{ ":fn": { s: aws.string(person.firstname), }, ":ln":{ s: aws.string(person.lastname), }, ":st":{ s: aws.string(person.status), }, }, updateexpression: aws.string("set firstname = :fn, lastname = :ln, status = :st"), returnvalues: aws.string("updated_new"), } // send update request to dynamo _, err := service.updateitem(input)
Now, the update works without any problem, the problem is that null values for firstname
and status
are also passed. I've tried reading their documentation, but I'm still a little confused. I know the java sdk allows you to pass a flag called update_skip_null_attributes
which allows you to skip those null values and update only those values that have data. I don't know what the equivalent is in go, any help/guidance would be great.
renew:
Try using the following model:
type usermodel struct { firstname string `json:"firstname,omitempty" dynamodbav:"firstname,omitempty"` lastname string `json:"lastname,omitempty" dynamodbav:"lastname,omitempty"` }
Follow the advice given by @jarmod and @fedonev. Logically and using the documentation it's understandable why this should work, unfortunately it doesn't
Decided to switch the sdk from v1 to v2 to see if updating it would help, although I'm stuck in the same predicament again. This is what my update function looks like.
update :=expression.Set(expression.Name("firstName"),expression.Value(user.FirstName)) update.Set(expression.Name("lastName"), expression.Value(user.LastName)) expr, err := expression.NewBuilder().WithUpdate(update).Build() if err != nil { "log error here..." } _, err = svc.UpdateItem(context.TODO(), &dynamodb.UpdateItemInput{ TableName: aws.String("people"), Key: map[string]types.AttributeValue{"id": id}, ExpressionAttributeNames: expr.Names(), ExpressionAttributeValues: expr.Values(), UpdateExpression: expr.Update(), ReturnValues: types.ReturnValueUpdatedNew, }) if err != nil { "log error here..." }
I ended up solving my problem by writing a query and create function that pretty much queries the json payload by the id we want to update and updates based on the difference of what we want the query to do, any empty fields will Replaced by query results. So far it solved my problem, but I'm still wondering how to update it with its intended functionality.
Correct answer
As @jarmod's comment says, when applying the dynamodbav:",omitempty"
tag to the marshalling structure Skip zero value fields :
type personupdate struct { firstname string `json:"firstname,omitempty" dynamodbav:",omitempty"` lastname string `json:"lastname,omitempty" dynamodbav:",omitempty"` status string `json:"status,omitempty" dynamodbav:",omitempty"` }
[Edit: Add usage] marshalmap
Zero value fields will now be ignored, respecting labels. Iterate over the map to construct an update expression:
av, _ := attributevalue.MarshalMap(person) update := expression.UpdateBuilder{} for k, v := range av { update = update.Set(expression.Name(k), expression.Value(v)) }
Build the expression and pass its output to updateitem
as shown in the op.
The above is the detailed content of How to update only a single field in DynamoDB using the AWS Go SDK. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

OpenSSL, as an open source library widely used in secure communications, provides encryption algorithms, keys and certificate management functions. However, there are some known security vulnerabilities in its historical version, some of which are extremely harmful. This article will focus on common vulnerabilities and response measures for OpenSSL in Debian systems. DebianOpenSSL known vulnerabilities: OpenSSL has experienced several serious vulnerabilities, such as: Heart Bleeding Vulnerability (CVE-2014-0160): This vulnerability affects OpenSSL 1.0.1 to 1.0.1f and 1.0.2 to 1.0.2 beta versions. An attacker can use this vulnerability to unauthorized read sensitive information on the server, including encryption keys, etc.

The library used for floating-point number operation in Go language introduces how to ensure the accuracy is...

Queue threading problem in Go crawler Colly explores the problem of using the Colly crawler library in Go language, developers often encounter problems with threads and request queues. �...

Backend learning path: The exploration journey from front-end to back-end As a back-end beginner who transforms from front-end development, you already have the foundation of nodejs,...

The difference between string printing in Go language: The difference in the effect of using Println and string() functions is in Go...

Under the BeegoORM framework, how to specify the database associated with the model? Many Beego projects require multiple databases to be operated simultaneously. When using Beego...

This article introduces a variety of methods and tools to monitor PostgreSQL databases under the Debian system, helping you to fully grasp database performance monitoring. 1. Use PostgreSQL to build-in monitoring view PostgreSQL itself provides multiple views for monitoring database activities: pg_stat_activity: displays database activities in real time, including connections, queries, transactions and other information. pg_stat_replication: Monitors replication status, especially suitable for stream replication clusters. pg_stat_database: Provides database statistics, such as database size, transaction commit/rollback times and other key indicators. 2. Use log analysis tool pgBadg

The problem of using RedisStream to implement message queues in Go language is using Go language and Redis...
