You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by gi...@apache.org on 2020/05/30 18:03:02 UTC
[beam] branch asf-site updated: Publishing website 2020/05/30
18:02:51 at commit 1bd1508
This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/beam.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 6186d1d Publishing website 2020/05/30 18:02:51 at commit 1bd1508
6186d1d is described below
commit 6186d1d659f58774e816243c30701ad1bf2dee6f
Author: jenkins <bu...@apache.org>
AuthorDate: Sat May 30 18:02:52 2020 +0000
Publishing website 2020/05/30 18:02:51 at commit 1bd1508
---
website/generated-content/documentation/index.xml | 2 +-
website/generated-content/documentation/programming-guide/index.html | 2 +-
website/generated-content/sitemap.xml | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/website/generated-content/documentation/index.xml b/website/generated-content/documentation/index.xml
index 72ad018..ebd0ca3 100644
--- a/website/generated-content/documentation/index.xml
+++ b/website/generated-content/documentation/index.xml
@@ -3162,7 +3162,7 @@ tuples - have numerical indices instead.</li>
languages: int, long, string, etc.</li>
<li>Often a field type can be marked as optional (sometimes referred to as nullable) or required.</li>
</ul>
-<p>Oten records have a nested structure. A nested structure occurs when a field itself has subfields so the
+<p>Often records have a nested structure. A nested structure occurs when a field itself has subfields so the
type of the field itself has a schema. Fields that are array or map types is also a common feature of these structured
records.</p>
<p>For example, consider the following schema, representing actions in a fictitious e-commerce company:</p>
diff --git a/website/generated-content/documentation/programming-guide/index.html b/website/generated-content/documentation/programming-guide/index.html
index 8bb8ecf..14a6287 100644
--- a/website/generated-content/documentation/programming-guide/index.html
+++ b/website/generated-content/documentation/programming-guide/index.html
@@ -1340,7 +1340,7 @@ structures that can often be determined by examining the type. Even within a SDK
clear structure that can be inferred by inspecting the class. By understanding the structure of a pipeline’s
records, we can provide much more concise APIs for data processing.</p><h3 id=what-is-a-schema>6.1. What is a schema</h3><p>Most structured records share some common characteristics:</p><ul><li>They can be subdivided into separate named fields. Fields usually have string names, but sometimes - as in the case of indexed
tuples - have numerical indices instead.</li><li>There is a confined list of primitive types that a field can have. These often match primitive types in most programming
-languages: int, long, string, etc.</li><li>Often a field type can be marked as optional (sometimes referred to as nullable) or required.</li></ul><p>Oten records have a nested structure. A nested structure occurs when a field itself has subfields so the
+languages: int, long, string, etc.</li><li>Often a field type can be marked as optional (sometimes referred to as nullable) or required.</li></ul><p>Often records have a nested structure. A nested structure occurs when a field itself has subfields so the
type of the field itself has a schema. Fields that are array or map types is also a common feature of these structured
records.</p><p>For example, consider the following schema, representing actions in a fictitious e-commerce company:</p><p><strong>Purchase</strong></p><table><thead><tr class=header><th><b>Field Name</b></th><th><b>Field Type</b></th></tr></thead><tbody><tr><td>userId</td><td>STRING</td></tr><tr><td>itemId</td><td>INT64</td></tr><tr><td>shippingAddress</td><td>ROW(ShippingAddress)</td></tr><tr><td>cost</td><td>INT64</td></tr><tr><td>transactions</td><td>ARRAY[ROW(Transaction)]</td></tr>< [...]
is a nested row containing its own schema. Each purchase also contains an array of credit-card transactions
diff --git a/website/generated-content/sitemap.xml b/website/generated-content/sitemap.xml
index bbbbe63..242273e 100644
--- a/website/generated-content/sitemap.xml
+++ b/website/generated-content/sitemap.xml
@@ -1 +1 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?><urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xhtml="http://www.w3.org/1999/xhtml"><url><loc>/categories/blog/</loc><lastmod>2020-05-28T15:14:36-07:00</lastmod></url><url><loc>/blog/</loc><lastmod>2020-05-28T15:14:36-07:00</lastmod></url><url><loc>/categories/</loc><lastmod>2020-05-28T15:14:36-07:00</lastmod></url><url><loc>/categories/python/</loc><lastmod>2020-05-28T15:14:36-07:00</lastmod></url><url><loc>/blog/ [...]
\ No newline at end of file
+<?xml version="1.0" encoding="utf-8" standalone="yes"?><urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xhtml="http://www.w3.org/1999/xhtml"><url><loc>/categories/blog/</loc><lastmod>2020-05-28T15:14:36-07:00</lastmod></url><url><loc>/blog/</loc><lastmod>2020-05-28T15:14:36-07:00</lastmod></url><url><loc>/categories/</loc><lastmod>2020-05-28T15:14:36-07:00</lastmod></url><url><loc>/categories/python/</loc><lastmod>2020-05-28T15:14:36-07:00</lastmod></url><url><loc>/blog/ [...]
\ No newline at end of file