incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Incubator Wiki] Trivial Update of "HeartProposal" by Frederick Haebin Na
Date Wed, 23 Jul 2008 09:52:59 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The following page has been changed by Frederick Haebin Na:
http://wiki.apache.org/incubator/HeartProposal

------------------------------------------------------------------------------
  ## page was renamed from HRdfStoreProposal
  == Abstract ==
- !Heart will develop a planet-scale RDF data store based on [http://hadoop.apache.org Hadoop]
& [http://hadoop.apache.org/hbase Hbase].
+ Heart will develop a planet-scale RDF data store based on [http://hadoop.apache.org Hadoop]
& [http://hadoop.apache.org/hbase Hbase].
  
  == Proposal ==
- !Heart will develop a Hadoop subsystem for RDF, called !Heart, which uses Hbase + !MapReduce
to store RDF data and execute queries (e.g., SPARQL) on them.
+ Heart will develop a Hadoop subsystem for RDF, called Heart, which uses Hbase + !MapReduce
to store RDF data and execute queries (e.g., SPARQL) on them.
  
  == Background ==
  We can store very sparse RDF data in a single table in Hbase, with as many columns as they
need. For example, we might make a row for each RDF subject in a table and store all the properties
and their values as columns in the table. This reduces costly self-joins in answering queries
asking questions on the same subject, which results in efficient processing of queries, although
we still need self-joins to answer RDF path queries.
@@ -15, +15 @@

  == Rationale ==
  === Heart Data Loader ===
  
- !Heart Data Loader (HDL) reads RDF data from a file, and organizes the data into a Hbase
table in such a way that efficient query processing is possible. In Hbase, we can store everything
in a single table. The sparsicy of RDF data is not a problem, because Hbase, which is a column-based
storage and adopts various compression techniques, is very good at dealing with nulls in the
table
+ Heart Data Loader (HDL) reads RDF data from a file, and organizes the data into a Hbase
table in such a way that efficient query processing is possible. In Hbase, we can store everything
in a single table. The sparsicy of RDF data is not a problem, because Hbase, which is a column-based
storage and adopts various compression techniques, is very good at dealing with nulls in the
table
  
  === Heart Query Processor ===
  
- !Heart Query Processor (HQP) executes RDF queries on RDF data stored in a Hbase table. It
translates RDF queries into API calls to Hbase, or !MapReduce jobs, gathers and returns the
results to the user.
+ Heart Query Processor (HQP) executes RDF queries on RDF data stored in a Hbase table. It
translates RDF queries into API calls to Hbase, or !MapReduce jobs, gathers and returns the
results to the user.
  
  Query processing steps are as follows:
  
@@ -29, +29 @@

  Implemenation of each step may proceed as an individual issue.
  === Heart Data Materializer ===
  
- !Heart Data Materializer (HDM) pre-computes RDF path queries and stores the results into
a Hbase table. Later, HQP uses those materialized data for efficient processing of RDF path
queries. 
+ Heart Data Materializer (HDM) pre-computes RDF path queries and stores the results into
a Hbase table. Later, HQP uses those materialized data for efficient processing of RDF path
queries. 
  
  == Current Status ==
  
@@ -41, +41 @@

  
  === Community ===
  
- !Heart seeks to develop developer and user communities during incubation. 
+ Heart seeks to develop developer and user communities during incubation. 
  
  == Core Developers ==
  
@@ -49, +49 @@

  
  == Alignment ==
  
- The developers of !Heart want to work with the Apache Software Foundation specifically because
Apache has proven to provide a strong foundation and set of practices for developing standards-based
infrastructure and server components. 
+ The developers of Heart want to work with the Apache Software Foundation specifically because
Apache has proven to provide a strong foundation and set of practices for developing standards-based
infrastructure and server components. 
  
  == Known Risks ==
  === Orphaned products ===
@@ -59, +59 @@

  
  === Homogenous Developers ===
  We have only two core developers, which makes them at least not homogenous.
- Edward and Inchul know each other because of their common interest in !Heart.
+ Edward and Inchul know each other because of their common interest in Heart.
  
  === Reliance on Salaried Developers ===
  Edward is a full-time open source developer at NHN, and Inchul is working
  on a PhD program majoring Computer Science at KAIST.
  
  === Relationships with Other Apache Products ===
- !Heart has a strong relationship with Apache [http://hadoop.apache.org Hadoop] & [http://hadoop.apache.org/hbase
Hbase]. Being part of Apache could help for a closer collaboration between the three projects.
+ Heart has a strong relationship with Apache [http://hadoop.apache.org Hadoop] & [http://hadoop.apache.org/hbase
Hbase]. Being part of Apache could help for a closer collaboration between the three projects.
  
  === An Excessive Fascination with the Apache Brand ===
  

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message