You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
DataPrepper throws an exception on start up if path_prefix is not defined under the parquet codec.
Caused by: org.opensearch.dataprepper.model.plugin.InvalidPluginConfigurationException: Plugin parquet in pipeline null is configured incorrectly: pathPrefix must not be null
at org.opensearch.dataprepper.plugin.PluginConfigurationConverter.convert(PluginConfigurationConverter.java:73) ~[data-prepper-core-2.4.0-SNAPSHOT.jar:?]
at org.opensearch.dataprepper.plugin.DefaultPluginFactory.getConstructionContext(DefaultPluginFactory.java:115) ~[data-prepper-core-2.4.0-SNAPSHOT.jar:?]
at org.opensearch.dataprepper.plugin.DefaultPluginFactory.loadPlugin(DefaultPluginFactory.java:74) ~[data-prepper-core-2.4.0-SNAPSHOT.jar:?]
at org.opensearch.dataprepper.plugins.sink.s3.S3Sink.<init>(S3Sink.java:63) ~[s3-sink-2.4.0-SNAPSHOT.jar:?]
... 41 more
The S3 sink configuration has path_prefix defined under the object_key_options object. I think the correct behavior would be to remove path_prefix from the parquet codec configuration
To Reproduce
Create an S3 sink pipeline using the parquet codec without path_prefix defined in the codec config
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: