Hi Infra,

Every message from gitbox to notifications@shardingsphere is sent individually 
and clogs my in-box.

I'm wondering if there is some configuration that we can use to automatically 
thread messages.

In this case, how can we change the github/gitbox notifications to 

Subject: issue #3121: can't use HintManager.getInstance().setMasterRouteOnly()

The notification would apply to all references to this issue: create, modify, 
comment, change of status, close. The subject could allow my mail reader to 
thread all the messages on the subject issue. As it is, this issue has created 
three individual messages sent to [email protected] and 
one thread that contains three replies, sent to 
[email protected]

I'm hoping that there is a technical solution to allow all of these messages to 
be aggregated into one thread.

Thanks,

Craig

> Begin forwarded message:
> 
> From: GitBox <[email protected]>
> Subject: [GitHub] [incubator-shardingsphere] maxiaoxian opened a new issue 
> #3121: can't use HintManager.getInstance().setMasterRouteOnly()
> Date: September 26, 2019 at 1:41:06 AM PDT
> To: [email protected]
> Reply-To: [email protected]
> 
> maxiaoxian opened a new issue #3121: can't use 
> HintManager.getInstance().setMasterRouteOnly()
> URL: https://github.com/apache/incubator-shardingsphere/issues/3121
> 
> 
>   ## Bug Report
> 
>   **For English only**, other languages will not accept.
> 
>   Before report a bug, make sure you have:
> 
>   - Searched open and closed [GitHub 
> issues](https://github.com/apache/incubator-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 **more than 7 days** and we cannot reproduce it on current 
> information, we will **close it**.
> 
>   Please answer these questions before submitting your issue. Thanks!
> 
>   ### Which version of ShardingSphere did you use?
>           4.0.0-RC2
>   ### Which project did you use? Sharding-JDBC or Sharding-Proxy?
>           Sharding-JDBC
>   ### Expected behavior
>          route to master
>   ### Actual behavior
>         throw a exception : HintManagerHolder has previous value, please 
> clear first. 
>   ### Reason analyze (If you can)
> 
>   ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule 
> configuration, when exception occur etc.
> 
>   // 读写分离配置
>           MasterSlaveRuleConfiguration masterSlaveRuleConfig =
>                   new MasterSlaveRuleConfiguration("ds", "fcWriteDataSource", 
> Arrays.asList("fcRead1DataSource", "fcRead2DataSource"));
> 
>           Set<MasterSlaveRuleConfiguration> masterSlaveRuleConfigurationSet = 
> new HashSet<>();
>           masterSlaveRuleConfigurationSet.add(masterSlaveRuleConfig);
> 
>           ShardingRuleConfiguration shardingRuleConfig = new 
> ShardingRuleConfiguration();
>           
> shardingRuleConfig.setMasterSlaveRuleConfigs(masterSlaveRuleConfigurationSet);
>           ...
> 
>   ### Example codes for reproduce this issue (such as a github link).
> 
> 
> ----------------------------------------------------------------
> 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.
> 
> For queries about this service, please contact Infrastructure at:
> [email protected]
> 
> 
> With regards,
> Apache Git Services

Craig L Russell
[email protected]

Reply via email to