From 7c762d770a82da397956b80379a6fb73505835af Mon Sep 17 00:00:00 2001
From: Google APIs <noreply@google.com>
Date: Wed, 26 Jul 2023 08:17:53 -0700
Subject: [PATCH] docs: clarified where ordering_key will be written if
 write_metadata is set

PiperOrigin-RevId: 551210991
---
 google/pubsub/v1/pubsub.proto | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/google/pubsub/v1/pubsub.proto b/google/pubsub/v1/pubsub.proto
index 9ff80f2f6b520..4468de17831e0 100644
--- a/google/pubsub/v1/pubsub.proto
+++ b/google/pubsub/v1/pubsub.proto
@@ -1030,7 +1030,11 @@ message CloudStorageConfig {
   // Message payloads and metadata will be written to files as an Avro binary.
   message AvroConfig {
     // When true, write the subscription name, message_id, publish_time,
-    // attributes, and ordering_key as additional fields in the output.
+    // attributes, and ordering_key as additional fields in the output. The
+    // subscription name, message_id, and publish_time fields are put in their
+    // own fields while all other message properties other than data (for
+    // example, an ordering_key, if present) are added as entries in the
+    // attributes map.
     bool write_metadata = 1;
   }