add offset and origin options to time_bucket_gapfill

[mmouterde]

Relevant system information:

• TimescaleDB version : 1.3.0

Describe the bug

• I'm using time_bucket function with the offset option.
• I would like to use the new gapfilling feature but the offset option is not provided.
• I can't benefit from the gapfilling feature without regressions.

Expected behavior time_bucket_gapfill takes an offset option

[k-rus]

Thank you for requesting the feature. We will followup.

[allstream]

Origin should be implemented as well, it's hard to use the gapfilling features without origin and offset since the data being aggregated isn't even within the range you essentially query for, but instead is seemingly the closest multiple of the bucket size from the start time and on...

[ricky-sb]

instead is seemingly the closest multiple of the bucket size from the start time and on...

Could you elaborate what you mean here?

And does anyone have any workarounds at the moment to implement this feature? Like could you get feature parity by tuning your query parameters and dealing with it on the client?

[PhilippS93]

Hi everyone, is this already on the roadmap?

Thanks!

[ateuber]

I spent too much time today trying to achieve this with the workaround mentioned in #1545, but it is too complicated (we also need to interpolate). Initially I expected that the start parameter would be enough, so I think this behavior should be mentioned in the time_bucket_gapfill documentation.

[Sytten]

Can we have this on the roadmap I also spent half a day before realizing why all my days were wrong :(

[eloyekunle]

it's a big API inconsistency since one would naturally expect time_bucket and time_bucket_gapfill to have similar behaviour everywhere else apart from the gap-filling itself.

[brakonstantin]

Is there a way to find out whether this issue is going to be addressed?

[jonatas]

Hello @brakonstantin, we coordinate our efforts based on our community votes. Here are the latest priorities. Please upvote to help us to prioritize it in the next months.

[diego-escobedo]

This would be awesome!

[aorticweb]

This would be very useful

[tomasrosauer]

This would be very useful!

[luislvasquez]

I need this so much right now :100:!! Any updates on this?

[Rayman-katib]

This would be awesome!

[jontingvold]

I'm also missing this feature.

[melicheradam]

+1, Would be great

[zaycev]

+1, this would be very handy

[aabrodskiy]

is there any update on this issue? been open since 2019 and without the "origin" parameter the time_bucket_gapfill function is effectively useless as it does not align with the requested datetime period.

[miguetronic]

Please make it real!

[MichaelSaucier]

Origin

Absolutely. We need the same fix for offset and origin to make time_bucket_gapfill work. Without these fixes, we are stuck writing the same function with the fixes, but without the performance and confidence of longevity.