You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by Stepan Migunov <St...@firstlinesoftware.com> on 2018/02/07 07:54:41 UTC

RE: 4.13.0-HBase-1.1 not released?

Hi James,
I have submitted patch on the JIRA. I've never done this before, so please
excuse me if something is wrong. Thanks,
Stepan.

-----Original Message-----
From: James Taylor [mailto:jamestaylor@apache.org]
Sent: Monday, November 20, 2017 6:13 PM
To: dev@phoenix.apache.org
Subject: Re: 4.13.0-HBase-1.1 not released?

Hi Stepan,
Please submit a patch on the JIRA.
Thanks,
James

On Mon, Nov 20, 2017 at 1:38 AM Stepan Migunov <
stepan.migunov@firstlinesoftware.com> wrote:

> Good news, thank you.
>
> Btw, do you know if https://issues.apache.org/jira/browse/PHOENIX-4056
> still unresolved? That means that Phoenix is not compatible with spark
> 2.2.
> I see  saveToPhoenix contains the follwing line:
> phxRDD.saveAsNewAPIHadoopFile("", ...). But spark 2.2 doesn't work if
> path is empty.
>
> It whould be great if this param will be changed to something like
> phxRDD.saveAsNewAPIHadoopFile(conf.get("phoenix.tempPath"),....), then
> we could be able to set param "phoenix.tempPath" to some temp path as
> workaround.
>
> Regards,
> Stepan.
>
> On 2017-11-18 23:22, James Taylor <ja...@apache.org> wrote:
> > FYI, we'll do one final release for Phoenix on HBase 1.1 (look for a
> 4.13.1
> > release soon). It looks like HBase 1.1 itself is nearing
> > end-of-life, so probably good to move off of it. If someone is
> > interested in being the RM for continued Phoenix HBase 1.1 releases,
> > please volunteer.
> >
> > On Mon, Nov 13, 2017 at 10:24 AM, James R. Taylor <
> jamestaylor@apache.org>
> > wrote:
> >
> > > Hi Xavier,
> > > Please see these threads for some discussion. Would be great if
> > > you
> could
> > > volunteer to be the release manager for Phoenix released on HBase 1.1.
> > >
> > > https://lists.apache.org/thread.html/8a73efa27edb70ea5cbc89b
> > > 43c312faefaf2b78751c9459834523b81@%3Cuser.phoenix.apache.org%3E
> > > https://lists.apache.org/thread.html/04de7c47724d8ef2ed7414d
> > > 5bdc51325b2a0eecd324556d9e83f3718@%3Cdev.phoenix.apache.org%3E
> > > https://lists.apache.org/thread.html/ae13def3c024603ce3cdde8
> > > 71223cbdbae0219b4efe93ed4e48f55d5@%3Cdev.phoenix.apache.org%3E
> > >
> > > Thanks,
> > > James
> > >
> > > On 2017-11-13 07:51, Xavier Jodoin <xa...@jodoin.me> wrote:
> > > > Hi,
> > > >
> > > > I would like to know if there is a reason why phoenix wasn't
> > > > released for hbase 1.1?
> > > >
> > > > Thanks
> > > >
> > > > Xavier Jodoin
> > > >
> > > >
> > >
> >
>

Re: 4.13.0-HBase-1.1 not released?

Posted by Xavier Jodoin <xa...@jodoin.me>.
Hi Stefan,

4.13.1-HBase-1.1 is available.

Xavier


On 2018-02-07 02:54 AM, Stepan Migunov wrote:
> Hi James,
> I have submitted patch on the JIRA. I've never done this before, so please
> excuse me if something is wrong. Thanks,
> Stepan.
>
> -----Original Message-----
> From: James Taylor [mailto:jamestaylor@apache.org]
> Sent: Monday, November 20, 2017 6:13 PM
> To: dev@phoenix.apache.org
> Subject: Re: 4.13.0-HBase-1.1 not released?
>
> Hi Stepan,
> Please submit a patch on the JIRA.
> Thanks,
> James
>
> On Mon, Nov 20, 2017 at 1:38 AM Stepan Migunov <
> stepan.migunov@firstlinesoftware.com> wrote:
>
>> Good news, thank you.
>>
>> Btw, do you know if https://issues.apache.org/jira/browse/PHOENIX-4056
>> still unresolved? That means that Phoenix is not compatible with spark
>> 2.2.
>> I see  saveToPhoenix contains the follwing line:
>> phxRDD.saveAsNewAPIHadoopFile("", ...). But spark 2.2 doesn't work if
>> path is empty.
>>
>> It whould be great if this param will be changed to something like
>> phxRDD.saveAsNewAPIHadoopFile(conf.get("phoenix.tempPath"),....), then
>> we could be able to set param "phoenix.tempPath" to some temp path as
>> workaround.
>>
>> Regards,
>> Stepan.
>>
>> On 2017-11-18 23:22, James Taylor <ja...@apache.org> wrote:
>>> FYI, we'll do one final release for Phoenix on HBase 1.1 (look for a
>> 4.13.1
>>> release soon). It looks like HBase 1.1 itself is nearing
>>> end-of-life, so probably good to move off of it. If someone is
>>> interested in being the RM for continued Phoenix HBase 1.1 releases,
>>> please volunteer.
>>>
>>> On Mon, Nov 13, 2017 at 10:24 AM, James R. Taylor <
>> jamestaylor@apache.org>
>>> wrote:
>>>
>>>> Hi Xavier,
>>>> Please see these threads for some discussion. Would be great if
>>>> you
>> could
>>>> volunteer to be the release manager for Phoenix released on HBase 1.1.
>>>>
>>>> https://lists.apache.org/thread.html/8a73efa27edb70ea5cbc89b
>>>> 43c312faefaf2b78751c9459834523b81@%3Cuser.phoenix.apache.org%3E
>>>> https://lists.apache.org/thread.html/04de7c47724d8ef2ed7414d
>>>> 5bdc51325b2a0eecd324556d9e83f3718@%3Cdev.phoenix.apache.org%3E
>>>> https://lists.apache.org/thread.html/ae13def3c024603ce3cdde8
>>>> 71223cbdbae0219b4efe93ed4e48f55d5@%3Cdev.phoenix.apache.org%3E
>>>>
>>>> Thanks,
>>>> James
>>>>
>>>> On 2017-11-13 07:51, Xavier Jodoin <xa...@jodoin.me> wrote:
>>>>> Hi,
>>>>>
>>>>> I would like to know if there is a reason why phoenix wasn't
>>>>> released for hbase 1.1?
>>>>>
>>>>> Thanks
>>>>>
>>>>> Xavier Jodoin
>>>>>
>>>>>