[close #776] Fix prewrite & commit log info to debug(#776)

[jackjeyis]

What problem does this PR solve?

Issue Number: close #issue_number

Problem Description: TBD

What is changed and how does it work?

Code changes

• Has exported function/method change
• Has exported variable/fields change
• Has methods of interface change
• Has persistent data change
• No code

Check List for Tests

This PR has been tested by at least one of the following methods:

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

Side effects

• Possible performance regression, WHY: TBD
• Increased code complexity, WHY: TBD
• Breaking backward compatibility, WHY: TBD
• NO side effects

Related changes

• Need to cherry-pick to the release branch
• Need to update the documentation
• Need to be included in the release note
• NO related changes

[shiyuhang0]

Delete this will be a break change. Some KeyException also need the retry, why do you want to exclude this?
If you still want to exclude some KeyException, please judge the type. here is an example

 if (e instanceof KeyException) {
      Kvrpcpb.KeyError ke = ((KeyException) e).getKeyError();
      if (ke == null) return true;
      if (!ke.getAbort().isEmpty()
          || ke.hasConflict()
          || ke.hasAlreadyExist()
          || ke.hasDeadlock()
          || ke.hasCommitTsExpired()
          || ke.hasTxnNotFound()) return false;
      return true;
    }

[jackjeyis]

ok，I review it again

[shiyuhang0]

It seems this test has nothing to do with this pr, right?

[shiyuhang0]

This test is based on the new constructor method added in this PR #775.
Do you mind move it to that PR, or the test will fail

[jackjeyis]

this test for verify write conflict will aways retry ,but need fast fail

[shiyuhang0]

could you explain why this test was added? Or what scenes/feature this test for

[shiyuhang0]

Why do you need to print error msg here?
Have you tried getKeyErr()? it should return the error and you should be able to get the error msg from getKeyErr().toString()

[zhangyangyu]

@jackjeyis thanks for your contribution. Is there any reason to change the log info? Does it cause any problem now?