Kevin Kim
- Total activity 436
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 3
- Subscriptions 209
Comments
Recent activity by Kevin Kim-
Official comment Hi Ryan! Good news, we are currently working on building this feature into our platform. While I don't have an exact date yet, we should have this capability in Fivetran relatively soon. Please sta...
-
Official comment Hi Adam, Thanks for your comment! We are currently working on a row filtering feature to allow users to pick criteria on the data they want to sync, for example if you have a timestamp column you c...
-
Official comment Hi Ami, Thanks for your question! We are currently building a row filtering feature, which lets you fitler out rows from being synced based on a critiera, e.g. as date, integer, and string filters....
-
Official comment Hi Longfei, Thanks for your post here, I'm the product manager for our Row Filtering feature, which is currently in beta only for Database connectors. We are currently building row filtering for Sa...
-
Official comment Hi Kishore, Thanks for your comment in our feature request portal. We don't have a timeline for this feature request yet, but I will review this with our engineering team. Could you share more deta...
-
Official comment Hi all, Thank you for your feedback on this post. We introduced the heartbeat mechanism to help with Postgres connector stability and monitoring several years ago. Since then, we have made substant...
-
Official comment Hi Ken, We do read from the online and archive logs for our Oracle connector for version 19c. I believe we have supported this since about early 2021 if I recall correctly!It seems that the docs yo...
-
Yes, that is one of the key features we are ensuring will work in Postgres 16!
-
Official comment Hi, Thanks for your post here! We are currently actively working on certifying Postgres 16 and should have this completed in the next couple of months. Please stay tuned as we do our testing and lo...
-
Official comment Hi Ramesh, Thanks for your post here! In history mode, we update the _fivetran_end column to when the record was made inactive. Would this address your use case? When a record is updated in the sou...