New in Product
Migrating from Partition Sync to Flexible Sync
You can now migrate your backend app from partition-based sync to flexible sync in a backward-compatible way.
- Partition Sync: documents in a synced cluster form a “partition” by having the same value for a field designated as “partition key”.
- Flexible Sync: lets you define a query in the client and sync only the objects that match the query.
The migration is automatic and aims to minimize disruption to end-users aside from a period of downtime. Learn more about the requirements and what to expect in the Migrate Device Sync Modes section of the Atlas App Services docs.
Full Text Search with MongoDB Realm
The Realm engineering team is pleased to introduce full-text search (FTS) support for Realm - a feature requested by many developers. The feature allows quick and efficient search within large datasets. A detailed explanation with examples on FTS with .NET SDK is provided by our engineer Ferdinando Papale on the MongoDB Developer Blog.
Realm Kotlin v1.10.1
Available now on Maven Central and Gradle Plugin Portal. This release improves testing Android apps by adding support for JVM tests and Robolectric, introduces support for data ingest or “write-only” sync, and makes it easier to work with Flexible Sync subscriptions with a new subscribe() API. For more details, check out the Realm Team Blog .
From the Community
How to save user custom data on signup ?
Kudos to our community member @Peter_Rauscher for helping fellow developers with a solution to add custom data when a new user signs-up. Steps to take:
- Register the user and insert a document into custom user data collection with an identifier from user object such as email.
- When the user is created, the custom user data creation function will run, and you can update the document with the users’ id in the custom user data field in the document you created in above step.
3rd Party Services deprecated, what are the alternatives ?
Thanks to our community members @Jason_Tulloch1, and @Adam_Holt for bringing up the discussion on 3rd party services and providing an alternative to handle AWS S3 requests.
The MongoDB team is extending the timeline for deprecation of 3rd party services from Aug 1, 2023 to Nov 1, 2024 and banners on documentation pages will be updated to reflect the new date. Additional communications on recommended actions will be shared in the coming months.
Please use our MongoDB Feedback Engine to provide your feedback on our offerings and upvote the features you hope to see.
Henna Singh
Community Manager
MongoDB Community Team
Know someone who might be interested in this newsletter? Share it with them. Subscribe here to receive a copy in your inbox.