We have a setup where we have a time column, let's say "timestamp", and then we have some other ID columns like "memberId" and "eventTypeId". In our tableIndexConfig we have something like

"tableIndexConfig": {
      "segmentPartitionConfig": {
        "columnPartitionMap": {
          "memberId": {
            "functionName": "Murmur",
            "numPartitions": 48
          },
          "eventTypeId": {
            "functionName": "Murmur",
            "numPartitions": 48
          }
        }
      },

and our routing config looks like

"routing": {
      "segmentPrunerTypes": [
        "time",
        "partition"
      ],
      "instanceSelectorType": "replicaGroup"
    },

I am curious when we have a query where we are specifying all of these fields in the WHERE clause, like

SELECT count(*) count from my_table 
  WHERE memberID = 489
    AND timestamp > 1748964616000
    AND eventTypeId = 4

Is it expected that all of this pruning will work in combination, so the broker can prune segments by these 3 different columns? I have read the docs here which speak to each one individually, but not in combination necessarily https://docs.pinot.apache.org/operators/operating-pinot/tuning/routing