Not quite yet. At the moment indexes are pure key-value pairs to prevent deserialization.
Anyhow we want to redesign the overall indexing system into a general SPI. This way you could plug in any kind of indexing. We would love to join forces with the community, especially with people having different needs (like yours) to get all of the important bits right.
What do you think, any interest / time to work on this?
Thanks
Chris
Does Hazelcast support-
1. storing location details as key or by creating index over location object
2. querying on location using predicates or other apis like near (location, radius), between (location1, location 2)