I've also wanted to bring this up after 5.1, but forgot while dealing with
the problems in 5.1.0
Do we want to maintain patch branches ?
For how long ?
What do we want to commit to the maintenance branches ?
Who commits to the maintenance branches ?
To kickstart the discussion, here are my
Since the nexus staging artifact is missing, let's sink this RC.
On Wed, May 12, 2021 at 4:22 PM Geoffrey Jacoby wrote:
> +1 (binding)
>
> Signatures (ok)
> Checksums (ok)
> Rat check (ok)
> mvn clean install -DskipTests (ok)
> Unit tests pass (1.8.0_212) (ok - ViewConcurrencyAndFailureIT
+1 (binding)
Signatures (ok)
Checksums (ok)
Rat check (ok)
mvn clean install -DskipTests (ok)
Unit tests pass (1.8.0_212) (ok - ViewConcurrencyAndFailureIT failed to
start up but passed on a rerun)
Geoffrey
On Wed, Apr 28, 2021 at 12:14 AM Viraj Jasani wrote:
> > The release files, including
Have we actually decided that branch-5.1 will produce our next version of
Phoenix?
I've been assuming that 4.16 (and 5.1, which I'll admit I forgot existed)
were just for bug fixes, and that the next significant version of Phoenix
would be 5.2 / 4.17 sometime in H2 of 2021. (Or potentially just
Hi all,
I noticed some changes that went into both master and the 4.x branch, but not
into branch-5.1.
Unfortunately I do not have time to check each edit.
When you commit changes, please do not forget about branch-5.1, which will
produce our next version of Phoenix.
Cheers.
-- Lars
[
https://issues.apache.org/jira/browse/PHOENIX-6457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl reopened PHOENIX-6457:
What about branch-5.1?
> Optionally store schema version string in SYSTEM.CATALOG
>
[
https://issues.apache.org/jira/browse/PHOENIX-6467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swaroopa Kadam updated PHOENIX-6467:
Summary: Support extract/synth indexes on expression and function in
SchemaTool (was:
Swaroopa Kadam created PHOENIX-6469:
---
Summary: Support CREATE SEQUENCE and CREATE FUNCTION DDL in
SchemaTool
Key: PHOENIX-6469
URL: https://issues.apache.org/jira/browse/PHOENIX-6469
Project:
Swaroopa Kadam created PHOENIX-6468:
---
Summary: Provide verify mode in SchemaTool to compare SQL on
cluster with provided SQL
Key: PHOENIX-6468
URL: https://issues.apache.org/jira/browse/PHOENIX-6468
[
https://issues.apache.org/jira/browse/PHOENIX-6467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swaroopa Kadam updated PHOENIX-6467:
Fix Version/s: 4.16.2
4.17.0
5.1.1
> Support
Swaroopa Kadam created PHOENIX-6467:
---
Summary: Support indexes on expression and function in SchemaTool
Key: PHOENIX-6467
URL: https://issues.apache.org/jira/browse/PHOENIX-6467
Project: Phoenix
With 3x binding votes and 1x non-binding vote, this vote passes.
Thanks to everyone who participated in this release.
On Wed, May 12, 2021 at 11:41 PM Viraj Jasani wrote:
> > I think ASF guidelines want the commit ID (not just a tag) in a VOTE
> > email, but let's just use that for future
> I think ASF guidelines want the commit ID (not just a tag) in a VOTE
> email, but let's just use that for future guidance.
Sounds good.
> We should also get https://phoenix.apache.org/tephra updated and start
> using that for Tephra communications. I think we're lucky that infra
> hasn't taken
Viraj Jasani created PHOENIX-6466:
-
Summary: Update Tephra site https://phoenix.apache.org/tephra
Key: PHOENIX-6466
URL: https://issues.apache.org/jira/browse/PHOENIX-6466
Project: Phoenix
## Description:
The mission of Phoenix is the creation and maintenance of software related
to
High performance relational database layer over Apache HBase for low
latency
applications
## Issues:
No issues to report to the board at this time.
## Membership Data:
Apache Phoenix was founded
Istvan Toth created PHOENIX-6465:
Summary: Close sessions explicitly in python-phoenixdb
Key: PHOENIX-6465
URL: https://issues.apache.org/jira/browse/PHOENIX-6465
Project: Phoenix
Issue
16 matches
Mail list logo
