-
Notifications
You must be signed in to change notification settings - Fork 13
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
Rework RequestPipeline
design
#40
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should review if we can rework the pipeline concepts before GA to remove additional allocations per request. Right now, the
IRequestPipelineFactory
andIRequestPipeline
are public to support VirtualizedCluster, but their API may break before GA.We should consider a design that doesn't force all consumers to use the existing request pipeline designed for distributed, multi-node scenarios. This allocates per request and can be avoided in situations where we have a single URL (node) to communicate with, such as when using ES Cloud.
It would be nice to avoid all "products" having to know about concepts such as pinging and sniffing.
The text was updated successfully, but these errors were encountered: