shardingjdbc forced to go the route of the main database query data in real time to avoid delays from the master data synchronization

@Bean 
public shardingsphere.demo.entity.Order Order () { 
    shardingsphere.demo.entity.Order the Order Order new new = (); 
    order.setId (the Random new new (100) .nextLong ()); 
    order.setOrderId (101); 
    order.setUserId (. 6); 
    orderMapper.insert (Order); 

    order.setId (the Random new new (100) .nextLong ()); 
    order.setOrderId (102); 
    order.setUserId (. 5); 
    orderMapper.insert (Order); 


    HintManager.getInstance () setMasterRouteOnly ();. // ----------------------------------- core with pagehelper similar plug tab acting only on the nearest one query, 
    List <the Order> byUserId orderMapper.findByUserId = (. 5); 


    . HintManager.getInstance () setMasterRouteOnly (); 
    List <the Order> B2 = orderMapper.findByUserId (. 6);

    List<Long> longs=new ArrayList<>();
    longs.add(5L);
    longs.add(6L);

    HintManager.getInstance().setMasterRouteOnly();
    List<Order> bys = orderMapper.findBys(longs);

    Map map=new HashMap<>();
    map.put("min",5);
    map.put("max",6);
    //orderMapper.findByUserIdBetween(map);
    return order;
}