Skip to content

Commit 8e83a37

Browse files
Document the Concept of realm Issue #1326: updating based on PR comments
1 parent a3c940f commit 8e83a37

File tree

1 file changed

+3
-7
lines changed

1 file changed

+3
-7
lines changed

site/content/in-dev/unreleased/realm.md

Lines changed: 3 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -17,9 +17,9 @@
1717
# specific language governing permissions and limitations
1818
# under the License.
1919
#
20-
Title: Entities
20+
Title: Realm
2121
type: docs
22-
weight: 400
22+
weight: 350
2323
---
2424

2525
This page explains what a realm is and what it is used for in Polaris.
@@ -50,8 +50,4 @@ This ensures that each realm's data is stored separately.
5050
authorization.
5151

5252
**Isolation:** In methods like `createEntityManagerFactory(@Nonnull RealmContext realmContext)` from `PolarisEclipseLinkPersistenceUnit` interface, the realm context influence how resources are created or managed based on the security policies of that realm.
53-
An example of this is the way a realm name is used to create a database connection url so that you have one database instance per realm, or it can be more granular and applied at primary key level (within the same database instance).
54-
55-
**MetaStore and Cache Management:** Realms are used to manage different instances or configurations of metadata stores and caches. An example of this is `LocalPolarisMetaStoreManagerFactory`.
56-
57-
**Persistence:** Some implementations of Polaris Persistence may use realm IDs in primary keys for Polaris data.
53+
An example of this is the way a realm name can be used to create a database connection url so that you have one database instance per realm, when applicable. Or it can be more granular and applied at primary key level (within the same database instance).

0 commit comments

Comments
 (0)