avro-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From fo...@apache.org
Subject [avro] branch master updated: AVRO-XXX: Fix typo in spec
Date Tue, 30 Apr 2019 08:49:28 GMT
This is an automated email from the ASF dual-hosted git repository.

fokko pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/avro.git

The following commit(s) were added to refs/heads/master by this push:
     new 544e372  AVRO-XXX: Fix typo in spec
544e372 is described below

commit 544e372c63daa720a01b4d558d53fb12aa6016b8
Author: Fokko Driesprong <fokko@apache.org>
AuthorDate: Tue Apr 30 10:49:23 2019 +0200

    AVRO-XXX: Fix typo in spec
 doc/src/content/xdocs/spec.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/src/content/xdocs/spec.xml b/doc/src/content/xdocs/spec.xml
index 0c3ff0b..09b5b35 100644
--- a/doc/src/content/xdocs/spec.xml
+++ b/doc/src/content/xdocs/spec.xml
@@ -605,7 +605,7 @@
         <p>In some situations a single Avro serialized object is to be stored for a
         longer period of time. One very common example is storing Avro records
         for several weeks in an <a href="http://kafka.apache.org/">Apache Kafka</a>
-        <p>In the period after a schema change this persistance system will contain
+        <p>In the period after a schema change this persistence system will contain
         that have been written with different schemas. So the need arises to know which schema
         was used to write a record to support schema evolution correctly.
         In most cases the schema itself is too large to include in the message,

View raw message