fix: Fixed transaction handling with SQLite registry #5588
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
This PR fixed the SQLite database lock issue in the Feast SQL Registry. The error
sqlite3.OperationalError: database is locked
was occurring because the_set_last_updated_metadata
method was being called from within the_apply_object
method's transaction context, but_set_last_updated_metadata
was trying to start its own transaction withself.write_engine.begin()
. This created a nested transaction scenario that SQLite doesn't handle well.Modified the methods now to accept an optional connection parameter to use the existing transaction (for calls from within other transactions).
Which issue(s) this PR fixes:
Fixes #5565