2 weeks ago
2 weeks ago
Hi @nikhilshetty4 ,
I think it might be some kind of bug related to that feautre. You are another person who is saying that it doesn't work as expected
Autoloader move file to archive immediately after ... - Databricks Community - 120692
2 weeks ago
Hello @nikhilshetty4!
To confirm, do the files show a non-null commit_time in cloud_files_state? Theyโll only move to the archive location after this is set and the retention period has elapsed.
2 weeks ago - last edited 2 weeks ago
Hi @Advika
Yes, the commit_time column contains valid timestamp values. However, the archive_time, archive_mode, and move_location columns are all showing null.
2 weeks ago
@nikhilshetty4, If the archive columns (archive_time, archive_mode, move_location) are null, it means files havenโt been picked up by cleanSource for move/delete yet. Move/delete occurs after commit_time is set, the retention period has passed, and the stream is actively processing. If the stream is stopped, cleanup wonโt occur, it resumes the next time the stream runs and processes data.
2 weeks ago - last edited 2 weeks ago
@Advika, Iโve tried setting the retention duration to 1 or 2 minutes and kept the stream running well beyond that time. Even when new files were processed during the stream, the data still wasnโt moved to the archive location.
I've attached the screenshot of cloud_files_state output:
I did see that there is no time restriction for MOVE in autoloader documentation:
2 weeks ago
Thanks for sharing the details, @nikhilshetty4.
I recommend raising a case with the Databricks Support team and including all the relevant details. This will help them investigate and resolve the issue more quickly.
2 weeks ago
Got it, Thanks! I'll raise a case with Databricks Support team.
Passionate about hosting events and connecting people? Help us grow a vibrant local communityโsign up today to get started!
Sign Up Now