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
Copy file name to clipboardExpand all lines: site/content/in-dev/unreleased/realm.md
+3-7Lines changed: 3 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,9 +17,9 @@
17
17
# specific language governing permissions and limitations
18
18
# under the License.
19
19
#
20
-
Title: Entities
20
+
Title: Realm
21
21
type: docs
22
-
weight: 400
22
+
weight: 350
23
23
---
24
24
25
25
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.
50
50
authorization.
51
51
52
52
**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