mxpi_dumpdata
If this plugin is used, the output data of the plugin will be saved to files on the drive, resulting in additional files. You need to manage those files and delete them if necessary. Do not use this plugin when processing private or sensitive data.
Function |
Data export plugin, which is used to export the MxpiBuffer data of the upstream plugin in JSON format. If the location property is not specified, the exported data is stored in the MxpiBuffer and sent to the downstream plugin. If the location property is specified, the data is exported to the specified file and the MxpiBuffer data of the upstream plugin is transparently transmitted to the downstream plugin. |
|---|---|
Constraints |
Only the data of the types defined by Protobuf can be exported from metadata. Customized C++ class or struct data cannot be exported. |
Plugin Base Class (Factory) |
mxpi_dumpdata |
Input/Output |
Input: buffer (data type: MxpiBuffer) Output: buffer (data type: MxpiBuffer) |
Property |
For details, see Table 1. |
Property Name |
Description |
Mandatory or Not |
Modifiable or Not |
|---|---|---|---|
filterMetaDataKeys |
During the export, the index content in the metadata is filtered. If the metadata contains the customized C++ class or struct data, you need to enter the index corresponding to the data. If there are multiple indexes, use commas (,) to separate them. For example, "ReserveMetadataGraph, MxstFrameExternalInfo". NOTE:
This property is invalid when requiredMetaDataKeys is set. |
No |
Yes |
requiredMetaDataKeys |
During the export, only the content of the specified index in the metadata is exported. If there are multiple indexes, use commas (,) to separate them, for example, mxpi_imagedecoder0, ReservedVisionList. |
No |
Yes |
location |
(Optional) Name of the file to which data is exported. If this parameter is left empty, data is not exported and is transferred to the next plugin. If this parameter is specified, data is exported to a file, and the MxpiBuffer of the upstream plugin is transparently transmitted to the downstream plugin. If the configured file name contains a directory name, a directory is automatically created. For example, after the file name test/file.output is configured, the test directory is created, and the data is dumped to the file.output file in the directory. |
No |
Yes |
dumpMemoryData |
Whether to export the dataStr field in MxVisionData and MxpiTensor. This field is used to save the memory data encoded by Base64 to a text file. The data length is large. The default value is true, indicating that this field is exported. The value false indicates that this field is not exported. |
No |
Yes |