Add blog post: Ignore Duplicate Writes feature announcement

[tylernix]

Summary

This PR adds a blog post announcing the new "Ignore Duplicate Writes" feature in OpenFGA, which allows developers to handle duplicate writes and missing deletes gracefully in the Write API.

What's New

🎉 Feature Announcement

• Ignore Duplicate Writes: New on_duplicate: "ignore" parameter for writes
• Ignore Missing Deletes: New on_missing: "ignore" parameter for deletes
• Streamlined Data Imports: Eliminates need for complex client-side retry logic

📝 Blog Post Content

• Problem Statement: Explains the friction of handling duplicates in large-scale data imports
• Solution Overview: Clear explanation of the new parameters and their benefits
• Practical Example: Complete cURL request showing the feature in action
• SDK Documentation: Links to implementation docs for all five OpenFGA SDKs

🙏 Community Recognition

• Special thanks to @phamhieu for contributing to the JavaScript SDK implementation

Blog Post Highlights

The Problem

Previously, OpenFGA would reject entire Write requests if they contained a single duplicate tuple or attempted to delete a non-existent tuple, forcing developers to build complex error handling.

The Solution

Two new optional parameters:

• on_duplicate: "ignore" - Skip existing tuples instead of failing
• on_missing: "ignore" - Skip non-existent tuples during deletion

SDK Support

Feature is available across all OpenFGA SDKs:

• Java SDK
• .NET SDK
• Python SDK
• Go SDK
• JavaScript SDK

Content Quality

• ✅ Clear, accessible writing for developers
• ✅ Practical code examples
• ✅ Direct links to implementation documentation
• ✅ Community contributor recognition
• ✅ Follows established blog post format and style

This announcement will help developers discover and adopt this workflow-improving feature for their data import and synchronization needs.

Summary by CodeRabbit

• New Features

  • Write API now supports ignoring duplicate writes and missing deletes in batch operations using new parameters.

• Documentation

  • Added announcement post with usage examples, curl request samples, and SDK integration guides.

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

A new blog post is added announcing a Write API feature update. The post describes the ability to ignore duplicate writes via on_duplicate: "ignore" and ignore missing deletes via on_missing: "ignore" within batch operations, including usage examples and SDK documentation links.

Changes

Cohort / File(s)	Summary
Blog announcement blog/ignore-duplicate-writes-announcement.md	New blog post announcing Write API feature for handling duplicate writes and missing deletes with configuration options, examples, and SDK links

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Verify announcement content accuracy and clarity
• Check formatting and links for validity
• Confirm all referenced SDK documentation links are correct

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The pull request title "Add blog post: Ignore Duplicate Writes feature announcement" directly and accurately summarizes the main change in the changeset. The PR adds a single new file (blog/ignore-duplicate-writes-announcement.md) that announces OpenFGA's new feature for ignoring duplicate writes in the Write API. The title is concise, specific, and clearly communicates the primary change without vague language or unnecessary noise. A teammate reviewing the pull request history would immediately understand that this PR introduces documentation for a feature announcement.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

🧹 Nitpick comments (1)

blog/ignore-duplicate-writes-announcement.md (1)

78-80: Reduce exclamation marks for a more professional tone.

The static analysis tool flagged the excessive use of exclamation marks in this section. Consider removing one or two to maintain a more measured, professional tone while keeping the enthusiasm.

- ## We want your feedback!
+ ## We want your feedback

- Please reach out through our [community channels](https://openfga.dev/docs/community) with any questions or feedback.
+ Please reach out through our [community channels](https://openfga.dev/docs/community) with any questions or feedback

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b4710a2 and 6b3b5c6.

📒 Files selected for processing (1)

• blog/ignore-duplicate-writes-announcement.md (1 hunks)

🧰 Additional context used

🪛 GitHub Actions: Deploy PR previews

blog/ignore-duplicate-writes-announcement.md

[error] 1-1: Blog author with key "openfga" not found in the authors map file. Valid author keys are: aaguiar, eharris, miparnisari, hello-caleb.

🪛 GitHub Actions: Test deployment

blog/ignore-duplicate-writes-announcement.md

[error] 1-1: Blog author with key "openfga" not found in the authors map file. Valid author keys are: aaguiar, eharris, miparnisari, hello-caleb.

🪛 LanguageTool

blog/ignore-duplicate-writes-announcement.md

[style] ~78-~78: Using many exclamation marks might seem excessive (in this case: 3 exclamation marks for a text that’s 2030 characters long)
Context: ...ssing-tuples). ## We want your feedback! Please reach out through our [communit...

(EN_EXCESSIVE_EXCLAMATION)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: markdown-link-check-md

🔇 Additional comments (2)

blog/ignore-duplicate-writes-announcement.md (2)

64-76: Verify SDK documentation links are correct.

The blog post references specific README sections for each SDK with anchor links (#conflict-options-for-write-operations). Please confirm these sections exist in each repository and the links resolve correctly.

---

12-30: Content quality looks good.

The problem statement is clear and relatable, the solution is well-explained, and the feature benefits are articulated effectively. The narrative flow is smooth and appropriate for a feature announcement.

[github-actions]

PR Preview Action v1.6.2
Preview removed because the pull request was closed.
2025-11-20 16:54 UTC

[dyeam0]

LGTM