Hibernate Extension Path to GA

XMLWordPrintableJSON

    • Type: Epic
    • Resolution: Unresolved
    • Priority: Major - P3
    • 1.0.0
    • Affects Version/s: None
    • Component/s: None
    • Path to GA
    • Java Drivers
    • None
    • In Progress
    • None
    • 38
    • 18
    • 38
    • 100
    • 0
    • 🟢 On Track
    • Hide

      2026-08-28 - 🟢 On Track

      • What was accomplished since the last update?
        • Features Merged
          • GROUP BY and HAVING over column references
          • Composite primary keys via @EmbeddedId, mapped to an _id sub-document
          • Value unwrapping for @Struct fields and HQL literals (groundwork for temporal types)
        • Release Pipeline Hardening (SSDLC)
          • CodeQL analysis of release refs, with the security configuration under our ownership
          • CodeQL SARIF and the SSDLC compliance report published as release assets
          • Reporting of authorized release-artifact publication to papertrail
          • Release workflow checkout action pinned by commit SHA
        • Features in Review
          • HQL datetime functions
          • GROUP BY and HAVING over expressions
          • Exclude _id from $project when unspecified
        • Features in Progress
          • Instant-like temporal types
          • Sequence-style identifier generation for @GeneratedValue
      • What's the focus over the next two weeks?
        • Merge HQL datetime functions and GROUP BY/HAVING over expressions (in review)
        • Complete aggregate functions in SELECT and HAVING, closing out GROUP BY support
        • Complete temporal types and sequence-style identifier generation
        • Begin composite key joins (@IdClass / @EmbeddedId) and DISTINCT support
      • Any risks/blockers/impediments?
        • GROUP BY support is de-risked: column references have merged, GROUP BY/HAVING over expressions is in review, and aggregate functions are next. It is no longer a single-owner bottleneck.
        • SSDLC release hardening, a policy prerequisite for GA, is now complete and is no longer an open release risk.
        • Scope continued to expand this cycle (temporal types and sequence-style identifier generation). Completed work was offset by the added scope, so the forecast held roughly flat against the date rather than pulling in.
        • No hard blockers. The forecast (P70 9/15) remains ahead of the .local NYC target.
      Show
      2026-08-28 - 🟢 On Track What was accomplished since the last update? Features Merged GROUP BY and HAVING over column references Composite primary keys via @EmbeddedId, mapped to an _id sub-document Value unwrapping for @Struct fields and HQL literals (groundwork for temporal types) Release Pipeline Hardening (SSDLC) CodeQL analysis of release refs, with the security configuration under our ownership CodeQL SARIF and the SSDLC compliance report published as release assets Reporting of authorized release-artifact publication to papertrail Release workflow checkout action pinned by commit SHA Features in Review HQL datetime functions GROUP BY and HAVING over expressions Exclude _id from $project when unspecified Features in Progress Instant-like temporal types Sequence-style identifier generation for @GeneratedValue What's the focus over the next two weeks? Merge HQL datetime functions and GROUP BY/HAVING over expressions (in review) Complete aggregate functions in SELECT and HAVING, closing out GROUP BY support Complete temporal types and sequence-style identifier generation Begin composite key joins (@IdClass / @EmbeddedId) and DISTINCT support Any risks/blockers/impediments? GROUP BY support is de-risked: column references have merged, GROUP BY/HAVING over expressions is in review, and aggregate functions are next. It is no longer a single-owner bottleneck. SSDLC release hardening, a policy prerequisite for GA, is now complete and is no longer an open release risk. Scope continued to expand this cycle (temporal types and sequence-style identifier generation). Completed work was offset by the added scope, so the forecast held roughly flat against the date rather than pulling in. No hard blockers. The forecast (P70 9/15) remains ahead of the .local NYC target.
    • Hide

      2026-08-28 - 🟢 On Track

      • What was accomplished since the last update?
        • Features Merged
          • GROUP BY and HAVING over column references
          • Composite primary keys via @EmbeddedId, mapped to an _id sub-document
          • Value unwrapping for @Struct fields and HQL literals (groundwork for temporal types)
        • Release Pipeline Hardening (SSDLC)
          • CodeQL analysis of release refs, with the security configuration under our ownership
          • CodeQL SARIF and the SSDLC compliance report published as release assets
          • Reporting of authorized release-artifact publication to papertrail
          • Release workflow checkout action pinned by commit SHA
        • Features in Review
          • HQL datetime functions
          • GROUP BY and HAVING over expressions
          • Exclude _id from $project when unspecified
        • Features in Progress
          • Instant-like temporal types
          • Sequence-style identifier generation for @GeneratedValue
      • What's the focus over the next two weeks?
        • Merge HQL datetime functions and GROUP BY/HAVING over expressions (in review)
        • Complete aggregate functions in SELECT and HAVING, closing out GROUP BY support
        • Complete temporal types and sequence-style identifier generation
        • Begin composite key joins (@IdClass / @EmbeddedId) and DISTINCT support
      • Any risks/blockers/impediments?
        • GROUP BY support is de-risked: column references have merged, GROUP BY/HAVING over expressions is in review, and aggregate functions are next. It is no longer a single-owner bottleneck.
        • SSDLC release hardening, a policy prerequisite for GA, is now complete and is no longer an open release risk.
        • Scope continued to expand this cycle (temporal types and sequence-style identifier generation). Completed work was offset by the added scope, so the forecast held roughly flat against the date rather than pulling in.
        • No hard blockers. The forecast (P70 9/15) remains ahead of the .local NYC target.

      2026-08-14 - 🟢 On Track

      • What was accomplished since the last update?
        • Features Merged
          • Index and unique constraint support
          • HQL row-value (tuple) predicates
          • HQL string functions
          • HQL CASE expression
          • Upsert and bulk upsert via StatelessSession
        • Features in Review
          • Composite primary keys via @EmbeddedId, mapped to an _id sub-document
          • GROUP BY and HAVING over column references
        • Features in Progress
          • HQL datetime functions
          • Value unwrapping for @Struct fields and HQL literals (groundwork for temporal types)
        • Scope
          • Continued to expand GA scope with additional high-priority features, including HQL CASE expressions, upsert, and datetime function/arithmetic support. Target release remains anchored to .local NYC.
      • What's the focus over the next two weeks?
        • Merge composite primary keys (@EmbeddedId) and GROUP BY/HAVING column references (in review)
        • Complete the remaining GROUP BY pieces: aggregate functions (accumulators) and GROUP BY/HAVING over expressions
        • Complete HQL datetime functions and arithmetic
        • Begin composite key joins (@IdClass / @EmbeddedId) and DISTINCT support
      • Any risks/blockers/impediments?
        • GROUP BY support has been split into independently deliverable pieces — GROUP BY/HAVING over column references (in review), aggregate functions (accumulators), and GROUP BY/HAVING over expressions. Almas took the column-references piece through review; the remaining pieces will be picked up next week. This is the last major area still open.
        • No hard blockers. The forecast (P70 9/01) remains ahead of the .local NYC target.

      2026-07-31 - 🟢 On Track

      • What was accomplished since the last update?
        • Features Merged
          • Expressions in HQL bulk UPDATE SET clause
          • @Table.schema support
          • Non-equijoin ON conditions
          • Compound equijoin ON conditions (composite primary keys)
        • Features in Review
          • Index and unique constraint support
          • HQL string concatenation
          • HQL row-value (tuple) predicates
        • Features in Progress
          • GROUP BY, HAVING, and aggregate functions
          • HQL datetime functions and arithmetic expressions
      • What's the focus over the next two weeks?
        • Merge index/unique constraint support, string concatenation, and row-value tuple predicates (in review)
        • Complete GROUP BY, HAVING, and aggregate functions
        • Complete HQL datetime functions and arithmetic expressions
        • Begin composite key joins (@IdClass / @EmbeddedId) and DISTINCT support
      • Any risks/blockers/impediments?
        • GROUP BY / HAVING / aggregate support (13 pts) remains the critical path. Its owner will be out for ~3 weeks, so it is being reassigned to keep it moving during his absence.
        • Slava will be unavailable for at least the next three weeks (two weeks vacation, one week backpressure from other work), reducing near-term capacity and review throughput.
        • Security (SECBUG) tickets from Mythos may reduce velocity over the next two weeks.
        • No hard blockers. The forecast (P70 8/21) remains ahead of the .local NYC target.

      2026-07-17 - 🟢 On Track

      • What was accomplished since the last update?
        • Features Merged
          • HQL pattern matching
          • HQL in / not in
          • HQL BETWEEN predicate
          • Expressions in SELECT and WHERE clauses
          • Optimistic locking support
          • Basic entity class hierarchy persistence and retrieval (single table and mapped superclass)
          • Required property for null semantics (MQL as the only supported value initially)
          • Prohibit org.bson.types, BSON document types, and UUID as domain types
          • Forbid the @JdbcTypeCode annotation
          • Clearer error message when startup connection fails
          • Automatic release publishing, including pre-releases
        • Features in Review
          • Non-equijoin ON conditions
          • Expressions in HQL bulk UPDATE SET clause
        • Features in Progress
          • Index and unique constraint support
          • @Table.schema support
          • GROUP BY, HAVING, and aggregate functions
        • Scope
          • Delivery is running well ahead of the initial estimate. With the target release still anchored to .local NYC, we have significantly expanded the GA scope to include additional high-priority features rather than pulling the date in.
        • Demo
          • Recorded the second project demo on 7/17. Attended by Dev Rel and AMP team representatives.
        • Team
          • Almas and Andre are both fully ramped and contributing merged work.
      • What's the focus over the next two weeks?
        • Merge non-equijoin ON conditions and bulk UPDATE SET expressions (in review)
        • Complete index/unique constraint support and @Table.schema
        • GROUP BY, HAVING, and aggregate functions
      • Any risks/blockers/impediments?
        • No blockers. GROUP BY / HAVING / aggregate support is the remaining critical path — it is now in progress and cannot be parallelized, so it effectively gates the epic end date. The forecast remains ahead of the .local NYC target even with the expanded scope.

      2026-07-03 - 🟢 On Track

      • What was accomplished since the last update?
        • Features Merged
          • Spring Boot auto-configuration module
          • Path expressions for fields nested in sub-documents (@Struct embeddables)
          • Native query support with parameter markers
          • Exception when an id column is explicitly named something other than _id
        • Features in Review
          • Optimistic locking support
          • HQL pattern matching
          • HQL in / not in
          • Required property for null semantics (MQL as the only supported value initially)
        • Features in Progress
          • Basic entity class hierarchy persistence and retrieval
        • Team
          • Almas is ramped up on the project. Andre is ramping.
      • What's the focus over the next two weeks?
        • Merge optimistic locking, HQL pattern matching, HQL in / not in, and the null-semantics property (all in review)
        • Complete entity class hierarchy persistence and retrieval
        • Re-plan the epic on Monday, incorporating feedback from the last demo; scope may be adjusted and additional tickets pulled in
      • Any risks/blockers/impediments?
        • No blockers. The target-date forecast continues to run ahead of the planned end date, leaving room to absorb additional scope from the re-planning.

      2026-06-19 - 🟢 On Track

      • What was accomplished since the last update?
        • Features Merged
          • $elemMatch translation for EXISTS-over-collection subqueries
          • Null/missing-field comparisons, including is null / is not null
          • Auto-inference of dialect and connection provider from the MongoDB JDBC URL, plus short names for MongoDialect/MongoConnectionProvider
          • Upgrade to Hibernate ORM 7.4
        • Features in Review
          • Path expressions for fields nested in sub-documents (@Struct embeddables)
          • Spring Boot auto-configuration module
          • Native query support with parameter markers
        • Features in Progress
          • Optimistic locking support
          • HQL pattern matching 
        • Team
          • Almas is onboarded and ramping up on the project.
          • Andre started on June 15 and will begin ramping next week.
      • What's the focus over the next two weeks?
        • Merge the Spring Boot auto-configuration module
        • Merge native query support with parameter markers (currently in review)
        • Merge nested sub-document field path expressions (currently in review)
        • Merge optimistic locking support
      • Any risks/blockers/impediments?
        • No blockers. The current target-date forecast rests on ~3 weeks of measured velocity from a small team and should firm up as the team ramps. The forecast is currently ahead
            of the planned end date.

      2026-06-05 - 🟢 On Track

      • What was accomplished since the last update?
        • Agreed on features required for GA, prioritized and story pointed the tickets, determined engineering capacity, and arrived at an initial target end date based on ~5 story points per engineering week.
        • Notably, we have excluded ternary logic support for GA, instead opting for a required configuration parameter that forces applications to choose MQL mode.  SQL mode (ternary) is deferred to the next release.
        • Features Merged
          • Upgrade from Hibernate 6.6 to Hibernate 7.3, a necessary precursor to support for $elemMatch translations
          • Inner and Left Outer Join support
        • Features in Review
          • $elemMatch translations
        • Features in Progress
          • Improved Spring Data/Boot Integration
      • What's the focus over the next two weeks?
        • Onboard Almas to the project
        • Merge above features that are in progress and review
        • Support comparisons against null
        • Support references to fields nested in sub-documents
      • Any risks/blockers/impediments?
        • None
      Show
      2026-08-28 - 🟢 On Track What was accomplished since the last update? Features Merged GROUP BY and HAVING over column references Composite primary keys via @EmbeddedId, mapped to an _id sub-document Value unwrapping for @Struct fields and HQL literals (groundwork for temporal types) Release Pipeline Hardening (SSDLC) CodeQL analysis of release refs, with the security configuration under our ownership CodeQL SARIF and the SSDLC compliance report published as release assets Reporting of authorized release-artifact publication to papertrail Release workflow checkout action pinned by commit SHA Features in Review HQL datetime functions GROUP BY and HAVING over expressions Exclude _id from $project when unspecified Features in Progress Instant-like temporal types Sequence-style identifier generation for @GeneratedValue What's the focus over the next two weeks? Merge HQL datetime functions and GROUP BY/HAVING over expressions (in review) Complete aggregate functions in SELECT and HAVING, closing out GROUP BY support Complete temporal types and sequence-style identifier generation Begin composite key joins (@IdClass / @EmbeddedId) and DISTINCT support Any risks/blockers/impediments? GROUP BY support is de-risked: column references have merged, GROUP BY/HAVING over expressions is in review, and aggregate functions are next. It is no longer a single-owner bottleneck. SSDLC release hardening, a policy prerequisite for GA, is now complete and is no longer an open release risk. Scope continued to expand this cycle (temporal types and sequence-style identifier generation). Completed work was offset by the added scope, so the forecast held roughly flat against the date rather than pulling in. No hard blockers. The forecast (P70 9/15) remains ahead of the .local NYC target. 2026-08-14 - 🟢 On Track What was accomplished since the last update? Features Merged Index and unique constraint support HQL row-value (tuple) predicates HQL string functions HQL CASE expression Upsert and bulk upsert via StatelessSession Features in Review Composite primary keys via @EmbeddedId, mapped to an _id sub-document GROUP BY and HAVING over column references Features in Progress HQL datetime functions Value unwrapping for @Struct fields and HQL literals (groundwork for temporal types) Scope Continued to expand GA scope with additional high-priority features, including HQL CASE expressions, upsert, and datetime function/arithmetic support. Target release remains anchored to .local NYC. What's the focus over the next two weeks? Merge composite primary keys (@EmbeddedId) and GROUP BY/HAVING column references (in review) Complete the remaining GROUP BY pieces: aggregate functions (accumulators) and GROUP BY/HAVING over expressions Complete HQL datetime functions and arithmetic Begin composite key joins (@IdClass / @EmbeddedId) and DISTINCT support Any risks/blockers/impediments? GROUP BY support has been split into independently deliverable pieces — GROUP BY/HAVING over column references (in review), aggregate functions (accumulators), and GROUP BY/HAVING over expressions. Almas took the column-references piece through review; the remaining pieces will be picked up next week. This is the last major area still open. No hard blockers. The forecast (P70 9/01) remains ahead of the .local NYC target. 2026-07-31 - 🟢 On Track What was accomplished since the last update? Features Merged Expressions in HQL bulk UPDATE SET clause @Table.schema support Non-equijoin ON conditions Compound equijoin ON conditions (composite primary keys) Features in Review Index and unique constraint support HQL string concatenation HQL row-value (tuple) predicates Features in Progress GROUP BY, HAVING, and aggregate functions HQL datetime functions and arithmetic expressions What's the focus over the next two weeks? Merge index/unique constraint support, string concatenation, and row-value tuple predicates (in review) Complete GROUP BY, HAVING, and aggregate functions Complete HQL datetime functions and arithmetic expressions Begin composite key joins (@IdClass / @EmbeddedId) and DISTINCT support Any risks/blockers/impediments? GROUP BY / HAVING / aggregate support (13 pts) remains the critical path. Its owner will be out for ~3 weeks, so it is being reassigned to keep it moving during his absence. Slava will be unavailable for at least the next three weeks (two weeks vacation, one week backpressure from other work), reducing near-term capacity and review throughput. Security (SECBUG) tickets from Mythos may reduce velocity over the next two weeks. No hard blockers. The forecast (P70 8/21) remains ahead of the .local NYC target. 2026-07-17 - 🟢 On Track What was accomplished since the last update? Features Merged HQL pattern matching HQL in / not in HQL BETWEEN predicate Expressions in SELECT and WHERE clauses Optimistic locking support Basic entity class hierarchy persistence and retrieval (single table and mapped superclass) Required property for null semantics (MQL as the only supported value initially) Prohibit org.bson.types, BSON document types, and UUID as domain types Forbid the @JdbcTypeCode annotation Clearer error message when startup connection fails Automatic release publishing, including pre-releases Features in Review Non-equijoin ON conditions Expressions in HQL bulk UPDATE SET clause Features in Progress Index and unique constraint support @Table.schema support GROUP BY, HAVING, and aggregate functions Scope Delivery is running well ahead of the initial estimate. With the target release still anchored to .local NYC, we have significantly expanded the GA scope to include additional high-priority features rather than pulling the date in. Demo Recorded the second project demo on 7/17. Attended by Dev Rel and AMP team representatives. Team Almas and Andre are both fully ramped and contributing merged work. What's the focus over the next two weeks? Merge non-equijoin ON conditions and bulk UPDATE SET expressions (in review) Complete index/unique constraint support and @Table.schema GROUP BY, HAVING, and aggregate functions Any risks/blockers/impediments? No blockers. GROUP BY / HAVING / aggregate support is the remaining critical path — it is now in progress and cannot be parallelized, so it effectively gates the epic end date. The forecast remains ahead of the .local NYC target even with the expanded scope. 2026-07-03 - 🟢 On Track What was accomplished since the last update? Features Merged Spring Boot auto-configuration module Path expressions for fields nested in sub-documents (@Struct embeddables) Native query support with parameter markers Exception when an id column is explicitly named something other than _id Features in Review Optimistic locking support HQL pattern matching HQL in / not in Required property for null semantics (MQL as the only supported value initially) Features in Progress Basic entity class hierarchy persistence and retrieval Team Almas is ramped up on the project. Andre is ramping. What's the focus over the next two weeks? Merge optimistic locking, HQL pattern matching, HQL in / not in, and the null-semantics property (all in review) Complete entity class hierarchy persistence and retrieval Re-plan the epic on Monday, incorporating feedback from the last demo; scope may be adjusted and additional tickets pulled in Any risks/blockers/impediments? No blockers. The target-date forecast continues to run ahead of the planned end date, leaving room to absorb additional scope from the re-planning. 2026-06-19 - 🟢 On Track What was accomplished since the last update? Features Merged $elemMatch translation for EXISTS-over-collection subqueries Null/missing-field comparisons, including is null / is not null Auto-inference of dialect and connection provider from the MongoDB JDBC URL, plus short names for MongoDialect/MongoConnectionProvider Upgrade to Hibernate ORM 7.4 Features in Review Path expressions for fields nested in sub-documents (@Struct embeddables) Spring Boot auto-configuration module Native query support with parameter markers Features in Progress Optimistic locking support HQL pattern matching  Team Almas is onboarded and ramping up on the project. Andre started on June 15 and will begin ramping next week. What's the focus over the next two weeks? Merge the Spring Boot auto-configuration module Merge native query support with parameter markers (currently in review) Merge nested sub-document field path expressions (currently in review) Merge optimistic locking support Any risks/blockers/impediments? No blockers. The current target-date forecast rests on ~3 weeks of measured velocity from a small team and should firm up as the team ramps. The forecast is currently ahead   of the planned end date. 2026-06-05 - 🟢 On Track What was accomplished since the last update? Agreed on features required for GA, prioritized and story pointed the tickets, determined engineering capacity, and arrived at an initial target end date based on ~5 story points per engineering week. Notably, we have excluded ternary logic support for GA, instead opting for a required configuration parameter that forces applications to choose MQL mode.  SQL mode (ternary) is deferred to the next release. Features Merged Upgrade from Hibernate 6.6 to Hibernate 7.3, a necessary precursor to support for $elemMatch translations Inner and Left Outer Join support Features in Review $elemMatch translations Features in Progress Improved Spring Data/Boot Integration What's the focus over the next two weeks? Onboard Almas to the project Merge above features that are in progress and review Support comparisons against null Support references to fields nested in sub-documents Any risks/blockers/impediments? None
    • None
    • Green
    • Hide
      * 08/11/2026 - GroupBy is the main feature dependent on 1 Engineer who is out until this week. Team is so far confident and progressing on other features not dependent on GroupBy. No change in launch condifence.
      * 07/20/2026 - High confidence to hit GA date after reprioritization activities. Code freeze date set as September 17th. Some additional features like composite primary keys/composite key joins, DISTINCT operator etc will be added without compromising on the target date. Internal package aimed to be made available to let the AMP team test.
      * 07/06/2026 - On track as of now. We are having discussions with the AMP team on some requests that may be beneficial for GA. We will be considering these based on effort estimates and running a reprioritization on our current set of features.
      * 06/18/2026 - Updating GA target date to 09/30/2026 to align with .local NYC. Current P90 estimate is 08/18.
      * 06/11/2026 - Hibernate ORM is back in active development with support by Jeff Yemin (Eng DRI). Estimation release date by mid October.
      * 03/23/2026 - Pushed back release date due to design changes in Backpressure adding ~2 months of additional work.
      Show
      * 08/11/2026 - GroupBy is the main feature dependent on 1 Engineer who is out until this week. Team is so far confident and progressing on other features not dependent on GroupBy. No change in launch condifence. * 07/20/2026 - High confidence to hit GA date after reprioritization activities. Code freeze date set as September 17th. Some additional features like composite primary keys/composite key joins, DISTINCT operator etc will be added without compromising on the target date. Internal package aimed to be made available to let the AMP team test. * 07/06/2026 - On track as of now. We are having discussions with the AMP team on some requests that may be beneficial for GA. We will be considering these based on effort estimates and running a reprioritization on our current set of features. * 06/18/2026 - Updating GA target date to 09/30/2026 to align with .local NYC. Current P90 estimate is 08/18. * 06/11/2026 - Hibernate ORM is back in active development with support by Jeff Yemin (Eng DRI). Estimation release date by mid October. * 03/23/2026 - Pushed back release date due to design changes in Backpressure adding ~2 months of additional work.
    • None
    • None
    • None

      This epic tracks the major feature areas, investigations, and enhancements required to deliver the MongoDB Extension for Hibernate ORM at General Availability (GA). The focus is on ensuring core functionality, migration ease, and a strong developer onboarding experience

      Product Roadmap 

      Estimation Worksheet

            Assignee:
            Jeffrey Yemin
            Reporter:
            Maxim Katcharov
            None
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              16 weeks, 4 days
              None