[ 
https://issues.apache.org/jira/browse/BEAM-14048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Elizaveta Lomteva updated BEAM-14048:
-------------------------------------
    Description: 
h3. Context:

CDAP plugins use their configuration classes (ex. {{{}SalesforceSinkConfig{}}}) 
to set the required parameters to prepare and run a pipeline in Source or Sink 
classes (ex. {{{}SalesforceBatchSink{}}}). The config instance is accepted as a 
Source/Sink constructor argument.

The configuration classes are usually placed in the {{{}cdap/plugin/\{<plugin 
name>}/plugin/\{sink|source}/{batch|streaming{}}}} folder (ex. [Salesforce 
repo|https://github.com/data-integrations/salesforce/tree/d0d83fd82bbdbbb7ef07168f3b1698eebdc90c3e/src/main/java/io/cdap/plugin/salesforce/plugin]).
h3. Task Description:

Required to design wrapper class(es) for the CDAP plugin config class so that 
the CDAP plugin config instance can be created in the Apache Beam connector 
based on user input and used when creating CDAP Source or Sink.
h3. Acceptance criteria:

Design and source code of CDAP Config wrapper that will
 # accept custom parameters as constructor arguments (JSON/string or something 
else)

 # return an instance of plugins configuration class (ex. 
{{{}SalesforceSinkConfig{}}})

  was:
h3. Context:

CDAP plugins use their configuration classes (ex. {{{}SalesforceSinkConfig{}}}) 
to set the required parameters to prepare and run a pipeline in Source or Sink 
classes (ex. {{{}SalesforceBatchSink{}}}). The config instance is accepted as a 
Source/Sink constructor argument.

The configuration classes are usually placed in the {{cdap/plugin/\{<plugin 
name>}/plugin/\{sink|source}/\{batch|streaming}}} folder (ex.[ Salesforce 
repo|https://github.com/data-integrations/salesforce/tree/d0d83fd82bbdbbb7ef07168f3b1698eebdc90c3e/src/main/java/io/cdap/plugin/salesforce/plugin]).
h3. Task Description:

Required to design wrapper class(es) for the CDAP plugin config class so that 
the CDAP plugin config instance can be created in the Apache Beam connector 
based on user input and used when creating CDAP Source or Sink.
h3. Acceptance criteria:

Design and source code of CDAP Config wrapper that will
 # accept custom parameters as constructor arguments (JSON/string or something 
else)

 # return an instance of plugins configuration class (ex. 
{{{}SalesforceSinkConfig{}}})


> [CDAP] Design and implement ConfigWrapper for building CDAP PluginConfigs
> -------------------------------------------------------------------------
>
>                 Key: BEAM-14048
>                 URL: https://issues.apache.org/jira/browse/BEAM-14048
>             Project: Beam
>          Issue Type: Task
>          Components: io-java-cdap
>            Reporter: Elizaveta Lomteva
>            Assignee: Vitaly Terentyev
>            Priority: P2
>              Labels: cdap-io-sprint-1
>
> h3. Context:
> CDAP plugins use their configuration classes (ex. 
> {{{}SalesforceSinkConfig{}}}) to set the required parameters to prepare and 
> run a pipeline in Source or Sink classes (ex. {{{}SalesforceBatchSink{}}}). 
> The config instance is accepted as a Source/Sink constructor argument.
> The configuration classes are usually placed in the {{{}cdap/plugin/\{<plugin 
> name>}/plugin/\{sink|source}/{batch|streaming{}}}} folder (ex. [Salesforce 
> repo|https://github.com/data-integrations/salesforce/tree/d0d83fd82bbdbbb7ef07168f3b1698eebdc90c3e/src/main/java/io/cdap/plugin/salesforce/plugin]).
> h3. Task Description:
> Required to design wrapper class(es) for the CDAP plugin config class so that 
> the CDAP plugin config instance can be created in the Apache Beam connector 
> based on user input and used when creating CDAP Source or Sink.
> h3. Acceptance criteria:
> Design and source code of CDAP Config wrapper that will
>  # accept custom parameters as constructor arguments (JSON/string or 
> something else)
>  # return an instance of plugins configuration class (ex. 
> {{{}SalesforceSinkConfig{}}})



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to