Using multiple fields as a cursor for incremental syncs

Connector Development
,
1

Hi Team,

I have an issue where I would like to use the date field and name filed in record in combination as a cursor field.

My records are like this eg below:

`{"type": "RECORD", "record": {"stream": "states_history_cases", "data": {"name": "Schleswig-Holstein", "state": "SH", "cases": 167, "date": "2022-09-18T00:00:00.000Z"}, "emitted_at": 1663690865497}}`
`{"type": "RECORD", "record": {"stream": "states_history_cases", "data": {"name": "Schleswig-Holstein", "state": "SH", "cases": 1179, "date": "2022-09-19T00:00:00.000Z"}, "emitted_at": 1663690865497}}`
`{"type": "RECORD", "record": {"stream": "states_history_cases", "data": {"name": "Hamburg", "state": "HH", "cases": 0, "date": "2020-01-01T00:00:00.000Z"}, "emitted_at": 1663690865498}}`

Is there a way I can do that. When I apply incremental sync the state changes. Acceptance test fails, when I get the record with state HH as the previous date is smaller than the next

2

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
Best,
The Community Assistance Team

1 Like
3

Hi @Zawar92,

Thanks for your post. Unfortunately, based on my understanding of our normalization process, you won’t be able to use multiple fields as a cursor field since normalization would break. I don’t think this is possible at the moment with Airbyte but I’m happy to forward this to our product team as feedback. I wish I had a better answer for you but I hope this helps!

Feel free to post more questions here in the forums.

1 Like
4

Thanks for the update @sajarin . Then maybe I will convert my streams to full-refresh. As soon as the team comes up with a solution, you can tell me.

5

Thanks for the update @sajarin . Then maybe I will convert my streams to full-refresh. As soon as the team comes up with a solution, you can tell me.

[Discourse post]