You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At this point, the batch document reads and document writes are semantically wrong. They are internally replacing a batch request with a number of separate requests, which changes the expected behavior.
Worse than that, the implementation parses/converts all inputs at once, but serializes and writes them one-by-one. A proper implementation would create something like a growing_tape_t and parse+convert+serialize entries one-by-one, but would submit those for write just once!
Bringing back the ukv_format_docs_internal_k would allow us to immediately choose the optimal underlying serialization format to avoid following conversions in the backend.
The text was updated successfully, but these errors were encountered:
At this point, the batch document reads and document writes are semantically wrong. They are internally replacing a batch request with a number of separate requests, which changes the expected behavior.
Worse than that, the implementation parses/converts all inputs at once, but serializes and writes them one-by-one. A proper implementation would create something like a
growing_tape_t
and parse+convert+serialize entries one-by-one, but would submit those for write just once!Bringing back the
ukv_format_docs_internal_k
would allow us to immediately choose the optimal underlying serialization format to avoid following conversions in the backend.The text was updated successfully, but these errors were encountered: