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.

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

Async puts should reflect to near-cache immediately when its future.get() returns #7155

Closed
serkan-ozal opened this issue Dec 23, 2015 · 0 comments · Fixed by #7167
Closed
Assignees
Labels
Source: Internal PR or issue was opened by an employee Team: Client Type: Enhancement
Milestone

Comments

@serkan-ozal
Copy link
Contributor

Currently at client side, when LocalUpdatePolicy is CACHE, in async puts, entries are put to near-cache in async way from another task when response is received. But with this way, when future.get() returns, entry might not be inside near-cache (but it will be there eventually).

@serkan-ozal serkan-ozal self-assigned this Dec 23, 2015
@serkan-ozal serkan-ozal added this to the 3.6 milestone Dec 23, 2015
@enesakar enesakar modified the milestones: 3.6.1, 3.6 Dec 23, 2015
@serkan-ozal serkan-ozal modified the milestones: 3.6, 3.6.1 Dec 24, 2015
@enesakar enesakar modified the milestones: Backlog, 3.6 Jan 5, 2016
@serkan-ozal serkan-ozal modified the milestones: 3.7, Backlog Feb 23, 2016
@mmedenjak mmedenjak added the Source: Internal PR or issue was opened by an employee label Aug 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Source: Internal PR or issue was opened by an employee Team: Client Type: Enhancement
Projects
None yet
3 participants