DSXchange

Hello,

I have a job which is identical in development and production.

In production it works because the partitioning behaves correctly on the two join stages in the job.

In development the job doesn't behave correctly and produces slightly different results each time I run the job.

I have actually fixed the problem in development by adding explicit sorts and partitioning which is not entirely unexpected, but I would like to know wht the two environments are behaving differently.

In fixing the job in development, in addition to the sort and partitioning that I added, I included the APT_NO_PART_INSERT and APT_NO_SORT_INSERT environment variables set to true.

The same set of changes worked in production, not surprisingly.

Can anyone shed any light on why development and production should behave differently? The above two environment variables defaulted to true when inserted in to the job so I don't think it's that. Is there another environment variable I could check, perhaps?

Many thanks and look forward to hearing from you.

Kind regards,
Bob.

Check that your C++ compiler versions, patch levels/PTF levels are identical across environments, assuming you have a compiler in production. Some places do not.

If your development compiler version got changed for any reason (it becomes an unsupported compiler version at that point), then very strange things can start happening, including unexpected and incorrect results.