You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rules:
sharding:
tables:
t_request_log:
#start date 20240910 - end date 20240910
actual-data-nodes: master.t_request_log_$->{(20241111..20301010).collect{t ->t.toString().padLeft(8,'0')}}_$->{1..10}
table-strategy:
complex:
sharding-columns: seed,create_time
sharding-algorithm-name: t_request_log_complex
sharding-algorithms:
t_request_log_complex:
type: CLASS_BASED
props:
strategy: COMPLEX
algorithmClassName: com.trusfort.xdid.config.LogComplexKeysShardingAlgorithm
According to the rules actual-data-nodes,the first table is' t_request_rog_20241111_1'. If this table does not exist, a null pointer exception will be reported when querying。
According to the rules actual-data-nodes,the first table is' t_request_rog_20241111_1'. If this table does not exist, a null pointer exception will be reported when querying。
This method will filter the logical table name t_request-log
Because the history table may be deleted, how should we handle it at this time?
The text was updated successfully, but these errors were encountered: