[SAMZA-2193] Fix unit test failures after rate limiter is a required config

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Component/s: test
• Assignee: Unassigned
• Reporter: Dengpan Yin
• Created: 15/May/19 00:44
• Updated: 20/May/19 22:13

Description

A recent code merge makes rate limiter as a required config. After that RB is created and before it's merged, some new tests are added without setting or disabling rate limiter.  This cause the unit-test failure. 

 

> Task :samza-core_2.11:test

testTableRetryPolicyToConfig FAILED
java.lang.IllegalArgumentException: Read rate limiter is enabled, there is no read rate limiter configured.
at com.google.common.base.Preconditions.checkArgument(Preconditions.java:135)
at org.apache.samza.table.descriptors.RemoteTableDescriptor.validate(RemoteTableDescriptor.java:343)
at org.apache.samza.table.descriptors.BaseTableDescriptor.toConfig(BaseTableDescriptor.java:75)
at org.apache.samza.table.descriptors.RemoteTableDescriptor.toConfig(RemoteTableDescriptor.java:270)
at org.apache.samza.table.remote.descriptors.TestRemoteTableDescriptor.testTableRetryPolicyToConfig(TestRemoteTableDescriptor.java:220)

Issue Links

• links to: GitHub Pull Request #1032