Filed https://issues.apache.org/jira/browse/PHOENIX-6433
We can discuss there.
In the end, IMHO, placing columns in distinct column families is a physical
optimization, not a logical construct...
Very much like indexes. And just like indexes these physical optimizations
should not leak into the
Lars Hofhansl created PHOENIX-6433:
--
Summary: DISCUSS: Disllow creating new tables with duplicate
column qualifiers by default.
Key: PHOENIX-6433
URL: https://issues.apache.org/jira/browse/PHOENIX-6433
I agree that having identical column names is generally a pain, and I have
no problem with disallowing them in statically defined Phoenix columns, as
long as the views on HBase tables and the dynamic column features are not
affected.
We may or may not want to add a property to override it (with
