Hi Subash,
Yes, your choice of MJS for its async capabilities is right in this
context. The only thing to keep in mind is that MJS is originally designed
for bulk operations. It gives you good performance when updating lots (say,
order of millions) of entries, but the regular sync version of
Hi Subash,
I'm not sure I follow the issue completely, but my understanding is that
when doing the import, you don't have a way to identify the campaign you
are creating in MJS to the corresponding entry in your local feed.
If that's the case, you might want to switch back to CampaignService,
Hi Anash,
Thanks for your reply, much helpful. What would you suggest here? MJS or
CampaignService? We choose MJS coz we will get xx number of products daily
to our feed and need to create each products as each campaigns so only we
choose MJS as we can see the jobs results and once job is
Hello, Anyone from Google? please help me here.
On Thursday, June 4, 2015 at 2:12:20 PM UTC+5:30, Subash NG wrote:
Hello,
We have been importing campaigns from json and we are using
mutatejobservice to do this, our issue right now is we can't parse our
product id into campaign settings.
Hello,
We have been importing campaigns from json and we are using
mutatejobservice to do this, our issue right now is we can't parse our
product id into campaign settings. We don't have any issues while importing
campaigns but when thought about Update we need to parse our ID into
campaign
