There are no plans to support SKIP PARSER ERRORS with JSON. That mode is supported only for CSV, in which case it causes us to attempt to recover after discovering that the input data is in some sense invalid CSV, as far as we’re concerned.
Do you indeed want the pipeline to attempt to keep loading after hitting malformed JSON, or are you perhaps more interested in “non-parser” errors, e.g. with the SKIP DUPLICATE KEY ERRORS or SKIP CONSTRAINT ERRORS clauses?
In the first case, the best option is likely to set the global variable pipelines_stop_on_error to false. That will make it so that if pipelines hit a parser error, they’ll output an error to information_schema.pipelines_errors, skip the problematic file, and then continue loading from the next file.