5 ms·

Is there a 'limits' doc somewhere? how many objects can an array hold? what is the depth limit for nested data?

ovaistariq 4y ago
The limitations are listed here: https://docs.tigrisdata.com/apidocs/#section/Limitations https://docs.tigrisdata.com/apidocs/#section/Limitations Apart from the size of the document, there is no limit on the size of the array or the depth of nested data. We plan on substantially increasing the document size limit.
- frellus 4y ago
  "The maximum allowed document size is 100KB" I suppose this is due to the FDB limitations, so this obviously isn't a blobstore nor will it ever be (?). For example, we need to store video and image files which are easily 100KB - 1GB in size. Tigris or FDB are great to store metadata in (and the metadata is just as important to us as anything) but the blob storage is a bit of a problem. Would be interesting to integrate something with, for example, MinIO or S3.
  - hchaudhary 4y ago
    Thank you for explaining your use case. This is one of the features we have in mind to support use cases similar to yours for storing videos, images, etc. But this may not happen this year. It would be great if you could add something here https://github.com/tigrisdata/tigris/issues https://github.com/tigrisdata/tigris/issues that will help us track and monitor similar use cases.
    - frellus 4y ago
      Done, and thanks a lot for the invitation to add, happy to contribute https://github.com/tigrisdata/tigris/issues/562 https://github.com/tigrisdata/tigris/issues/562
      - hchaudhary 4y ago
        Thank you! appreciate your contributions. Please do not hesitate for future contributions in terms of feature requests, code contributions, etc.
hchaudhary 4y ago
There is no limit on array size or on nested data; the only limit is on the document size, which we will slowly relax. But if the object is deeply nested, then we need to extract all these nested keys(which may be slightly costly) and index them as we also allow filtering on any key of the object. If the depth is not significant then the cost is negligible.

The limitations are listed here: https://docs.tigrisdata.com/apidocs/#section/Limitations https://docs.tigrisdata.com/apidocs/#section/Limitations Apart from the size of the document, there is no limit on the size of the array or the depth of nested data. We plan on substantially increasing the document size limit.

frellus 4y ago
"The maximum allowed document size is 100KB" I suppose this is due to the FDB limitations, so this obviously isn't a blobstore nor will it ever be (?). For example, we need to store video and image files which are easily 100KB - 1GB in size. Tigris or FDB are great to store metadata in (and the metadata is just as important to us as anything) but the blob storage is a bit of a problem. Would be interesting to integrate something with, for example, MinIO or S3.
- hchaudhary 4y ago
  Thank you for explaining your use case. This is one of the features we have in mind to support use cases similar to yours for storing videos, images, etc. But this may not happen this year. It would be great if you could add something here https://github.com/tigrisdata/tigris/issues https://github.com/tigrisdata/tigris/issues that will help us track and monitor similar use cases.
  - frellus 4y ago
    Done, and thanks a lot for the invitation to add, happy to contribute https://github.com/tigrisdata/tigris/issues/562 https://github.com/tigrisdata/tigris/issues/562
    - hchaudhary 4y ago
      Thank you! appreciate your contributions. Please do not hesitate for future contributions in terms of feature requests, code contributions, etc.

hchaudhary 4y ago

There is no limit on array size or on nested data; the only limit is on the document size, which we will slowly relax. But if the object is deeply nested, then we need to extract all these nested keys(which may be slightly costly) and index them as we also allow filtering on any key of the object. If the depth is not significant then the cost is negligible.