-1
As Jacob found this dependency issue PHOENIX-6348, we should have the fix
before the next RC.
Hi Istvan, thank you for the quick response and jump on this for the fix.
On Fri, Jan 29, 2021 at 12:03 PM Istvan Toth wrote:
> My bad, I got confused and mixed up bulk loading which uses
My bad, I got confused and mixed up bulk loading which uses phoenix-client
and IndexTool, which uses the Hbase classpath, and thus phoenix-server.
regards
István
On Fri, Jan 29, 2021 at 8:36 PM Istvan Toth wrote:
> Jacob, are you sure you were using phoenix-client for the test ?
> The stack
Jacob, are you sure you were using phoenix-client for the test ?
The stack trace in PHOENIX-6348 suggests that you tried to use phoenix-core
or perhaps phoenix-server instead (which indeed doesn't work).
regards
Istvan
On Fri, Jan 29, 2021 at 1:49 PM Istvan Toth wrote:
> Copying here from
Copying here from PHOENIX-6348 and PHOENIX-6349 for greater exposure:
Let me know if the solution in PHOENIX-6349 is acceptable.
If I get the timely +1 for PHOENIX-6349, then I'll put up the
phoenix-thirdparty 1.1.0RC0 today,
so that we can have a phoenix-thirdparty release on Monday to Wendsday.
Xinyi, i have updated fixVersion for relevant cases and mentioned you on
Jiras where i am not sure about the conclusion.
create-release scripts should update change log correctly this time.
On Fri, 29 Jan 2021 at 4:04 PM, Viraj Jasani wrote:
> Apart from latest Jiras mentioned by Istvan for
Apart from latest Jiras mentioned by Istvan for fixVersion discrepancies,
when I used this script [1], I could see more such discrepancies, meaning
CHANGES.md is out of sync from git commits landed on branch 4.16.
As of now, I can see:
37 Jiras missing fixVersion 4.16
4 git commits without Jira
As I started testing the builds found a dependency issue -
PHOENIX-6348
This will need to be addressed as this affects core functionality related
to running the IndexTool.
Thanks
Jacob
On 2021/01/28 05:09:44, Xinyi Yan wrote:
> Hello Everyone,
>
> This is a call for a vote on Apache Phoenix
I haven't had a chance to test the release yet, but I'd like to point out
that (at least) the following JIRAs didn't have the 4.16.0 fix version set.
(Some of that is probably my fault)
PHOENIX-6342
PHOENIX-5296
PHOENIX-6327
PHOENIX-6329
PHOENIX-6330
Missing some commits from the generated
Hello Everyone,
This is a call for a vote on Apache Phoenix 4.16.0 RC0. This is the next
minor release of Phoenix 4, compatible with Apache HBase 1.3, 1.4, 1.5
and 1.6.
The VOTE will remain open for at least 72 hours.
[ ] +1 Release this package as Apache phoenix 4.16.0
[ ] -1 Do not release
