Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Do not separate dhstore backends and non-dhstore backends. #153

Open
gammazero opened this issue Sep 9, 2023 · 1 comment
Open

Do not separate dhstore backends and non-dhstore backends. #153

gammazero opened this issue Sep 9, 2023 · 1 comment
Assignees
@gammazero
Labels
question Further information is requested

Comments

@gammazero
Copy link
Collaborator

gammazero commented Sep 9, 2023 •
edited
Loading

Now that dhstore supports non-encrypted lookups (dhfind), there is no need to separate dhstore backends and not-dhstore backends, unless we intend to allow mixed dh and non-dh storage deployments.
@gammazero gammazero self-assigned this Sep 9, 2023
@gammazero
Copy link
Collaborator Author

We need to keep the ability to specify separate backends as long as we continue to provide support for both double-hashed and non-double-hashed storage. There are at least two situations where an indexer operator may need this:

  1. When maintaining existing indexers with non-double-hashed storage and adding new indexers that do double hashed indexing.
  2. When assigning some publishers to indexers that use double-hashed storage, and other publisher to indexers that do not.

@gammazero gammazero added the question Further information is requested label Sep 10, 2023
gammazero added a commit that referenced this issue Sep 10, 2023
@gammazero
Ne separate dh and non-dh backends
2612b59 
Now that dhstore supports non-encrypted lookups (dhfind), there is no need to separate dhstore backends and not-dhstore backends.

This assumes there is no support for mixed dh and non-dh storage deployments.

Fixes #153
gammazero added a commit that referenced this issue Sep 19, 2023
@gammazero
Ne separate dh and non-dh backends
bc285f1 
Now that dhstore supports non-encrypted lookups (dhfind), there is no need to separate dhstore backends and not-dhstore backends.

This assumes there is no support for mixed dh and non-dh storage deployments.

Fixes #153
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gammazero gammazero

Labels
question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gammazero