Fix AO/CO visimap first row number integer overflow (#4564)
There is a scenario during AO/CO delete or update where the first row number obtained is negative. The error is caused when the first row number in the aovisimap of an AO/CO table exceeds int max. There is currently a bug where the first row number is retrieved from the tuple as an int, but the first row number is an int64. We fixed this by retrieving as an int64. Co-authored-by: NJimmy Yih <jyih@pivotal.io> Co-authored-by: NDavid Kimura <dkimura@pivotal.io>
Showing
想要评论请 注册 或 登录