-
-
Notifications
You must be signed in to change notification settings - Fork 0
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
fix: Always update product for redis events #104
Conversation
Signed-off-by: John Gomersall <[email protected]>
Signed-off-by: John Gomersall <[email protected]>
if ( | ||
source !== ProductSource.FULL_LOAD && | ||
source === ProductSource.INCREMENTAL_LOAD && | ||
lastModified?.getTime() === previousLastModified?.getTime() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you use last_updated_t instead of last_modified_t? last_updated_t is also changed when update_all_products.pl reanalyzes the product
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've made the changes. More files affected but mostly renaming columns
Signed-off-by: John Gomersall <[email protected]>
… data from later transactions on a full import Signed-off-by: John Gomersall <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
…ther tests Signed-off-by: John Gomersall <[email protected]>
Signed-off-by: John Gomersall <[email protected]>
…for-redis-events fix: Re-implement changes from PR #104
What
Always import product updates for events. Also switch to using last_updated_t from Product Opener for incremental bulk imports
Fixes bug(s)