Saltar al contenido
Al usar AWS re:Post, aceptas las AWS re:Post Términos de uso
AWS re:Postre:Post
Acerca de re:Post

I can't commit changes to DynamoDB

1

Using NoSQL Borkbench. I create a new data model with two tables, and then I commit to Amazon DynamoDB. It worked.

But oops, I left a field out in one table, so I add it, and then go and hit the Commit to Amazon DynamoDB button again. Now I get this error:

Error Could not commit to DynamoDB as table creation failed: ResourceInUseException: Table already exists: Devices.

Ok, so the table already exists, but shouldn’t I be able to make changes to it? So let’s skip that datamodel change. Let me just start adding some data to those tables (using NoSQL Workbench). Maybe it won’t let me change the model once it is created, but I must surely be able to add data to the DynamoDB, no? No. Same error when I try to commit.

Can someone tell me where my misunderstanding is? I am assuming that NoSQL Workbench has created a database in memory, that it then should be able to send to the cloud.

  • ccole-aws
    hace 3 años

    Hello, I'm doing research on making this tool better. What would your desired behavior be? After changing the data model (i.e. adding a new GSI, new attribute, adding sample data), be able to commit the changes to the existing table. Is the preference to overwrite the existing table? Do you need a rollback option? Or the re-committing would just create a version of the table?

Temas
Bases de datos
Etiquetas
Amazon DynamoDB
Idioma
English

preguntada hace 5 años1,8 mil visualizaciones

2 Respuestas
1

After three months I would have expected Amazon to have addressed this issue. As you said it's a KNOWN issue. Come on guys, appending data is vital to any tool.

respondido hace 4 años

  • ccole-aws
    hace 3 años

    Hello, I'm doing research on making this tool better. What would your desired behavior be? After changing the data model (i.e. adding a new GSI, new attribute, adding sample data), be able to commit the changes to the existing table. Is the preference to overwrite the existing table? Do you need a rollback option? Or the re-committing would just create a version of the table?

0
Respuesta aceptada

Thank you for using NoSQL Workbench. Currently we don’t support this functionality. Its a known issue and also have added in our backlog and will do our best to address it . Please stay tuned for more updates. quick fix: you can delete the entire table and commit the updated table.

Thanks, Amazon DynamoDB Team

AWS

respondido hace 5 años

  • myAWSAdventure
    hace 5 años

    Thank you. Good to know it isn't me. I will follow your advice.

  • DWPalme
    hace 4 años

    Deleting the entire table and committing the update burns a lot of resources that we have to pay for. That is a useless answer.

No has iniciado sesión. Iniciar sesión para publicar una respuesta.

Una buena respuesta responde claramente a la pregunta, proporciona comentarios constructivos y fomenta el crecimiento profesional en la persona que hace la pregunta.

Contenido relevante