Enable hashed storage for new projects by default in development
We introduced hashed storage type in 10.0 and is currently considered Beta.
This stage applies for Geo now as well. Hashed storage improves the Geo replication as group/project renames no longer require a synchronization.
To move forward towards production readiness, we should broaden the usage of hashed storage in Geo context.
A next step would be enabling hashed storage for new projects in the GDK by default to gather feedback.
We can do this by modifying db/fixtures/development, so that half the projects we set up use legacy storage, and the other half use hashed storage. We may also want to modify the application_settings rows so that new projects will be created with hashed storage enabled.
Edited by Nick Thomas