Database to file strange file size

[DennyLokoOnfly]

Hello,

I've had Swing configured to run for a few weeks now, but something strange has started happening. One database keeps growing regularly, as expected, and it seems that Sling is able to collect its data, as shown in the logs. However, the file size of the output file appears to have been reset.

What could have caused this?

It's worth mentioning that every execution has finished successfully. Not only does the file size seem incorrect, but the data in the file itself is also missing. I'm using the free version of Sling.

Thanks!

source: BOOKING
target: S3_EXPORT

defaults:
  primary_key: id
  object: booking/{stream_schema}/{stream_table}/{YYYY}_{MM}_{DD}_{HH}_{mm}_{ss}.parquet

  target_options:
    format: parquet

streams:
  main_booking.*:

  main_booking.customers:
    columns:
      birthday: string

  main_booking.hotels:
    columns:
      check_in_hour: string
      check_out_hour: string
  
  main_booking.migrations:
    disabled: true

env:
  SLING_ALLOW_EMPTY: TRUE

Logs showing the increasing size of the table:

Output files:

[flarco]

That's quite strange. Assume you didn't upgrade the sling version on the 17th...
What sling version are you using?
Can you try with env var SLING_DUCKDB_COMPUTE=false?

[DennyLokoOnfly]

I'm using version 1.4.10 and will try with this env var. As soon I have an answer, will let you know.