From 0a3f0df5dfec99dfa9dd88136f16494cf8d7f228 Mon Sep 17 00:00:00 2001 From: SimeonBrazeSA <137236059+SimeonBrazeSA@users.noreply.github.com> Date: Thu, 13 Jun 2024 09:20:59 +1000 Subject: [PATCH 1/3] Update event_delivery_semantics.md Customer asked question about how they could find the schema-id. Product described the process here https://brazetechnology.slack.com/archives/C037JNLUF0R/p1718152155589319?thread_ts=1718152054.348379&cid=C037JNLUF0R Customer asked in this support case https://braze.lightning.force.com/lightning/r/Case/500VP00000BH5zRYAT/view --- .../braze_currents/event_delivery_semantics.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_docs/_user_guide/data_and_analytics/braze_currents/event_delivery_semantics.md b/_docs/_user_guide/data_and_analytics/braze_currents/event_delivery_semantics.md index 84833f352d7..0737d48d04f 100644 --- a/_docs/_user_guide/data_and_analytics/braze_currents/event_delivery_semantics.md +++ b/_docs/_user_guide/data_and_analytics/braze_currents/event_delivery_semantics.md @@ -77,7 +77,7 @@ Currents will never write empty files. ### Avro schema changes -From time to time, Braze may make changes to the Avro schema when fields are added, changed, or removed. For our purposes here, there are two types of changes: breaking and non-breaking. In all cases, the `` will be advanced to indicate the schema was updated. +From time to time, Braze may make changes to the Avro schema when fields are added, changed, or removed. For our purposes here, there are two types of changes: breaking and non-breaking. In all cases, the `` will be advanced to indicate the schema was updated. Currents events written to Azure Blob Storage, Google Cloud Storage, Amazon S3 will write the `` in the path. For example `//////` #### Non-breaking changes From 3f79f7de657869495a00a9c8cc34014bb76e980b Mon Sep 17 00:00:00 2001 From: Josh McCrowell <113209750+josh-mccrowell-braze@users.noreply.github.com> Date: Thu, 13 Jun 2024 10:23:49 -0400 Subject: [PATCH 2/3] Update _docs/_user_guide/data_and_analytics/braze_currents/event_delivery_semantics.md --- .../braze_currents/event_delivery_semantics.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_docs/_user_guide/data_and_analytics/braze_currents/event_delivery_semantics.md b/_docs/_user_guide/data_and_analytics/braze_currents/event_delivery_semantics.md index 0737d48d04f..fb4d20f1629 100644 --- a/_docs/_user_guide/data_and_analytics/braze_currents/event_delivery_semantics.md +++ b/_docs/_user_guide/data_and_analytics/braze_currents/event_delivery_semantics.md @@ -77,7 +77,7 @@ Currents will never write empty files. ### Avro schema changes -From time to time, Braze may make changes to the Avro schema when fields are added, changed, or removed. For our purposes here, there are two types of changes: breaking and non-breaking. In all cases, the `` will be advanced to indicate the schema was updated. Currents events written to Azure Blob Storage, Google Cloud Storage, Amazon S3 will write the `` in the path. For example `//////` +From time to time, Braze may make changes to the Avro schema when fields are added, changed, or removed. For our purposes here, there are two types of changes: breaking and non-breaking. In all cases, the `` will be advanced to indicate the schema was updated. Currents events written to Azure Blob Storage, Google Cloud Storage, and Amazon S3 will write the `` in the path. For example `//////` #### Non-breaking changes From e3dc82f212c39a568c169e16f384ef34eb4b0c55 Mon Sep 17 00:00:00 2001 From: Josh McCrowell <113209750+josh-mccrowell-braze@users.noreply.github.com> Date: Thu, 13 Jun 2024 10:24:02 -0400 Subject: [PATCH 3/3] Update _docs/_user_guide/data_and_analytics/braze_currents/event_delivery_semantics.md --- .../braze_currents/event_delivery_semantics.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_docs/_user_guide/data_and_analytics/braze_currents/event_delivery_semantics.md b/_docs/_user_guide/data_and_analytics/braze_currents/event_delivery_semantics.md index fb4d20f1629..99944adb2e0 100644 --- a/_docs/_user_guide/data_and_analytics/braze_currents/event_delivery_semantics.md +++ b/_docs/_user_guide/data_and_analytics/braze_currents/event_delivery_semantics.md @@ -77,7 +77,7 @@ Currents will never write empty files. ### Avro schema changes -From time to time, Braze may make changes to the Avro schema when fields are added, changed, or removed. For our purposes here, there are two types of changes: breaking and non-breaking. In all cases, the `` will be advanced to indicate the schema was updated. Currents events written to Azure Blob Storage, Google Cloud Storage, and Amazon S3 will write the `` in the path. For example `//////` +From time to time, Braze may make changes to the Avro schema when fields are added, changed, or removed. For our purposes here, there are two types of changes: breaking and non-breaking. In all cases, the `` will be advanced to indicate the schema was updated. Currents events written to Azure Blob Storage, Google Cloud Storage, and Amazon S3 will write the `` in the path. For example `//////`. #### Non-breaking changes