Define Exports option not available

After some trying and playing around with the python script (catalyst2_pipeline.py (7.1 KB)), I was able to generate something better but got the following warning messages.

(   3.630s) [pvbatch.0       ]vtkSOADataArrayTemplate:338   WARN| 23vtkSOADataArrayTemplateIdE (0x560192aeb580): GetVoidPointer called. This is very expensive for non-array-of-structs subclasses, as the scalar array must be generated for each call. Using the vtkGenericDataArray API with vtkArrayDispatch are preferred. Define the environment variable VTK_SILENCE_GET_VOID_POINTER_WARNINGS to silence this warning.
(   3.624s) [pvbatch.1       ]vtkSOADataArrayTemplate:338   WARN| 23vtkSOADataArrayTemplateIdE (0x558637bab690): GetVoidPointer called. This is very expensive for non-array-of-structs subclasses, as the scalar array must be generated for each call. Using the vtkGenericDataArray API with vtkArrayDispatch are preferred. Define the environment variable VTK_SILENCE_GET_VOID_POINTER_WARNINGS to silence this warning.
(   3.630s) [pvbatch.2       ]vtkSOADataArrayTemplate:338   WARN| 23vtkSOADataArrayTemplateIdE (0x55842f5b8390): GetVoidPointer called. This is very expensive for non-array-of-structs subclasses, as the scalar array must be generated for each call. Using the vtkGenericDataArray API with vtkArrayDispatch are preferred. Define the environment variable VTK_SILENCE_GET_VOID_POINTER_WARNINGS to silence this warning.
(   3.630s) [pvbatch.3       ]vtkSOADataArrayTemplate:338   WARN| 23vtkSOADataArrayTemplateIdE (0x55bd003d7360): GetVoidPointer called. This is very expensive for non-array-of-structs subclasses, as the scalar array must be generated for each call. Using the vtkGenericDataArray API with vtkArrayDispatch are preferred. Define the environment variable VTK_SILENCE_GET_VOID_POINTER_WARNINGS to silence this warning.
(  32.188s) [pvbatch.0       ]vtkSOADataArrayTemplate:338   WARN| 23vtkSOADataArrayTemplateIdE (0x56019199f160): GetVoidPointer called. This is very expensive for non-array-of-structs subclasses, as the scalar array must be generated for each call. Using the vtkGenericDataArray API with vtkArrayDispatch are preferred. Define the environment variable VTK_SILENCE_GET_VOID_POINTER_WARNINGS to silence this warning.
(  32.183s) [pvbatch.1       ]vtkSOADataArrayTemplate:338   WARN| 23vtkSOADataArrayTemplateIdE (0x558636719930): GetVoidPointer called. This is very expensive for non-array-of-structs subclasses, as the scalar array must be generated for each call. Using the vtkGenericDataArray API with vtkArrayDispatch are preferred. Define the environment variable VTK_SILENCE_GET_VOID_POINTER_WARNINGS to silence this warning.
(  32.188s) [pvbatch.2       ]vtkSOADataArrayTemplate:338   WARN| 23vtkSOADataArrayTemplateIdE (0x55842e159880): GetVoidPointer called. This is very expensive for non-array-of-structs subclasses, as the scalar array must be generated for each call. Using the vtkGenericDataArray API with vtkArrayDispatch are preferred. Define the environment variable VTK_SILENCE_GET_VOID_POINTER_WARNINGS to silence this warning.
(  32.188s) [pvbatch.3       ]vtkSOADataArrayTemplate:338   WARN| 23vtkSOADataArrayTemplateIdE (0x55bcfef785d0): GetVoidPointer called. This is very expensive for non-array-of-structs subclasses, as the scalar array must be generated for each call. Using the vtkGenericDataArray API with vtkArrayDispatch are preferred. Define the environment variable VTK_SILENCE_GET_VOID_POINTER_WARNINGS to silence this warning.

This is what I got:

Found a similar topic on discourse with this warning message. Can someone help me with this?
Post with same warning message