support for offset and origin options in time_bucket_gapfill

[eloyekunle]

time_bucket has offset and origin parameters which help with aligning timestamps in queries. There are no equivalents for the time_bucket_gapfill function, and I can't find a workaround.

Are there plans to add these options to time_bucket_gapfill?

[pmwkaa]

Hey @eloyekunle, I can't tell any specific time-frame regarding it at the moment, but we are aware about the high demand of this feature and had several community requests before #1304, #1435

[eloyekunle]

@pmwkaa can you or someone from the team give some pointers about contributing a fix for this to the codebase? I write C and I'm pretty familiar with Timescale so I can take a stab at this. cc @mfreed

[milosjovac]

Any news on this issue?

[ghost]

Any workaround at the moment if I want to use time_bucket, and absolutely force it to use my "origin" timestamp (start date)? I'm willing to add/subtract a row due to the alignment...

[aabrodskiy]

Will this be implemented please?
Currently time_bucket_gapfill does not take origin and offset and effectively all bucketing originates from jan 1 midnight which is not desired nor usable...