This is a grouping of related issues. Feel free to vote (👍) for this issue to indicate that this is an area that you think we should spend time on, but consider also voting for individual issues for things you consider especially important.
EF9
The following work is a roughly prioritized list of work tentatively planned for the EF9 release. More details of the full scope of Cosmos work over several releases can be found in All work section below.
Important: This plan is not a commitment; it will evolve as we continue to learn throughout the release. Some things not currently planned for EF9 may get pulled in. Some things currently planned for EF9 may get punted out.
The general approach for Cosmos in EF9 is:
- Necessary infrastructure/test work
- Bring the query pipeline up-to-date with relational
- As much as possible in parallel, implement high-value enhancements
- Bring complex types support close to relational level
- Small config items, like RBAC
- High-value smaller query items
- Depending on how this work goes, stretch goals are:
- Better use of partition keys (Will do if query is in good shape in time.)
- Partial updates and CUD batching
Completed
General improvements
Query fundamentals
Function translations
ReadItem and partition key management
Infra/internal work
Planned
No more planned work for 9 at this time.
Punted
Stretch
T-shirt sizes are:
- Small: Days or less
- Medium: Days to a couple of weeks
- Large: Several weeks
- X-Large: Many weeks
All work
These are areas either fundamental to the underlying architecture and implementation, and/or fundamental user experiences that users expect, on one side, from any EF Core provider, and on the other side by any mechanism used to access Cosmos. For example, SelectMany is a fundamental query pattern that should work on any EF Core provider. Similarly, partition keys are fundamental to working with Cosmos, and hence EF must expose/provide this functionality.
Query fundamentals
At the time of writing (beginning of EF9 work), the Cosmos query pipeline code has fallen behind the relational code by a considerable about. The architecture now employed by relational providers must be ported to Cosmos before any other major changes are made to the query pipeline.
Following this, some fundamental improvements are needed to the query pipeline. Many of these areas have model building, change tracking, update pipeline aspects as well, but they involve a lot of query work.
--- EF9 cut line ---
Non-query fundamentals
Many of these areas have query aspects, but much of the work can be done independently of query.
--- EF9 cut line ---
Higher-level experiences
--- EF9 cut line ---
Other work
Query enhancements
--- EF9 cut line ---
Query optimizations
--- EF9 cut line ---
Bugs
--- EF9 cut line ---
Nice-to-have
--- EF9 cut line ---
Testing and internal quality
--- EF9 cut line ---
Currently blocked/infeasible
--- EF9 cut line ---
This is a grouping of related issues. Feel free to vote (👍) for this issue to indicate that this is an area that you think we should spend time on, but consider also voting for individual issues for things you consider especially important.
EF9
The following work is a roughly prioritized list of work tentatively planned for the EF9 release. More details of the full scope of Cosmos work over several releases can be found in All work section below.
The general approach for Cosmos in EF9 is:
Completed
General improvements
WithPartionKeyshould be model values, not store values #33535Idto JSONidunless explicitly configured otherwise #34179Query fundamentals
Function translations
ReadItem and partition key management
Infra/internal work
Planned
No more planned work for 9 at this time.
Punted
Stretch
T-shirt sizes are:
All work
These are areas either fundamental to the underlying architecture and implementation, and/or fundamental user experiences that users expect, on one side, from any EF Core provider, and on the other side by any mechanism used to access Cosmos. For example,
SelectManyis a fundamental query pattern that should work on any EF Core provider. Similarly, partition keys are fundamental to working with Cosmos, and hence EF must expose/provide this functionality.Query fundamentals
At the time of writing (beginning of EF9 work), the Cosmos query pipeline code has fallen behind the relational code by a considerable about. The architecture now employed by relational providers must be ported to Cosmos before any other major changes are made to the query pipeline.
Following this, some fundamental improvements are needed to the query pipeline. Many of these areas have model building, change tracking, update pipeline aspects as well, but they involve a lot of query work.
--- EF9 cut line ---
Non-query fundamentals
Many of these areas have query aspects, but much of the work can be done independently of query.
--- EF9 cut line ---
Higher-level experiences
--- EF9 cut line ---
Other work
Query enhancements
--- EF9 cut line ---
Query optimizations
--- EF9 cut line ---
Bugs
--- EF9 cut line ---
Nice-to-have
--- EF9 cut line ---
Testing and internal quality
--- EF9 cut line ---
Currently blocked/infeasible
--- EF9 cut line ---