Valentin Kulichenko
- Total activity 92
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 0
- Subscriptions 42
Comments
Recent activity by Valentin Kulichenko-
Hi Matt, We have this feature on the roadmap, but without a specific timeline at this point. Let us evaluate it deeper and see if it's possible to prioritize. In the meantime, can you please share ...
-
Official comment This feature is now available. To use the IAM+PrivateLink combination, you need to additionally provide 'database endpoint' in the setup form. Information on how to locate it in the AWS console is ...
-
Official comment Hi Jorge, Thanks for creating the request. We don't currently have this feature on the immediate roadmap, but we will consider adding it. I will keep you posted here on any progress. Thanks,Val Kul...
-
Official comment Hi Gonçalo, Thanks for creating the request. We have this feature on the roadmap, I will keep you posted on the progress. Thanks,Val Kulichenko, Fivetran Product Team
-
Hi Ashish, Thanks for creating this request. We're evaluating the feature – I will add an update once I have more information. Thanks,Val Kulichenko, Fivetran Product Team
-
Official comment Filtering can be done via the Row Filtering feature, which can be used with any connector, not just Postgres: https://fivetran.com/docs/core-concepts/features/row-filter#rowfiltering Replication fr...
-
Official comment Hi Daniel, We added the support for GEOMETRY and GEOGRAPHY types. You can find the full list of data types supported by the CockroachDB connector here: https://fivetran.com/docs/connectors/database...
-
Hi Daniel, Just a quick update. I added this feature to the roadmap. Assuming there are no bump, we should roll out it within the next 2-3 months. Thanks,Val, Fivetran Product Team
-
Official comment Hi Tyler, MongoDB doesn't expose time series collections in change streams, which is why our connector doesn't pick them up. This is a limitation on their side. The only potential way to handle suc...
-
Hi Raj, We're currently working on an improvement that will derive schema changes from DDL events in the binlog, instead of doing a full refresh on every sync. This is not exactly what you've been ...