Hello, do you have detailed changelog about the ne...
# releases
k
Hello, do you have detailed changelog about the new release 1.6.0 ? 🙏 They have been pushed here and here with no more element. Thank you
p
Impatient? 😉 There is a pull request with release notes https://github.com/airbytehq/airbyte/pull/56423/files It looks like official release will be tomorrow
Airbyte 1.6 was released on April 3, 2025.
k
ahah fore sure ! so the tag has been generated a bit too early compared with previous releases 😅 thanks ! 🙂
j
@Kevin Lefevre They're just wanting to build the suspense for you 😉
k
obviously ! end of April is coming 😄
j
watches clock feverishly I see the alpha in there, just waiting for the stable 1.6 helm chart so I can move something I built in Cloud over 😅
p
Don't get too attached to the date from that draft pull request 😉
j
Hah, I know. I'm just not quite brave enough to use the alpha charts in prod and am getting a declarative component schema error on a low-code connector that appears it'll be fixed in 1.6. So just being impatient 😂
k
has the release been deployed ?
p
No, but it looks like it's getting closer https://github.com/airbytehq/airbyte/pull/56423
j
Just a heads-up, looks like this landed on Friday—1.6.0 charts are live and working well for us
k
thanks 🔥
j
Release notes since they haven't posted them here yet: https://github.com/airbytehq/airbyte-platform/releases/tag/v1.6.0
w
@Justin Beasley did you by any chance encounter the following database migration error when upgrading to v1.6.0?
Copy code
DEBUG   airbyte-bootloader: org.flywaydb.core.internal.command.DbMigrate$FlywayMigrateException: Migration failed !                                  
DEBUG   airbyte-bootloader: Caused by: org.flywaydb.core.api.FlywayException: Migration failed !                                                                         
DEBUG   airbyte-bootloader: Caused by: org.jooq.exception.IntegrityConstraintViolationException: SQL [alter table connection alter dataplane_group_id set not null];
DEBUG   airbyte-bootloader: Caused by: org.postgresql.util.PSQLException: ERROR: column "dataplane_group_id" of relation "connection" contains null values
j
@Wesley Verheul Nope, no errors for me. What version were you upgrading from? We were coming from 1.5.1
w
@Justin Beasley Hmm, we are also coming from 1.5.1.... Do you use an external database?
j
Yes, we're on GCP (using a private GKE Autopilot cluster for Airbyte) and use a private Cloud SQL instance for the db
w
Ok, that is practically the same except that we use compute engine instead of GKE at the moment
We install with
abctl
instead of with
helm
directly but I can't imagine that this would be the issue (abctl uses helm under the hood, error is specifically related to a database constraint)
j
yeah, seems odd that there would be a record there with a null in the first place. but maybe that's the reason for the constraint being added 😂
I believe all OSS instances would only have a single dataplane, so you could likely just fill that value
w
It's weird as the error relates to the migration script adding the
dataplane_group_id
to the
connection
table. Looking at the Airbyte docs, this table does not have that column (or the docs are not up to date). @Justin Beasley could you do me a favor and check if that column is present in the
connection
table in your db?
j
@Wesley Verheul Yes, my
connection
records have a value for `dataplane_group_id`—and it looks like the authoritative source of this value is from the
dataplane_group
table. Depending on how you granted your user permissions originally, it's possible you aren't seeing those new tables—so you may need to re-grant permissions if you don't see them in the list. The current version of Airbyte for me as a total of 65 tables in the
public
schema.