Skip to content

Filter wrong formatted discovery addresses #197

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 19, 2019

Conversation

nicktorwald
Copy link

Instead of discarding the full list of addresses when at least one
address does not match the format like host[:port] a discoverer just
skips this broken address and carries on processing.

Change discovery function requirements description in part of single
value support. This is done to be consistent with other Tarantool
connectors.

Closes: #195, #196

@coveralls
Copy link

coveralls commented Jun 3, 2019

Coverage Status

Coverage increased (+0.01%) to 72.252% when pulling 5224914 on nicktorwald/gh-195-discard-discovery-addr into 2473ffa on master.

@nicktorwald nicktorwald force-pushed the nicktorwald/gh-195-discard-discovery-addr branch from a911a05 to ff10903 Compare June 4, 2019 06:58
@nicktorwald nicktorwald requested a review from Totktonada June 4, 2019 06:59
Copy link
Member

@Totktonada Totktonada left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review for 'Do not use call_16 method in the tarantool client'.

I would clarify the commit message to clearly state that support of call_16 is removed.

I think it also worth to fix README re single/list result from a cluster discovery function right in this commit (because it is changed here).

Copy link
Member

@Totktonada Totktonada left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review for 'Filter wrong formatted discovery addresses'.

@nicktorwald nicktorwald force-pushed the nicktorwald/gh-195-discard-discovery-addr branch 2 times, most recently from 680e8de to 5313a92 Compare June 12, 2019 18:55
@nicktorwald nicktorwald requested a review from Totktonada June 12, 2019 19:18
Copy link
Member

@Totktonada Totktonada left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The code looks ok for me. Just several notes about commit messages.

#196 is closed in the commit re call_16 / call_17, not in 'Filter wrong formatted discovery addresses'.

'Change discovery function requirements in part of single value support' — did you mean that a non-list value is forbidden? If so, this is also actually about the commit re call_16 / call_17.

Please, fix comments and merge.

The call_16 became obsolete when tarantool-1.6 was gone. There're
no reasons to continue using the old version by default.

Change discovery function requirements in part of single
value support. This is done to be consistent with other Tarantool
connectors.

Closes: #196
Instead of discarding the full list of addresses when at least one
address does not match the format like host[:port] a discoverer just
skips the broken address and carries on processing.

Closes: #195
@nicktorwald nicktorwald force-pushed the nicktorwald/gh-195-discard-discovery-addr branch from 5313a92 to 5224914 Compare June 18, 2019 20:07
@nicktorwald nicktorwald merged commit b53e0ba into master Jun 19, 2019
@nicktorwald nicktorwald deleted the nicktorwald/gh-195-discard-discovery-addr branch June 19, 2019 10:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

cluster discovery: don't discard the entire result when there are bad addresses
3 participants