Jacob Isaac created PHOENIX-6432:
Summary: Add support for additional load generators
Key: PHOENIX-6432
URL: https://issues.apache.org/jira/browse/PHOENIX-6432
Project: Phoenix
Issue Type: Su
[
https://issues.apache.org/jira/browse/PHOENIX-6430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob Isaac updated PHOENIX-6430:
-
Summary: Add support for full row update for tables when no columns
specfied in scenario (was:
[
https://issues.apache.org/jira/browse/PHOENIX-6431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob Isaac updated PHOENIX-6431:
-
Summary: Add support for auto assigning pmfs (was: Added support for auto
assigning pmfs)
> A
Jacob Isaac created PHOENIX-6431:
Summary: Added support for auto assigning pmfs
Key: PHOENIX-6431
URL: https://issues.apache.org/jira/browse/PHOENIX-6431
Project: Phoenix
Issue Type: Sub-tas
Viraj, yeah similar discussion.
Istvan, good point. Of course you cannot guard against what folks do at the
HBase level, and we should still allow that. Just like in PHOENIX-6343.
But we could disallow creating new tables like this in Phoenix, also like
PHOENIX-6343.
I just think that causes m
Somewhat similar discussion we had on PHOENIX-6343 and why the duplicate
column check was restricted to default CF only.
On Sat, 27 Mar 2021 at 10:42 AM, Istvan Toth
wrote:
> The first thing that comes to my mind is that this would limit
> functionality when defining views on existing raw HBase
