+1 on the release.
While I would not exactly LIKE to be RM, I may be able to make the time for
it if no-one else volunteers. (but please do)
On Mon, Aug 26, 2024 at 9:41 PM Viraj Jasani wrote:
> We are in good shape. We can wait for just one more soon to be committed
> change (PHOENIX-7394) and
[
https://issues.apache.org/jira/browse/PHOENIX-7382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani updated PHOENIX-7382:
--
Description:
PHOENIX-7001 introduced a Change Data Capture (CDC) feature by leveraging
Phoen
[
https://issues.apache.org/jira/browse/PHOENIX-7393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani reassigned PHOENIX-7393:
-
Assignee: Grzegorz Kokosinski
> Exclude woodstox-core to fix CVE-2022-40152
>
We are in good shape. We can wait for just one more soon to be committed
change (PHOENIX-7394) and we should be good to start with 5.2.1 release.
Anyone else would like to be RM for 5.2.1? I have limited bandwidth at the
moment.
When we target 5.3.0 in a couple of months, I can be RM again but in
[
https://issues.apache.org/jira/browse/PHOENIX-7394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani updated PHOENIX-7394:
--
Fix Version/s: 5.2.1
5.3.0
5.1.4
> MaxPhoenixColumnSize
[
https://issues.apache.org/jira/browse/PHOENIX-7394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani reassigned PHOENIX-7394:
-
Assignee: Jing Yu
> MaxPhoenixColumnSizeExceededException should not print rowkey
> --
Viraj Jasani created PHOENIX-7394:
-
Summary: MaxPhoenixColumnSizeExceededException should not print
rowkey
Key: PHOENIX-7394
URL: https://issues.apache.org/jira/browse/PHOENIX-7394
Project: Phoenix
Hi,
REMOVE DATASOURCE V1:
After removing V1 code, it is possible to configure V1 name as a V2 long
name.
I have to test it to be sure but this can be done by moving the
class PhoenixDataSource under package "org.apache.phoenix.spark".
In this way, it will have no impact on old applications which u
