[
https://issues.apache.org/jira/browse/FLINK-38245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
david radley updated FLINK-38245:
---------------------------------
Description:
Initial implementation of
[Flip-532|https://cwiki.apache.org/confluence/display/FLINK/FLIP-532%3A+Donate+GetInData+HTTP+Connector+to+Flink]
on a server side branch
Initial phase - get something out and working tasks
* find the documented process for this - legal requirements
* Add Apache 2 licenses to every file, java pom etc
* change connector name Flink connector http
* change java package names to follow the standard
* ensure tests succeed
* merge
Follow-on tasks
* split up the poms to have a sql one
* assess shading is in line with SQL non-sql way that are expected for Flink
connectors
* change the config to use Flink config parameter names and gid fallback keys
* move content of README to documentation folder
* review pom to ensure it have the same standard checking, licenses, format etc
* keep coverage checks if possible.
* Check github actions are inline with the other Flink connectors
* publish to Maven snapshot
Other tasks:
* new component in Jira / Github
* knit in the http connector into the Flink docs
* first release
Initial assumptions:
* changes go to main
* release at some stage later,
* v120 only currently
was:
Initial implementation of
[Flip-532|https://cwiki.apache.org/confluence/display/FLINK/FLIP-532%3A+Donate+GetInData+HTTP+Connector+to+Flink]
on a server side branch
tasks
find the documented process for this - legal requirements * Add Apache 2
licenses to every file, java pom etc
* change connector name Flink connector http
* change java package names to follow the standard
* split up the poms to have a sql one
* assess shading is in line with SQL non-sql way that are expected for Flink
connectors
* change the config to use Flink config parameter names and gid fallback keys
* move content of README to documentation folder
* review pom to ensure it have the same standard checking, licenses, format etc
* keep coverage checks if possible.
* publish to Maven snapshot
Check github actions are inline with the other Flink connectors
Follow on tasks
* new component in Jira / Github
* knit in the http connector into the Flink docs
* first release
Initial assumptions:
* changes go to main
* release at some stage later,
* v120 only currently
> FLIP-532: Donate GetInData HTTP Connector to Flink
> --------------------------------------------------
>
> Key: FLINK-38245
> URL: https://issues.apache.org/jira/browse/FLINK-38245
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Common
> Reporter: david radley
> Priority: Major
>
> Initial implementation of
> [Flip-532|https://cwiki.apache.org/confluence/display/FLINK/FLIP-532%3A+Donate+GetInData+HTTP+Connector+to+Flink]
> on a server side branch
> Initial phase - get something out and working tasks
> * find the documented process for this - legal requirements
> * Add Apache 2 licenses to every file, java pom etc
> * change connector name Flink connector http
> * change java package names to follow the standard
> * ensure tests succeed
> * merge
> Follow-on tasks
> * split up the poms to have a sql one
> * assess shading is in line with SQL non-sql way that are expected for Flink
> connectors
> * change the config to use Flink config parameter names and gid fallback keys
> * move content of README to documentation folder
> * review pom to ensure it have the same standard checking, licenses, format
> etc
> * keep coverage checks if possible.
> * Check github actions are inline with the other Flink connectors
> * publish to Maven snapshot
> Other tasks:
> * new component in Jira / Github
> * knit in the http connector into the Flink docs
> * first release
> Initial assumptions:
> * changes go to main
> * release at some stage later,
> * v120 only currently
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
