Skip to content

Conversation

@labrenbe
Copy link
Member

@labrenbe labrenbe commented Nov 3, 2025

  • Add configOverrides for the SNI check to NiFi
  • Create a ConfigMap for the NiFi flow file keeping LakehouseKafkaIngest.json for backward compatibility
  • Use the new Headless Service for the Kafka3ConnectionService in NiFi

@sbernauer sbernauer moved this to Development: In Review in Stackable Engineering Nov 4, 2025
sbernauer
sbernauer previously approved these changes Nov 4, 2025
Copy link
Member

@Techassi Techassi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is basically the same change as in #319. Can we only use one CM for this?

@labrenbe
Copy link
Member Author

labrenbe commented Nov 4, 2025

This is basically the same change as in #319. Can we only use one CM for this?

If you're referring to the ConfigMap containing the NiFi flow then unfortunately not because the NiFi flow in this demo uses additional data sets.

@Techassi
Copy link
Member

Techassi commented Nov 4, 2025

This is basically the same change as in #319. Can we only use one CM for this?

If you're referring to the ConfigMap containing the NiFi flow then unfortunately not because the NiFi flow in this demo uses additional data sets.

Well... That's unfortunate.

@Techassi Techassi dismissed their stale review November 4, 2025 10:08

ConfigMap has slightly different content. We therefor cannot use the same CM.

@labrenbe labrenbe enabled auto-merge (squash) November 4, 2025 10:20
@labrenbe labrenbe merged commit 0dd7c45 into main Nov 4, 2025
2 checks passed
@labrenbe labrenbe deleted the fix/demo-data-lakehouse-iceberg-trino-spark branch November 4, 2025 10:51
@sbernauer sbernauer moved this from Development: In Review to Development: Done in Stackable Engineering Nov 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Development: Done

Development

Successfully merging this pull request may close these issues.

4 participants