Now let's get to the `0.29.19` changelog. As with ...
# announcements
a
Now let's get to the
0.29.19
changelog. As with last time, bug fixes are in the thread! New Destination: Databricks 🎉 New Source: Google Search Console New Source: Close.com 🏗️ Python CDK: Now supports auth workflows involving query params. 🏗️ Java CDK: You can now run the connector gradle build script on Macs with M1 chips! (contributed by @Harsha Teja Kanna) 💎 Google Ads source: You can now specify user-specified queries in GAQL. GitHub source: All streams with a parent stream use cached parent stream data when possible. Shopify source: Substantial performance improvements to the incremental sync mode. Stripe source: Now supports the
PaymentIntents
stream. Pipedrive source: Now supports the
Organizations
stream. Sendgrid source: Now supports the
SingleSendStats
stream. Bing Ads source: Now supports the
Report
stream. GitHub source: Now supports the
Reactions
stream. MongoDB source: Now Airbyte native! Also, a quick shout out to @Jinni Gu and their team who made the DynamoDB destination that we announced last week! As usual, thank you to all of our contributors: @Harsha Teja Kanna, @Manav, @Maciej Nędza, @mauro, @Brian M, @Iakov Salikov, @Eliziario (Marcos Santos), @coeurdestenebres, and @mohammadbolt
🏆 3
airbyte rocket 18
airbyte heart 7
airbyte 3
👍 1
airbyte star 3
🐛 Facebook Marketing source: Numeric values are no longer wrapped into strings. 🐛 Facebook Marketing source: Fetching conversion data now works as expected. (contributed by @Manav) 🐛 Keen destination: Timestamps are now parsed correctly. 🐛 S3 destination: Parquet schema parsing errors are fixed. 🐛 Snowflake destination: No longer syncs unnecessary tables with S3. 🐛 SurveyMonkey source: Cached responses are now decoded correctly. 🐛 Okta source: Incremental sync now works as expected.
👍 1
j
Should I be seeing the new MongoDB connector in sources?
MongoTesting is when I imported the new connector when it was released previously
j
awesome updates!
u
MongoTesting is when I imported the new connector when it was released previously
after upgrading yes you should see!
j
ok i dont 😞
may be related to what @Liren Tu is working on?
l
No. I think this is a frontend issue. On frontend, it determines if a connector has a new version by checking the definition ID. https://github.com/airbytehq/airbyte/blob/master/airbyte-webapp/src/core/resources/SourceDefinition.ts#L48-L51 This mechanism works for connectors added automatically. But for manually added connectors, their IDs are different. So the frontend cannot find a match. I will create a ticket.