Hi Darshit, The way I've seen this dealt with in the past is really more through process: have a upgrade schema client that's responsible for running DDL both on the primary and secondary cluster (and disable replication while these commands are running to prevent any race conditions). More details here [1]. Thanks, James
[1] http://mail-archives.apache.org/mod_mbox/phoenix-user/201606.mbox/%3CCAAF1JdggbF5YSCjHAnrjqTZU04dxLdNkCLvh-tpdeok0j853Gg%40mail.gmail.com%3E On Sun, Jun 26, 2016 at 12:14 AM, darshit kandpal <[email protected]> wrote: > Hello folks, > > I was struggling with the problem of automatically syncing up the table > schema of the phoenix tables as soon as any change is made or a new table > is created because hbase replication works only if the two clusters have > same tables. > > > Is there a trap based method for this which triggers the same table to be > created in the other cluster as soon as it is created in the master cluster. > > Also when the waledits are shipped only the puts and deletes are replayed. > Shouldnt replaying the creates and alters solve this problem permanently? > If not i wanted to understand why not? > > Thanks for your time > > Darshit > >
