Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cube's last modified time will set to wrong date when incremental job failed #58

Closed
lukehan opened this issue Nov 17, 2014 · 1 comment
Assignees
Labels

Comments

@lukehan
Copy link
Contributor

lukehan commented Nov 17, 2014

When incremental refresh job failed, the cube's last modified time will set to 1970-01-01 08:00:00
This is wrong value, it should always keep the last success refresh timestamp.

Screenshot:
screen shot 2014-11-17 at 9 48 19 am

@lukehan lukehan added the bug label Nov 17, 2014
@lukehan lukehan added this to the v0.7 Release milestone Nov 17, 2014
@janzhongi
Copy link
Contributor

when the last segment is null.system does not show last_modified_time correctly.
has fixed this issue.
the last_build_time will be the latest avaliable 'Ready' status segment.
if no segment,will show cre_time by default.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants