You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@accumulo.apache.org by ct...@apache.org on 2016/11/22 19:38:35 UTC
[17/50] [abbrv] accumulo-website git commit: Use more specific links
to original blog posts
Use more specific links to original blog posts
Project: http://git-wip-us.apache.org/repos/asf/accumulo-website/repo
Commit: http://git-wip-us.apache.org/repos/asf/accumulo-website/commit/96a13b9e
Tree: http://git-wip-us.apache.org/repos/asf/accumulo-website/tree/96a13b9e
Diff: http://git-wip-us.apache.org/repos/asf/accumulo-website/diff/96a13b9e
Branch: refs/heads/master
Commit: 96a13b9e3c182228295d2b6fe28901c768acdd52
Parents: 899f3b1
Author: Christopher Tubbs <ct...@apache.org>
Authored: Wed Oct 26 15:45:42 2016 -0400
Committer: Christopher Tubbs <ct...@apache.org>
Committed: Wed Oct 26 15:45:42 2016 -0400
----------------------------------------------------------------------
_posts/blog/2014-05-03-accumulo-classloader.md | 2 +-
_posts/blog/2014-05-27-getting-started-with-accumulo-1.6.0.md | 2 +-
.../blog/2014-06-25-scaling-accumulo-with-multivolume-support.md | 2 +-
_posts/blog/2014-07-09-functional-reads-over-accumulo.md | 2 +-
...09-02-generating-keystores-for-configuring-accumulo-with-ssl.md | 2 +-
_posts/blog/2015-03-20-balancing-groups-of-tablets.md | 2 +-
.../blog/2015-04-06-replicating-data-across-accumulo-clusters.md | 2 +-
7 files changed, 7 insertions(+), 7 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/96a13b9e/_posts/blog/2014-05-03-accumulo-classloader.md
----------------------------------------------------------------------
diff --git a/_posts/blog/2014-05-03-accumulo-classloader.md b/_posts/blog/2014-05-03-accumulo-classloader.md
index c748720..83fbe33 100644
--- a/_posts/blog/2014-05-03-accumulo-classloader.md
+++ b/_posts/blog/2014-05-03-accumulo-classloader.md
@@ -4,7 +4,7 @@ date: 2014-05-03 17:00:00 +0000
author: Dave Marion
---
-Originally posted at [https://blogs.apache.org/accumulo/](https://blogs.apache.org/accumulo/)
+Originally posted at [https://blogs.apache.org/accumulo/entry/the_accumulo_classloader](https://blogs.apache.org/accumulo/entry/the_accumulo_classloader)
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.
http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/96a13b9e/_posts/blog/2014-05-27-getting-started-with-accumulo-1.6.0.md
----------------------------------------------------------------------
diff --git a/_posts/blog/2014-05-27-getting-started-with-accumulo-1.6.0.md b/_posts/blog/2014-05-27-getting-started-with-accumulo-1.6.0.md
index e577327..010611a 100644
--- a/_posts/blog/2014-05-27-getting-started-with-accumulo-1.6.0.md
+++ b/_posts/blog/2014-05-27-getting-started-with-accumulo-1.6.0.md
@@ -4,7 +4,7 @@ date: 2014-05-27 17:00:00 +0000
author: Josh Elser
---
-Originally posted at [https://blogs.apache.org/accumulo/](https://blogs.apache.org/accumulo/)
+Originally posted at [https://blogs.apache.org/accumulo/entry/getting_started_with_apache_accumulo](https://blogs.apache.org/accumulo/entry/getting_started_with_apache_accumulo)
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.
http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/96a13b9e/_posts/blog/2014-06-25-scaling-accumulo-with-multivolume-support.md
----------------------------------------------------------------------
diff --git a/_posts/blog/2014-06-25-scaling-accumulo-with-multivolume-support.md b/_posts/blog/2014-06-25-scaling-accumulo-with-multivolume-support.md
index 13fd3ba..2e1857b 100644
--- a/_posts/blog/2014-06-25-scaling-accumulo-with-multivolume-support.md
+++ b/_posts/blog/2014-06-25-scaling-accumulo-with-multivolume-support.md
@@ -4,7 +4,7 @@ date: 2014-06-25 17:00:00 +0000
author: Dave Marion & Eric Newton
---
-Originally posted at [https://blogs.apache.org/accumulo/](https://blogs.apache.org/accumulo/)
+Originally posted at [https://blogs.apache.org/accumulo/entry/scaling_accumulo_with_multi_volume](https://blogs.apache.org/accumulo/entry/scaling_accumulo_with_multi_volume)
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.
http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/96a13b9e/_posts/blog/2014-07-09-functional-reads-over-accumulo.md
----------------------------------------------------------------------
diff --git a/_posts/blog/2014-07-09-functional-reads-over-accumulo.md b/_posts/blog/2014-07-09-functional-reads-over-accumulo.md
index e5d05d4..5dc5c9a 100644
--- a/_posts/blog/2014-07-09-functional-reads-over-accumulo.md
+++ b/_posts/blog/2014-07-09-functional-reads-over-accumulo.md
@@ -4,7 +4,7 @@ date: 2014-07-09 17:00:00 +0000
author: Josh Elser
---
-Originally posted at [https://blogs.apache.org/accumulo/](https://blogs.apache.org/accumulo/)
+Originally posted at [https://blogs.apache.org/accumulo/entry/thinking_about_reads_over_accumulo](https://blogs.apache.org/accumulo/entry/thinking_about_reads_over_accumulo)
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.
http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/96a13b9e/_posts/blog/2014-09-02-generating-keystores-for-configuring-accumulo-with-ssl.md
----------------------------------------------------------------------
diff --git a/_posts/blog/2014-09-02-generating-keystores-for-configuring-accumulo-with-ssl.md b/_posts/blog/2014-09-02-generating-keystores-for-configuring-accumulo-with-ssl.md
index 549dcfe..0c87503 100644
--- a/_posts/blog/2014-09-02-generating-keystores-for-configuring-accumulo-with-ssl.md
+++ b/_posts/blog/2014-09-02-generating-keystores-for-configuring-accumulo-with-ssl.md
@@ -4,7 +4,7 @@ date: 2014-09-02 17:00:00 +0000
author: Josh Elser
---
-Originally posted at [https://blogs.apache.org/accumulo/](https://blogs.apache.org/accumulo/)
+Originally posted at [https://blogs.apache.org/accumulo/entry/generating_keystores_for_configuring_accumulo](https://blogs.apache.org/accumulo/entry/generating_keystores_for_configuring_accumulo)
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. [Apache Thrift][thrift] 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.
http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/96a13b9e/_posts/blog/2015-03-20-balancing-groups-of-tablets.md
----------------------------------------------------------------------
diff --git a/_posts/blog/2015-03-20-balancing-groups-of-tablets.md b/_posts/blog/2015-03-20-balancing-groups-of-tablets.md
index 7dc924e..7fb7b25 100644
--- a/_posts/blog/2015-03-20-balancing-groups-of-tablets.md
+++ b/_posts/blog/2015-03-20-balancing-groups-of-tablets.md
@@ -4,7 +4,7 @@ date: 2015-03-20 17:00:00 +0000
author: Keith Turner
---
-Originally posted at [https://blogs.apache.org/accumulo/](https://blogs.apache.org/accumulo/)
+Originally posted at [https://blogs.apache.org/accumulo/entry/balancing_groups_of_tablets](https://blogs.apache.org/accumulo/entry/balancing_groups_of_tablets)
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.
http://git-wip-us.apache.org/repos/asf/accumulo-website/blob/96a13b9e/_posts/blog/2015-04-06-replicating-data-across-accumulo-clusters.md
----------------------------------------------------------------------
diff --git a/_posts/blog/2015-04-06-replicating-data-across-accumulo-clusters.md b/_posts/blog/2015-04-06-replicating-data-across-accumulo-clusters.md
index 573adef..d480bf3 100644
--- a/_posts/blog/2015-04-06-replicating-data-across-accumulo-clusters.md
+++ b/_posts/blog/2015-04-06-replicating-data-across-accumulo-clusters.md
@@ -4,7 +4,7 @@ date: 2015-04-06 17:00:00 +0000
author: Josh Elser
---
-Originally posted at [https://blogs.apache.org/accumulo/](https://blogs.apache.org/accumulo/)
+Originally posted at [https://blogs.apache.org/accumulo/entry/data_center_replication](https://blogs.apache.org/accumulo/entry/data_center_replication)
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.