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

Jump to bottom

Gh-374: Add details of cache suffixes to changelog #373

Merged
merged 4 commits into from
Sep 6, 2023
Merged

Gh-374: Add details of cache suffixes to changelog #373

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
3cf1c20
Update federation-changes.md with Cache Suffix
GCHQDev404 Aug 22, 2023
70672b0
Update docs/gaffer2.0/federation-changes.md
GCHQDeveloper314 Sep 5, 2023
ae914b8
Update docs/gaffer2.0/federation-changes.md
GCHQDeveloper314 Sep 5, 2023
cf014c4
Update docs/gaffer2.0/federation-changes.md
GCHQDeveloper314 Sep 5, 2023
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
22 changes: 22 additions & 0 deletions docs/gaffer2.0/federation-changes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -238,3 +238,25 @@ By default, `GetSchema` results will be merged with `MergeSchema`. This returns
| GetSchema | MergeSchema |
| GetTraits | CollectionIntersect |
| others | ConcatenateMergeFunction |




## SuffixCacheName

All Cache implementations are given a name and you can have multiple caches like NamedOperations, NamedViews, etc.

However within FederatedStore where multiple graphs may exist, a cache name has the suffix of `graphId` added by default for identity and keeping caches for different graphs separate, e.g NamedOperationCache_graph1, NamedOperationCache_graph2, NamedOperationCache_graph3.

The User can configure all the cache suffix for a graph in the StoreProperties using a flag that takes priority over graphId.

`gaffer.cache.service.default.suffix`

The User can configure the individual cache suffix for a graph in the StoreProperties using the flags that takes priority over default.suffix.
`gaffer.cache.service.named.operation.suffix`,
`gaffer.cache.service.job.tracker.suffix`,
`gaffer.cache.service.named.view.suffix`,
`gaffer.cache.service.federated.store.suffix`

This also means two FederatedStores (or any graphs) can be made to share the same cache, e.g. load balancing FederatedStore instances.