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.

Sign up for GitHub

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

Jump to bottom

Join/Config: Structured way for storing runtime configuration #31

Closed
farbodahm opened this issue Sep 8, 2024 · 0 comments · Fixed by #35
Closed

Join/Config: Structured way for storing runtime configuration #31

farbodahm opened this issue Sep 8, 2024 · 0 comments · Fixed by #35
Assignees
@farbodahm
Labels
join joins are complex and big; So they deserve a separate tag! refactor Good code bases should have a refactor tag!

Comments

@farbodahm
Copy link
Owner

Currently Streame uses a map[string]any map for storing configuration related state that get generated on runtime.

I prefer to have a more structured/typed data structure for storing these kind of runtime generated configurations.

  • Note: Currently that configuration is only used in join for assigning type of each input on runtime. For example, if we have a join from Order to User, then it will map Order to StreamType and User to TableType.
@farbodahm farbodahm added join joins are complex and big; So they deserve a separate tag! refactor Good code bases should have a refactor tag! labels Sep 8, 2024
@farbodahm farbodahm self-assigned this Nov 13, 2024
farbodahm added a commit that referenced this issue Nov 13, 2024
@farbodahm
feat: add new type for runtime configs, #31
14a49fe
@farbodahm farbodahm linked a pull request Nov 14, 2024 that will close this issue
Feature/delayed primary stream #35
Merged
@farbodahm farbodahm mentioned this issue Nov 16, 2024
Merged
@github-project-automation github-project-automation bot moved this from In Progress to Done in Streame Status Tracker Nov 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@farbodahm farbodahm

Labels
join joins are complex and big; So they deserve a separate tag! refactor Good code bases should have a refactor tag!
Projects
Streame Status Tracker
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Feature/delayed primary stream farbodahm/streame
1 participant
@farbodahm