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

query cache xml configuration Eviction policy must be set to an eviction policy type rather than null #9988

Closed
Danny-Hazelcast opened this issue Feb 28, 2017 · 1 comment

Comments

@Danny-Hazelcast
Copy link
Member

@Danny-Hazelcast Danny-Hazelcast commented Feb 28, 2017

3.8

i get com.hazelcast.config.InvalidConfigurationException: Eviction policy must be set to an eviction policy type rather than null, NONE, RANDOM or custom eviction policy comparator must be specified!

i have the xml configured as.
<eviction eviction-policy="NONE"></eviction>

when i do not explicitly configure <eviction eviction-policy="NONE"></eviction> default works without issue

@Danny-Hazelcast
Copy link
Member Author

@Danny-Hazelcast Danny-Hazelcast commented Feb 28, 2017

Ahmet Mırçık
apart from exception message (it seems to need clarification), queryCache doesn't support NONE, RANDOM or null as an eviction policy. It uses the same internal eviction mechanism with icache. They both don't support those policies.

@jerrinot jerrinot modified the milestones: 3.8.1, 3.8.2 Mar 20, 2017
@tombujok tombujok modified the milestones: 3.8.3, 3.8.2 May 8, 2017
@tombujok tombujok modified the milestones: 3.8.4, 3.8.3 Jun 20, 2017
@tombujok tombujok modified the milestones: 3.8.5, 3.8.4 Jul 31, 2017
@tombujok tombujok modified the milestones: 3.8.6, 3.8.5 Aug 21, 2017
@tombujok tombujok modified the milestones: 3.8.6, 3.8.7 Sep 14, 2017
@ahmetmircik ahmetmircik self-assigned this Sep 14, 2017
@ahmetmircik ahmetmircik modified the milestones: 3.8.7, 3.8.6 Sep 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

5 participants