Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Critical
-
Resolution: Not a Bug
-
Affects Version/s: None
-
Fix Version/s: 2.1.0
-
Component/s: Data Summarization
-
Labels:None
-
Environment:
Build Details
Bid Manager Build : tsa-build-bidmgr-2013-01-03-p4-r3233d3855feb8f9d546b1da4f6c166182ae3b93a
-
Sprint:Sprint 1 - Matunuck, Sprint 2, Sprint 4 - Cumberland, Sprint 5 - Cumberland, Sprint 6 - Cumberland, Sprint 7 - Cumberland
Description
Steps to reproduce
------------------
Step 1: Create a Merchant
Step 2: Create an order for the merchant.
Step 3: Check the log.
Step 4: Execute the Query to get the status of the listings.
[SELECT * FROM `st-tracker`.searchEngineListings where searchEngineAccountID in (940,941,942);]
Step 5: Recreate an order for the Merchant with different BL and BA.
Step 6: Check the log.
Step 7: Execute the Query to get the status of the listings.
[SELECT * FROM `st-tracker`.searchEngineListings where searchEngineAccountID in (940,941,942,943,944,945);]
After redeploying the campaign then the sources and listings searchEngineStatus of old campaign is setting to deleted. Again the sources and listings for old and new deployed campaigns are recreated with searchEngineStatus = 'ok'.
please find the attached file redeployCamp.txt
P.S : In the log when the Campaigns are redeployed then in seupdate parameters the search engine Account id's are replicated.
cal/tsa/bidmgr/libs/thirdparty/mail.jar:/usr/local/tsa/bidmgr/libs/thirdparty/commons-collections-3.2.1.jar com.thesearchagency.searchengines.SearchEngineUpdater -d 3 --inactive --seaccount 943,944,945,943,944,945 --groups --listings
