[DISCUSS] Releasing the next Omid version

Hi! Most of the planned OMID changes for Phoenix 5.2 have landed. The only outstanding ticket that I'm aware of is OMID-226 which I also expect to land soon. Unless someone has more changes targeted for the next release, I propose that we release the next Omid version soon after OMID-226. I

[jira] [Resolved] (PHOENIX-4793) Backport PHOENIX-4303, PHOENIX-4305, PHOENIX-4321 to 4.x branches.

[ https://issues.apache.org/jira/browse/PHOENIX-4793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla resolved PHOENIX-4793. -- Resolution: Won't Fix > Backport PHOENIX-4303, PHOENIX-4305,

[jira] [Resolved] (PHOENIX-6411) Verify and add transactions usability in Phoenix Spark connector

[ https://issues.apache.org/jira/browse/PHOENIX-6411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rajeshbabu Chintaguntla resolved PHOENIX-6411. -- Resolution: Fixed > Verify and add transactions usability in Phoenix

[jira] [Created] (PHOENIX-6779) Account for connection attempted & failure metrics in all paths

Daniel Wong created PHOENIX-6779: Summary: Account for connection attempted & failure metrics in all paths Key: PHOENIX-6779 URL: https://issues.apache.org/jira/browse/PHOENIX-6779 Project: Phoenix

Re: [Discuss] 5.1.3 Release plan

Looks there are good amount[1] of bugs are fixed in 5.1.3. Hence asked. 1. https://issues.apache.org/jira/issues/?jql=project%20%3D%20PHOENIX%20AND%20fixVersion%20%3D%205.1.3 On 23/08/22, 9:33 PM, "Istvan Toth" wrote: There is currently no 5.1.3 planned, the next release will be

Re: [Discuss] 5.1.3 Release plan

There is currently no 5.1.3 planned, the next release will be 5.2.0. The 5.1 branch is quite stable, you may consider using 5.1 HEAD. regards Istvan On Tue, Aug 23, 2022 at 4:01 PM Battula, Brahma Reddy wrote: > Hi All, > > May I know the release plan for 5.1.3..? > > > Regards > Brahma Reddy

Re: Phoenix Index tool deletes data from main table and does not populate local index

Hi, This list is for the Apache Phoenix releases. If you use a vendor version, please contact your vendor for support. regards Istvan On Mon, Aug 22, 2022 at 7:21 PM Pradheep Shanmugam via user < u...@phoenix.apache.org> wrote: > HI, > > I am using CDP 7.3.1 > I am trying create a phoenix

[jira] [Commented] (OMID-223) Refactor Omid to use HBase 2 APIs internally

[ https://issues.apache.org/jira/browse/OMID-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583706#comment-17583706 ] ASF GitHub Bot commented on OMID-223: - stoty closed pull request #109: OMID-223 Refactor Omid to use

[jira] [Resolved] (OMID-223) Refactor Omid to use HBase 2 APIs internally

[ https://issues.apache.org/jira/browse/OMID-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth resolved OMID-223. -- Fix Version/s: 1.0.3 Resolution: Fixed Committed to master. I have also added myself as a

[jira] [Updated] (OMID-223) Refactor Omid to use HBase 2 APIs internally

[ https://issues.apache.org/jira/browse/OMID-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Istvan Toth updated OMID-223: - Summary: Refactor Omid to use HBase 2 APIs internally (was: Refactor Omid to use HBase 2 APIs

[Discuss] 5.1.3 Release plan

Hi All, May I know the release plan for 5.1.3..? Regards Brahma Reddy Battula

[jira] [Commented] (OMID-223) Refactor Omid to use HBase 2 APIs internally.

[ https://issues.apache.org/jira/browse/OMID-223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583415#comment-17583415 ] ASF GitHub Bot commented on OMID-223: - Aarchy commented on PR #109: URL: