Skip to content

Conversation

@MateuszNaKodach
Copy link
Collaborator

No description provided.

@smcvb smcvb added Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Type: Feature Use to signal an issue is completely new to the project. labels Oct 6, 2025
@smcvb smcvb requested a review from a team October 6, 2025 07:04
Copy link
Contributor

@smcvb smcvb left a comment

Choose a reason for hiding this comment

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

Although the feature is nice, the main sample should not use our PostgreSQL Extension. Hence, pushing this towards main seems incorrect to me. Furthermore, the use of the properties file will close this sample off from Spring support. Perhaps it's time we started to have several branches on this repository for the "rough flavors."

@MateuszNaKodach
Copy link
Collaborator Author

Although the feature is nice, the main sample should not use our PostgreSQL Extension. Hence, pushing this towards main seems incorrect to me. Furthermore, the use of the properties file will close this sample off from Spring support. Perhaps it's time we started to have several branches on this repository for the "rough flavors."

Personally, I'd merge that. It just an option, good showcase which present how to configure another EventStorageEngine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Type: Feature Use to signal an issue is completely new to the project.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants