pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olga Natkovich" <ol...@yahoo-inc.com>
Subject Merge of types branch onto the trunk
Date Thu, 08 Jan 2009 21:11:19 GMT
As many of you know, for more than nine month now we have been doing
most of our development work on the types branch. The code on the types
branch is almost a complete rewrite of the system with dramatically (10x
on some queries) performance speedup and many new features such as
introduction of the type system, addition of limit, etc. This code has
been successfully used in Yahoo for the last several month and is
It is now time for us to move the code from the types branch to the
trunk to make it our main code base. Here is the proposal for the move:
(1) The move will happen next Monday, 1/12, 2-3 pm. The move will
consist of two parts: moving current trunk (using svn mv command) to a
new branch called "pretypes" so that it can still be available to those
who need it; moving types branch (using svn mv)  to the trunk so that
all main development and use can be done from it. We expect the move to
take approximately 1 hour and we would ask the users not to use SVN
during that time.
(2) Once the move is complete, you can access the content of the old
trunk via the following command:
svn co http://svn.apache.org/repos/asf/hadoop/pig/branches/pretypes
(3) We strongly encourage you to move your work on to the latest trunk
code as it is more efficient and is the code that will be supported
going forward. The new code is not completely backward compatible and
will require changes especially in the area of the UDFs. We have
documentation to ease the transition:
http://wiki.apache.org/pig/TrunkToTypesChanges - document that describes
changes needed for transition
tm - PigLating manual for the latest code
http://wiki.apache.org/pig/UDFManual - Manual for using and writing UDFs
with the latest code
(4) If you are a owner of a UDF in the piggybank, make sure that your
UDFs are transitioned to the latest code. 
Let us know if you have questions or concerns. Unless we here serious
objections between now and Monday, we will go ahead with the plan above.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message