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
WASM UDF support #1653
Comments
/bounty $600 |
💎 $600 bounty • Dozer DataSteps to solve:
Additional opportunities:
Thank you for contributing to getdozer/dozer! Add a bounty • Share on socials
|
This comment was marked as outdated.
This comment was marked as outdated.
@hi-rustin, use the attempt comment above to indicate you've started working on it. |
/attempt #1653 |
Hi! I also wanted to explore this issue /attempt #1653 |
Note: The user @hi-rustin is already attempting to complete issue #1653 and claim the bounty. If you attempt to complete the same issue, there is a chance that @hi-rustin will complete the issue first, and be awarded the bounty. We recommend discussing with @hi-rustin and potentially collaborating on the same solution versus creating an alternate solution. |
💡 @tachyonicbytes submitted a pull request that claims the bounty. You can visit your org dashboard to reward. |
@tachyonicbytes Perhaps before contributing to the open source community you need to ask the original people if they have started work. Otherwise, it's going to be an endless race for speed :( |
/attempt #1653
|
📝 Description:
This is a proposal for a new feature in Dozer Core, to enhance the functionality by allowing users to define a SQL User Defined Function (UDF) implemented in WASM (AssemblyScript)
🌟 Feature Details:
Users should be able to define a WASM UDF usable in Dozer SQL.
In order to implement an UDF a user should:
.wasm
file to the project folder (for example in the directoryudfs/wasm/my_function.wasm
)dozer-config.yaml
:Upon startup Dozer should load the wasm function and make it available in Dozer SQL.
my_function()
should now be usable from SQL as:The text was updated successfully, but these errors were encountered: