张扶摇 created AMBARI-26602:
----------------------------
Summary: Add KingbaseES database support for Ambari Server
metadata storage
Key: AMBARI-26602
URL: https://issues.apache.org/jira/browse/AMBARI-26602
Project: Ambari
Issue Type: New Feature
Reporter: 张扶摇
Dear Ambari maintainers,
I am planning to contribute support for KingbaseES as a database backend for
Ambari Server within the next two months.
The goal is to allow Ambari Server to use KingbaseES for metadata storage,
configuration data, cluster state, and other Ambari-managed persistence data.
KingbaseES provides compatibility modes for common SQL dialects, which may make
it possible to adapt Ambari with relatively limited changes to the existing
database integration layer.
To ensure code quality and minimize risk to existing users, I plan to follow
these principles:
1. Non-invasive implementation
- Add KingbaseES support through database-specific configuration, JDBC
driver integration, schema scripts, and dialect-related changes where necessary.
- Avoid changing existing core Ambari logic unless strictly required.
- Ensure that existing supported databases are not affected.
2. Database schema and compatibility validation
- Verify Ambari Server installation and initialization with KingbaseES.
- Validate schema creation, table definitions, indexes, constraints,
sequences, and upgrade-related SQL scripts.
- Check whether KingbaseES can reuse an existing compatible database path,
or whether a dedicated KingbaseES database type should be introduced.
3. Testing coverage
- Add or update tests where applicable for database initialization and
persistence behavior.
- Manually validate key Ambari Server workflows, including setup, startup,
cluster registration, configuration changes, service management, and restart
scenarios.
- Run the existing test suite before submitting the pull request.
4. Documentation
- Update the relevant Ambari setup and database configuration documentation.
- Document the required KingbaseES version, JDBC driver version, connection
URL format, and any required database compatibility mode or initialization
settings.
I would like to ask the community whether this type of database adaptation is
acceptable for Ambari.
Specifically, I would appreciate guidance on the following points:
1. Would the Ambari community accept support for KingbaseES as an additional
Ambari Server database backend?
2. Should KingbaseES be implemented as a dedicated database type, or should it
reuse an existing compatible database path where possible?
3. Are there any preferred locations or conventions for adding
database-specific schema scripts, JDBC configuration, or dialect handling?
4. What level of automated testing and documentation would be expected for such
a contribution?
If the community agrees with this direction, I will continue the implementation
and submit a pull request for review.
Thank you.翻译一下
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
