Hello!
I suggest generating a surrogate affinity key in this case, such as
@AffinityKeyMapped String affKey = key1 + "-" + key2;
You can also file a feature request against Apache Ignite JIRA, but given
the lack of community interest towards indexing nested objects, it is
unlikely to be done.
Hello team,
If we generate @AffinityKeyMapped field from multiple other fields and then use
those original fields in SQL WHERE condition, they are not used for partition
pruning:
https://ignite.apache.org/docs/latest/perf-and-troubleshooting/sql-tuning#partition-pruning
Because Ignite doesn't
