<@U06CQR1HGC9> can you confirm this behavior we’re...
# singer-targets
t
@ruslan_bergenov can you confirm this behavior we’re seeing in target-bigquery? https://gitlab.com/meltano/sdk/-/issues/300#note_850348987 cc @edgar_ramirez_mondragon
r
@taylor @edgar_ramirez_mondragon, we'll take a look and get back to you. I may reach out with some questions.
Hi @taylor, @edgar_ramirez_mondragon, I see that target-bigquery tries to manipulate (merge) state messages, which is its default behavior, but not desired for your data and use case and it's failing on your state file. Try disabling state merging. State message won't be manipulated in any way, but will just be passed as is. Whatever state message we get - that will be our state file. Method A. When you call target-bigquery thru command line, pass this flag:
'--no-merge_state_messages'
Method B. Disable state merging via target config file
Copy code
{
  "project_id": "{your-project-id}",
  "dataset_id": "{your_dataset_id}",
  "merge_state_messages": 0
}
t
@ruslan_bergenov that’s helpful context. Looks like we should recommend users have that set as false for use in Meltano. I’ll note it in the issue.