DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
...
We can see the one real redundancy example in the following picture. (I just highlight only one segment.)
Whenthere is no requirement for real-time analytics based on remote storage directly. It has the following drawbacks:
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
public static final String LOG_REMOTE_COPY_LAG_MS_PROP = "log.remote.copy.lag.ms";
public static final String LOG_REMOTE_COPY_LAG_BYTES_PROP = "log.remote.copy.lag.bytes"; |
The default value are 0 -2 so that the whole remote storage module keeps the original behavior.
...
We can use follow tests to cover the change:
Type\Configure | local retention time | local retention size | lag time | lag size | Expect result |
Special cases which can help to understand the basic rule for code review
| * | * | -2 (default value) | * | No lag time check but check lag size if need |
* | * | 0 | * | No any delay check. | |
-1 | * | -1 | * | Invalid configure | |
* | * | * | -2 (default value) | No lag size check but check lag time if need | |
* | * | * | 0 | No any delay check. | |
* | -1 | * | -1 | Invalid configure | |
Typical user cases which can test with deployment | 3 days
| -1
| -2 (default value) | -2 (default value) | No lag |
1 day | -2 (default value) | lag: 1 day | |||
-1 | -2 (default value) | lag: 3 days | |||
-1 | 3 GB | -2 (default value) | -2 (default value) | No lag | |
-2 (default value) | 1 GB | lag: 1 GB | |||
-2 (default value) | -1 | lag: 3 GB | |||
3 days | 3 GB | -2 (default value) | -2 (default value) | No lag | |
1 day | -11 GB | lag: 1 days or 1 GB | |||
-1 | -1 | lag: 3 days or 3 GB |
Unit Tests:
- Test upload eligibility logic with different configure values
- Test configuration validation for topic
...