[Fix] fix deserialization error for QueryPlan exception

[link3280]

Proposed changes

Issue Number: close #65

Problem Summary:

Deserialization error on QueryPlan with exceptions.

Checklist(Required)

1. Does it affect the original behavior: (No)
2. Has unit tests been added: (No Need)
3. Has document been added or modified: (No Need)
4. Does it need to update dependencies: (No)
5. Are there any changes that cannot be rolled back: (No)

Further comments

If this is a relatively large or complex change, kick off the discussion at [email protected] by explaining why you chose the solution you did and what alternatives you considered, etc...

[JNSimba]

Thank you for your pr, is it also possible to add @JsonIgnoreProperties(ignoreUnknown = true) directly to the entity class of QueryPlan ?

[link3280]

Yes. Do you mean adding the annotation alone or also with the exception field? I think the exception msg is helpful and should be exposed to users properly.

[JNSimba]

However, the response of queryPlan has been judged in RestService.getQueryPlan, and an exception is also thrown when an error occurs, so is there no need to record the exception in queryPlan?