Skip to content

restate-datafusion visibility and re-usability #2989

New issue

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

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

Already on GitHub? # to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

muhamadazmy
Copy link
Contributor

@muhamadazmy muhamadazmy commented Mar 24, 2025

restate-datafusion visibility and re-usability

Summary:
Change visibility of some structs, traits and macros for re-usability
of by other crates

This is a preparation for the next steps where we move the table
definition and logic out of this crate.


Stack created with Sapling. Best reviewed with ReviewStack.

…ion`

Summary:
In follow up PRs the restate-datafusion package will become a core
package and will be used by other crates to implement their own datafusion
integration, hence a short and more generic name is desirable.

The rename is done via Cargo.toml to avoid renaming the entire crate
and lose the files change history on github

It is still possible to rename the crate dir afterwards without additional
changes to clear confusion if needed.
Summary:
Change visibility of some structs, traits and macros for re-usability
of by other crates

This is a preparation for the next steps where we move the table
definition and logic out of this crate.
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant