We currently have a sort of in-memory cache by virtue of how Tracks work internally, but that's not at all set up for the type of random access that would be required by FETCH. Consider adding a minimal in-memory or on-disk cache component so we can serve FETCH requests locally and also locally fulfill Joining Fetch requests.
We currently have a sort of in-memory cache by virtue of how Tracks work internally, but that's not at all set up for the type of random access that would be required by FETCH. Consider adding a minimal in-memory or on-disk cache component so we can serve FETCH requests locally and also locally fulfill Joining Fetch requests.