[jira] [Updated] (STREAMPIPES-347) Add FieldRenamer JVM processor for multiple fields

["Dominik Riemer (Jira)" <ji...@apache.org>]

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

Dominik Riemer updated STREAMPIPES-347:
---------------------------------------
    Fix Version/s: post-1.0
                       (was: 0.90.0)

> Add FieldRenamer JVM processor for multiple fields
> --------------------------------------------------
>
>                 Key: STREAMPIPES-347
>                 URL: https://issues.apache.org/jira/browse/STREAMPIPES-347
>             Project: StreamPipes
>          Issue Type: New Feature
>          Components: Pipeline Elements
>            Reporter: Patrick Wiener
>            Priority: Major
>              Labels: newbie, suggestion-postpone
>             Fix For: post-1.0
>
>
> *Context*
> Rename multiple events field at once.
> {code:java}
> {
>   "time_stamp": 1234,
>   "sensor_id": "sensor1",
>   "sensor_measurement": 24.0
> }
> {code}
> rename "sensor_id" -> "id", "sensor_measurement", "measurement": new event
> {code:java}
> {
>   "time_stamp": 1234,
>   "id": "sensor1",
>   "measurement": 24.0
> }{code}
>  *Problem*
> Currently, we do have a FieldRenamer implemented using Flink wrapper, yet only allowing to rename one field at a time, i.e., renaming n fields requires a sequence of #n FieldRenamer processors. In addition, this option is unavailable when using lite version, i.e., standalone Java extensions.
> *Solution*
> Add FieldRenamer JVM processor using something like CollectionStaticProperty to allow arbitrary number of mappings, where a user can select a mapping property and add a new field name in a text field right next to it.
>  
> [EDIT]: There is a duplicate https://issues.apache.org/jira/browse/STREAMPIPES-338 
> While this allows to rename single fields, it still does not support multi field renaming in one step.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)