we have noticed that in the Postgres source version 1.0.3 there was a change implemented, which hides Incremental mode on tables with no cursor field. Here is the respective PR.
With this change there is now no possibility to have Incremental mode on views. In our case, we use views on source to filter out for sensitive information which should not go to the DWH, but we still want to create history for the views based on updated_at cursor field.
Please, is this intended behaviour to restrict Incremental mode only to tables or is it unintended side effect?
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.
The Community Assistance Team
Hey could you check if this issue https://github.com/airbytehq/oncall/issues/641 is resonating with you?
Hey, the link does not work for me. Is the issue number correct? Issue 641 in airbyte repo is from 2020 and it seems unrelated. Thanks!
The problem only occurs with certain version of Airbyte, if upgraded to latest version, this problem is gone. This issue can be closed.
Hey yeah we fixed it recently. Thanks a lot.