sanjeet006py

> Another thing we should consider is that maxlookback on index should inherit the value of the base table. The behavior should be exactly similar to TTL where both the...

Jenkins test this please

@gjacoby126 @haridsv please re-review the PR, I have addressed the earlier comments. Thanks

@kadirozde I have addressed all the review comments. Please re-review. Thanks

Thanks a lot @virajjasani . I have resolved the conflicts. The conflicts were around the version changes for 5.3.0 creation. Please re-review. Thanks

Once current PR validation is done. Shall I squash and rebase all my changes into one commit or merge procedure will take care of that?

@virajjasani the latest build is complete. Are we good to merge the PR? Thanks

> (worth doing as separate Jira/PR though) Created JIRA: https://issues.apache.org/jira/browse/PHOENIX-7597

@tkhurana @virajjasani the perf analysis is done: https://docs.google.com/document/d/1oQzEMP4LXOFxLHlKt1SZ5uvRLd3Vk90x39gn1hVBn0Y/edit?tab=t.0#heading=h.32xuccojgowv. Overall I see enabling CompactionScanner for flushes will have some overhead (as expected) but no big enough to cause performance degradation. Thanks

@virajjasani @tkhurana @jpisaac can you please review the PR. Thanks