[Feature Request]: GraphQL Input, Output, Update, Delete
- Dominant language
- Java
- Stars
- 1.5k
- Forks
- 476
- Avg merge
- 18h 33m
- Merged PRs (30d)
- 204
Description
### What would you like to happen?
Migration: https://issues.apache.org/jira/browse/HOP-2300
As a developer I'd like to have transforms that support GraphQL fully:
- Other services should be able send data to Hop's GraphQL interface. (Hop GraphQL Input)
- Hop can output data to a GraphQL interface (Hop GraphQL Output)
- Hop can update data points stored in another service via GraphQL (Hop GraphQL Update)
- Hop can delete data points stored in another service via GraphQL (Hop GraphQL Delete)
### Issue Priority
Priority: 3
### Issue Component
Component: Transforms
Contributor guide
Research direction
Start by reviewing the linked Apache JIRA migration HOP-2300 and the repository's Transforms component to understand the intended scope. The work is complete when GraphQL Input, Output, Update, and Delete transforms support the stated interactions with GraphQL services, with corresponding validation and tests identified during investigation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, java
- Domain
- api, data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100