Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge policy and UCN #1456

Merged
merged 4 commits into from
Jan 16, 2025
Merged

Merge policy and UCN #1456

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
3e5cb10
merge policy + vector collection
shultseva Jan 6, 2025
f58e7fc
Update docs/modules/clusters/pages/user-code-namespaces.adoc
shultseva Jan 7, 2025
c6b1487
note
shultseva Jan 9, 2025
cea9500
Update docs/modules/network-partitioning/pages/split-brain-recovery.adoc
Rob-Hazelcast Jan 9, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/modules/clusters/pages/user-code-namespaces.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@ Your resources can be run on a Hazelcast cluster to support your business logic.

* MapStore
* Split brain events
* Custom merge policies
* `ExecutorService` runnable
* Jet jobs
Expand Down
5 changes: 5 additions & 0 deletions docs/modules/network-partitioning/pages/split-brain-recovery.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -562,6 +562,11 @@ com.hazelcast.spi.merge.SplitBrainMergeTypes$AtomicReferenceMergeTypes.
See SplitBrainMergingTypes for supported merging types.
```

=== User Code Namespace

You can use your custom resource for the merge policy class through the User Code Namespace feature.
For more details, refer to the xref:clusters:user-code-namespaces.adoc[User Code Namespaces]

Rob-Hazelcast marked this conversation as resolved.
Show resolved Hide resolved
=== Best Practices

Here are some best practices when implementing your own merge policy
Expand Down
Loading