是否有原生支持Union-Find（不相交集合）数据结构的数据库系统？

Great question! Let's break this down: your core need is finding a database that out-of-the-box (OOTB) supports the Union-Find (disjoint-set) data structure—meaning you don’t have to build and maintain your own implementation from scratch.

Options for OOTB Union-Find-like functionality #

While most general-purpose relational databases don’t expose explicit union() or find() APIs, there are a few categories of databases that either natively support Union-Find’s core use cases or provide ready-to-use tools for it:

• Graph Databases
  This is the closest match for OOTB Union-Find support. Graph databases like Neo4j, JanusGraph, and Amazon Neptune are built to handle connectivity and component-based operations—exactly what Union-Find is designed for.
  For example:

  • To mimic a find() operation (retrieve all nodes in the same component as a target), you can run a native traversal query like MATCH (n)-[*]-(m) WHERE id(n) = $targetId RETURN m in Neo4j.
  • To perform a union() (merge two components), you simply create a relationship between nodes from each component; the database’s underlying graph engine handles efficient component merging behind the scenes, just like Union-Find’s union operation.

• Distributed Graph Processing Engines (with storage integration)
  Tools like Apache Spark GraphX come with built-in implementations of connected components (the primary use case for Union-Find) that work seamlessly with stored datasets. You can directly call the connectedComponents() method to compute all disjoint sets in your data—this is a fully OOTB solution for large-scale Union-Find tasks, and Spark integrates with various storage systems (like HDFS, S3, or relational databases) to pull in your data.

• Specialized NoSQL Extensions
  Some NoSQL databases offer pre-built extensions that add Union-Find-aligned capabilities. For example, Redis has modules like RedisGraph that enable graph-based connectivity operations. While these aren’t part of the default Redis installation, they’re easy to enable and require no custom code, making them close to an OOTB solution.

A quick note on general-purpose relational databases #

Most SQL databases (PostgreSQL, MySQL, etc.) don’t have native Union-Find support. You can certainly implement Union-Find using tables and custom functions (like PL/pgSQL in PostgreSQL), but that requires writing your own logic—so it doesn’t meet the "out-of-the-box" requirement.

内容的提问来源于stack exchange，提问作者user976850