Google v201101 sync reports do not correctly handle SEAs linked to a TSA account with a SEU that is linked to a different TSA account

SEA = search engine account (aka Google campaign in AdWords)

SEU = search engine user (aka Google account in AdWords)

compared results of the build specified in Environment (which uses v201101 Google API version) against build tsa-build-bidmgr-2011-06-21-p458-r29728/ (which uses v13 Google API version)

===PREREQUISITE TO REPRODUCE BUG===

verify SEU 3201 is linked to Martian Tourism account

verify SEU 8 is linked to CSC account

verify there is an SEA that has accountID=17 and searchEngineUserID=3201

===STEPS TAKEN===

// with each build (v13 and v201101) you're testing with, do the following...

// use the SEU db shard (as opposed to account db shard)

delete from sync_google.googleAds where searchEngineUserID in (8,3201);

delete from sync_google.googleKeywords where searchEngineUserID in (8,3201);

// use the account db shard

delete from st-tracker.sources where accountID=17;

// link /usr/local/tsa/bidmgr to the build you are testing with

./seupdate.sh -d3 --distribution 3 --groups --listings --accountid 17

// save this resultset for later comparison

select * FROM `st-tracker`.sources where accountID=17 group by searchEngineAccountID;

===PROBLEM===

What you should see from the resultset is that v13 returned data for the SEA that uses accountID=17 and searchEngineUserID=3201, but v201101 does not return data for that

For select * FROM `st-tracker`.sources where accountID=17 group by searchEngineAccountID; gives 20 rows for v13 but only 19 (usually) for v201101. The missing row is:

id altKey accountID siteID searchEngineAccountID keywordID distributionID searchEngineIdentifier searchEngineGroupIdentifier searchEngineMatchType searchEngineGroupID isBiddable campaignID description type keyword sourceURL cost maxCost waypointID landingURL passParams trackPerformance searchEngineStatus searchEngineStatusText lastChecked

296647990 17 0 33948 0 3 Content Network 1430323888 content 3 true 0 Content Network 7 Content Network 0.11 0.11 true ok Content Network 0000-00-00 00:00:00

I did a query on all the SEAs v13 gets back...

mysql> SELECT id,accountID,searchEngineUserID,description,searchEngineIdentifier FROM tsacommon.searchEngineAccounts where id in (43,69,4465,28206,28207,28451,30739,30960,30961,31227,31300,33917,33918,33948,36626,36627,36628,36633,36634,56515);

----------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------

20 rows in set (0.00 sec)

... the missing SEA in v2011 is that row where searchEngineUserID=3201

SEU 3201 is linked to accountID 618

mysql> SELECT id,accountID,description FROM tsacommon.searchEngineUsers where id in (8,3201);

------------------------------------------------

------------------------------------------------

------------------------------------------------

2 rows in set (0.00 sec)

I verified data for SEU 3201 is pulled into the google_sync tables on its shard in v201101

So it seems the issue has to do with the mismatch between the TSA account shard and the SEU shard for creating sources (which get created on the TSA account shard by reading from the SEU shard google_sync tables)