Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: Mercury, Kinsei
-
Fix Version/s: Kinsei
-
Component/s: None
-
Labels:None
-
Environment:
Tested on QA2
bidmgr-distribution-2.9.1-RC2-bin.tar.gz
-
Story Points:2
-
Sprint:Sprint 1
Description
Steps:
--------
1. Run sedatacheck.sh for an account that has performance data for both Google and Bing with date range.
./sedatacheck.sh -d3 -U274 -T2016-04-22 -E2016-04-26
./sedatacheck.sh -d3 -U273 -T2016-04-22 -E2016-04-26
Note: It has performance data on the specified dates.
2. Verify the staging.googleDailyCheck and staging.bingDailyCheck tables for the data.
Expected: It should not download the performance data for the End date specified.
Actual: It is downloading the performance data for the end date in case of Bing.
mysql> SELECT * FROM staging.bingDailyCheck WHERE campaignid IN (SELECT searchEngineIdentifier FROM tsacommon.searchEngineAccounts WHERE description LIKE "%bb9971f9-36db-47fa-a079-c4b1d3d5699d%");
----------------------------------------------------------------------------------------+
| date | campaignid | campaign | imps | clicks | cost |
----------------------------------------------------------------------------------------+
| 2016-04-22 | 248595311 | bb9971f9-36db-47fa-a079-c4b1d3d5699d_12503_57_251_GT | 6323 | 24 | 6.67 |
| 2016-04-22 | 248595312 | bb9971f9-36db-47fa-a079-c4b1d3d5699d_12503_57_251_GM | 8 | 0 | 0 |
| 2016-04-26 | 248600313 | bb9971f9-36db-47fa-a079-c4b1d3d5699d_12503_57_373_GT | 3076 | 12 | 2.74 |
| 2016-04-26 | 248600314 | bb9971f9-36db-47fa-a079-c4b1d3d5699d_12503_57_373_GM | 2 | 0 | 0 |
----------------------------------------------------------------------------------------+
4 rows in set (0.00 sec)
mysql> SELECT * FROM staging.googleDailyCheck WHERE campaignid IN (SELECT searchEngineIdentifier FROM tsacommon.searchEngineAccounts WHERE description LIKE "%bb9971f9-36db-47fa-a079-c4b1d3d5699d%");
------------------------------------------------------------------------------------------------------+
| date | acctname | campaignid | campaign | imps | clicks | cost | conv |
------------------------------------------------------------------------------------------------------+
| 2016-04-22 | 389227739 | bb9971f9-36db-47fa-a079-c4b1d3d5699d_12503_57_250_GT | 32 | 0 | 0 | 0 | |
| 2016-04-22 | 389227859 | bb9971f9-36db-47fa-a079-c4b1d3d5699d_12503_57_250_GM | 50 | 1 | 410000 | 0 |
------------------------------------------------------------------------------------------------------+
2 rows in set (0.00 sec)
Note: In case of Google this scenario is working fine.
See the below sedatacheck log
2016-05-10 09:06:56.700 (3) [P2T1]: Deleting existing records where ((`date`>="2016-04-22") and (`date`<"2016-04-26") and (`campaignid` in ("248595311","248595312","248600313","248600314")))
