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

Fixes transfer of MapConfig fields when dynamically added from client #15391

Merged
merged 1 commit into from Aug 9, 2019
Merged

Fixes transfer of MapConfig fields when dynamically added from client #15391

merged 1 commit into from Aug 9, 2019

Conversation

vbekiaris
Copy link
Collaborator

readBackupData and statisticsEnabled were not taken into account when
a new MapConfig was added dynamically from a client

Fixes #15382 on master

@vbekiaris
Fixes transfer of MapConfig fields when dynamically added from client
3a3f224 
readBackupData and statisticsEnabled were not taken into account when
a new MapConfig was added dynamically from a client
@vbekiaris vbekiaris added this to the 4.0 milestone Jul 30, 2019
@vbekiaris vbekiaris self-assigned this Jul 30, 2019
@vbekiaris vbekiaris mentioned this pull request Aug 9, 2019
Merged
@vbekiaris vbekiaris merged commit 01ae42e into hazelcast:master Aug 9, 2019
@mmedenjak mmedenjak added the Source: Internal PR or issue was opened by an employee label Apr 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@mdogan mdogan mdogan approved these changes

@mmedenjak mmedenjak mmedenjak approved these changes

Assignees

@vbekiaris vbekiaris

Labels
Module: Config Source: Internal PR or issue was opened by an employee Team: Client Team: Core Type: Defect
Projects
None yet
Milestone
4.0
Development

Successfully merging this pull request may close these issues.

Dynamic MapConfig from client side does not respect some options
3 participants
@vbekiaris @mdogan @mmedenjak