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

New javascript transform #667

Closed
ghost opened this issue Jul 20, 2019 · 3 comments
Closed

New javascript transform #667

ghost opened this issue Jul 20, 2019 · 3 comments
Labels
domain: processing Anything related to processing Vector's events (parsing, merging, reducing, etc.) domain: transforms Anything related to Vector's transform components needs: approval Needs review & approval before work can begin. type: feature A value-adding code addition that introduce new functionality.

Comments

@ghost
Copy link

ghost commented Jul 20, 2019

Recently Fabrice Bellard, creator of QEMU and FFMPEG, released QuickJS embeddable JavaScript engine.

It is MIT licensed and its compiled size is just a few hundred kilobytes.

So it might be a good idea to add javascript transform, similar to lua transform.

@zsherman
Copy link
Contributor

Wow, this would be really useful from my perspective.

@afoninsky
Copy link

Guys, can you specify what's the status of this pull request? Look forward to seeing this feature in the next release. Thank you.

@binarylogic binarylogic added type: feature A value-adding code addition that introduce new functionality. and removed type: new feature labels Jun 16, 2020
@binarylogic binarylogic removed this from the Improve Data Processing milestone Jul 26, 2020
@binarylogic binarylogic added domain: processing Anything related to processing Vector's events (parsing, merging, reducing, etc.) domain: transforms Anything related to Vector's transform components needs: approval Needs review & approval before work can begin. labels Aug 7, 2020
@binarylogic binarylogic unassigned ghost Aug 7, 2020
@jszwedko
Copy link
Member

Hi all!

Vector's focus is on improving VRL to handle all data transformation needs. We want to avoid having a lot of transforms that are similar to remap but use a different language, so we won't be prioritizing this. If there is anything that you need that VRL doesn't support, we would welcome an issue for it. There is the potential that we will add support for custom transforms using WASM or some other mechanism so this could also be supported that way.

Thanks for everyone's thoughts here!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
domain: processing Anything related to processing Vector's events (parsing, merging, reducing, etc.) domain: transforms Anything related to Vector's transform components needs: approval Needs review & approval before work can begin. type: feature A value-adding code addition that introduce new functionality.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants