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

Hazelcast 3.3.X Expiration Time should not be updated #3923

Closed
atoppi opened this issue Oct 27, 2014 · 0 comments · Fixed by #3934
Closed

Hazelcast 3.3.X Expiration Time should not be updated #3923

atoppi opened this issue Oct 27, 2014 · 0 comments · Fixed by #3934
Assignees
@ahmetmircik
Labels
Team: Core Type: Defect
Milestone
3.3.3

Comments

@atoppi
Copy link

atoppi commented Oct 27, 2014

In Hazelcast 3.3.X series, Expiration Time = Creation Time + TTL. Its value is updated on every set operation on a map, but Hazelcast uses only the first value set for ExpirationTime. So a getExpirationTime() returns a wrong and misleading value.

For more information see #3920 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ahmetmircik ahmetmircik

Labels
Team: Core Type: Defect
Projects
None yet
Milestone
3.3.3
Development

Successfully merging a pull request may close this issue.

Fixes expiration time changes after TTL updates ahmetmircik/hazelcast
3 participants
@pveentjer @ahmetmircik @atoppi