It would appear not at this point. Though it would be great to get the full
Hbase + Phoenix stacks supported out-of-the-box.



On Thu, 4 Feb 2016 at 16:56 James Taylor <[email protected]> wrote:

> That's good news. Phoenix is in BigTop too. Did EMR not include it?
>
> On Thu, Feb 4, 2016 at 4:48 PM, j pimmel <[email protected]> wrote:
>
>> Thanks for the update James.
>>
>> Is the latest HBase getting integrated into BigTop - perhaps I'm looking
>> in the wrong place, but this is what I found and it's hard to tell if it's
>> the latest.
>>
>>
>> https://github.com/apache/bigtop/tree/master/bigtop-packages/src/common/hbase
>>
>> It seems like the latest EMR version uses BigTop and though it's not
>> clear what they use from it and whether HBase will start re-appearing in
>> current EMR releases, it seems like standards are getting baked in and it
>> would likely ease adoption?
>>
>>
>> http://docs.aws.amazon.com/ElasticMapReduce/latest/ReleaseGuide/emr-release-components.html
>>
>> Thanks
>>
>> J
>>
>> On Thu, 4 Feb 2016 at 14:39 James Taylor <[email protected]> wrote:
>>
>>> The problem is that EMR hasn't updating their HBase version past 0.94 in
>>> the last two years. Phoenix stopped doing releases supporting 0.94 a year
>>> ago and HBase has moved well past 0.94 as well. Phoenix will run just fine
>>> on EMR if they update their HBase version. My two cents: I'd recommend
>>> continuing to let the folks over at EMR know that you'd like to see this
>>> happen. We don't have any control over that, though.
>>>
>>> Thanks,
>>> James
>>>
>>> On Thu, Feb 4, 2016 at 7:04 AM, James Heather <
>>> [email protected]> wrote:
>>>
>>>> I asked about Phoenix on EMR, and also received no response.
>>>>
>>>> It would be nice to have a comment on this from someone in the know, if
>>>> only to confirm that Phoenix and EMR are no longer friends.
>>>>
>>>> James
>>>>
>>>>
>>>> On 26/01/16 16:37, j pimmel wrote:
>>>>
>>>>> Hi all
>>>>>
>>>>> I'm just evaluating using HBase with phoenix on EMR and see that the
>>>>> most recent supported version is on EMR 3.11.0 (compared to EMR latest
>>>>> 4.1.0) which bundles HBase 0.94.18.
>>>>>
>>>>> Given that the latest HBase version is at 1.13 I'm wondering what key
>>>>> phoenix features would end up being unsupported when trying to use the
>>>>> older version EMR HBase version (if it works at all).
>>>>>
>>>>> Thanks
>>>>>
>>>>> J
>>>>>
>>>>
>>>>
>>>
>

Reply via email to