Aias00 opened a new issue, #7304:
URL: https://github.com/apache/shenyu/issues/7304

   ## Background
   
   ClickHouse is actively maintained, but `shenyu-plugin-logging-clickhouse` is 
an optional persistence sink. Moving it isolates its client dependency and 
release cadence from ShenYu core while preserving official support.
   
   Related lifecycle issue: #6655. Historical data-mapping issue: #5229. 
Depends on #7294.
   
   ## Scope
   
   ### plugin-store
   
   - Add the ClickHouse logging plugin and Spring Boot starter using the 
supported `logging-common` API.
   - Port current fixes for null/blank TTL configuration, config refresh, 
client-init failure handling, and shutdown.
   - Port and expand unit tests for DDL/config generation, schema and status 
mapping, TTL handling, event serialization, batching, write failure, config 
refresh, repeated start, and cleanup.
   - Add Testcontainers-based E2E with a real ClickHouse server. Generate 
gateway traffic, query the stored record, verify status/header/body fields, 
update configuration, and verify shutdown.
   - Document schema ownership/migration, table and TTL settings, 
credentials/TLS, retention, supported versions, and upgrade compatibility.
   
   ### apache/shenyu
   
   - Remove plugin/starter/default-bootstrap dependencies after store parity.
   - Update current enum/admin seed/menu/docs/dependency/license/distribution 
entries while preserving historical upgrade SQL.
   - Ensure the default distribution no longer contains the ClickHouse client.
   - Publish migration notes for existing tables and plugin configuration.
   
   ## Acceptance Criteria
   
   - [ ] Unit tests cover TTL edge cases, mapping, refresh, failures, repeated 
start, and cleanup.
   - [ ] E2E persists and queries a real access-log row in disposable 
ClickHouse.
   - [ ] Regression coverage preserves the corrected status-field behavior from 
#5229.
   - [ ] #6655 is fixed or guarded by lifecycle tests.
   - [ ] Existing schemas/configurations have documented upgrade steps.
   - [ ] Publication ownership and main-repository removal are coordinated.
   
   


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to