Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] StreamClass-based contracts #91

Open
s-vitaliy opened this issue Apr 25, 2024 · 2 comments
Open

[FEATURE] StreamClass-based contracts #91

s-vitaliy opened this issue Apr 25, 2024 · 2 comments
Assignees
Labels
code/new-feature New feature or request

Comments

@s-vitaliy
Copy link
Contributor

The streaming plugins and the stream operator utilize a specific set of entities that must be consistent across both applications. These include:

  • The value of schema mismatch annotation
  • The structure of the stream status resource

These aspects are planned to be updated in future versions of Arcane Operator as follows:

  • The Stream class resource will incorporate additional fields that provide a description of the schema mismatch reporting mechanism.
  • The Stream class resource will include extra fields that explain the structure of the stream status resource.
@s-vitaliy s-vitaliy added the code/new-feature New feature or request label Apr 25, 2024
@s-vitaliy s-vitaliy self-assigned this Apr 25, 2024
@s-vitaliy s-vitaliy transferred this issue from SneaksAndData/arcane-framework Jun 3, 2024
@s-vitaliy s-vitaliy moved this to Backlog in Arcane Jun 3, 2024
@s-vitaliy
Copy link
Contributor Author

Also if the stream plugin cannot run in backfill mode, it should be defined in StreamClass.

@s-vitaliy s-vitaliy changed the title StreamClass-based contracts [FEATURE] StreamClass-based contracts Aug 9, 2024
@s-vitaliy
Copy link
Contributor Author

Also, stream class should provide configuration for retries (see: #124)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code/new-feature New feature or request
Projects
Status: Backlog
Development

No branches or pull requests

1 participant