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

Add ability for backend engines to have "engine-specific behavior" #65

Open
richtia opened this issue Mar 29, 2024 · 0 comments
Open

Add ability for backend engines to have "engine-specific behavior" #65

richtia opened this issue Mar 29, 2024 · 0 comments

Comments

@richtia
Copy link
Member

richtia commented Mar 29, 2024

This came up in the following discussion: substrait-io/substrait#615 (comment)

For BFT / dialect testing I think we will need to add the ability for an engine to have an 
"engine-specific behavior"  which is defined as part of the dialect but not rooted in any 
substrait yaml. I think, for now, a minimal standard  of "at least 2 engines" will be a good guideline.
@richtia richtia changed the title Add ability for some backend engines to have "engine-specific behavior" Add ability for backend engines to have "engine-specific behavior" Mar 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant