First, it is poor etiquette to specifically send project members emails. Please refrain from doing this in the future for any project at the ASF unless you have explicit approval from that person.
Second, there is no official release of Phoenix that advertises support against any HBase 2.1.x release. As such, I can only imagine that you are building from the master branch and deploying this on your own. If this is the case, please move your discussion to the developers list, as ASF guidelines expressly prohibit discussions on non-releases software anywhere except the dev list. Please confirm what exactly you are doing before we proceed further.
On Fri, Oct 25, 2019 at 10:16 PM Venkat Chunduru <[hidden email]> wrote:
I am working on moving our existing Phoenix to latest version of Phoenix 5 with Hbase 2.1 from current version of Phoenix 4.13 hbase 1.2 and getting compatibility issues and seeking some help on how to migrate to current version of phoenix as i am under time crunch hoping to get help , thank you for your help in advance.
org.apache.phoenix.schema.ColumnNotFoundException: ERROR 504 (42703): Undefined column. columnName=SYSTEM.CATALOG.TRANSACTION_PROVIDER
Collective[i] (short for Collective Intelligence) dramatically improves sales and marketing performance using technology, applications and a revolutionary network designed to help our clients better understand their buyers and grow revenue. Our goal is to maximize human potential and minimize mistakes. In most cases, the results are astounding. We cannot, however, stop emails from sometimes being sent to the wrong person. If you are not the intended recipient, please notify us by replying to this email's sender and deleting it (and any attachments) permanently from your system. If you are meant to receive this email, please respect the confidentiality of this communication's contents.
The views and opinions included in this email belong to the author and do not necessarily reflect the views and opinions of Collective[i]. Our employees are obliged not to make any defamatory statements or otherwise infringe on another party’s legal rights. In the event of any damages or other liabilities arising from such statements, our employees shall be fully and solely personally responsible for the content of their emails.