<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (earth2marsh)</title>
    <link>https://pinboard.in/u:earth2marsh/public/</link>
    <description>recent bookmarks from earth2marsh</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="http://opentsdb.net/"/>
	<rdf:li rdf:resource="http://www.cloudera.com/blog/2011/10/introducing-crunch/"/>
	<rdf:li rdf:resource="http://developer.yahoo.com/blogs/hadoop/posts/2010/08/pig_and_hive_at_yahoo/"/>
	<rdf:li rdf:resource="http://developer.yahoo.com/blogs/hadoop/posts/2010/01/comparing_pig_latin_and_sql_fo/"/>
	<rdf:li rdf:resource="http://engineering.twitter.com/2011/08/storm-is-coming-more-details-and-plans.html"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://opentsdb.net/">
    <title>OpenTSDB - A Distributed, Scalable Monitoring System</title>
    <dc:date>2013-10-10T00:32:03+00:00</dc:date>
    <link>http://opentsdb.net/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[Carbon / Graphite alternative "a distributed, scalable Time Series Database (TSDB) written on top of HBase. OpenTSDB was written to address a common need: store, index and serve metrics collected from computer systems (network gear, operating systems, applications) at a large scale, and make this data easily accessible and graphable."]]></description>
<dc:subject>analytics metrics database distributed hadoop monitoring</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:e20aac2d2e6f/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:analytics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:metrics"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:database"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:distributed"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:hadoop"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:monitoring"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.cloudera.com/blog/2011/10/introducing-crunch/">
    <title>Introducing Crunch: Easy MapReduce Pipelines for Hadoop | Apache Hadoop for the Enterprise | Cloudera</title>
    <dc:date>2012-02-15T04:09:10+00:00</dc:date>
    <link>http://www.cloudera.com/blog/2011/10/introducing-crunch/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA[""]]></description>
<dc:subject>hadoop java mapreduce pipeline data jobs</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:b32e8dd57c9a/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:hadoop"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:java"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:mapreduce"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:pipeline"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:jobs"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://developer.yahoo.com/blogs/hadoop/posts/2010/08/pig_and_hive_at_yahoo/">
    <title>Pig and Hive at Yahoo! · Yahoo! Hadoop Blog</title>
    <dc:date>2012-01-25T07:04:10+00:00</dc:date>
    <link>http://developer.yahoo.com/blogs/hadoop/posts/2010/08/pig_and_hive_at_yahoo/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["The data preparation phase is often known as ETL (Extract Transform Load) or the data factory. "Factory" is a good analogy because it captures the essence of what is being done in this stage: Just as a physical factory brings in raw materials and outputs products ready for consumers, so a data factory brings in raw data and produces data sets ready for data users to consume. Raw data is loaded in, cleaned up, conformed to the selected data model, joined with other data sources, and so on. Users in this phase are generally engineers, data specialists, or researchers.

The data presentation phase is usually referred to as the data warehouse. A warehouse stores products ready for consumers; they need only come and select the proper products off of the shelves. In this phase, users may be engineers using the data for their systems, analysts, or decisionmakers.

Given the different workloads and different users for each phase, we have found that different tools work best in each phase. Pig (combined with a workflow system such as Oozie) is best suited for the data factory, and Hive for the data warehouse."]]></description>
<dc:subject>comparison hadoop pig hive data factory</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:79edac77752e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:comparison"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:hadoop"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:pig"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:hive"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:data"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:factory"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://developer.yahoo.com/blogs/hadoop/posts/2010/01/comparing_pig_latin_and_sql_fo/">
    <title>Comparing Pig Latin and SQL for Constructing Data Processing Pipelines · Yahoo! Hadoop Blog</title>
    <dc:date>2012-01-25T05:54:01+00:00</dc:date>
    <link>http://developer.yahoo.com/blogs/hadoop/posts/2010/01/comparing_pig_latin_and_sql_fo/</link>
    <dc:creator>earth2marsh</dc:creator><description><![CDATA["SQL's ubiquity is convenient. However, I believe that Pig Latin is a more natural choice for constructing data pipelines, for several reasons:

Pig Latin is procedural, where SQL is declarative.
Pig Latin allows pipeline developers to decide where to checkpoint data in the pipeline.
Pig Latin allows the developer to select specific operator implementations directly rather than relying on the optimizer.
Pig Latin supports splits in the pipeline.
Pig Latin allows developers to insert their own code almost anywhere in the data pipeline."]]></description>
<dc:subject>hadoop mapreduce sql pig comparison</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:bec43fa8578d/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:hadoop"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:mapreduce"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:sql"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:pig"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:comparison"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://engineering.twitter.com/2011/08/storm-is-coming-more-details-and-plans.html">
    <title>[from sordyl] Twitter open sources Storm a mapreduce framework</title>
    <dc:date>2011-08-05T13:34:40+00:00</dc:date>
    <link>http://engineering.twitter.com/2011/08/storm-is-coming-more-details-and-plans.html</link>
    <dc:creator>earth2marsh</dc:creator><dc:subject>twitter hadoop mapreduce cep</dc:subject>
<dc:identifier>https://pinboard.in/u:earth2marsh/b:ffe95fd19b53/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:twitter"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:hadoop"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:mapreduce"/>
	<rdf:li rdf:resource="https://pinboard.in/u:earth2marsh/t:cep"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>