Issue 1:
As I know,when we execute update SQL without sharding-key ,Sharding-JDBC will update all the table . I think this is not safe for production environment. I want throw en exception when update without sharding-key, Sharding-JDBC can help me do it ?

Issue 2:
For English only, other languages we will close it directly.

Please answer these questions before submitting your issue. Thanks!

Before submit a new issue, please check existed issue first, to make sure your issue is not a duplicated one.

Which version of Sharding-Sphere do you using?

3.0.0.M3

Which project do you using? Sharding-JDBC or Sharding-Proxy?

Sharding-JDBC

Expected behavior

skywalking monitor the performance of sharding-sphere

Actual behavior

skywalking auto agent plugin couldn't collect data,so I read the source code of agent plugin,I found that the class name it hooked was sharding-jdbc 1.5.x version.Then I used the opentracing api to load skywalking agent.when I restarted the application,collector server console print many null point Exception like the folllow text, I'm wondering if the versions of skywalking and sharding-sphere aren't match,but I have tried many tests,so can you give me some advices of how to make the Skywalking work with sharding-sphere or a demo case for me . thanks very much

Sep 12, 2018 1:31:44 PM io.grpc.internal.SerializingExecutor run

SEVERE: Exception while executing runnable io.grpc.internal.ServerImpl$JumpToApplicationThreadServerStreamListener$1MessagesAvailable@5f8a026

java.lang.NullPointerException

at org.apache.skywalking.apm.collector.configuration.service.ComponentLibraryCatalogService.getComponentId(ComponentLibraryCatalogService.java:50)

at org.apache.skywalking.apm.collector.analysis.segment.parser.provider.parser.standardization.SpanIdExchanger.exchange(SpanIdExchanger.java:62)

at org.apache.skywalking.apm.collector.analysis.segment.parser.provider.parser.SegmentParse.preBuild(SegmentParse.java:116)

at org.apache.skywalking.apm.collector.analysis.segment.parser.provider.parser.SegmentParse.parse(SegmentParse.java:68)

at org.apache.skywalking.apm.collector.analysis.segment.parser.provider.service.SegmentParseService.parse(SegmentParseService.java:42)

at org.apache.skywalking.apm.collector.agent.grpc.provider.handler.TraceSegmentServiceHandler$1.onNext(TraceSegmentServiceHandler.java:48)

at org.apache.skywalking.apm.collector.agent.grpc.provider.handler.TraceSegmentServiceHandler$1.onNext(TraceSegmentServiceHandler.java:45)

at io.grpc.stub.ServerCalls$StreamingServerCallHandler$StreamingServerCallListener.onMessage(ServerCalls.java:248)

at io.grpc.internal.ServerCallImpl$ServerStreamListenerImpl.messagesAvailable(ServerCallImpl.java:252)

at io.grpc.internal.ServerImpl$JumpToApplicationThreadServerStreamListener$1MessagesAvailable.runInContext(ServerImpl.java:629)

at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)

at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

at java.lang.Thread.run(Thread.java:748)

Reason analyze

Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc

For bug report, please MUST provide the reproduce example codes (such as a github link).