Skip to content

Commit

Permalink
Clarify the identifier requirement to be ordered
Browse files Browse the repository at this point in the history
Signed-off-by: Christian Simon <simon@swine.de>
  • Loading branch information
simonswine committed Nov 11, 2020
1 parent 24a45f1 commit 2493aa6
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/proposals/cross-tenant-query-federation.md
Original file line number Diff line number Diff line change
Expand Up @@ -84,7 +84,7 @@ Having a query spanning multiple tenants, the existing methods are no longer cor

#### Proposal

The identifier for aforementioned features for queries involving more than a single tenant should be derived from: An ordered, distinct list of tenant IDs, which is joined by a `|`.
The identifier for aforementioned features for queries involving more than a single tenant should be derived from: An ordered, distinct list of tenant IDs, which is joined by a `|`. This will produce a reproducible identifier for the same set of tenants no matter which order they have been specified.

While this feature is considered experimental, this provides some insights and ability to limit multi-tenant queries with these short comings:

Expand Down

0 comments on commit 2493aa6

Please sign in to comment.