Obsolete
Status Update
No update yet.
Comments
bl...@google.com
zy...@google.com
I can see @0 is broken right now. Could you use @-604700000 instead?
The calculation is 3600000 * 24 * 7 = 604800000 and cut a little from the end.
It allows you to time travel back to 7 days ago, which is practically the same as @0 (when it works).
The calculation is 3600000 * 24 * 7 = 604800000 and cut a little from the end.
It allows you to time travel back to 7 days ago, which is practically the same as @0 (when it works).
al...@gmail.com
Hi.
I tried using -604800000 and it doesn't fail anymore but returns no results. Should I submit as another bug?
I tried using -604800000 and it doesn't fail anymore but returns no results. Should I submit as another bug?
zy...@google.com
How about @-604700000, does it give you anything?
al...@gmail.com
sorry for the late reply.
@-604700000 does not work either.
No results are returned when using such decorator.
@-604700000 does not work either.
No results are returned when using such decorator.
zy...@google.com
Are you able to use standardSQL to help us debug the issue? For example:
#standardSQL
SELECT *
FROM t
FOR SYSTEM_TIME AS OF TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 1 HOUR);
If it doesn't work either, please add job_id to this thread.
#standardSQL
SELECT *
FROM t
FOR SYSTEM_TIME AS OF TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 1 HOUR);
If it doesn't work either, please add job_id to this thread.
al...@gmail.com
your example works and returns data with standard sql
I would say it's a decorator interpretation/manipulation error because seems to be working if I pass it like: @timestamp1-timestamp2
@1572038264000-1572643087000
I would say it's a decorator interpretation/manipulation error because seems to be working if I pass it like: @timestamp1-timestamp2
@1572038264000-1572643087000
th...@google.com
al...@gmail.com
Hello.
Just as an update, seems that now providing decorators as @-604700000 return results.
But @0 is still the same initial error.
Just as an update, seems that now providing decorators as @-604700000 return results.
But @0 is still the same initial error.
sv...@google.com
Closing this for now, please reopen if it is still an issue.
Description
Problem you have encountered:
I'm running bigquery legacy sql and using the special decorator @0 it gives an error on any table:
Invalid snapshot time 1570001838355 for table upbeat-stratum-242175:my_dataset.my_data. Cannot read before 1570001838359
What you expected to happen:
return results according to decorator
Steps to reproduce:
make a query using @0 decorator for a table
Other information (workarounds you have tried, documentation consulted, etc):