lightning/parser: support STARTING BY and IGNORE n LINES

[lance6716]

Signed-off-by: lance6716 lance6716@gmail.com

What problem does this PR solve?

Issue Number: ref #40499

Problem Summary:

What is changed and how it works?

• STARTING BY: add token. When meet it reset the state of parser
• IGNORE n LINES: skip output for n times readRecords

Hide these configuration for lightning, only prepare for future LOAD DATA integration

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has not been approved.

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[lance6716]

/cc @gozssky @lichunzhu @GMHDBJD @kennytm

[sleepymole]

@lance6716 Could you explain why we need these two configurations? Is it possible to do them outside the parser?

[lance6716]

@lance6716 Could you explain why we need these two configurations? Is it possible to do them outside the parser?

I can't come up with a simple change outside parser. We need use parser to know where a line ends, and these two configurations can skip errors when find line endings.

I have added some unit tests, when the skipped content contains special characters like fields delimiter it's very complex.

[lance6716]

/hold

IGNORE n LINES should be able to move out of parser, let caller call ReadUntilTerminator for n times. And I'll check if put more restriction on STARTING BY could simplify the code

[lance6716]

should be replaced by #40821