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 the production environment, the same clause results in table creation errors or runtime failures, with Phoenix logs indicating unsupported or invalid compression properties. The Phoenix 4.x documentation explicitly limits compression support to HBase 1.x, and no migration path is provided for HBase 2.x.

Unresolved decisions remain regarding whether future Phoenix releases will reintroduce compression support for HBase 2.x or prescribe an alternative approach.

Unresolved Questions

• Will Phoenix 5.x re‑enable compression support for HBase 2.x?
• Is there an officially recommended workflow for applying compression to Phoenix tables on HBase 2.x?
• What is the impact on performance and compatibility when setting compression at the HBase shell level after Phoenix table creation?