This is a dumb bug that came in with /api/v2 because we needed min/max time to clamp the search window. The time cache needs to be attached to the ClusterEntry so that it can be shared between connections. Right now it is recreated too often because it is recreated when we create a connection.
This is a dumb bug that came in with /api/v2 because we needed min/max time to clamp the search window. The time cache needs to be attached to the ClusterEntry so that it can be shared between connections. Right now it is recreated too often because it is recreated when we create a connection.