[
https://issues.apache.org/jira/browse/AMBARI-25951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17752592#comment-17752592
]
caijialiang commented on AMBARI-25951:
--------------------------------------
[~FanYuping]
You've thought this through comprehensively. Indeed, there's a lot of
stack-related logic in Ambari Common, such as HDFS resources, Ranger, Solr, and
others. However, these are abstracted as common logic for stacks and aren't
tightly bound to specific stacks.
What I mean is that stacks could be maintained as separate sub-projects,
allowing Ambari to support various stacks without the need for rigid coupling
during releases.
This approach would enable those with expertise in big data operations to focus
on stack development and releases, while others familiar with Ambari could
concentrate on enhancing its core functionality. Ambari's release cycle might
be longer, but stacks could have a more agile and frequent release schedule,
primarily focused on service management logic. Ambari's releases would
emphasize its own feature enhancements and new capabilities. The release and
iteration of stacks could be influenced more by the Bigtop community.
Of course, there are existing challenges, particularly in swiftly deploying and
setting up a cluster for testing within the Bigtop and Ambari environments. I'm
also working on addressing this issue by developing scripts for rapid and
flexible deployment to meet various environment requirements.
> Support Bigtop stack 3.3.0
> --------------------------
>
> Key: AMBARI-25951
> URL: https://issues.apache.org/jira/browse/AMBARI-25951
> Project: Ambari
> Issue Type: Task
> Reporter: Lei Yao
> Priority: Major
> Fix For: 2.9.0
>
>
> Since Apache Bigtop prepare for releasing 3.3.0 , Bigtop stack 3.3.0 should
> be supported
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org
For additional commands, e-mail: issues-h...@ambari.apache.org
