Apache Pinot

Hi <@U01G51G5VCG> - I think you want to check out partitioning on <https://docs.pinot.apache.org/operators/operating-pinot/tuning/routing>, as a way of avoiding sending the query to all servers (with broker-side pruning).

Thanks <@U01ECR21TEE>. I did look at this, though i felt this might be required if the data is partitioned by some dimensional field. Is this also required for time dimension field as well?

You’re right that the time dimension is special, but (sadly) I don’t know whether that changes how you’d configure things to prune via partitioning.

```          if (RoutingConfig.TIME_SEGMENT_PRUNER_TYPE.equalsIgnoreCase(segmentPrunerType)) {
            TimeSegmentPruner timeSegmentPruner = getTimeSegmentPruner(tableConfig, propertyStore);
            if (timeSegmentPruner != null) {
              segmentPruners.add(timeSegmentPruner);
            }
          }```

Based on quick check at the code: we do have time based segment pruning at the broker level ^^

<@UDQU92KBK> Is the broker level pruning based on time enabled by default? Or do i need to set the routing config accordingly?

Hi <@U01G51G5VCG> , the broker time pruner is not enabled by default. To enable it, you need to add routing config like following:
```"routing": {
    "segmentPrunerTypes": ["Time"]
  }```

Thanks. Let me try this out. Though one question, is this supported in version 0.6?

It's merged recently, seems like it's not in 0.6.

<@U01D96G20BF> could we update the docs as well?

<@UDQU92KBK> Any idea when we'll cut next release?

Oh this is not part of the 0.6.0 release, perhaps we should update the doc with the next release then.

<@UDQU92KBK> asking last question again, do you know when will next version be released? So that we could take advantage of this

There isn't a concrete plan that I am aware of, however, we have been trying to get one every couple of months (last one was Nov/Dec). We can bring this up in the dev channel.