Pull unique/eng changes to 2.x

[cbot59]

Description

Pull #260 changes to 2.x

Fixes # (issue)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

N/A

• Unit Test
• Integration Test
• Reactive Integration Test

Test Configuration:

• Spring Version : 5.0.10.RELEASE
• Spring Boot Version : 2.0.6.RELEASE
• Redis Driver Version

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• [] New and existing unit tests pass locally with my changes

[sonus21]

Can you please format this using google java formatter?

[cbot59]

@sonus21 I pulled the code changes based on unique-enq branch in which already applied its own styling and exist in master. If I apply the google-java-style format, the style would be different compared to master branch. Would it be okay?

A simple example.
master (left) vs local after applying google-java-formatter (right)