One of the recommendations in HBase is to have short column names. Now when phoenix user defines a logical but longer column names this affects the HFile size of such a table (column names are repeated). Even if we use compression and data block encoding, the size while in transit and in memory is still a concern.
Was there any consideration of leveraging catalog table to have the mapping to get best of both world (logical names in phoenix but efficient and short names in hbase)? Thanks, Satish
