My main issue with the below Edward is that its a vote on 'hbase
shell'. I would suggest that we instead vote on whether the proposed
hbase shell extensions -- RDF, Matrix, Relational Algebra, HQL Server,
etc. -- belong in hbase core.
In its current state, the 'hbase shell' is buggy and needs filling out
but IMO, it is a critical hbase feature. It makes hbase familiar
because you can do basic data definition, administrative functions, and
simple queries using something that resembles the ubiquitous SQL.
The extensions on the other hand, IMO, do not fit the scope of the hbase
project. While I see much of merit in each of the proposed
developments, when done as patches and wiki additions to the hbase core,
they strike me as noise and a distraction.
Below I suggest an alternate wording for the vote. See what you think.
Do the proposed extensions to hbase shell, listed below, belong in hbase
core:
-------------------------------------------------------------------------------------
[ ] +1 Yes, the proposed 'hbase shell' extensions belong in hbase core
[ ] +0
[ ] -0
[ ] -1 No, the proposed 'hbase shell' extensions do not belong in hbase core
-------------------------------------------------------------------------------------
http://wiki.apache.org/lucene-hadoop/Hbase/RDF
http://wiki.apache.org/lucene-hadoop/Hbase/Matrix
http://wiki.apache.org/lucene-hadoop/Hbase/HbaseShell (The section
on 'Relational Algebra').
Below are a partial list of JIRAs:
HADOOP-2329 Addition of Built-In Value Data Types for efficient
accessing and stroing data
HADOOP-2013 JOINs in select statement
HADOOP-2328 Non-index join columns
HADOOP-2143 Cell-value index option using lucene
HADOOP-2005 SPARQL operations can be defined using modified
relational algebra operators
Reading voting rules for the Apache HTTP project,
http://httpd.apache.org/dev/guidelines.html, if you put up the proposal,
for sure you have a binding vote. As to who else has binding votes and
as to how the vote will be determined, is a little up in the air. I'd
guess the current hbase committers have binding votes. But 3 plus
binding votes are required to carry a motion. To avoid the possibility
of all 3 binding votes not being in favor and to avoid an unsettled
proposition, I'd suggest that we give binding votes to others who have
made contributions to hbase?
St.Ack
edward yoon wrote:
Hi, community.
I'm edward yoon, a worker for the 'hbase shell on hadoop + hbase' and 'RDF,
Matrix storage on hadoop + hbase'.
Now I and other guys who did register for the hbase shell project would
graduate as a contrib project from hbase sub-package.
First i'm introducing ourselves.
I'm work for R&D center at NHN, corp( http://en.wikipedia.org/wiki/NHN )
And, i'm with an database expert, inchul(Ph.d candidate) and yongho(MM) and an
enterpriser, jaesun(Ph.D) and some university's labs.
I believe that our work will makes the hadoop an even better platform for
scientific and advanced analytics programming.
So far, i was work alone on hbase for try to become a committer for company.
But, it seems to slow way.
After set up the hbase shell code to somewhere under contrib package,
I'd like to contribute these all for one set at once after internal works.
So, i propose to graduate hbase shell as a contrib project.
If you find portraits of interest, please vote for the contrib project.
1. http://wiki.apache.org/lucene-hadoop/Hbase/HbaseShell
2. http://wiki.apache.org/lucene-hadoop/Hbase/RDF
3. http://wiki.apache.org/lucene-hadoop/Hbase/Matrix (Not yet)
here's mine :
-------------------------------------------------------------------------------------
[ ] +1 Remove the hbase shell to other contrib project from hbase
[ ] +0
[ ] -0
[ ] -1 Retain the hbase shell as a package on hbase
-------------------------------------------------------------------------------------
Ok, Thanks for your opinion.
But, if you voted against, please one more vote for a future release of the
hbase shell on hbase.
I was proposed the addition of extensions as describe below
1. Relational algebra on Hbase
2. HQL Socket server for executing the hql query in other applications
Should it be committed to hbase core?
here's mine :
-------------------------------------------------------------------------------------
[ ] +1 Proposed shell extensions should be committed to hbase core
[ ] +0
[ ] -0
[ ] -1 Retain the hbase shell as a package on hbase
-------------------------------------------------------------------------------------
Thank you very much.
If you have any ideas, please let me know.
Thanks,
Edward.
------------------------------
B. Regards,
Edward yoon @ NHN, corp.
Home : http://www.udanax.org
_________________________________________________________________
You keep typing, we keep giving. Download Messenger and join the i’m Initiative
now.
http://im.live.com/messenger/im/home/?source=TAGLM
