Troubleshooting

Back Next

Troubleshooting a mapping in advanced mode

Review the rules and guidelines for configuring a mapping in advanced mode.

The Source transformation returns a JSON parsing error, even though my JSON file is good. What should I do?: When you select a JSON file in the source object, you receive the following error:
error [The file or partition directory [<path>/<JSON file>] is not valid. The parser encountere the following error while parsing the content: [Unexpected character 1 at 1]. Select a valid [Json] file or partition director.]

The error occurs when there is an array of primitives without a field name in the JSON file. For example, the following array causes a parsing error:
[10,20,30,40,50,0]

The Source transformation parses the following array successfully:
{"numbers":[10,20,30,40,50,0]}

As a workaround, wrap the top-level array in a struct element before reading the file in the Source transformation.
I received error "version `GLIBC_2.28' not found" when running a mapping in advanced mode.: Contact your system administrator to resolve this issue.; During Python installation, the Linux package managers identify the corresponding dependency packages based on the node's operating system version. If you install Python on RHEL 8.x, the installer pulls a build based on GLIBC_2.28.; This error occurs when all the following conditions apply:
You previously installed a custom Python version under RHEL 7.x.
You upgrade to RHEL 8.x and then reinstall the same custom Python version.
You attempt to run a mapping in advanced mode that contains a Python transformation.; The mapping in advanced mode fails because the custom Python installation requires a higher version of GLIBC than the version in the Spark Docker image.; To resolve the error, locate the Python installation folder from a Secure Agent node that is still running on RHEL 7.x and then copy that folder over to the RHEL 8.x node.