spring-projects / spring-projects/spring-data-jpa
Introduce Annotation Metadata parsing for AOT Repository generation
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 3.3k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Using an initialized EntityManagerFactory is convenient because it provides a wide range of information that we don't need to determine ourselves. Initializing Hibernate comes with the risk of configuration arrangements that we cannot satisfy or that require much more contextual components (e.g. Schema actions, initialization of beans) and therefore it makes sense to explore a mode of operation that can provide metamodel details without the need to initialize EntityManagerFactory.
Specifically, we need:
- Domain model mapping metadata
- Access to named queries
- Access to entity graphs
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the AOT repository-generation entry point and map how it currently obtains metadata from an initialized EntityManagerFactory. Compare the required domain model mappings, named queries, and entity graphs against the issue description; done means those details can be obtained through annotation metadata without initializing EntityManagerFactory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- backend, build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100