[
https://issues.apache.org/jira/browse/GEODE-5113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16444751#comment-16444751
]
Darrel Schneider commented on GEODE-5113:
-----------------------------------------
How is it that you are able "to configure a Maximum on an LRU Heap Eviction
Policy"?
You can not create an instance of EvictionAttributes for LRU Heap and configure
a maximum. The static factory methods on EvictionAttributes that return an
instance for LRU Heap do not set the maximum. Was the internal API being used
or does some other way exist?
Every instance of EvictionAttributes can have getMaximum called on it. Since
the maximum is never set for LRU Heap it seemed better to return zero, the java
default for an int, instead of throwing an exception. Did this change break an
existing application?
> EvictionAttributes.getMaximum() no longer throws
> UnsupportedOperationException for LRU Heap
> -------------------------------------------------------------------------------------------
>
> Key: GEODE-5113
> URL: https://issues.apache.org/jira/browse/GEODE-5113
> Project: Geode
> Issue Type: Bug
> Components: eviction
> Reporter: Fred Krone
> Priority: Major
>
>
> Previously, the EvictionAttributes.getMaximum() used to throw an
> UnsupportedOperationException if the user tried to configure a Maximum on an
> LRU Heap Eviction Policy (Apache Geode 1.4). Now Geode (and by extension,
> GemFire) will just silently return 0.
>
> in 1.4
> [https://github.com/apache/geode/blob/rel/v1.4.0/geode-core/src/main/java/org/apache/geode/internal/cache/EvictionAttributesImpl.java#L138-L144]
>
> in 1.5
> [https://github.com/apache/geode/blob/rel/v1.5.0/geode-core/src/main/java/org/apache/geode/internal/cache/EvictionAttributesImpl.java#L95-L101]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
