When Phoenix 4.0.0-incubating RC was generated, HBase 0.98.1 was not available in Maven. It was compiled/installed locally for Phoenix build so hbase-defaults.xml in 4.0.0-incubating hadoop2 client release artifact got in this state somehow but otherwise the artifact is fine. It doesn't happen if you build with 4.0.0-incubating release tag and won't affect 4.1 release.
//mujtaba On Fri, Jul 25, 2014 at 12:37 PM, James Taylor <[email protected]> wrote: > Thanks for following up on this, Gabriel. I don't know what went > wrong, but you're right, we need to fix it. @Jesse - any ideas? > > Thanks, > James > > On Fri, Jul 25, 2014 at 6:02 AM, Gabriel Reid <[email protected]> > wrote: > > Hi guys, > > > > There was a mail on the user list today (see archive at > > http://s.apache.org/4H9) around issues with the hadoop2 build of > > phoenix 4.0.0. It appears that the hbase-default.xml file in that > > build refers to 0.98.1-hadoop1 in the hbase.defaults.for.version. This > > looks to me like at least parts of hbase 0.98.1-hadoop1 were included > > in the hadoop2 build of phoenix 4.0.0. > > > > I tried rebuilding the hadoop2 version from source (git tag > > v4.0.0-incubating-release) and didn't run into this issue (i.e. the > > hbase.defaults.for.version setting was 0.98.1-hadoop2, so I'm not able > > to replicate this build problem. > > > > Does anyone have any idea what might have gone wrong, and/or what we > > can do to prevent this for the 4.1 release? > > > > - Gabriel >
