dobet opened a new issue, #30537:
URL: https://github.com/apache/shardingsphere/issues/30537

   ## Question
   
   **For English only**, other languages will not accept.
   
   Before asking a question, make sure you have:
   
   - Googled your question.
   - Searched open and closed [GitHub 
issues](https://github.com/apache/shardingsphere/issues).
   - Read documentation: [ShardingSphere 
Doc](https://shardingsphere.apache.org/document/current/en/overview).
   
   Please pay attention on issues you submitted, because we maybe need more 
details. 
   If no response anymore and we cannot reproduce it on current information, we 
will **close it**.
   
   
   Now, I have two mysql server mysql01 and mysql 02. And I have used sharding.
   
   mysql01 have A database sbtest. It has 10000000 row data.
   
   Now, I create a sharding rule between mysql01 and mysql02 that use hash_mod 
and sharding-count is 4.
   
   I want use migration data from mysql01.sbtest.sbtest1 to 
mysql01.sbtest.t_sbtest_0, mysql01.sbtest.t_sbtest_2, mysql02.sbtest.t_sbtest1, 
mysql02.sbtest.t_sbtest03.
   
   but get Error
   ```
   mysql> REGISTER MIGRATION SOURCE STORAGE UNIT ds_3 ( 
URL="jdbc:mysql://127.0.0.1:3310/sbtest", USER="root", PASSWORD="123456", 
PROPERTIES("minPoolSize"="1", "maxPoolSize"="20", "idleTimeout"="6000"));
   ERROR 30000 (HY000): Unknown exception: Cannot invoke 
"org.apache.shardingsphere.data.pipeline.common.context.PipelineContext.getContextManager()"
 because the return value of 
"org.apache.shardingsphere.data.pipeline.common.context.PipelineContextManager.getContext(org.apache.shardingsphere.data.pipeline.common.context.PipelineContextKey)"
 is null
   ```
   I don't not what can i do. 
   
   
   
   
   
   
   


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