You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an application with two DynamoDB tables. In our integration runs, we run rspec with parallel tasks and threads. Unfortunately, we are running into an error where one class has deleted/cleared a table (using the DynamoidReset module described here as a spec helper) in one thread, and another tries to take an operation on a non-existing table. Is there a way to circumvent this besides namespacing every spec file to its own table?
The text was updated successfully, but these errors were encountered:
I have no idea how to solve this issue with current implementation of Dynamoid config. Table namespaces could help but there is only one global namespace. It could be changed but every model caches it (full table name, actually).
Dynamic configuring was asked in issues several times and I planned to implement it in the next versions.
I have an application with two DynamoDB tables. In our integration runs, we run rspec with parallel tasks and threads. Unfortunately, we are running into an error where one class has deleted/cleared a table (using the DynamoidReset module described here as a spec helper) in one thread, and another tries to take an operation on a non-existing table. Is there a way to circumvent this besides namespacing every spec file to its own table?
The text was updated successfully, but these errors were encountered: