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
I would like to request an API for selectively invalidating vertices in the database-level cache described in 10.3 Database-Level Caching.
Use Case
When running multiple instances of Titan on different servers, one may update a certain vertex and notify other servers of the update by vertex ID. If another server acts upon the update by e.g. pushing a change event to clients, it prepares a JSON representation of the vertex to transmit. This JSON representation is likely to contain stale data from the db-cache.
Any way to circumvent the cache and directly fetch data from the storage backend would be great, without having to disable the cache altogether.
I would like to request an API for selectively invalidating vertices in the database-level cache described in 10.3 Database-Level Caching.
Use Case
When running multiple instances of Titan on different servers, one may update a certain vertex and notify other servers of the update by vertex ID. If another server acts upon the update by e.g. pushing a change event to clients, it prepares a JSON representation of the vertex to transmit. This JSON representation is likely to contain stale data from the db-cache.
Any way to circumvent the cache and directly fetch data from the storage backend would be great, without having to disable the cache altogether.
Example
APIs like these would be handy:
Vertex::invalidateCache()
TitanGraph::invalidateCache(Object... ids)
The text was updated successfully, but these errors were encountered: