Compression property fails when moving Phoenix 4.x from HBase 1.x to 2.x
Compression Property Compatibility The goal is to maintain the same column‑family compression settings when a Phoenix 4.x deployment is shifted from a local HBase 1.x cluster to a production HBase 2.x cluster. In the local environment, the CREATE TABLE … WITH COLUMN FAMILIES … COMPRESSION=<type> clause is accepted and the table functions normally. In t