mirror of
https://github.com/maybe-finance/maybe.git
synced 2025-08-07 14:35:23 +02:00
Refactor transaction enrichment to support batch processing (#1803)
* Refactor transaction enrichment to support batch processing - Add method to enrich transactions in batches - Implement job scheduling for unenriched transactions - Improve logging and error handling for transaction enrichment * Re-enable enrichment * Fix transaction enrichment query to use correct table references - Update queries to explicitly join and reference account_entries and account_transactions tables - Remove unnecessary name presence check before enrichment - Improve query precision for unenriched transaction selection * Optimize transaction enrichment query joins - Refactor database joins to use explicit table references - Improve query performance for unenriched transaction selection - Ensure correct table aliasing in enrichment methods * Remove deprecated data enrichment job and method - Delete EnrichDataJob as it's no longer used - Remove `enrich_data_later` method from Account model - Update Account::Syncer to directly call `enrich_data` instead of scheduling a job
This commit is contained in:
parent
abd932c894
commit
b84a33c09d
5 changed files with 62 additions and 54 deletions
|
@ -15,8 +15,7 @@ class Account::Syncer
|
|||
|
||||
# Enrich if user opted in or if we're syncing transactions from a Plaid account on the hosted app
|
||||
if account.family.data_enrichment_enabled? || (account.plaid_account_id.present? && Rails.application.config.app_mode.hosted?)
|
||||
# Temporarily disable until optimizations complete
|
||||
# account.enrich_data_later
|
||||
account.enrich_data
|
||||
else
|
||||
Rails.logger.info("Data enrichment is disabled, skipping enrichment for account #{account.id}")
|
||||
end
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue