Page MenuHomePhabricator

Audit & support for benevity import
Closed, ResolvedPublic

Description

I renamed this to what it has become - will open another for the slowness

Event Timeline

Opps this wasn't the one to move in - we should leave this until after BE - @RLewis - what was the one that was about auditing the totals?

@Eileenmcnaughton just adding in another issue i've encountered when importing a benevity file for the EUR currency file.

I've added the file to the server under the Benevity folder, October 2019 - error eur file

Eileenmcnaughton renamed this task from Benevity import taking a long time with large files to Audit & support for benevity import.Nov 12 2019, 9:15 PM
Eileenmcnaughton updated the task description. (Show Details)

Change 556775 had a related patch set uploaded (by Eileen; owner: Eileen):
[wikimedia/fundraising/crm@master] Exclude major matching gifts donors from totals calc

https://gerrit.wikimedia.org/r/556775

Change 556775 merged by jenkins-bot:
[wikimedia/fundraising/crm@master] Exclude major matching gifts donors from totals calc

https://gerrit.wikimedia.org/r/556775

Change 556860 had a related patch set uploaded (by Eileen; owner: Eileen):
[wikimedia/fundraising/crm@master] Add message support for recovering from a borked import

https://gerrit.wikimedia.org/r/556860

Change 556861 had a related patch set uploaded (by Eileen; owner: Eileen):
[wikimedia/fundraising/crm@master] Fix issue where source field was sometimes messing with imports

https://gerrit.wikimedia.org/r/556861

after some attempts I determined that the speed issue with matching gift donors with many gifts was getting worse the more contributions we added at a rapid rate. I’m pretty sure this indicates the join for the wmf_donor fields just won’t scale to 20k+ donations on a single donor. I worked with Elliott & Dallas to alter the triggers to exclude our most significant matching gift donors. I discussed with @NNichols & if not having that info for those 2 contacts ever becomes an issue she will raise a phab then. I had thought that we would look at doing this in Jan but it became apparently it would be impossible to get the file in if we left it until then & we had opportunity with queues relatively slow so we did it.

Change 556860 merged by jenkins-bot:
[wikimedia/fundraising/crm@master] Add message support for recovering from a borked import

https://gerrit.wikimedia.org/r/556860

Change 556861 merged by jenkins-bot:
[wikimedia/fundraising/crm@master] Fix issue where source field was sometimes messing with imports

https://gerrit.wikimedia.org/r/556861

I added this upstream https://github.com/civicrm/civicrm-core/pull/16143 for the confusing financial_type_id is not valid message - I don't think we need to backport it now we know it's a deadlock