Bing: generate_discrepancies does not discover discrepancies

Steps:

1. Log into bidmanager as tsaapp in xml-01 jail.

2. Pick up and account and execute following steps.

3. Run bingreports.sh for the selected account from date 2012-04-25 till 2012-04-30. Ensure that data is pulled in by running

./bingreports.sh --seuser 20000102 -d3 --date 2012-04-25

SELECT * FROM staging.bingReports WHERE AccountID=1611828

4. After ensuring that data is present in staging, run sesummarizer for this account from 2012-05-25 till 2012-05-30 and check for data in DB.

./sesummarize.sh -d3 --distribution 147 --seuser 20000102 --date 2012-04-25

SELECT * FROM tmp.searchEngineActivitySummary201204 WHERE accountID=10000095

5. Run warehouse summarizer for this account from 2012-05-25 till 2012-05-30 and check for data in DB.

./whsumm.sh -d3 --distribution 147 --accountid 10000095 --date 2012-04-30

SELECT * FROM warehouse_1.whDailyGroupPerf WHERE accountID=10000095

6. Now that we have data in our database, run generate_discrepancies script.Since the data is intact, the file generated will not have any discrepancies.

./generate-discrepancies.sh -d3 --distribution 147 -a10000095 -T 2012-04-25 -E 2012-04-30

7. Manually induce discrepancy by editing a value in warehouse database.

UPDATE warehouse_1.whDailyGroupPerf SET seclicks=10 WHERE id=2137009;

8. Repeat step 6 and notice if the discrepancy is discovered by the application.

Expected:

The discrepancy must be caught and published in the discrepancy file.

Actual:

The discrepancy is not caught and the file is still empty.