-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
feat(new transform): New merge
transform
#1504
Conversation
a9dc7ff
to
9147835
Compare
997ac28
to
1e9f355
Compare
The feature is incomplete, however, the approach is settled, and overall it's ready for review. What remains to be added is:
|
merge
transform
Nice work! Do you plan to do those remaining items in this PR or in separate PRs? |
I'd move some of the pending things from the checklist to the separate PRs:
I'd like to take care of the last point - multiple partial event queues - as part of this one. |
Btw, I think it's time to team up for test harness setup. |
Signed-off-by: MOZGIII <[email protected]>
…d, ignoring the value Signed-off-by: MOZGIII <[email protected]>
Signed-off-by: MOZGIII <[email protected]>
Signed-off-by: MOZGIII <[email protected]>
Signed-off-by: MOZGIII <[email protected]>
Signed-off-by: MOZGIII <[email protected]>
…te of the value Signed-off-by: MOZGIII <[email protected]>
Sounds good. Also, regarding the Let's schedule time next week to dive into the test harness. I'll ping you. |
…ier understanding Signed-off-by: MOZGIII <[email protected]>
Signed-off-by: MOZGIII <[email protected]>
Signed-off-by: MOZGIII <[email protected]>
Signed-off-by: MOZGIII <[email protected]>
Signed-off-by: MOZGIII <[email protected]>
We'll most likely be reusing that logic pretty soon. Signed-off-by: MOZGIII <[email protected]>
Signed-off-by: MOZGIII <[email protected]>
@MOZGIII mind resolving the conflicts? Then hopefully we can get this merged 🚀 |
@binarylogic sure, will do shortly. I'd like to have feedback from @lukesteensen on #1504 (comment) before the merge. |
Yep, I think if we can get this green on CI then we should be in a good place to merge. |
Nice! Let's make the final changes in #1504 (comment) and then we can merge @MOZGIII . |
It's not as optimized at the previous variant, however it's way easier to understand and maintain. Signed-off-by: MOZGIII <[email protected]>
There are some merge conflicts that are in the |
Signed-off-by: MOZGIII <[email protected]>
Ideally, we should alter that commit (1421277) to only include the changes relevant to this PR. |
Signed-off-by: MOZGIII <[email protected]>
Ended up with a merge resolution that negates the irrelevant changes, not sure how correct that is. |
Signed-off-by: MOZGIII <[email protected]>
That's fine. I'll review to make sure nothing is off. |
Thanks @binarylogic! I've tried to solve the |
I'll do a final pass on this, get the checks passing, and then merge. |
Just one sec, I'll update the docs. I'm only supposed to update the text at |
Yep, modify everything in the |
- Pull the latest field descriptions from the code for merge transform - Update the field names at merge transform and docker source - Update schema to allow `merge` at the `function_category` - Remove `guides` and `resources` from merge transform - not sure what those are about - Fix some minor nitpicks Signed-off-by: MOZGIII <[email protected]>
Signed-off-by: MOZGIII <[email protected]>
Done! So, one concern I had is with 687e281#diff-cc6d35117dc2abae06d7b7f10c958363L6-L9 - the |
Signed-off-by: binarylogic <[email protected]>
|
||
Where possible, Vector will handle event merging at the source level. For | ||
example, the [`file`][docs.sources.file] contains a `message_start_indicator` | ||
option and the [`docker`][docs.sources.file] contains an `auto_partial_merge` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@binarylogic here is a wrong link, should be [`docker`][docs.sources.docker]
Please forgive my ignorance in case it's been already answered, I couldn't find the answer in this PR or other issues. |
@Alexx-G thanks for reaching out! You're looking for this: #1718 |
Yep, this is exactly what I'm looking for. Can't believe I missed. |
Closes #1488.