Azure table : concurrent update strange behavior

[pabeucher]

I'm submitting a...

[ ] Regression 
[X ] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

We have one table with several entities
Some entities have the same partitionKey.
Each entities have a unique RowKey

When we process two updates at the same time with same PartitionKey but different RowKey we have a strange behavior => the two entities are mixed with same content

I noticed the lib use azure replaceEntity to do an update. When testing same case with Microsoft lib and mergeEntity function we don t have the issue, but I would prefer to use nest lib as it’s integration is more interesting with Nest

Expected behavior

Each updated entities are correctly and independently updated

Minimal reproduction of the problem with instructions

Create to update at the same time

What is the motivation / use case for changing the behavior?

Environment

Nest version: 6.9 to 7.0

 
For Tooling issues:
- Node version: 10.14 and + 
- Platform:  Mac. Linux and Windows

Others:
Package manager : npm

[ayshiff]

@manekinekko Can I work on this ? 👍

[ayshiff]

@manekinekko What are your thoughts on this ?

I did find some ressources on concurrency but nothing really helpful for this case.
Do you have any idea where it could come from ?

[manekinekko]

@ayshiff sorry about the delay. I haven't seen the notification for this issue.

If you are still investigating this, maybe you can try what @pabeucher said and replace replaceEntity with mergeEntity.