[
https://issues.apache.org/jira/browse/PHOENIX-6410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated PHOENIX-6410:
-
Release Note: phoenixdb now supports retrieving primary key and index
information via the meta
[
https://issues.apache.org/jira/browse/PHOENIX-6410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth resolved PHOENIX-6410.
--
Fix Version/s: python-phoenixdb-1.0.2
Release Note: phoenixdb now supports retrieving
+1 for EOL'ing 4.x branches.
As Josh and I, share the feedback from the same set of users,
it would still be a good idea to hear from others but as it's been already
been 12 days since your first mail out, just a notice can be given for
72hrs(?)
before dropping the next 4.x versions from JIRA and
+1 (binding)
* Signature: ok
* Checksum : ok
* Rat check (1.8.0_191): ok
- mvn clean apache-rat:check
* Built from source (1.8.0_191): ok
- mvn clean install -DskipTests
* Unit tests pass (1.8.0_191): ok (have not tested the ITs)
Neha Gupta created PHOENIX-6472:
---
Summary: In case of region inconsistency phoenix should stop
gracefully
Key: PHOENIX-6472
URL: https://issues.apache.org/jira/browse/PHOENIX-6472
Project: Phoenix
+1 (binding)
* Xsums/sigs work
* Keys works
* Source release looks fine
* Validated that cookie support fix works
Ran tests against HBase 2.2.7 and Phoenix 5.2.0-SNAPSHOT which all
passed (except those tests which expect no extra tables present).
On 5/14/21 3:46 PM, Istvan Toth wrote:
Hello
