<#3631 bug: Tap with state_partitioning_keys stora...
# meltano-repo-activity
g
#3631 bug: Tap with state_partitioning_keys storage behaviour disabled no longer respected Issue created by DanielPDWalker Singer SDK Version 0.54.1 Is this a regression? • Yes Python Version 3.10 Bug scope Taps (catalog, state, etc.) Operating System Linux Description
tap-aptem
has
state_partitioning_keys
storage disabled: https://github.com/Matatika/tap-aptem/blob/358564117be4e881350f4815a1a74244a5c8609e/tap_aptem/client.py#L167 After bumping the tap
singer-sdk
version to
0.54.1
we are getting the partitions contexts stored again. This results in a massive state record, impacting the performance. A side effect of this I also saw was my Meltano Cloud pipeline run for this tap: 1. Failed (timeout) 2. Retry Failed (timeout) 3. Retry Failed - duplicate entries error
ValueError: State file contains duplicate entries for partition: {'AwardingBodyQualificationId': 12345, 'AwardingBodyQualification': '***'}.
Like if the tap didn't complete the run the state was partially written back, then again on the next run, and then you have duplicates. Link to Slack/Linen No response meltano/sdk