-
Notifications
You must be signed in to change notification settings - Fork 647
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
Fuseki to send ETag
response headers
#2305
Comments
Hashing as a general solution doesn't extend to large graphs. Transactions are serializable. One way to generate a unique fingerprint would be to have UUID per database version. Another way, with more information, is to have a UUID per dataset (fixed) then create the etag from that id+version and increment the version each write-commit. Blank nodes don't matter. These tags are independent of content but unique to the version per server. (does not work for replication with RDF Delta) |
Presumably this might require some new interface/API for Dataset implementations to allow them to expose this version information ? With the variety of implementations that users use in the wild eg Text Indexing, General purpose datasets this would also need to carry through wrappers in some form |
I was thinking |
ETags would be applied by Fuseki, possibly via the data service at the endpoint. A UUID per (storage) dataset would be useful generally as being global and temporal unique. |
Version
4.7.0
Feature
Graphs without bnodes can be safely hashed and the hash can be used as a strong
ETag
value.Graphs with bnodes can be hashed and the hash could be used as a weak
ETag
value?Are you interested in contributing a solution yourself?
Perhaps?
The text was updated successfully, but these errors were encountered: