<p dir="auto">For English only, other languages we will close it directly.</p>
<p dir="auto">Please answer these questions before submitting your issue. Thanks!</p>
<p dir="auto">Before submit a new issue, please check existed issue first, to make sure your issue is not a duplicated one.</p>
<h3 dir="auto">Which version of Sharding-Sphere do you using?</h3>
<p dir="auto">3.0.0M3</p>
<h3 dir="auto">Which project do you using? Sharding-JDBC or Sharding-Proxy?</h3>
<p dir="auto">Sharding-JDBC</p>
<h3 dir="auto">Expected behavior</h3>
<p dir="auto">there are two data sources ds-2017 and ds-2018 use year sharding database<br>
very data sources use month sharding tabale table1..12<br>
using create_date field in table sharding rule<br>
query 2017-08-01 to 2018-09-01 data</p>
<p dir="auto">Sharding-Sphere-SQL.log<br>
select * from ds-2017.table1..12 where create_date between ? and ?<br>
select * from ds-2018.table1..12 where create_date between ? and ?<br>
way not<br>
select * from ds-2017.table8..12 where create_date between ? and ?<br>
select * from ds-2018.table1..09 where create_date between ? and ?</p>
<p dir="auto">It's my sharding rule problem?</p>
<p dir="auto">if database sharding rule and table sharding rule can unified processing, use the same doBetweenSharding() method then can return the specified database corresponds to the specified table<br>
like ds-2017 contain table8..table12  ds-2018 contain table1..09<br>
Map&lt;String, List&gt; result = [{ds2017, [table8,table9....,table12]}, {ds2018, [table1.....,table9]}]</p>
<p dir="auto">please help answer this question thank you!</p>
<h3 dir="auto">Actual behavior</h3>
<h3 dir="auto">Reason analyze</h3>
<h3 dir="auto">Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc</h3>
<h3 dir="auto">For bug report, please <em>MUST</em> provide the reproduce example codes (such as a github link).</h3>
<h2 dir="auto">Bug Report</h2>
<p dir="auto"><strong>For English only</strong>, other languages will not accept.</p>
<p dir="auto">Before report a bug, make sure you have:</p>
<ul dir="auto">
<li>Searched open and closed <a href="https://github.com/apache/shardingsphere/issues">GitHub issues</a>.</li>
<li>Read documentation: <a href="https://shardingsphere.apache.org/document/current/en/overview" rel="nofollow">ShardingSphere Doc</a>.</li>
</ul>
<p dir="auto">Please pay attention on issues you submitted, because we maybe need more details.<br>
If no response anymore and we cannot reproduce it on current information, we will <strong>close it</strong>.</p>
<p dir="auto">Please answer these questions before submitting your issue. Thanks!</p>
<h3 dir="auto">Which version of ShardingSphere did you use?</h3>
<p dir="auto">master</p>
<h3 dir="auto">Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?</h3>
<p dir="auto">Proxy + Agent</p>
<h3 dir="auto">Expected behavior</h3>
<p dir="auto"><code class="notranslate">build_info</code>, <code class="notranslate">proxy_state</code>, <code class="notranslate">proxy_meta_data_info</code> are only exported once.</p>
<h3 dir="auto">Actual behavior</h3>
<p dir="auto"><code class="notranslate">build_info</code>, <code class="notranslate">proxy_state</code>, <code class="notranslate">proxy_meta_data_info</code> will be repeatedly exported.</p>
<p dir="auto"><a target="_blank" rel="noopener noreferrer nofollow" href="https://user-images.githubusercontent.com/16010265/215697339-8436f4c8-7074-4663-a774-c3497b33e0bf.png"><img src="https://user-images.githubusercontent.com/16010265/215697339-8436f4c8-7074-4663-a774-c3497b33e0bf.png" alt="image" style="max-width: 100%;"></a></p>
<h3 dir="auto">Reason analyze (If you can)</h3>
<h3 dir="auto">Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.</h3>
<h3 dir="auto">Example codes for reproduce this issue (such as a github link).</h3>