Enhanced statistics, added hana driver, added query element based commit scope#7
Enhanced statistics, added hana driver, added query element based commit scope#7bhuesemann wants to merge 6 commits intoscriptella:masterfrom
Conversation
- filtered statements count (by if expression) - nested execution statements count (count output rows of a query) - processing start time for query and scripting elements (e.g. to measure the time a long running query execution runs before delivering the first row to scriptella - configurable query element based commit for batched connections (e.g. to set explicite commit after query element execution has ended to flush containing (eventually batched) scripting elements. Thus following non-batched connection can read the committed result.
There was a problem hiding this comment.
Make it boolean. Update getter and setter
|
Thank you for your contribution! I apologize for the very late response. Unfortunately I have no time to work on Scriptella these days :( Are you still interested in merging these changes? If so, I would like the above comments to be addressed. Also, the fact that unit tests are failing is quite concerning: |
|
Many thanks for taking the time to look through my changes. Yes, I'll address your comments and will try to fix all points. Unfortunately it may take some time as I'm currently quite busy, too. But I'm really impressed by the crisp and clear design of the framework. I've successfully used it for a fully automated cross database replication framework that is selfgenerating the templates all 100% in scriptella logic. Next I'll add delta loading and bitemporal historisation and everything looks quite declarative and easy to maintain. I've also added a simple parallel execution scriptella driver (based on a NotifyingBlockingThreadPoolExecutor) that I may contribute at a later time. I know some of the existing ETL Tools (eg. Informatica) very well and Scriptella is not the silverbullet to replace those. But I see its value for the generation of standard ETL processes. I even began to POC it as a automated data comparision/testing framework but have no time to finish. |
3 participants
ToDo: complete regression testing because I've not configured the regression test automation tool yet