Skip to content

Conversation

@mdumandag
Copy link
Contributor

It is not possible to run the CP data structures on the metadata
group name. We now fail-fast if someone tries to use the METADATA
as the CP group name. Also, the group name comparison made
case-insensitive.

Closes #374

@mdumandag mdumandag added this to the 4.1 milestone Mar 10, 2021
@mdumandag mdumandag self-assigned this Mar 10, 2021
It is not possible to run the CP data structures on the metadata
group name. We now fail-fast if someone tries to use the `METADATA`
as the CP group name. Also, the group name comparison made
case-insensitive.
@mdumandag mdumandag force-pushed the cp-metadata-group-name branch from 69cfbeb to 3cc15a3 Compare March 12, 2021 14:45
Copy link
Contributor

@srknzl srknzl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking good. I wonder why metadata cannot be used as group name

@mdumandag
Copy link
Contributor Author

@mdumandag mdumandag merged commit e259d86 into hazelcast:master Mar 24, 2021
@mdumandag mdumandag deleted the cp-metadata-group-name branch March 24, 2021 14:47
@degerhz degerhz changed the title Fail fast on the METADATA group name for CP data structures Fail fast on the METADATA group name for CP data structures [API-389] Apr 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Do not allow using METADATA as the group name on the CP data structures

2 participants