Disconnection and waiting must not be required between creation and deleting a dataspace

Step to get the bug by using an application that can create dataspace in the RDDMS:

  • Connect to AWS Pre-shipping M25
  • Create a new dataspace
  • This new dataspace is not even listed to use it
  • Disconnect then reconnect rapidly there we still unable to push object or delete this new dataspace
  • Wait for 1-2 minutes then close the connection & reconnect again to get this dataspace available then to push object or delete it

The fix maybe to put the dataspace ACL in the cache after publication

Assignee Loading
Time tracking Loading