TODO list after normalize pdclient to client-java

[yegetables]

• com.pingcap.tikv.util.ConvertUpstreamUtils.isTiKVVersionGreatEqualThanVersion method: If the upstream changes the method name from StoreVersion.minTiKVVersion to StoreVersion.isTiKVVersionGreatEqualThanVersion, remove this method and use the upstream method directly. change method name StoreVersion.minTiKVVersion to StoreVersion.isTi… tikv/client-java#647

• TiDBOptions txnPrewriteBatchSize,txnCommitBatchSize,writeBufferSize,writeThreadPerTask,retryCommitSecondaryKey,prewriteMaxRetryTimes are deleted, because these configuration items involve the private constructor of TwoPhaseCommitter. Upstream does not provide a public constructor for use. Temporarily disable the settings of several configuration items to restore the upstream updated configuration. (recovery of documents involved).

• TiFlash cache missing need to fix. [TISPARK-488] Fix TiFlash region cache  #1380 Temporarily fixed in TiSpark.

• If the retry logic of batchGet is added upstream. Re-check the test result of batchGetRetryTest. Restore the test or modify/delete the test [fix #643] fix retry with resolvedlocks info tikv/client-java#645

According to the removed class by #2491, the following prs need to be paid attention to. we need to judge if they are needed to port to upstream.

• Retry

  • Fix txnHeartBeat retry: TTL enhancement #2304
  • retry enhancement: do not retry for some key error #1768 Fix retry bug #2279

• Region manager

  • Fix region manager race: Fix region manager race #1987

  • Optimize region cache miss：Optimize region cache miss #2106 + fix not leader error due to region not invalidatedhttps://github.com/Fix not leader error due to region not invalidated #2135

  • fix region may be missed: fix region may be missed #2433

• support log desensitization： support log desensitization #1798

• Fix ResolveLock not called in Scan API Fix ResolveLock not called in Scan API #2089

• fix region may be missed fix region may be missed #2433 （done）

• Make TiSpark's Explain clearer and easier to read: Make TiSpark's Explain clearer and easier to read #2439

• support clustered index support clustered index #1915 ( maintain CoprocessorIterator in TiSpark or upstream ?)

[shiyuhang0]

TiFlash cache missing needs to fix. [TISPARK-488] Fix TiFlash region cache #1380 Temporarily fixed in TiSpark

• Fix cache miss and delete an useless test #2608

If the retry logic of batchGet is added upstream. Re-check the test result of batchGetRetryTest. Restore the test or modify/delete the test tikv/client-java#645

• [close #684] Fix batch get blocked by write (#685) tikv/client-java#691

Fix region manager race: #1987. (seems has done in client-java)
Optimize region cache miss：#2106 + fix not leader error due to region not invalidatedhttps://github.com/#2135

• These three pr is difficult to backport. upstream has a big difference, it is hard to say if they are ported.
• Consider to rewrite regioncache to reduce the cache number. tikv/client-java#696
• [close #693] Add test for RangeSplitter tikv/client-java#694

fix region may be missed: #2433

• [fix #623] region may be missed tikv/client-java#624

support log desensitization： #1798

• Support log desensitization tikv/client-java#680

Fix ResolveLock not called in Scan API #2089

• [to #656] Fix scan with lock tikv/client-java#670

Make TiSpark's Explain clearer and easier to read: #2439
support clustered index #1915 ( maintain CoprocessorIterator in TiSpark or upstream ?)
Fix txnHeartBeat retry: #2304
retry enhancement: #1768 #2279

• need not port

[shiyuhang0]

Sometimes, it is difficult to judge which is better (TiSpark or client-java), for example, return null or throw an exception; whether retry for a certain error
In such case, here are two suggestions:

• follow the behavior of TiDB
• reference client-go

[yegetables]

有时候，很难判断哪个更好（TiSpark或者client-java），比如返回null或者抛出异常；是否为某个错误重试 这种情况，这里有两个建议：

• 随行 TiDB 的行为
• 参考客户端

The previous integration test table was not found whether it was caused by a cache miss

I found that the integration test on jenkins seems to be refactored once? (curious)

[shiyuhang0]

table not found may not result from the cache miss. it supposed to be fixed in this pr tikv/client-java#670.

integration test should not be refactored.

[shiyuhang0]

All things have been done or a corresponding issue has been opend