> I got stuck how to manage to do that. Github projects with a not-yet-working sample turn out to be helpful.
>Ideally it could be like a mix of REST filter + filtering in generated java code but There are at least two ways to do that: 1) ProjectableFilterableTable. At execution time you'll be given a set of filters and you'll be able to pick the "supported by your REST" set of filters. 2) MongoFIlter like approach. You create a rule that matches "Filter(conditions, RestTableScan)", decomposes filter expressions to the "supported ones" and rewrites the Filter to Filter(non_supported_by_rest_conditions, RestTableScan(supported_by_rest_filters)). This way at query planning time you'll be able to pass "the set of filters to RestTableScan, so it can use when calling the REST"
