NPE is a known issue and it's already fixed. You can build from master and
check if it works for you.
As for the original issue, can you provide the full test code? Also did you
deploy classes on server nodes?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Date-compare-fetch-in-the-Query-tp3308p3348.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Just wanted share solution i found on the exception:
javax.cache.CacheException: Failed to run reduce query locally.
by putting *limit* to the Query i was able to fetch the data
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Date-compare-fetch-in-the-Query-tp3308p3339.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Can you provide the full test that you're running? Did you check the logs for
exceptions?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Date-compare-fetch-in-the-Query-tp3308p3326.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
No Filter is not happening
p.getUpdatedDate().before(get1HourBefore()) --- Both are java.util.Date
Objects
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Date-compare-fetch-in-the-Query-tp3308p3322.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi,
Can query itself doesn't do any comparisons, it simply calls the filter you
provided. Does this happen?
Did you verify that the filter is implemented correctly (e.g., that
get1HourBefore() returns the correct value for comparison)?
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Date-compare-fetch-in-the-Query-tp3308p3315.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.