Updates to the plan for EF Core 6.0

[ajcvickers]

In January we announced the plan for EF Core 6.0. Since then we have learned more and gathered more data from customers. These inputs have lead to some updates to the plan. This includes punting some smaller enhancements to the next release, as well as scoping of some the bigger items.

Scoped into 6.0:

The most notable changes scoped into EF Core 6.0 are:

• We have been doing extensive customer development around the Cosmos provider. This has resulted in the following enhancements being pulled into EF Core 6.0:
  • Azure Cosmos DB provider should default to implicit ownership
  • Find/FindAsync performs SQL API query when entity has embedded entities
  • Set partition key on join entity type by convention
  • Optimize more queries that could use ReadItem
  • Detect partition key filters in more queries
  • Translate subquery in filter condition
  • FromSql support
  • Allow to specify consistency level for CUD operations
  • Configure TTL per entity/entity type/collection
  • API to configure container facets (throughput, size, partition key, etc.)
  • Diagnostic events including statistics (query cost, activity id)
  • Support aggregate operators
  • Distinct operator in queries
  • Add translators for member/methods which map to built-in functions
  • Add basic support for collections and dictionaries of primitive types

The most notable changes scoped out of EF Core 6.0 are:

• We have improved test infrastructure and added new tests to support the work done for EF Core 6. Additional improvements in this area have been scoped out of the EF Core 6.0 release.
• Migrations bundles are still in the plan, but most of the other Migrations features have been cut due to resource constraints.
• Raw SQL queries for primitive and unmapped types has been cut from 6.0 due to resourcing constraints and priority adjustments.
• The following miscellaneous issues were cut from the 6.0 release due to resource constraints:
  • Complete full/free-text search on SQLite and SQL Server
  • SQL Server spatial indexes
  • Use the new batching API from ADO.NET

[ajcvickers]

Closing in favor of an update to the announcement post: #23870 (comment)