You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@kudu.apache.org by ab...@apache.org on 2020/08/03 18:19:39 UTC
[kudu-site] branch asf-site updated: Publish commit(s) from site
source repo: dd10e5918 Fix link to Kudu examples in community page
c8191e299 site: add builds@kudu.apache.org
This is an automated email from the ASF dual-hosted git repository.
abukor pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/kudu-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 60eb1cd Publish commit(s) from site source repo: dd10e5918 Fix link to Kudu examples in community page c8191e299 site: add builds@kudu.apache.org
60eb1cd is described below
commit 60eb1cda198e702cd71f537f0bbd71e67e9e3ef9
Author: Attila Bukor <ab...@apache.org>
AuthorDate: Mon Aug 3 20:19:27 2020 +0200
Publish commit(s) from site source repo:
dd10e5918 Fix link to Kudu examples in community page
c8191e299 site: add builds@kudu.apache.org
Site-Repo-Commit: dd10e5918c13c73f27f1ce652ca1d10dabec58fd
---
community.html | 25 ++++++++++++-------------
feed.xml | 2 +-
2 files changed, 13 insertions(+), 14 deletions(-)
diff --git a/community.html b/community.html
index 1577ffc..233ced6 100644
--- a/community.html
+++ b/community.html
@@ -110,10 +110,9 @@
<p>Get help using Kudu or contribute to the project on our mailing lists or our chat room:</p>
<ul>
- <li><strong><a href="http://mail-archives.apache.org/mod_mbox/kudu-user/">user@kudu.apache.org</a></strong>
+ <li><strong><a href="https://lists.apache.org/list.html?user@kudu.apache.org">user@kudu.apache.org</a></strong>
(<a href="mailto:user-subscribe@kudu.apache.org">subscribe</a>)
(<a href="mailto:user-unsubscribe@kudu.apache.org">unsubscribe</a>)
-(<a href="http://mail-archives.apache.org/mod_mbox/kudu-user/">archives</a>) -
for usage questions, help, and announcements.</li>
<li><strong><a class="icon slack" href="https://getkudu-slack.herokuapp.com/">Kudu Slack channel</a></strong> -
where many Kudu developers and users hang out to answer questions and chat.</li>
@@ -122,34 +121,34 @@ where many Kudu developers and users hang out to answer questions and chat.</li>
<p><strong>Developer mailing lists</strong></p>
<ul>
- <li><strong><a href="http://mail-archives.apache.org/mod_mbox/kudu-dev/">dev@kudu.apache.org</a></strong>
+ <li><strong><a href="https://lists.apache.org/list.html?dev@kudu.apache.org">dev@kudu.apache.org</a></strong>
(<a href="mailto:dev-subscribe@kudu.apache.org">subscribe</a>)
(<a href="mailto:dev-unsubscribe@kudu.apache.org">unsubscribe</a>)
-(<a href="http://mail-archives.apache.org/mod_mbox/kudu-dev/">archives</a>) -
for people who want to contribute code to Kudu.</li>
- <li><strong><a href="http://mail-archives.apache.org/mod_mbox/kudu-issues/">issues@kudu.apache.org</a></strong>
+ <li><strong><a href="https://lists.apache.org/list.html?builds@kudu.apache.org">builds@kudu.apache.org</a></strong>
+(<a href="mailto:builds-subscribe@kudu.apache.org">subscribe</a>)
+(<a href="mailto:builds-unsubscribe@kudu.apache.org">unsubscribe</a>)
+for discussions and notifications surrounding build infrastructure.</li>
+ <li><strong><a href="https://lists.apache.org/list.html?issues@kudu.apache.org">issues@kudu.apache.org</a></strong>
(<a href="mailto:issues-subscribe@kudu.apache.org">subscribe</a>)
(<a href="mailto:issues-unsubscribe@kudu.apache.org">unsubscribe</a>)
-(<a href="http://mail-archives.apache.org/mod_mbox/kudu-issues/">archives</a>) -
receives an email notification for all ticket updates made in the <a href="https://issues.apache.org/jira/browse/KUDU">Kudu JIRA issue tracker</a>.</li>
- <li><strong><a href="http://mail-archives.apache.org/mod_mbox/kudu-reviews/">reviews@kudu.apache.org</a></strong>
+ <li><strong><a href="https://lists.apache.org/list.html?reviews@kudu.apache.org">reviews@kudu.apache.org</a></strong>
(<a href="mailto:reviews-subscribe@kudu.apache.org">subscribe</a>)
(<a href="mailto:reviews-unsubscribe@kudu.apache.org">unsubscribe</a>)
-(<a href="http://mail-archives.apache.org/mod_mbox/kudu-reviews/">archives</a>) -
receives an email notification for all code review requests and responses on the
<a href="http://gerrit.cloudera.org:8080/#/q/status:open+project:kudu">Kudu Gerrit</a>.</li>
- <li><strong><a href="http://mail-archives.apache.org/mod_mbox/kudu-commits/">commits@kudu.apache.org</a></strong>
+ <li><strong><a href="https://lists.apache.org/list.html?commits@kudu.apache.org">commits@kudu.apache.org</a></strong>
(<a href="mailto:commits-subscribe@kudu.apache.org">subscribe</a>)
(<a href="mailto:commits-unsubscribe@kudu.apache.org">unsubscribe</a>)
-(<a href="http://mail-archives.apache.org/mod_mbox/kudu-commits/">archives</a>) -
receives an email notification of all code changes to the
-<a href="https://github.com/apache/incubator-kudu/">Kudu Git repository</a>.</li>
+<a href="https://github.com/apache/kudu/">Kudu Git repository</a>.</li>
</ul>
<p><strong>Other developer resources</strong></p>
<ul>
- <li><strong><a class="icon github" href="https://github.com/apache/incubator-kudu">GitHub</a></strong></li>
+ <li><strong><a class="icon github" href="https://github.com/apache/kudu">GitHub</a></strong></li>
<li><strong><a class="icon gerrit" href="http://gerrit.cloudera.org:8080/#/q/status:open+project:kudu">Gerrit Code Review</a></strong></li>
<li><strong><a class="icon jira" href="https://issues.apache.org/jira/browse/KUDU">JIRA Issue Tracker</a></strong></li>
</ul>
@@ -232,7 +231,7 @@ before you get started.</p>
<h4 id="request-and-review-examples">Request and review examples.</h4>
-<p>The <a href="https://github.com/cloudera/kudu-examples">kudu-examples</a> repository
+<p>The <a href="https://github.com/apache/kudu/tree/master/examples">examples</a> directory
includes working code examples. As more examples are requested and added, they
will need review and clean-up. This is another way you can get involved.</p>
diff --git a/feed.xml b/feed.xml
index c535fa1..204b32f 100644
--- a/feed.xml
+++ b/feed.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.1.1">Jekyll</generator><link href="/feed.xml" rel="self" type="application/atom+xml" /><link href="/" rel="alternate" type="text/html" /><updated>2020-07-31T18:46:28+02:00</updated><id>/feed.xml</id><entry><title type="html">Building Near Real-time Big Data Lake</title><link href="/2020/07/30/building-near-real-time-big-data-lake.html" rel="alternate" type="t [...]
+<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.1.1">Jekyll</generator><link href="/feed.xml" rel="self" type="application/atom+xml" /><link href="/" rel="alternate" type="text/html" /><updated>2020-08-03T20:19:03+02:00</updated><id>/feed.xml</id><entry><title type="html">Building Near Real-time Big Data Lake</title><link href="/2020/07/30/building-near-real-time-big-data-lake.html" rel="alternate" type="t [...]
<p>This is the second part of the series. In <a href="https://boristyukin.com/building-near-real-time-big-data-lake-part-i/">Part 1</a>
I wrote about our use-case for the Data Lake architecture and shared our success story.</p>