[ 
https://issues.apache.org/jira/browse/BEAM-11838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17345753#comment-17345753
 ] 

Beam JIRA Bot commented on BEAM-11838:
--------------------------------------

This issue is assigned but has not received an update in 30 days so it has been 
labeled "stale-assigned". If you are still working on the issue, please give an 
update and remove the label. If you are no longer working on the issue, please 
unassign so someone else may work on it. In 7 days the issue will be 
automatically unassigned.

> An x-lang wrapper for DebeziumIO
> --------------------------------
>
>                 Key: BEAM-11838
>                 URL: https://issues.apache.org/jira/browse/BEAM-11838
>             Project: Beam
>          Issue Type: Bug
>          Components: cross-language, io-java-debezium
>            Reporter: Pablo Estrada
>            Assignee: Benjamin Gonzalez
>            Priority: P2
>              Labels: stale-assigned
>
> DebeziumIO outputs data in JSON format by default, so it's a perfect 
> candidate to be made available as a xlang transform.
> The DebeziumIO module provides a base to implement this, but for an 
> effective, easy-to-use connector in Python, we will need the following things:
>  * A new Java module that includes the per-database dependencies (Debezium's 
> MySQL, Postgres, DB2, Oracle connector dependencies). This is necessary so 
> that users can simply specify a database on the Python side, and the Java 
> side will automatically provide the dependency.
>  * A thorough review of the current default JSON output from DebeziumIO
>  * A set of parameters to be received by the Python wrapper. Maybe we'll use 
> the same format as the existing DebeziumIO (i.e. mandatory parameters: host, 
> user, password; and keyword parameters)
>  
> A short guide: 
> [https://beam.apache.org/documentation/programming-guide/#mulit-language-pipelines]
> An example of this kind of change: [https://github.com/apache/beam/pull/12145]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to