The first thing that comes to my mind is that this would limit
functionality when defining views on existing raw HBase tables (though
aliasing the columns may solve that)
Another thing to consider is how this would affect dynamic column use cases
for either native Phoenix tables of views on HBase t
Jacob Isaac created PHOENIX-6430:
Summary: Added support for full row update for tables when no
columns specfied in scenario
Key: PHOENIX-6430
URL: https://issues.apache.org/jira/browse/PHOENIX-6430
P
As you may or may not know, Phoenix allows for duplicate column names as long
as they are placed in different column families.
You can create a table such as CREATE TABLE t (pk1 ..., x.v1, y.v1, ...).
Now each time you want to refer to v1 you need to qualify it with its column
family or you get
Jacob Isaac created PHOENIX-6429:
Summary: Add support for global connections and sequential data
generators
Key: PHOENIX-6429
URL: https://issues.apache.org/jira/browse/PHOENIX-6429
Project: Phoenix
[
https://issues.apache.org/jira/browse/PHOENIX-6420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tanuj Khurana updated PHOENIX-6420:
---
Affects Version/s: 5.0.0
4.16.0
> Wrong result when conditional and
Hello Everyone,
This is a call for a vote on Apache Phoenix 4.16.1 RC1. This is the next
patch 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.1
[ ] -1 Do not release thi
