Hi,
You can find more release-related discussion on the dev mailing list.
There're ongoing discussion and planning around the next 5.x release and a
4.14.x patch release in the work.
On Tue, May 21, 2019 at 12:45 AM lishuang0826
wrote:
> Hi,
>
> I wonder what will the phoenix roadmap be since
Hi,I wonder what will the phoenix roadmap be since it has been nearly a year since the last office release publised.Thanks
On 05/15/2019 13:03，Francis Chuang wrote：
Due to the incompatibility,
Hi Francis/Jaanai
Thank you, I was about to start a new deployment, I will stick with 4.14.1
and HBase 1.4.x
On Wed, May 15, 2019 at 10:33 AM Francis Chuang
wrote:
> Due to the incompatibility, you will need to wait for a new release in
> the 5.x branch to get 5.x working with HBase 2.0.x.
>
>
Due to the incompatibility, you will need to wait for a new release in
the 5.x branch to get 5.x working with HBase 2.0.x.
Phoenix 5.0.0 is also only compatible with 2.0.0 (found this out a few
months ago) as PHOENIX-4826[1] adds support for HBase 2.0.1, but is
currently unreleased.
My
Hi Jaanai,
Sorry I could not understand much from
https://issues.apache.org/jira/browse/PHOENIX-5268
Because of this recent change, there will not be a Phoenix release for
HBase 2.0.x in future Or there is an existing compatibility issue ?
What is the Phoenix version recommended for a new
Hi, Jestan
Now Phoenix 5.0.0 is not compatible with HBase 2.0.5,
https://issues.apache.org/jira/browse/PHOENIX-5268
Jaanai Zhang
Best regards!
Jestan Nirojan 于2019年5月15日周三 上午5:04写道：
> Hi William,
>
> Thanks, It is working with
Hi William,
Thanks, It is working with coalesce(functionThatMightReturnNull(), now())
without an explicit null;
Phoenix Version is 5.0.0.0 which uses HBase 2.0.5
I have not opened any issue for this, I am not sure how it is suppose to
work.
I am developing a phoenix driver for metabase
Just took a look at the implementation, seems like Phoenix relies on the
first expression to not be an expression that is not just an explicit
"null" because it needs to evaluate for data type coercion. What's the use
case for specifying an explicit null?
On the other hand, the following should
Jestan,
It seems like a bug to me. What version of Phoenix are you using, and did
you create a ticket already?
On Tue, May 14, 2019 at 10:26 AM Jestan Nirojan
wrote:
> Hi,
>
> I am trying to use COALESCE function to handle default value in WHERE
> condition like below.
>
> select * from table1
