Support multiple MongoDB databases via @Table.catalog

XMLWordPrintableJSON

    • Type: New Feature
    • Resolution: Unresolved
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: Model
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Goal

      Let an application map entities to different MongoDB databases from a single SessionFactory by routing @Table.catalog to a MongoDB database (a MongoDB database is the analog of a SQL catalog). This is the "collections from different databases" goal originally captured in HIBERNATE-39, split out here.

      Why deferred

      Correctly supporting catalog as a database requires cross-catalog joins and transactions to behave as they do relationally. MongoDB has cross-database transactions but not cross-database $lookup (joins), so entities in different databases could not be joined. This is blocked on cross-database $lookup, tracked at SPM-1973.

      Catalog is rejected at boot today (HIBERNATE-39). Because no mapping uses catalog, adding catalog-to-database routing later is an additive change.

            Assignee:
            Unassigned
            Reporter:
            Jeffrey Yemin
            None
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: