Hey <!channel>! Let's go over all the changes from...
# announcements
a
Hey <!channel>! Let's go over all the changes from 
v.32.1
 and prior! But first, there's an important announcement I need to make about upgrading Airbyte to 
v.32.1
. ⚠️ WARNING ⚠️ ------------------------ Upgrading to
v.32.0
is equivalent to a major version bump. If your current version is < 
v.32.0
 , you must upgrade to 
v.32.0
 first before upgrading to any later version
Keep in mind that this upgrade requires your all of your connector 
Specs
 to be retrievable, or Airbyte will fail on startup. You can force delete your connector 
Specs
 by setting the 
VERSION_0_32_0_FORCE_UPGRADE
 environment variable to 
true
. Steps to specifically check out 
v.32.0
 and details around this breaking change can be found here. ------------------------ Now back to our regularly scheduled programming. 🎃 Hacktoberfest Submissions 🎃 ----------------------------------------- New Destination: ScyllaDB (contributed by @Ivica Taseski) New Source: Azure Table Storage (contributed by @geekwhocodes) New Source: Linnworks (contributed by @Juozas) ----------------------------------------- Source MySQL: Now has basic performance tests. Source Salesforce: We now automatically transform and handle incorrect data for the
anyType
and
calculated
types. 🐛 IBM Db2 Source: Now handles conversion from
DECFLOAT
to
BigDecimal
correctly. 🐛 MSSQL Source: Now handles
VARBINARY
correctly. 🐛 CockroachDB Source: Improved parsing of various data types. As usual, thank you so much to our wonderful contributors this week that have made Airbyte into what it is today: @Achmad Syarif Hidayatullah, @Tuan Nguyen, @Ivica Taseski, @Hai To, @Juozas, @gunu, @Shadab, @Per-Victor Persson, and @Harsha Teja Kanna!
airbyte star 4
💥 2
airbyte 6
airbyte rocket 7
🎉 22
n
where do we see the release notes to what’s new in v.32.1? not just the connectors mentioned here
a
@Noel Gomez The full release notes can be found here!
n
Thanks
m
we upgraded yesterday from 0.30.25 directly to 0.32.1. what did we break specifically?
l
Upgrading to 0.32.1 directly should be safe actually. It will only be unsafe to upgrade once we release the next minor version bump, as that will remove the upgrade logic. But the 0.32.X patch updates should be safe to upgrade directly to
Though @mauro I actually would have expected you to see an error thrown when trying to upgrade from a version <0.32.0 to a version >0.32.0, something like
Copy code
Cannot upgrade from version 0.30.25 to version 0.32.1 directly...
did you not see such an error?
m
no. I have
Copy code
2021-11-17 12:10:34 INFO i.a.s.ServerApp(runAutomaticMigration):359 - {cloud_workspace_app_root=/workspace/server/logs} - Running Automatic Migration from version : 0.30.2-alpha to version : 0.32.1-alpha
then the server started normally (it printed the ascii art logo). (I do have some errors on the first api/v1/health request though --
java.lang.IllegalArgumentException: argument "content" is null
)
c
@mauro would it be possible to share the logs from when you did the upgrade if you still have them?
nvm! i was able to recreate it.