René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Bytewax materializer sets incremental materialization date before materialization completes","articleBody":"## Expected Behavior \r\n\r\nThere should be an option to match the LocalMaterializer behavior, which waits for materialization to finish before updating the incremental materialization timestamp for a feature view\r\n\r\n## Current Behavior\r\n\r\nThe incremental materialization timestamp is updated as soon as the materialization job is successfully created, even though that job may not successfully complete.  This means that some updates will never be materialized to the online store.\r\n\r\n## Steps to reproduce\r\n\r\nSet the batch_engine image to an image that immediately exits with exit code 1.  Run an incremental materialization with end date set to current time.  Observe that the pods and job fail.  Run an incremental materialization again.  Observe that the start date is now the end date of the last run.\r\n\r\n### Specifications\r\n\r\n- Version: 0.31\r\n- Platform: fedora linux\r\n- Subsystem: bytewax batch_engine\r\n\r\n## Possible Solution\r\n\r\nOptionally allow for a synchronous materialization in bytewax, which will wait for a feature view materialization to finish before returning success and moving on to the next feature view and throwing an exception if the job fails.  This will match the behavior of the LocalMaterializer\r\n","author":{"url":"https://github.com/james-crabtree-sp","@type":"Person","name":"james-crabtree-sp"},"datePublished":"2023-10-09T19:35:57.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/3787/feast/issues/3787"}