[
https://issues.apache.org/jira/browse/HBASE-24319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17099174#comment-17099174
]
Josh Elser commented on HBASE-24319:
------------------------------------
{quote}A simplified explanation is that you have to duplicate outside of the
set of profiles whatever it is that is done by the profile you consider to be
the default. Let me go make an example PR under a ticket that expressly says it
is for that purpose.
{quote}
[~busbey] had mentioned this on HBASE-24280.
[~zhangduo] has an interest in keeping the build command simple on master, not
needing to deal with extra arguments since hadoop2 support was dropped there.
[~stoty] happened to stumble by in all this, but has done some (effective) work
down in Phoenix with profiles to build against the gamut of HBase 2 release
lines (with the subtle changes that Phoenix has yet to detangle itself from).
He might have some interest in trying to help out here in HBase.
[~ndimiduk] and [~stack] just as an FYI as they were involved in the
discussions on the UT failure.
> Clearly document how profiles for the sake of Hadoop compatibility work
> across all branches
> -------------------------------------------------------------------------------------------
>
> Key: HBASE-24319
> URL: https://issues.apache.org/jira/browse/HBASE-24319
> Project: HBase
> Issue Type: Task
> Components: build
> Reporter: Josh Elser
> Priority: Major
>
> In HBASE-24280, we investigated a test failure which was ultimately caused by
> the simultaneous activation of the (intended mutually exclusive) hadoop-2 and
> hadoop-3 profiles.
> After master has moved to only supporting profile activation via the profile
> itself (rather than a system property) with the removal of the hadoop-2
> profile, the build was inadvertently broken as all branches (or is it just
> 2.x branches and master?) use the one build/yetus scripts in dev-support.
> To make sure that these scripts continue to work against all branches, we
> need to have a clear decision on how profile activation is expected to work
> in our HBase build. Otherwise, we'll come back to this problem where each
> branch does things ever-so-slightly different, requiring a bunch of {{if
> branch-2; else if branch-2.2; else if branch-2.3}} type changes to our yetus
> scripts.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
