Loading
Resolve "Geo: LFS not being synced"
What does this MR do?
In a previous refactor we did, one important query condition was lost. This query impacts LFS synchronization of new objects when using FDW queries. In %12.1, we stopped supporting legacy queries and removed them completely. So before %12.1 there was a small chance some users were impacted, but after %12.1 Geo all users were impacted by this mistake.
Does this MR meet the acceptance criteria?
Conformity
- Changelog entry
- Documentation created/updated or follow-up review issue created
- Code review guidelines
- Merge request performance guidelines
- Style guides
- Database guides
- Separation of EE specific content
Performance and Testing
The fix was manually tested
- Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
- Tested in all supported browsers
Closes #32696 (closed)
Edited by Gabriel Mazzetto