Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BLOB type is not preserved by replication #8044

Open
aafemt opened this issue Mar 14, 2024 · 4 comments
Open

BLOB type is not preserved by replication #8044

aafemt opened this issue Mar 14, 2024 · 4 comments

Comments

@aafemt
Copy link
Contributor

aafemt commented Mar 14, 2024

Stream BLOBs become segmented in target database.

@dyemanov
Copy link
Member

I suppose it could be easily done by a separate tag e.g. opStoreBlob2. But given that we already had a suggestion to drop segmented blobs at all (in favor of stream blobs), maybe it should be considered instead?

@aafemt
Copy link
Contributor Author

aafemt commented Mar 17, 2024

opStreamedBlob would sound better for me (no impression that it supersede opStoreBlob at least).

Segmented BLOBs has its own usage. I'll vote against their dropping.

@sim1984
Copy link

sim1984 commented Mar 18, 2024

I would not vote for the abolition of segmented BLOBs, but rather for changes to the type of default BLOBs. By default, BLOBs are streaming, but if you really want to, then we make them segmented. Segmented BLOBs have only one use - to store lists of objects of the same size. In other cases, they have no advantages over streaming ones.

@aafemt
Copy link
Contributor Author

aafemt commented Mar 18, 2024

Size of objects may vary but yes, preserving boundaries between them is a useful feature. The same way in network world stream-oriented TCP is mostly used but message-oriented UDP still keep a niche.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants