good-134 commented on issue #32591:
URL: 
https://github.com/apache/shardingsphere/issues/32591#issuecomment-2296066427

   
   
![image](https://github.com/user-attachments/assets/532c1c96-1e2b-4995-a453-11d1e1b96d15)
   
   
![image](https://github.com/user-attachments/assets/a269b919-580d-4e94-bf11-beff669d4f06)
   
   
   I have debugged the variables availableTargetNames and actualTarget as you 
suggested.
   availableTargetNames contains the logical table name agreement.
   actualTarget contains a single physical table name agreement_2.
   From this, it seems that my custom sharding algorithm is correctly mapping 
the logical table to the appropriate physical table. However, my original 
question was about why my configuration works even though I didn't specify the 
physical table names explicitly in the actual-data-nodes property.
   Could it be that ShardingSphere relies on the sharding algorithm to resolve 
the physical table names from the logical table name, even when the 
actual-data-nodes doesn't explicitly list all the tables? Is this behavior 
expected?
   
   Thank you for your help.


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