Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resource delete is not performed immediately after response. Wrong total count #178

Open
offtherailz opened this issue Apr 26, 2018 · 0 comments

Comments

@offtherailz
Copy link
Member

offtherailz commented Apr 26, 2018

After a resource delete, if I perform a text search immediately after the response to the delete request I have this result:
image
As you can see 11 results but totalCount is 10.
Probably there is some missing lock condition.

Sometimes totalCount is coherent but the deleted resource is still in the list.
e.g.

// after deleting resource 1
{
  totalCount: 1,
  results: { 
     id: 1
  }
}
@offtherailz offtherailz changed the title resource delete is not propagated immediately Resource delete is not propagated immediately Apr 26, 2018
@offtherailz offtherailz changed the title Resource delete is not propagated immediately Resource delete is not performed immediately (from REST Point of view) Apr 26, 2018
@offtherailz offtherailz changed the title Resource delete is not performed immediately (from REST Point of view) Resource delete is not performed immediately after response. Wrong total count Apr 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant