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

Rework RequestPipeline design #40

Open
Tracked by #69
stevejgordon opened this issue Jan 25, 2022 · 0 comments
Open
Tracked by #69

Rework RequestPipeline design #40

stevejgordon opened this issue Jan 25, 2022 · 0 comments

Comments

@stevejgordon
Copy link
Collaborator

stevejgordon commented Jan 25, 2022 •
edited
Loading

We should review if we can rework the pipeline concepts before GA to remove additional allocations per request. Right now, the IRequestPipelineFactory and IRequestPipeline 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.
@stevejgordon stevejgordon added the GA Target completion before GA 8.0.0 label Jan 25, 2022
@stevejgordon stevejgordon removed the GA Target completion before GA 8.0.0 label Nov 4, 2022
@stevejgordon stevejgordon changed the title Optimise IRequestPipeline Rework RequestPipeline design Jun 9, 2023
@stevejgordon stevejgordon mentioned this issue Jun 9, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@stevejgordon