Bump ravendb from 7.2.3.post1 to 7.2.3.post2

[dependabot]

Bumps ravendb from 7.2.3.post1 to 7.2.3.post2.

Release notes

Sourced from ravendb's releases.

7.2.3.post2 - Bulk Insert Performance & others

Bulk insert got a performance pass: entities are converted straight to their JSON-able form without a serialize/parse round trip, finished buffers are handed to the sender instead of being copied, and the client now applies backpressure instead of buffering without a bound when the server reads slower than the client writes. BulkInsertOptions.use_compression is honored again and gzips the request body. Time series timestamps written through bulk insert are no longer shifted by the machine's local UTC offset. The client also gained an on-disk topology cache (a port of .NET's TopologyLocalCache), enabled by default, and the logs configuration API was rewritten for the RavenDB 7.x logging schema.

Docs: Bulk insert, Conventions, Time series - append

PyPi: https://pypi.org/project/ravendb/7.2.3.post2/

Highlights

Bulk insert performance

Writing a document no longer goes through json.dumps followed by json.loads - the entity is converted directly into its JSON-able form. A full buffer is handed over to the thread sending the request rather than deep-copied, and flushing is decided by the buffer size alone. The queue of buffers waiting to be sent is now bounded (BulkInsertOperation.MAX_BUFFERS_TO_FLUSH), so a server that reads slower than the client writes slows the client down instead of growing its memory. BulkInsertOptions.use_compression was previously ignored; it now gzips the outgoing body.

from ravendb.documents.bulk_insert_operation import BulkInsertOptions
options = BulkInsertOptions(use_compression=True)
with store.bulk_insert(options=options) as bulk_insert:
for i in range(100_000):
bulk_insert.store(User(name=f"user/{i}"))

If the request carrying the data ends before all of it was sent, the client raises instead of waiting forever for a free slot:

from ravendb.exceptions.documents.bulkinsert import BulkInsertAbortedException
try:
with store.bulk_insert() as bulk_insert:
bulk_insert.store(User(name="users/1"))
except BulkInsertAbortedException as e:
print(f"Bulk insert aborted: {e}")

New constants: BulkInsertOperation.MAX_BUFFERS_TO_FLUSH New methods: Utils.entity_to_dict reimplemented without a JSON round trip

On-disk topology cache

The client now persists the database and cluster topology to disk on every topology update, and seeds itself from that cache when none of the initial urls can be reached at startup. This mirrors .NET's TopologyLocalCache and is enabled by default, writing to a per-user OS cache directory (%LOCALAPPDATA%\ravendb\topology, ~/Library/Caches/ravendb/topology, or $XDG_CACHE_HOME/ravendb/topology). Caching is best-effort: a failure to read or write the cache never breaks a topology update.

from ravendb import DocumentStore
store = DocumentStore(["http://localhost:8080"], "Northwind")
store.conventions.topology_cache_location = "/var/cache/my-app/ravendb"
or opt out entirely
store.conventions.disable_topology_cache = True
store.initialize()
</tr></table>

... (truncated)

Commits

• fbc98d1 Merge pull request #307 from poissoncorp/RDBC-1104-version-7.2.3.post2
• 55403c1 RDBC-1104 Bump version for hotfix to 7.2.3.post2
• 395776e Merge pull request #306 from poissoncorp/RDBC-1104-bulk-insert-performance
• ebc716f Compress the bulk insert body when the option asks for it
• d7a2dc6 Make bulk insert wait for the server instead of buffering without a bound
• b1b4e52 Hand the finished buffer over instead of copying it twice
• 49c0f41 Let the buffer size alone decide when to flush
• afd28cb Convert an entity to a document without a JSON round trip
• 813ba79 Pin the entity-to-document conversion semantics with unit tests
• 0c9fa83 Merge pull request #304 from poissoncorp/unskip-tests
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)