Redshift not loading sorted data as sorted

0

Following this doc: https://docs.aws.amazon.com/redshift/latest/dg/vacuum-load-in-sort-key-order.html

It seems that we're loading things according to these guidelines but our data is still defaulting to loading as unsorted. If we're using a time based sort key and there is overlap in this way:

Existing sort keys in table:

1 2 3

New sort keys in COPY:

3 4 5

Would the overlap on the 3 value explain the behavior we're seeing, even if the data could technically be considered sorted?

질문됨 2년 전486회 조회
1개 답변
0

Yes, I think that is the issue ; the documentation explicitly mentions that new rows are higher:

All the new rows are higher in sort order than the existing rows , including rows marked for deletion. In this instance, Amazon Redshift uses the first eight bytes of the sort key to determine sort order.

hope this helps

AWS
전문가
답변함 2년 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠