adnanhemani commented on PR #4667: URL: https://github.com/apache/polaris/pull/4667#issuecomment-4712595164
Thanks for the clear framing — the constraints you've laid out match where I want this to land. Will address in this PR: - Add `OpenLineageIngestProvider.ingest(OpenLineageIngestRequest) → OpenLineageIngestResult`, explicitly OL-specific and named that way. - `OpenLineageIngestRequest` carries the already-dispatched typed event + realm id as plain data. No `SecurityContext`, no `Response`. - `OpenLineageIngestResult` is a thin accept/reject/unavailable enum — HTTP mapping stays in the adapter. - Default `NoOpOpenLineageIngestProvider` wired via CDI. The adapter calls the provider; `OpenLineageAdapter` stays responsible for mapping provider result to `201`. One thing I want to flag rather than silently change: the `/api/v1/lineage` path is intentional. It's the standard OpenLineage HTTP transport path that Spark/Flink/Airflow/dbt already target natively — changing it to something like `/api/v1/lineage/openlineage` would break the zero-config compatibility goal. I'll respond inline on that thread with more detail and am happy to take it to the dev list for broader input if useful. -- 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]
