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

Propagate warnings through context #298

Merged
merged 4 commits into from
Aug 16, 2023

Conversation

fpetkovski
Copy link
Collaborator

The engine does not return warnings from storage which causes problems with partial response detection in Thanos.

I initially thought we had to change the interface of each operator, but @MichaHoffmann had a neat idea to propagate warnings through the context since they have no impact on flow control.

The engine does not return warnings from storage which causes problems
with partial response detection in Thanos.

I initially thought we had to change the interface of each operator,
but @MichaHoffmann had a neat idea to propagate warnings through the context
since they have no impact on flow control.

Signed-off-by: Filip Petkovski <filip.petkovsky@gmail.com>
Signed-off-by: Filip Petkovski <filip.petkovsky@gmail.com>
Signed-off-by: Filip Petkovski <filip.petkovsky@gmail.com>
Copy link
Member

@saswatamcode saswatamcode left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

Signed-off-by: Filip Petkovski <filip.petkovsky@gmail.com>
Copy link
Contributor

@MichaHoffmann MichaHoffmann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@saswatamcode saswatamcode merged commit c64fc7b into thanos-io:main Aug 16, 2023
fpetkovski added a commit to fpetkovski/promql-engine that referenced this pull request Aug 16, 2023
This is a follow up commit to thanos-io#298 which
enables propagating warnings from remote engines into the distributed
query context.
fpetkovski added a commit to fpetkovski/promql-engine that referenced this pull request Aug 16, 2023
This is a follow up commit to thanos-io#298 which
enables propagating warnings from remote engines into the distributed
query context.
fpetkovski added a commit to fpetkovski/promql-engine that referenced this pull request Aug 16, 2023
This is a follow up commit to thanos-io#298 which
enables propagating warnings from remote engines into the distributed
query context.

Signed-off-by: Filip Petkovski <filip.petkovsky@gmail.com>
fpetkovski added a commit that referenced this pull request Aug 16, 2023
This is a follow up commit to #298 which
enables propagating warnings from remote engines into the distributed
query context.

Signed-off-by: Filip Petkovski <filip.petkovsky@gmail.com>
Player256 pushed a commit to Player256/promql-engine that referenced this pull request Aug 16, 2023
* Propagate warnings through context

The engine does not return warnings from storage which causes problems
with partial response detection in Thanos.

I initially thought we had to change the interface of each operator,
but @MichaHoffmann had a neat idea to propagate warnings through the context
since they have no impact on flow control.

Signed-off-by: Filip Petkovski <filip.petkovsky@gmail.com>

* Fix lint

Signed-off-by: Filip Petkovski <filip.petkovsky@gmail.com>

* Replace fmt.Errorf with errors.New

Signed-off-by: Filip Petkovski <filip.petkovsky@gmail.com>

* Use custom type as key

Signed-off-by: Filip Petkovski <filip.petkovsky@gmail.com>

---------

Signed-off-by: Filip Petkovski <filip.petkovsky@gmail.com>
Player256 pushed a commit to Player256/promql-engine that referenced this pull request Aug 16, 2023
This is a follow up commit to thanos-io#298 which
enables propagating warnings from remote engines into the distributed
query context.

Signed-off-by: Filip Petkovski <filip.petkovsky@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants