-
Notifications
You must be signed in to change notification settings - Fork 143
Issues: jhalterman/expiringmap
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
When the size reaches maxSize, the first Key will receive two expired callbacks
#90
opened Jul 29, 2024 by
chenxin4839
[FEATURE] ExpiringMap builder method to configure the map not to accept null values
#79
opened Mar 23, 2022 by
rohit5ram
ExpiringMap may return already expired entry (ExpirationPolicy.ACCESSED)
#77
opened Feb 2, 2022 by
nuessgens
Is it really thread safe?! it behaves differently than ConcurrentHahMap. please run code below.
#75
opened Nov 6, 2021 by
abprojects055
Ability to expire entries on map access instead of in scheduled executor
#61
opened Feb 28, 2019 by
qualidafial
Make computeIfAbsent / computeIfPresent operations atomic
#59
opened Aug 7, 2018 by
egor-doudkin-mpf
When Expiration Policy is ACCESSED, New short duration time does not is rescheduled.
#57
opened May 14, 2018 by
reachmirai
Variable Expiration Map expires more than entries count in the Map
#49
opened Jun 18, 2017 by
erdalbitik
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.