Feature request: being able to provide a StartTime for BQ/GCS/RedShift/S3 exports

fullstorydev / hauser

Service for moving your Fullstory export files to a data warehouse

MIT License

49 stars 23 forks source link

Feature request: being able to provide a StartTime for BQ/GCS/RedShift/S3 exports #76

Closed glarchev closed 3 years ago

glarchev commented 4 years ago

Currently we can provide a StartTime for local exports only. It would be nice to be able to specify StartTime for all other exports as well.

jameremo commented 4 years ago

Thanks, @glarchev! The current workaround for this issue is to insert a dummy record into the sync table in Redshift/BigQuery with the BundleEndTime set to your desired start time.

It's worth noting, however, that if we complete #74, we'll likely negate this workaround in the S3 and GCS only cases. This is a valid request for hauser in the long term.

camphillips22 commented 3 years ago

I believe that now that #95 is merged, this issue is resolved. There is now a StartTime parameter that determines when to start exporting if there is no sync file/table available.