iting0321 opened a new pull request, #4705:
URL: https://github.com/apache/polaris/pull/4705

   <!--
   ๐Ÿ“ Describe what changes you're proposing, especially breaking or user-facing 
changes. 
   ๐Ÿ“– See https://github.com/apache/polaris/blob/main/CONTRIBUTING.md for more.
   -->
   ## Description
   
   This introduces lineage domain models, service interfaces, persistence SPI, 
runtime service wiring,config guards, and unit tests. 
   No REST endpoints, DB schema, RBAC, parsing, forwarding, or concrete 
persistence implementation are added in this PR.
   Lineage remains disabled by default.
    
    ## Changes
   
     - Add `polaris-core` lineage models for datasets, edges, column edges, 
field references, queries, and
     graph responses in `polaris-core/.../lineage/`.
     - Add `LineagePersistence` SPI and `LineageService` interface in 
`polaris-core/.../lineage/`.
     - Add runtime `DefaultLineageService`, `DisabledLineagePersistence`, and 
`LineageConfiguration` in
     `runtime/service/.../lineage/`.
     - Add `ENABLE_LINEAGE` feature flag, defaulting to disabled, in 
`polaris-core/.../config/FeatureConfiguration.java`.
     - Add unit tests for disabled guard behavior and enabled-path persistence 
delegation in `runtime/
     service/.../DefaultLineageServiceTest.java`.
   
   ## Checklist
   - [x] ๐Ÿ›ก๏ธ Don't disclose security issues! (contact [email protected])
   - [x] ๐Ÿ”— Clearly explained why the changes are needed, or linked related 
issues: Fixes #
   - [x] ๐Ÿงช Added/updated tests with good coverage, or manually tested (and 
explained how)
   - [x] ๐Ÿ’ก Added comments for complex logic
   - [ ] ๐Ÿงพ Updated `CHANGELOG.md` (if needed)
   - [ ] ๐Ÿ“š Updated documentation in `site/content/in-dev/unreleased` (if needed)
   


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