Oliverwqcwrw opened a new issue, #239:
URL: https://github.com/apache/rocketmq-connect/issues/239

   **BUG REPORT**
   
   1. Please describe the issue you observed:
   
   - What did you do (The steps to reproduce)?
   
   as below:
   
   > 
            Main Class配置
         org.apache.rocketmq.connect.runtime.StandaloneConnectStartup
         
         
         Program arguments配置
         
         -c  ${user 
path}/rocketmq-connect/distribution/conf/connect-standalone.conf
         
         Environment variables配置
         
         CONNECT_HOME=${user path}/rocketmq-connect/distribution
   
   - What is expected to see?
   
   > 
        Main Class配置
         org.apache.rocketmq.connect.runtime.DistributedConnectStartup
         
         
         Program arguments配置
         
         -c  ${user 
path}/rocketmq-connect/distribution/conf/connect-distributed.conf
         
         Environment variables配置
         
         CONNECT_HOME=${user path}/rocketmq-connect/distribution
   
   - What did you see instead?
   
   2. Please tell us about your environment:
   
   3. Other information (e.g. detailed explanation, logs, related issues, 
suggestions on how to fix, etc):
   
   **FEATURE REQUEST**
   
   1. Please describe the feature you are requesting.
   
   2. Provide any additional detail on your proposed use case for this feature.
   
   2. Indicate the importance of this issue to you (blocker, must-have, 
should-have, nice-to-have). Are you currently using any workarounds to address 
this issue?
   
   4. If there are some sub-tasks involved, use -[] for each sub-task and 
create a corresponding issue to map to the sub-task:
   
   - [sub-task1-issue-number](example_sub_issue1_link_here): sub-task1 
description here, 
   - [sub-task2-issue-number](example_sub_issue2_link_here): sub-task2 
description here,
   - ...
   


-- 
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]

Reply via email to