-
-
Notifications
You must be signed in to change notification settings - Fork 196
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
Dynamoid conflicts with parallel rspec tests #477
Comments
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. |
Hi,
Has this already been implemented? |
No, it hasn't been implemented yet. |
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: