Hi! When Geoffrey proposed releasing Phoenix 5.2.0, I asked for time to release a new Omid version first, as there are a lot of unreleased fixes in master.
One of those fixes removes the need to add a lot of explicit excludes for the Omid HBase-1 artifacts when depending on Omid for HBase 2. However, the discussion on dropping HBase 1.x support from Phoenixhas been re-opened, and so far there are no objections. We can either release the Omid master as is (perhaps with some dependency version bumps), or we could just drop HBase 1.x support, and simplify the project structure quite a bit for the next version. In case we drop support for Hbase 1, we also need to decide whether to keep the maven build infrastructure (shims and flatten-maven-plugin) for supporting different HBase releases for an upcoming HBase 3 release (if the API changes will require it), or to remove it altogether ? We'll need to update the dependencies and exclusions in Phoenix either way. What do you think ? Can we make an official decision to drop Phoenix 4.x soon, and drop HBase 1 support from Omid for the next release, or should I just go ahead with the Omid next release process, and worry about removing the HBase 1.x support from Omid later ? Also, as we're making incompatible changes to the way Omid is to be consumed via maven, I think that we should bump the version either to 1.1.0, or 2.0.0. (I prefer 1.1.0, as the API doesn't change.) Looking forward to your input, Istvan
