accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ctubb...@apache.org
Subject [2/2] accumulo git commit: Jekyll build from gh-pages:96a13b9
Date Wed, 26 Oct 2016 19:47:42 GMT
Jekyll build from gh-pages:96a13b9

Use more specific links to original blog posts


Project: http://git-wip-us.apache.org/repos/asf/accumulo/repo
Commit: http://git-wip-us.apache.org/repos/asf/accumulo/commit/d6fc392c
Tree: http://git-wip-us.apache.org/repos/asf/accumulo/tree/d6fc392c
Diff: http://git-wip-us.apache.org/repos/asf/accumulo/diff/d6fc392c

Branch: refs/heads/asf-site
Commit: d6fc392c96e57971e449a4891ad129743baf64bd
Parents: 56754f2
Author: Christopher Tubbs <ctubbsii@apache.org>
Authored: Wed Oct 26 15:45:42 2016 -0400
Committer: Christopher Tubbs <ctubbsii@apache.org>
Committed: Wed Oct 26 15:46:08 2016 -0400

----------------------------------------------------------------------
 blog/2014/05/03/accumulo-classloader.html         |  2 +-
 .../27/getting-started-with-accumulo-1.6.0.html   |  2 +-
 ...scaling-accumulo-with-multivolume-support.html |  2 +-
 .../07/09/functional-reads-over-accumulo.html     |  2 +-
 ...ystores-for-configuring-accumulo-with-ssl.html |  2 +-
 blog/2015/03/20/balancing-groups-of-tablets.html  |  2 +-
 ...replicating-data-across-accumulo-clusters.html |  2 +-
 feed.xml                                          | 18 +++++++++---------
 8 files changed, 16 insertions(+), 16 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/accumulo/blob/d6fc392c/blog/2014/05/03/accumulo-classloader.html
----------------------------------------------------------------------
diff --git a/blog/2014/05/03/accumulo-classloader.html b/blog/2014/05/03/accumulo-classloader.html
index af92036..8134365 100644
--- a/blog/2014/05/03/accumulo-classloader.html
+++ b/blog/2014/05/03/accumulo-classloader.html
@@ -180,7 +180,7 @@
           
           <h5>Dave Marion - 03 May 2014 </h5>
 
-<p>Originally posted at <a href="https://blogs.apache.org/accumulo/">https://blogs.apache.org/accumulo/</a></p>
+<p>Originally posted at <a href="https://blogs.apache.org/accumulo/entry/the_accumulo_classloader">https://blogs.apache.org/accumulo/entry/the_accumulo_classloader</a></p>
 
 <p>The Accumulo classloader is an integral part of the software. The classloader is
created before each of the services (master, tserver, gc, etc) are started and it is set as
the classloader for that service. The classloader was rewritten in version 1.5 and this article
will explain the new behavior.</p>
 

http://git-wip-us.apache.org/repos/asf/accumulo/blob/d6fc392c/blog/2014/05/27/getting-started-with-accumulo-1.6.0.html
----------------------------------------------------------------------
diff --git a/blog/2014/05/27/getting-started-with-accumulo-1.6.0.html b/blog/2014/05/27/getting-started-with-accumulo-1.6.0.html
index 4b53a35..1dc0310 100644
--- a/blog/2014/05/27/getting-started-with-accumulo-1.6.0.html
+++ b/blog/2014/05/27/getting-started-with-accumulo-1.6.0.html
@@ -180,7 +180,7 @@
           
           <h5>Josh Elser - 27 May 2014 </h5>
 
-<p>Originally posted at <a href="https://blogs.apache.org/accumulo/">https://blogs.apache.org/accumulo/</a></p>
+<p>Originally posted at <a href="https://blogs.apache.org/accumulo/entry/getting_started_with_apache_accumulo">https://blogs.apache.org/accumulo/entry/getting_started_with_apache_accumulo</a></p>
 
 <p>On May 12th, 2014, the Apache Accumulo project happily announced version 1.6.0 to
the community. This is a new major release for the project which contains many numerous new
features and fixes. For the full list of notable changes, I’d recommend that you check out
the release notes that were published alongside the release itself. For this post, I’d like
to cover some of the changes that have been made at the installation level that are a change
for users who are already familiar with the project.</p>
 

http://git-wip-us.apache.org/repos/asf/accumulo/blob/d6fc392c/blog/2014/06/25/scaling-accumulo-with-multivolume-support.html
----------------------------------------------------------------------
diff --git a/blog/2014/06/25/scaling-accumulo-with-multivolume-support.html b/blog/2014/06/25/scaling-accumulo-with-multivolume-support.html
index c6fe94b..1a4580c 100644
--- a/blog/2014/06/25/scaling-accumulo-with-multivolume-support.html
+++ b/blog/2014/06/25/scaling-accumulo-with-multivolume-support.html
@@ -180,7 +180,7 @@
           
           <h5>Dave Marion & Eric Newton - 25 Jun 2014 </h5>
 
-<p>Originally posted at <a href="https://blogs.apache.org/accumulo/">https://blogs.apache.org/accumulo/</a></p>
+<p>Originally posted at <a href="https://blogs.apache.org/accumulo/entry/scaling_accumulo_with_multi_volume">https://blogs.apache.org/accumulo/entry/scaling_accumulo_with_multi_volume</a></p>
 
 <p>MapReduce is a commonly used approach to querying or analyzing large amounts of
data. Typically MapReduce jobs are created using using some set of files in HDFS to produce
a result. When new files come in, they get added to the set, and the job gets run again. A
common Accumulo approach to this scenario is to load all of the data into a single instance
of Accumulo.</p>
 

http://git-wip-us.apache.org/repos/asf/accumulo/blob/d6fc392c/blog/2014/07/09/functional-reads-over-accumulo.html
----------------------------------------------------------------------
diff --git a/blog/2014/07/09/functional-reads-over-accumulo.html b/blog/2014/07/09/functional-reads-over-accumulo.html
index 6914fd3..b4a966e 100644
--- a/blog/2014/07/09/functional-reads-over-accumulo.html
+++ b/blog/2014/07/09/functional-reads-over-accumulo.html
@@ -180,7 +180,7 @@
           
           <h5>Josh Elser - 09 Jul 2014 </h5>
 
-<p>Originally posted at <a href="https://blogs.apache.org/accumulo/">https://blogs.apache.org/accumulo/</a></p>
+<p>Originally posted at <a href="https://blogs.apache.org/accumulo/entry/thinking_about_reads_over_accumulo">https://blogs.apache.org/accumulo/entry/thinking_about_reads_over_accumulo</a></p>
 
 <p>Table structure is a common area of discussion between all types of Accumulo users.
In the relational database realm, there was often a straightforward way that most users could
agree upon that would be ideal to store and query some dataset. Data was identified by its
schema, some fixed set of columns where each value within that column had some given characteristic.
One of the big pushes behind the “NoSQL” movement was a growing pain in representing evolving
data within a static schema. Applications like Accumulo removed that notion for a more flexible
layout where the columns vary per row, but this flexibility often sparks debates about how
data is “best” stored that often ends without a clear-cut winner.</p>
 

http://git-wip-us.apache.org/repos/asf/accumulo/blob/d6fc392c/blog/2014/09/02/generating-keystores-for-configuring-accumulo-with-ssl.html
----------------------------------------------------------------------
diff --git a/blog/2014/09/02/generating-keystores-for-configuring-accumulo-with-ssl.html b/blog/2014/09/02/generating-keystores-for-configuring-accumulo-with-ssl.html
index db1f502..d089059 100644
--- a/blog/2014/09/02/generating-keystores-for-configuring-accumulo-with-ssl.html
+++ b/blog/2014/09/02/generating-keystores-for-configuring-accumulo-with-ssl.html
@@ -180,7 +180,7 @@
           
           <h5>Josh Elser - 02 Sep 2014 </h5>
 
-<p>Originally posted at <a href="https://blogs.apache.org/accumulo/">https://blogs.apache.org/accumulo/</a></p>
+<p>Originally posted at <a href="https://blogs.apache.org/accumulo/entry/generating_keystores_for_configuring_accumulo">https://blogs.apache.org/accumulo/entry/generating_keystores_for_configuring_accumulo</a></p>
 
 <p>One of the major features added in Accumulo 1.6.0 was the ability to configure Accumulo
so that the Thrift communications will run over SSL. <a href="http://thrift.apache.org/">Apache
Thrift</a> is the remote procedure call library that is leverage for both intra-server
communication and client communication with Accumulo. Issuing these calls over a secure socket
ensures that unwanted actors cannot inspect the traffic sent across the wire. Given the sometimes
sensitive nature of data stored in Accumulo and the authentication details for users, ensuring
that no prying eyes have access to these communications is critical.</p>
 

http://git-wip-us.apache.org/repos/asf/accumulo/blob/d6fc392c/blog/2015/03/20/balancing-groups-of-tablets.html
----------------------------------------------------------------------
diff --git a/blog/2015/03/20/balancing-groups-of-tablets.html b/blog/2015/03/20/balancing-groups-of-tablets.html
index 1349f3d..02e10b5 100644
--- a/blog/2015/03/20/balancing-groups-of-tablets.html
+++ b/blog/2015/03/20/balancing-groups-of-tablets.html
@@ -180,7 +180,7 @@
           
           <h5>Keith Turner - 20 Mar 2015 </h5>
 
-<p>Originally posted at <a href="https://blogs.apache.org/accumulo/">https://blogs.apache.org/accumulo/</a></p>
+<p>Originally posted at <a href="https://blogs.apache.org/accumulo/entry/balancing_groups_of_tablets">https://blogs.apache.org/accumulo/entry/balancing_groups_of_tablets</a></p>
 
 <p>Accumulo has a pluggable tablet balancer that decides where tablets should be placed.
Accumulo’s default configuration spreads each tables tablets evenly and randomly across
the tablet servers. Each table can configure a custom balancer that does something different.</p>
 

http://git-wip-us.apache.org/repos/asf/accumulo/blob/d6fc392c/blog/2015/04/06/replicating-data-across-accumulo-clusters.html
----------------------------------------------------------------------
diff --git a/blog/2015/04/06/replicating-data-across-accumulo-clusters.html b/blog/2015/04/06/replicating-data-across-accumulo-clusters.html
index 5d953c2..ab08f96 100644
--- a/blog/2015/04/06/replicating-data-across-accumulo-clusters.html
+++ b/blog/2015/04/06/replicating-data-across-accumulo-clusters.html
@@ -180,7 +180,7 @@
           
           <h5>Josh Elser - 06 Apr 2015 </h5>
 
-<p>Originally posted at <a href="https://blogs.apache.org/accumulo/">https://blogs.apache.org/accumulo/</a></p>
+<p>Originally posted at <a href="https://blogs.apache.org/accumulo/entry/data_center_replication">https://blogs.apache.org/accumulo/entry/data_center_replication</a></p>
 
 <p>Traditionally, Apache Accumulo can only operate within the confines of a single
physical location. The primary reason for this restriction is that Accumulo relies heavily
on Apache ZooKeeper for distributed lock management and some distributed state. Due to the
consistent nature of ZooKeeper and its protocol, it doesn’t handle wide-area networks (WAN)
well. As such, Accumulo suffers the same problems operating over a WAN.</p>
 

http://git-wip-us.apache.org/repos/asf/accumulo/blob/d6fc392c/feed.xml
----------------------------------------------------------------------
diff --git a/feed.xml b/feed.xml
index b913665..5760584 100644
--- a/feed.xml
+++ b/feed.xml
@@ -6,13 +6,13 @@
 </description>
     <link>https://accumulo.apache.org/</link>
     <atom:link href="https://accumulo.apache.org/feed.xml" rel="self" type="application/rss+xml"/>
-    <pubDate>Wed, 26 Oct 2016 15:26:19 -0400</pubDate>
-    <lastBuildDate>Wed, 26 Oct 2016 15:26:19 -0400</lastBuildDate>
+    <pubDate>Wed, 26 Oct 2016 15:46:03 -0400</pubDate>
+    <lastBuildDate>Wed, 26 Oct 2016 15:46:03 -0400</lastBuildDate>
     <generator>Jekyll v3.2.1</generator>
     
       <item>
         <title>Replicating data across Accumulo clusters</title>
-        <description>&lt;p&gt;Originally posted at &lt;a href=&quot;https://blogs.apache.org/accumulo/&quot;&gt;https://blogs.apache.org/accumulo/&lt;/a&gt;&lt;/p&gt;
+        <description>&lt;p&gt;Originally posted at &lt;a href=&quot;https://blogs.apache.org/accumulo/entry/data_center_replication&quot;&gt;https://blogs.apache.org/accumulo/entry/data_center_replication&lt;/a&gt;&lt;/p&gt;
 
 &lt;p&gt;Traditionally, Apache Accumulo can only operate within the confines of a
single physical location. The primary reason for this restriction is that Accumulo relies
heavily on Apache ZooKeeper for distributed lock management and some distributed state. Due
to the consistent nature of ZooKeeper and its protocol, it doesn’t handle wide-area networks
(WAN) well. As such, Accumulo suffers the same problems operating over a WAN.&lt;/p&gt;
 
@@ -78,7 +78,7 @@
     
       <item>
         <title>Balancing Groups of Tablets</title>
-        <description>&lt;p&gt;Originally posted at &lt;a href=&quot;https://blogs.apache.org/accumulo/&quot;&gt;https://blogs.apache.org/accumulo/&lt;/a&gt;&lt;/p&gt;
+        <description>&lt;p&gt;Originally posted at &lt;a href=&quot;https://blogs.apache.org/accumulo/entry/balancing_groups_of_tablets&quot;&gt;https://blogs.apache.org/accumulo/entry/balancing_groups_of_tablets&lt;/a&gt;&lt;/p&gt;
 
 &lt;p&gt;Accumulo has a pluggable tablet balancer that decides where tablets should
be placed. Accumulo’s default configuration spreads each tables tablets evenly and randomly
across the tablet servers. Each table can configure a custom balancer that does something
different.&lt;/p&gt;
 
@@ -112,7 +112,7 @@
     
       <item>
         <title>Generating Keystores for configuring Accumulo with SSL</title>
-        <description>&lt;p&gt;Originally posted at &lt;a href=&quot;https://blogs.apache.org/accumulo/&quot;&gt;https://blogs.apache.org/accumulo/&lt;/a&gt;&lt;/p&gt;
+        <description>&lt;p&gt;Originally posted at &lt;a href=&quot;https://blogs.apache.org/accumulo/entry/generating_keystores_for_configuring_accumulo&quot;&gt;https://blogs.apache.org/accumulo/entry/generating_keystores_for_configuring_accumulo&lt;/a&gt;&lt;/p&gt;
 
 &lt;p&gt;One of the major features added in Accumulo 1.6.0 was the ability to configure
Accumulo so that the Thrift communications will run over SSL. &lt;a href=&quot;http://thrift.apache.org/&quot;&gt;Apache
Thrift&lt;/a&gt; is the remote procedure call library that is leverage for both intra-server
communication and client communication with Accumulo. Issuing these calls over a secure socket
ensures that unwanted actors cannot inspect the traffic sent across the wire. Given the sometimes
sensitive nature of data stored in Accumulo and the authentication details for users, ensuring
that no prying eyes have access to these communications is critical.&lt;/p&gt;
 
@@ -230,7 +230,7 @@ rpc.javax.net.ssl.trustStorePassword  truststore-password
     
       <item>
         <title>Functional reads over Accumulo</title>
-        <description>&lt;p&gt;Originally posted at &lt;a href=&quot;https://blogs.apache.org/accumulo/&quot;&gt;https://blogs.apache.org/accumulo/&lt;/a&gt;&lt;/p&gt;
+        <description>&lt;p&gt;Originally posted at &lt;a href=&quot;https://blogs.apache.org/accumulo/entry/thinking_about_reads_over_accumulo&quot;&gt;https://blogs.apache.org/accumulo/entry/thinking_about_reads_over_accumulo&lt;/a&gt;&lt;/p&gt;
 
 &lt;p&gt;Table structure is a common area of discussion between all types of Accumulo
users. In the relational database realm, there was often a straightforward way that most users
could agree upon that would be ideal to store and query some dataset. Data was identified
by its schema, some fixed set of columns where each value within that column had some given
characteristic. One of the big pushes behind the “NoSQL” movement was a growing pain in
representing evolving data within a static schema. Applications like Accumulo removed that
notion for a more flexible layout where the columns vary per row, but this flexibility often
sparks debates about how data is “best” stored that often ends without a clear-cut winner.&lt;/p&gt;
 
@@ -294,7 +294,7 @@ rpc.javax.net.ssl.trustStorePassword  truststore-password
     
       <item>
         <title>Scaling Accumulo with Multi-Volume Support</title>
-        <description>&lt;p&gt;Originally posted at &lt;a href=&quot;https://blogs.apache.org/accumulo/&quot;&gt;https://blogs.apache.org/accumulo/&lt;/a&gt;&lt;/p&gt;
+        <description>&lt;p&gt;Originally posted at &lt;a href=&quot;https://blogs.apache.org/accumulo/entry/scaling_accumulo_with_multi_volume&quot;&gt;https://blogs.apache.org/accumulo/entry/scaling_accumulo_with_multi_volume&lt;/a&gt;&lt;/p&gt;
 
 &lt;p&gt;MapReduce is a commonly used approach to querying or analyzing large amounts
of data. Typically MapReduce jobs are created using using some set of files in HDFS to produce
a result. When new files come in, they get added to the set, and the job gets run again. A
common Accumulo approach to this scenario is to load all of the data into a single instance
of Accumulo.&lt;/p&gt;
 
@@ -455,7 +455,7 @@ rpc.javax.net.ssl.trustStorePassword  truststore-password
     
       <item>
         <title>Getting Started with Apache Accumulo 1.6.0</title>
-        <description>&lt;p&gt;Originally posted at &lt;a href=&quot;https://blogs.apache.org/accumulo/&quot;&gt;https://blogs.apache.org/accumulo/&lt;/a&gt;&lt;/p&gt;
+        <description>&lt;p&gt;Originally posted at &lt;a href=&quot;https://blogs.apache.org/accumulo/entry/getting_started_with_apache_accumulo&quot;&gt;https://blogs.apache.org/accumulo/entry/getting_started_with_apache_accumulo&lt;/a&gt;&lt;/p&gt;
 
 &lt;p&gt;On May 12th, 2014, the Apache Accumulo project happily announced version
1.6.0 to the community. This is a new major release for the project which contains many numerous
new features and fixes. For the full list of notable changes, I’d recommend that you check
out the release notes that were published alongside the release itself. For this post, I’d
like to cover some of the changes that have been made at the installation level that are a
change for users who are already familiar with the project.&lt;/p&gt;
 
@@ -519,7 +519,7 @@ rpc.javax.net.ssl.trustStorePassword  truststore-password
     
       <item>
         <title>The Accumulo ClassLoader</title>
-        <description>&lt;p&gt;Originally posted at &lt;a href=&quot;https://blogs.apache.org/accumulo/&quot;&gt;https://blogs.apache.org/accumulo/&lt;/a&gt;&lt;/p&gt;
+        <description>&lt;p&gt;Originally posted at &lt;a href=&quot;https://blogs.apache.org/accumulo/entry/the_accumulo_classloader&quot;&gt;https://blogs.apache.org/accumulo/entry/the_accumulo_classloader&lt;/a&gt;&lt;/p&gt;
 
 &lt;p&gt;The Accumulo classloader is an integral part of the software. The classloader
is created before each of the services (master, tserver, gc, etc) are started and it is set
as the classloader for that service. The classloader was rewritten in version 1.5 and this
article will explain the new behavior.&lt;/p&gt;
 


Mime
View raw message