feat: Add GraphQL service for searching and filtering concepts #808
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR introduces a new GraphQL API endpoint to the OCL API, enabling efficient searching and filtering of concepts within sources. The implementation leverages Elasticsearch for fast text-based queries while providing a robust fallback to database searches.
Changes
• New Django App: Added core/graphql/ with complete GraphQL schema and resolvers
• GraphQL Schema: Implemented conceptsFromSource query supporting:
• Fetching concepts by specific IDs with optional pagination
• Text-based search with Elasticsearch integration
• Automatic fallback to database search when Elasticsearch is unavailable
• Version resolution for sources (HEAD or specific versions)
• Mapping relationships included in responses
• Dependencies: Added Strawberry GraphQL libraries (strawberry-graphql, strawberry-graphql-django)
• URL Integration: Added GraphQL endpoint at /graphql/ with GraphiQL interface enabled
• Testing: Comprehensive test suite covering pagination, search ordering, error handling, and fallback
scenarios
• Infrastructure: Updated Docker Compose configuration and added documentation
Technical Details
• Uses async resolvers for optimal performance
• Implements custom ordering based on Elasticsearch relevance scores
• Includes proper error handling and GraphQL validation
• Follows existing codebase patterns for source/version resolution and data serialization
• Maintains compatibility with existing REST API endpoints
Verification Steps