Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upAdd context to 2.0 storage interfaces #2823
Comments
This comment has been minimized.
This comment has been minimized.
|
@AlekSi Thanks for the interest. Yes, the plan is to add I think it makes sense to tackle the issue in tsdb first before we implement it in Prometheus as the wrapper is pretty thin. |
This comment has been minimized.
This comment has been minimized.
|
Yepp, I saw that tsdb issue. This issue is about adding context to generic storage interfaces which, eventually, will be used for cancellation signals. How they will be handled depends on specific implementations, including tsdb. In the simplest case, they can just ignore them. |
This comment has been minimized.
This comment has been minimized.
|
Yes, as you said it makes sense to add them to the shim layer now. We can
than use it in tsdb later after figuring out our desired semantics.
If you want to file a PR adding those, that would be great.
…On Thu, Jun 8, 2017 at 5:31 PM Alexey Palazhchenko ***@***.***> wrote:
Yepp, I saw that tsdb issue. This issue is about adding context to generic
storage interfaces which, eventually, will be used for cancellation
signals. How they will be handled depends on specific implementations,
including tsdb. In the simplest case, they can just ignore them.
I'm prototyping remote storage implementation now, that's why I'm
interested in adding contexts now rather then when/if tsdb support them.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2823 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEuA8iRZedMpzLaQyfFvC3I3OnNxxz8Mks5sCBPdgaJpZM4N0Lm8>
.
|
This comment has been minimized.
This comment has been minimized.
|
+1 I just came across the need for this working on the remote APIs for 2.0. |
This comment has been minimized.
This comment has been minimized.
We postponed that work. Feel free to work on it if you need it right now. I expect to return to it later. |
brian-brazil
added
priority/P3
component/local storage
kind/enhancement
priority/P2
and removed
priority/P3
labels
Jul 14, 2017
brian-brazil
referenced this issue
Jul 14, 2017
Closed
Pass context to SeriesIterator.ValueAtOrBeforeTime/RangeValues #2886
This comment has been minimized.
This comment has been minimized.
|
|
This comment has been minimized.
This comment has been minimized.
|
@AlekSi can we close this one since there is an open issue for the same in the tsdb repo |
This comment has been minimized.
This comment has been minimized.
|
Please see discussion above why those are separate issues. |
This comment has been minimized.
This comment has been minimized.
|
yep , sorry. I missed some important bits on the first read. |
AlekSi commentedJun 8, 2017
Having
context.ContextinStorage,Querier,Appenderand probably few other types would be helpful for remote storages. Even if Prometheus will usecontext.TODO()in the first 2.0 release, having at least somewhat stable interface is a good thing.I can implement it if you agree.