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.

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

Querying a storenode should not require keeping local history #481

Closed
jm-clius opened this issue Apr 12, 2021 · 1 comment
Closed

Querying a storenode should not require keeping local history #481

jm-clius opened this issue Apr 12, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@jm-clius
Copy link
Contributor

Currently querying a storenode for history requires mounting store protocol. Currently this implies that every node querying history will itself act as a storenode and keep local history. The configuration for keeping history and querying for history needs to be separated.

Previously this separate configuration was allowed, but resulted in nil access errors (#439) prompting a change in how/when protocols are mounted. It should be possible, though, to have store protocol mounted and query for historical messages from storenode without having to keep local history.

Acceptance criteria

  • A wakunode2 can be configured with a storenode and successfully query that storenode for historical messages without having to be a "full" storenode that keeps local history itself.
@oskarth
Copy link
Contributor

oskarth commented Apr 27, 2021

Probably duplicate of above, closing

@oskarth oskarth closed this as completed Apr 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants