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年前

ログインしていません。 ログイン 回答を投稿する。

優れた回答とは、質問に明確に答え、建設的なフィードバックを提供し、質問者の専門分野におけるスキルの向上を促すものです。

質問に答えるためのガイドライン

関連するコンテンツ