lm-ylj opened a new issue, #7884: URL: https://github.com/apache/seatunnel/issues/7884
### Search before asking - [X] I had searched in the [feature](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22Feature%22) and found no similar feature requirement. ### Description When I use Redis as a Sink, I encountered the following problems: 1.Redis keys cannot be customized. If a custom key is generated during the Transform phase, this additional field will be introduced in the value For example, the expected key to be written is pay:pay_channel:{order_no}, and the data for order_no comes from upstream 2.Currently, only the entire JSON data can be written, and it cannot support writing a specific field value or specifying a fixed value For example, the expected value to be written to Redis is {order_no}, rather than the entire JSON data ### Usage Scenario _No response_ ### Related issues _No response_ ### Are you willing to submit a PR? - [X] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
