asfgit closed pull request #8154: NIFI-12509 Changing default TTL of
HazelcastMapCacheClient
URL: https://github.com/apache/nifi/pull/8154
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specifi
turcsanyip commented on code in PR #8154:
URL: https://github.com/apache/nifi/pull/8154#discussion_r1426583899
##
nifi-nar-bundles/nifi-hazelcast-bundle/nifi-hazelcast-services/src/main/java/org/apache/nifi/hazelcast/services/cacheclient/HazelcastMapCacheClient.java:
##
@@ -78,1
simonbence commented on code in PR #8154:
URL: https://github.com/apache/nifi/pull/8154#discussion_r1426407692
##
nifi-nar-bundles/nifi-hazelcast-bundle/nifi-hazelcast-services/src/main/java/org/apache/nifi/hazelcast/services/cacheclient/HazelcastMapCacheClient.java:
##
@@ -78,1
turcsanyip commented on code in PR #8154:
URL: https://github.com/apache/nifi/pull/8154#discussion_r1425785361
##
nifi-nar-bundles/nifi-hazelcast-bundle/nifi-hazelcast-services/src/main/java/org/apache/nifi/hazelcast/services/cacheclient/HazelcastMapCacheClient.java:
##
@@ -78,1
simonbence opened a new pull request, #8154:
URL: https://github.com/apache/nifi/pull/8154
Current default TTL is 0, which in terms of Hazelcast means that the cache
will be ever-growing. Having Max Size Policy on the imap (backs the cache) can
be reached via instance (server side) so it lo
