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
Describe the issue
One of the requirements for data partitioning and multitennancy is that one tenant's data cannot affect another tenant. However the default setting: conditional_create_duplicate_identifiers_enabled=false means that Resource identifiers must be globally unique across tenants (see error message below). This is not expected when partitioning is enabled. I propose that this setting is default true when partitioning is enabled so that identifiers from separate tenants can have the same values. I might go one step further to suggest that this setting is not needed at the top level as I cannot see a case where we would want to set it to true or false independently of enabling or disabling partitioning as a whole.
Environment (please complete the following information):
HAPI FHIR Version
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Additional context
The default configuration for partitioning produces this error log when I run my partitioning tests that create two identical resources in two separate tenants. I would expect that partitioning works by default.
NOTE: Before filing a ticket, please see the following URL:
https://github.com/hapifhir/hapi-fhir/wiki/Getting-Help
Describe the issue
One of the requirements for data partitioning and multitennancy is that one tenant's data cannot affect another tenant. However the default setting:
conditional_create_duplicate_identifiers_enabled=false
means that Resource identifiers must be globally unique across tenants (see error message below). This is not expected when partitioning is enabled. I propose that this setting is default true when partitioning is enabled so that identifiers from separate tenants can have the same values. I might go one step further to suggest that this setting is not needed at the top level as I cannot see a case where we would want to set it to true or false independently of enabling or disabling partitioning as a whole.Environment (please complete the following information):
Additional context
The default configuration for partitioning produces this error log when I run my partitioning tests that create two identical resources in two separate tenants. I would expect that partitioning works by default.
The text was updated successfully, but these errors were encountered: