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 "TajoProposal" by HyunsikChoi
Date Mon, 25 Feb 2013 08:16:01 GMT
Dear Wiki user,

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

The "TajoProposal" page has been changed by HyunsikChoi:
http://wiki.apache.org/incubator/TajoProposal?action=diff&rev1=6&rev2=7

Comment:
Fixed some typo errors.

  We will discuss the milestone and the future plan in an open forum. We plan to encourage
an environment that supports a meritocracy. The contributors will have different privileges
according to their contributions.
  
  == Community ==
- Big data analysis has gained attention from open source communities, industrial and academic
areas. Some projects related to Hadoop already have very large and active communities. We
expect that Tajo also will establish an active community. Since Tajo is relatively mature
than other projects that aims at low-latency system projects that support SQL and is already
in the alpha stage, it will attract a large community soon.
+ Big data analysis has gained attention from open source communities, industrial and academic
areas. Some projects related to Hadoop already have very large and active communities. We
expect that Tajo also will establish an active community. Since Tajo already works for some
features and is in the alpha stage, it will attract a large community soon.
  
  == Core Developers ==
  Core developers are very experienced in the Apache Hadoop ecosystem. To achieve more diversity
of developers, we will be eager to recruit developers from diverse companies.
@@ -42, +42 @@

  = Known Risks =
  
  == Orphaned Products ==
- Most of codes have been developed by two core developers, who are Hyunsik Choi and Jihoon
Son. However, they are guaranteed to have enough time to develop Tajo for years. As you can
see the commit history, they have participated in this project for about two years. Recently,
Tajo has been supported by two IT companies in Korea. In addition, we will be eager to recruit
additional committers in order to mitigate this risk.
+ Most of codes have been developed by only two core developers, who are Hyunsik Choi and
Jihoon Son. It may be a risk of being orphaned. However, they are guaranteed to have enough
time to develop Tajo for years. As you can see the commit history, they have participated
in this project for about two years. Recently, Tajo has been supported by two IT companies
in Korea. So, the risk of being orphaned is relatively low. In addition, we will be eager
to recruit additional committers in order to eliminate this risk.
  
  == Inexperience with Open Source ==
  Most of the initial committers have experience working on open source projects. Eli Reisman
and Hyunsik Choi have experience as committers and PMC members on other Apache projects.
  
  == Homogeneous Developers ==
- Although they have four affiliations, what most of core developers are in South Korea is
a risk. This is because their offline activities are limited due to their location. Since
we surely recognize this risk, we will write more complete documents and presentation materials
as early as possible. Then, we will be eager to recruit additional committers around the world.
+ Although they have four affiliations, what most of core developers are in South Korea is
a risk. This is because their offline activities are limited due to their location. Since
we surely recognize this risk, we will write more complete documents and presentation materials
in order to disseminate Tajo's internal and users guide. In addition, to mitigate this risk
we will be eager to recruit additional committers around the world.
  
  == Reliance on Salaried Developers ==
  It is expected that Tajo development will occur on both salaried time and on volunteer time.
Hyunsik Choi and Jihoon Son belong to Database lab., Korea Univ. They will be paid by the
lab to contribute Tajo for years. Jin Ho Kim and Sangwook Kim are paid by their employer to
contribute to this project. Eli Reisman will contribute to this project on volunteer time.
In addition, we will be eager to recruit additional committers including salaried and non-salaried
developers.
  
  == Relationships with Other Apache Products ==
- Tajo has some overlapping function with Apache Incubator Drill. However, it is more mature
than Drill. In addition, there are some significant differences. Drill is a distributed system
specialized for low-latency query processing by using column operation and streaming intermediate
data. Drill has very simple query optimizer. However, some queries including big-big table
join and sort are not available in that manner. Drill will support some of query types.
+ Tajo has some overlapping function with Apache Incubator Drill. However, Tajo is more mature
than Drill. In addition, there are some significant differences. Drill is a distributed system
specialized for low-latency query processing by using column operations and intermediate data
streaming. Drill has very simple query optimizer. However, some queries including big-big
table join and sort are not available in that manner. Drill will support some of query types.
  
  In contrast, Tajo has advanced query optimization system. Tajo mainly aims at scalable and
efficient processing on all query types. By using the query optimizer, Tajo will only chase
low latency query processing for some query types that can be executed in online aggregation
manner.
  
- Besides, Tez has some overlapping functions with Tajo. However, Tez is under pre-alpha stage
and may be a prototype. When Tez becomes feasible, Tajo could use Tez as an underlying framework
according to the applicability. However, Tajo will still use its row/native columnar execution
engine and its optimizer. Tajo may be potentially the first application of Tez.
+ Besides, Tez has some overlapping functions with Tajo. However, Tez is in the pre-alpha
stage and may be a prototype. When Tez becomes feasible, Tajo could use Tez as an underlying
framework according to the applicability. However, Tajo will still use its row/native columnar
execution engine and its optimizer. Tajo may be potentially the first application of Tez.
  
  == A Excessive Fascination with the Apache Brand ==
- We believe that the Apache brand will help us to find contributors and to grow the community.
The community and development process will make this project more stable and ubiquitous APIs.
In addition, Tajo depends other project in Apache Hadoop ecosystem. We expect that cooperative
work occurs with other projects in the same place.
+ We believe that the Apache brand will help us to find contributors and to grow the community.
The community and development process will make this project more stable and help establish
ubiquitous APIs. In addition, Tajo depends other project in Apache Hadoop ecosystem. We expect
that cooperative work occurs with other projects in the same place.
  
  = Documentation =
- Tajo's demonstration paper was accepted to IEEE ICDE 2013. Since this conference will be
held in April 2013, we cannot publicly show the paper. So, we attached some presentation material.
Checkout this [[http://www.slideshare.net/hyunsikchoi/tajo-intro|Slide]].
+ Tajo's demonstration paper was accepted to IEEE ICDE 2013. Since this conference will be
held in April 2013, we cannot publicly show the paper. Instead, we attached some presentation
material. Checkout this [[http://www.slideshare.net/hyunsikchoi/tajo-intro|Slide]].
  
  In addition, some documents (e.g., getting started) are available at [[http://tajo-project.github.com/tajo/]]
  

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


Mime
View raw message