Skip to content
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

DOCSP-34887: v1.11.1 release #151

Merged
merged 5 commits into from
Dec 11, 2023

Conversation

ccho-mongodb
Copy link
Contributor

@ccho-mongodb ccho-mongodb commented Dec 11, 2023

Pull Request Info

PR Reviewing Guidelines

JIRA - https://jira.mongodb.org/browse/DOCSP-34887
Staging - https://preview-mongodbcchomongodb.gatsbyjs.io/kafka-connector/DOCSP-34887-v1.11.1/whats-new/#std-label-kafka-connector-whats-new-1.11.1

Self-Review Checklist

  • Is this free of any warnings or errors in the RST?
  • Did you run a spell-check?
  • Did you run a grammar-check?
  • Are all the links working?
  • Are the facets and meta keywords accurate?

Copy link
Contributor

@jordan-smith721 jordan-smith721 left a comment

Choose a reason for hiding this comment

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

LGTM w/ one small fix and a suggestion

both the connector side and the server side .

Version 1.9 introduced a bug related to ``MongoSourceTask.start`` that can cause a resource leak on
both the connector side and the server side .
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
both the connector side and the server side .
both the connector side and the server side.

What's New in 1.11.1
--------------------

- Fixed wildcard matching for partial field name matching. To learn more about
Copy link
Contributor

Choose a reason for hiding this comment

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

S: The wording of this first sentence is a little confusing to, but possibly because I don't know these features well. Would it make sense to say something like this to avoid the repeated " matching" phrase:

Suggested change
- Fixed wildcard matching for partial field name matching. To learn more about
- Fixed partial name matching with wildcards. To learn more about

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think the "with" association makes it less clear how wildcards are associated with partial name matching.

Maybe "Fixed wildcard matching on partial field names in documents." could make this more clear without repeating "matching"?

@ccho-mongodb ccho-mongodb merged commit cf381ac into mongodb:master Dec 11, 2023
2 checks passed
ccho-mongodb pushed a commit that referenced this pull request Dec 11, 2023
* DOCSP-34887: v1.11.1 release

(cherry picked from commit cf381ac)
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.

2 participants