Heh. I just remember that last time in August you said that you already migrating to more recent version of HBase and have no problems to maintain 0.98 internally during for short time. As an alternative can we add shims, so most of the difference in API can be grouped there and will be easy to maintain. Most of the changes are related to removing deprecated API in Put/Get/Delete and name changes like HAdmin -> Admin, so it may be covered by a couple of support classes. After that it will be possible to get Phoenix compiled against 2.0 with some little changes related to shaded coprocessor API (possible may be added to shims as well) and tephra which is also using deprecated API.
Thanks, Sergey On Tue, Oct 10, 2017 at 4:49 AM, Andrew Purtell <apurt...@apache.org> wrote: > Until we migrate our production at Salesforce off of 0.98 we will still > have to support 0.98 internally, and a number of our staff are committers, > so I suspect there will be adequate support for the 0.98 branch for another > couple of releases. > > On Mon, Oct 9, 2017 at 12:36 PM, Sergey Soldatov <sergeysolda...@gmail.com > > > wrote: > > > I remember that we discussed that a couple times already without any > final > > decision, so let me raise this question again. HBase 2.0 is getting close > > to the release and to support it we will need to do a lot of refactoring > in > > the code even just to get Phoenix compiled. And already we may start to > > remove all deprecated API that was removed from 2.0 to minimize the > further > > changes that are directly related to 2.0 support. > > > > Thoughts? > > > > Thanks, > > Sergey > > > > > > -- > Best regards, > Andrew > > Words like orphans lost among the crosstalk, meaning torn from truth's > decrepit hands > - A23, Crosstalk >
