In places (in thor) where an expanding array of rows is allocated from the roxie/thor memory manager (i.e.. most activities that need to gather large numbers of rows), we will hit issues (either incorrect behaviour or failures) when the array size exceeds 4Gb. With 64-bit pointers, that effectively creates a limit on the number of rows at 500 million.
This is likely to cause us issues before too long.
In places (in thor) where an expanding array of rows is allocated from the roxie/thor memory manager (i.e.. most activities that need to gather large numbers of rows), we will hit issues (either incorrect behaviour or failures) when the array size exceeds 4Gb. With 64-bit pointers, that effectively creates a limit on the number of rows at 500 million.
This is likely to cause us issues before too long.