You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@polaris.apache.org by "snazy (via GitHub)" <gi...@apache.org> on 2026/05/18 13:00:22 UTC
[PR] NoSQL: Fix batched multipart NoSQL object fetches [polaris]
snazy opened a new pull request, #4475:
URL: https://github.com/apache/polaris/pull/4475
The NoSQL backend has a hard size limit for individual rows. Objects that exceed this limit are split across multiple database rows. The number of "parts" is noted as a _hint_ in the object-id. In case that hint is wrong, which can happen when such large objects are _updated_ (replaced), the fetch/read logic can behave wrong. This change fixes this behavior.
There is currently no use case for updating/replacing such objects, so this is a proactive hardening fix.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@polaris.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] NoSQL: Fix batched multipart NoSQL object fetches [polaris]
Posted by "snazy (via GitHub)" <gi...@apache.org>.
snazy merged PR #4475:
URL: https://github.com/apache/polaris/pull/4475
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@polaris.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org