You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
TimestampRange should allow customization of inclusive/exclusive #2608
My application expects inclusive upper timestamp bounds. The super hacky workaround I currently have to make it work with bigtable is adding 1ms (minimum timestamp resolution) onto all end timestamps.
// Specified a contiguous range of microsecond timestamps.
message TimestampRange {
// Inclusive lower bound. If left empty, interpreted as 0.
int64 start_timestamp_micros = 1;
// Exclusive upper bound. If left empty, interpreted as infinity.
int64 end_timestamp_micros = 2;
}
For now, your workaround is what I would recommend, but we can certainly consider adding this feature.
Activity
dhermes commentedon Oct 25, 2016
We are at the mercy of the spec
For now, your workaround is what I would recommend, but we can certainly consider adding this feature.
automl: add base dataset samples for automl ga [(#2608)](GoogleCloudP…