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

Content type support in Email mapper #343

Closed
potiuk opened this issue Jul 15, 2019 · 0 comments
Closed

Content type support in Email mapper #343

potiuk opened this issue Jul 15, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@potiuk
Copy link
Collaborator

potiuk commented Jul 15, 2019

Is your feature request related to a problem? Please describe.
Unfortunately, currently the EmailOperator only accepts the mime_subtype parameter.
However it only works for multipart subtypes, as the operator appends the subtype
to the multipart/ prefix. Therefore passing either html or plain from Oozie makes no sense.

As a result the email will always be sent with the EmailOperator's default Content-Type value,
which is multipart/mixed.

Describe the solution you'd like
Extends the EmailOperator to support content type as well.

@potiuk potiuk added the enhancement New feature or request label Jul 15, 2019
@potiuk potiuk removed this from the Delta (nice-to-have time permitting) milestone Jul 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants