Redshift not loading sorted data as sorted


Following this doc:

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?

asked 2 years ago533 views
1 Answer

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

answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions