Redis integration #3018

[washerath]

#3018
#3018

[linux-foundation-easycla]

• ✅ login: washerath / name: Wasantha Herath (5b224c4)
• ❌ The email address for the commit (9b24db5, 96949e4) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please submit a support request ticket.

[janusgraph-bot]

Please verify the committer name, email, and GitHub username association are all correct and match CLA records.

[li-boxuan]

@washerath Thank you for your contribution! A few things to notice:

1. EasyCLA is failing because you need to sign a CLA under Linux Foundation. The bot is complaining that it cannot find your user id, so that it cannot direct you to the CLA sign page. In order to fix this, you need to make sure you do your git commits using your GitHub account. Otherwise, GitHub cannot link your commit to your account. Then the bot should be able to proceed and guide you to sign your CLA. See this for more details.
2. You also need to "sign" your commit by appending a sign-off message at the end of each commit. You can take a look at any other commit in the repository. You can also follow this guide.
3. For every new file, you need to add a Copyright header otherwise the CI won't proceed with the build. Take a look at any existing file in the repository.
4. I remember you mentioned that you had to solve some performance issues. Do you have any statistics/benchmarks regarding the current performance with your Redis integration?

[janusgraph-bot]

Please verify the committer name, email, and GitHub username association are all correct and match CLA records.

[li-boxuan]

@washerath Just checking if you would like to proceed with this PR. Any help needed?

[washerath]

@li-boxuan Yes, I would like to contribute. As I see some checks have failed on my commit. I'll try to resolve them and try again.

[FlorianHockmann]

@washerath Is it correct that this PR is still open or was it superseded by your new PR: #4180? Because in that case, we could close this one.