-
Notifications
You must be signed in to change notification settings - Fork 202
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
[BUG] Parquet Codec requires path_prefix #3201
Comments
dlvenable
added a commit
to dlvenable/data-prepper
that referenced
this issue
Aug 22, 2023
…ill keep untested and errant code paths out of the project. Resolves opensearch-project#3201. Signed-off-by: David Venable <[email protected]>
dlvenable
added a commit
to dlvenable/data-prepper
that referenced
this issue
Aug 22, 2023
…ill keep untested and errant code paths out of the project. Resolves opensearch-project#3201. Signed-off-by: David Venable <[email protected]>
4 tasks
dlvenable
added a commit
to dlvenable/data-prepper
that referenced
this issue
Aug 22, 2023
…ill keep untested and errant code paths out of the project. Resolves opensearch-project#3201. Signed-off-by: David Venable <[email protected]>
dlvenable
added a commit
that referenced
this issue
Aug 22, 2023
…ill keep untested and errant code paths out of the project. Resolves #3201. (#3205) Signed-off-by: David Venable <[email protected]>
github-project-automation
bot
moved this from Unplanned
to Done
in Data Prepper Tracking Board
Aug 22, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
DataPrepper throws an exception on start up if
path_prefix
is not defined under the parquet codec.The S3 sink configuration has
path_prefix
defined under theobject_key_options
object. I think the correct behavior would be to removepath_prefix
from the parquet codec configurationTo Reproduce
Create an S3 sink pipeline using the parquet codec without path_prefix defined in the codec config
Example S3 sink config
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: