-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Can't Handle GCP Memory Store Redis having extra characters in ClusterNode Entry #2862
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Addressed with pull-request: |
The comma is introduced by redis/redis#9564 (cluster hostname support). Another segment uses aux fields (redis/redis#10536). |
I have updated the pull-request with the fix to typo and added the unit test for the case (updated both class headers with author name per requirements checklist). Can you review? |
without this fix there's a problem with parsing of the cluster nodes command ouput (e.g. a trailing comma after cport is making the parsing fail) with this change we're converting regexp parsing to code parsing which also includes support for trailing commas after cport fixes gh-2862
Without this fix there's a problem with parsing of the cluster nodes command output (e.g. a trailing comma after cport is making the parsing fail) with this change we're converting regexp parsing to code parsing which also includes support for trailing commas after cport Closes #2862 Original Pull Request: #3000
Without this fix there's a problem with parsing of the cluster nodes command output (e.g. a trailing comma after cport is making the parsing fail) with this change we're converting regexp parsing to code parsing which also includes support for trailing commas after cport Closes #2862 Original Pull Request: #3000
There is an extra character in Cluster Node Line Entry for Google Cloud Platform Memory Store Redis and when using the Jedis with spring-data-redis, the following exception is thrown:
Connector. Sample entries causing ClusterNode information does not define host and port:
sample entry:
The text was updated successfully, but these errors were encountered: