You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2019/09/26 08:41:06 UTC
[GitHub] [incubator-shardingsphere] maxiaoxian opened a new issue #3121:
can't use HintManager.getInstance().setMasterRouteOnly()
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:
users@infra.apache.org
With regards,
Apache Git Services
Re:Gitbox/github notifications are not threaded
Posted by Juan Pan <pa...@apache.org>.
Hi Craig,
It is really troublesome. I hope Infra can take some actions as well.
From my experiences, some Email clients, e.g, foxmail for mac, can aggregate emails into one thread by topic. Maybe you can have a try if you want. Currently, i am using a Chinese email client helping me do that.
In addition, creating rules to filter emails is a another solution, but not very practical i think. :)
Regard,
Trista
Juan Pan
panjuan@apache.org
Juan Pan(Trista), Apache ShardingSphere
On 09/26/2019 18:36，Craig Russell<ap...@gmail.com> wrote：
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 notifications@shardingsphere.apache.org and one thread that contains three replies, sent to incubator-shardingsphere@noreply.github.com
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 <gi...@apache.org>
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: notifications@shardingsphere.apache.org
Reply-To: dev@shardingsphere.apache.org
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:
users@infra.apache.org
With regards,
Apache Git Services
Craig L Russell
clr@apache.org
Gitbox/github notifications are not threaded
Posted by Craig Russell <ap...@gmail.com>.
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 notifications@shardingsphere.apache.org and one thread that contains three replies, sent to incubator-shardingsphere@noreply.github.com
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 <gi...@apache.org>
> 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: notifications@shardingsphere.apache.org
> Reply-To: dev@shardingsphere.apache.org
>
> 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:
> users@infra.apache.org
>
>
> With regards,
> Apache Git Services
Craig L Russell
clr@apache.org