opensharding / opensharding-spi-impl Goto Github PK

we should add a distribution module to assembly spi jar using profile.

Current annotation ShardingTransactionType is implemented by spring-aop.
And depend part of hibernate when be used to change transaction type for shardind-proxy.
So it's necessary to refactor this part features to remove these dependence.

• remove spring-aop-boot-starter dependence
• separate jdbc and proxy transaction-spring
• remove hibernate dependence by spi

currently，we only support revert sql contains primary key generated by shardingsphere or existing in values. we can get database generateKey after physical statement have completed.

Replacing inheritance with combinations

currently, we integrated with saga using graph based engine.
it need us to collect all participated actual SQL, then submit to saga actuator in commit/rollback phase. if application crashed before invoking saga actuator, undo log of branch transaction SQL will not be saved, so recovery thread will not be executed correctly.

it's better that encapsulating every actual SQL as a saga task, then submit to saga actuator realtime instead of batch processing all the SQLs at commit/rollback phase. this architecture will make the boundary more clear between shardingsphre and saga, currently we have done some additional work for integrating saga.

• optimize code
• do refactor

Another compile error like issue #55.

1. I deployed the ss dependencies by following command in ss dev branch
   mvn clean install -Dmaven.test.skip -Prelease
2. I try to compile spi-impl by following command
   mvn clean install -Dmaven.test.skip -U
3. and I got some compiled errors:
   

After check ss git history, it seems that sharding-core-optimize module had renamed to sharding-core-preprocessor on 27 Sep:

BTW , the version of both project is 4.0.0-RC3-SNAPSHOT .

Class 'NativeZookeeperRegistryCenter' must either be declared abstract or implement abstract method 'initLock(String)' in 'RegistryCenter' in 4.0.0-RC2-SNAPSHOT version

• fix compile error
• do refactor

好多pom架包下载不下来，毫无头绪。。。。

before commit this issue, I understand there must be some stratagy to check compile or dependecis or something like that by travis . however , I do got confused by some compiled erorr, please give me a hand cherry @cherrylzhao

1. I deployed the ss dependencies by following command in ss dev branch

mvn clean install -Dmaven.test.skip -Prelease

2. I try to compile spi-impl by following command

mvn clean install -Dmaven.test.skip -U

3. and I got some compiled errors

for example , SQLRevertExecutorContext.java in spi-impl, one variable

the path for OptimizedStatement is org.apache.shardingsphere.core.optimize.statement.OptimizedStatement

but in ss , the packge path for OptimizedStatement is org.apache.shardingsphere.core.optimize.api.statement

BTW , the version of both project is 4.0.0-RC2-SNAPSHOT .

saga-actuator only provide a central recovery mechanism. recovery thread will be started independent on server side. but this could not work for sharding-sphere, physical datasource only kept on the application side. so we need make every application instance recovery independently. if one instance have crashed, it can be failover to another available instance.