executor: remove default search time range of cluster_log when query without time range. (#16938)

[sre-bot]

cherry-pick #16938 to release-4.0

---

What problem does this PR solve?

Before this PR, when query the cluster_log table, if the user doesn't specify the time range, the default behavior is searching the recent 30 minutes logs, But DBA think this is not right, maybe return an error when the user query cluster_log doesn't specify the time range, just as below:

mysql>select * from `CLUSTER_LOG`
(1105, u"denied to scan logs, please specified the start time, such as `time > '2020-01-01 00:00:00'`")
mysql>select * from `CLUSTER_LOG` where time > "2020-04-28 17:00:10"
(1105, u"denied to scan logs, please specified the end time, such as `time < '2020-01-01 00:00:00'`")
mysql>select * from `CLUSTER_LOG` where time > "2020-04-28 17:00:10" and time < '2020-04-28 18:00:00'
(1105, u"denied to scan full logs (use `SELECT * FROM cluster_log WHERE message LIKE '%'` explicitly if intentionally)")

How it Works:

Related changes

• Need to cherry-pick to the release branch

Check List

Tests

• Unit test

Side effects

• Breaking backward compatibility

Release note

• Remove the default search time range of cluster_log when querying without time range.

[sre-bot]

/run-all-tests

[Deardrops]

/rebuild

[zz-jason]

LGTM

[Deardrops]

LGTM

[sre-bot]

Your auto merge job has been accepted, waiting for:

• 17118
• 17107
• 16165

[sre-bot]

/run-all-tests