Thanks Jeffrey. I did a svn checkout from the tip of the hbase trunk and built off of that and with the 2.0 profile, it wasn't building. It seems like the build from Jenkins was on the 1.0 profile (default). I can successfully build that myself, but not with the 2.0 profile.
Has anyone been able to do this? Thanks, Abe On Tue, Feb 25, 2014 at 6:23 PM, Jeffrey Zhong <[email protected]>wrote: > Apache 4.0 is at https://github.com/apache/incubator-phoenix/tree/4.0. > Jenkin build is at > https://builds.apache.org/view/H-L/view/Phoenix/job/Phoenix-4.0/. > > Since there are interface changes between 0.96 & 0.98, the Phoenix 4.0 > branch can only work on current tip of hbase0.98 and hbase trunk branch. > (the changes to make it work on 0.96 should not much though) or hbase0.98 > + HBASE-10486. > > -Jeffrey > > From: Stan Campbell <[email protected]> > Date: Tuesday, February 25, 2014 2:53 PM > To: <[email protected]> > Cc: Jeffrey Zhong <[email protected]> > Subject: Re: Building 4.0 > > Can you point me to the 4.0 repo? > On Feb 25, 2014 2:46 PM, "Mujtaba Chohan" <[email protected]> wrote: > >> 4.0 branch builds against latest HBase0.98 but currently not with 0.96. >> @Jeffrey Zhong >> >> -mujtaba >> >> >> >> >> On Tue, Feb 25, 2014 at 1:27 PM, Abe Weinograd <[email protected]> wrote: >> >>> I am having some issues building 4.0. >>> >>> I built HBase the same way Jenkins is for the 4.0 branch. When building >>> Phoenix, i get a bunch of Hbase related "cannot find symbol". I am trying >>> to build for CDH5 (running Hadoop 2.2 and HBase 0.96.1) >>> >>> I am building Phoenix with hadoop.profile=2 >>> >>> Anything obvious that I am missing? >>> >>> Thanks, >>> Abe >>> >> >> > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity > to which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You.
