gjacoby126 commented on pull request #2707: URL: https://github.com/apache/hbase/pull/2707#issuecomment-734076588
Question: would it be possible to do the following? 1. Mark sufficient existing APIs to create/read from Tags in coproc as LimitedPrivate(COPROC) to unblock existing Phoenix development efforts _but only for branch-2_ and if needed branch-1 2. Develop a better, more abstracted LimitedPrivate API as @anoopsjohn , @Apache9 and @shahrs87 are discussing above, to be released in HBase 2.5 (and potentially 1.7) 3. When HBase 3.0 is released, the new LimitedPrivate API in 2.5 becomes the only Tag API for coprocs. Reverting the temporary LimitedPrivate annotations on the existing methods to Private would be less impactful as part of a major release transition. This gives Phoenix and other coproc developers an approved path that works for all current release branches without a long delay. It avoids either ignoring the IA, or having an awkward situation where "Phoenix 5.1 with HBase 2.5 supports Feature X, but the same Phoenix with HBase 2.4 doesn't", which already happens too often for other reasons. But we still further the HBase community's long-standing efforts to better abstract away implementation details and only expose interfaces. @anoopsjohn @Apache9 and @apurtell , wdyt? Of course happy to hear other suggestions. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
