Hazelcast query long(Int64) type doesn't work NOT IN condition
See original GitHub issueI try to use NOT IN
but I am not successed. It is throw:
InvalidOperationException: Exception of type 'System.InvalidOperationException' was thrown.
and lots of map and property name.
My query: Id NOT IN ( 13, 17, 22533)
So I try that: Id NOT IN ( 13L, 17L, 22533L)
In that case, exception thrown like HazelcastException: 'For input string: "13L"'
Then I change my query to Id IN ( 13, 17, 22533)
, it worked.
Why IN condition is working but NOT IN condition is not working, I still dont understand.
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Hazelcast not working correctly with SqlPredicate and ...
This is not an option when working with spring-data-hazelcast as it always converts @Query based searches to SqlPredicates.
Read more >Hazelcast Platform Operator API Docs
This is a reference for the Hazelcast Platform Operator API types. These are all the types and fields that are used in the...
Read more >Locking Maps
Hazelcast offers two ways of locking map entries: pessimistic locking and optimistic locking. Hazelcast uses and manages its own partition threads. Each ...
Read more >Queue
Hazelcast distributed queue performs no batching while iterating over the queue. All items are copied locally and iteration occurs locally. Creating a Queue....
Read more >Querying Maps with the Predicate API
The Predicates class includes many operators for your query requirements. ... Hazelcast does not check the validity of JSON strings that are added...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Note that querying with the wrong field does not affect the server and other clients. It only returns the wrong result where the query is done.
If there is a client that does
writer.WriteLong("id", Id);
with wrong name, this could affect the server and other clients. Since restarting solved your problem, I think there is a problem with yourWritePortable
method in one of your clients.Since restart solves your problem, you need to replace your faulty clients with correct ones and restart the server one final time. Since the mystery is solved and this is not a bug but a wrong usage, I am closing the issue.
Ok, you are right about that. When I restart, it is worked. But still it does not solve my problem 😃 Because I have multiple c# clients. One of them could query like that. After a while the problem shown again.
My server version: 3.11.2 C# clients all of them: 3.10