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

Refactor lambda code to share code between processor and sink #5196

Draft
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

kkondaka
Copy link
Collaborator

Description

Refactor lambda code to share code between processor and sink

Issues Resolved

Resolves #[Issue number to be closed when this PR is merged]

Check List

  • New functionality includes testing.
  • New functionality has a documentation issue. Please link to it in this PR.
    • New functionality has javadoc added
  • [ X] Commits are signed with a real name per the DCO

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

//lambdaLatencyMetric.record(latency.toMillis(), TimeUnit.MILLISECONDS);
//totalFlushedEvents += eventCount;

convertLambdaResponseToEvent(resultRecords, response, flushedBuffer, successHandler);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We dont need this for sink and hence should not be in common code.

@JsonPropertyDescription("Codec configuration for parsing Lambda responses")
@JsonProperty("response_codec")
@Valid
private PluginModel responseCodecConfig;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we dont need this for sink ; should be specific to processor

Signed-off-by: Kondaka <[email protected]>
Signed-off-by: Kondaka <[email protected]>
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

Successfully merging this pull request may close these issues.

2 participants