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
{{ message }}
This repository has been archived by the owner on Apr 11, 2023. It is now read-only.
The order of results returned from a call to EDV is currently determined by the underlying storage provider. We'd like a way to allow a client to control this.
This is tricky because all the documents stored in EDV are encrypted by the client, so the EDV server doesn't really have anything (useful) it can base a sort order on. Encrypted index name + values are encrypted hash values, and so there's no real useful order there.
Probably the only thing it could sort on is based on the time the data was inserted into the underlying database.
Also, the EDV spec doesn't specify sort order options. If we add this capability, we should get it in the spec.
If we want to do this, there are some options...
Allow sort based on the limited information EDV knows (insertion time)
Investigate the possibility of allowing limited plaintext metadata to be used with encrypted documents. This will be tricky from a standards compliance point of view.
The text was updated successfully, but these errors were encountered:
The order of results returned from a call to EDV is currently determined by the underlying storage provider. We'd like a way to allow a client to control this.
This is tricky because all the documents stored in EDV are encrypted by the client, so the EDV server doesn't really have anything (useful) it can base a sort order on. Encrypted index name + values are encrypted hash values, and so there's no real useful order there.
Probably the only thing it could sort on is based on the time the data was inserted into the underlying database.
Also, the EDV spec doesn't specify sort order options. If we add this capability, we should get it in the spec.
If we want to do this, there are some options...
The text was updated successfully, but these errors were encountered: