on Document view we do attempt to download the vector-cache file and retain on the client side so can view the text, metadata, and other assets.
However, when the vector-cache is sufficiently large (like 100MB+) the client will fail to parse such a large JSON body, not to mention that it also takes forever to load - if it does.
We can dramatically improve the UX here by dropping the support of trying to read arbitrary-size JSON files since we can just read the metadata exactly from the vector database given that we are using pagination now.
on Document view we do attempt to download the vector-cache file and retain on the client side so can view the text, metadata, and other assets.
However, when the vector-cache is sufficiently large (like 100MB+) the client will fail to parse such a large JSON body, not to mention that it also takes forever to load - if it does.
We can dramatically improve the UX here by dropping the support of trying to read arbitrary-size JSON files since we can just read the metadata exactly from the vector database given that we are using pagination now.