Comments (2)
Immutable copies are really difficult in java as it does not have proper const correctness. A solution would be use cglib type immutable proxies for the data being input in dataset. This would cause potentially serious performance penalties to block against wrong usage and generate a Runtime exception. (It is wrong modelling to modify some data in dataset, a builder should copy and generate new objects, not modify them). Will think about this, but i do not think there is a very clean solution out there.
from databuilderframework.
Also your data classes should only have final attributes. That way, there is no risk of mutations by others. Serialization and Deserialization of such classes now work fine with jackson either with @JsonProperty annotation in constructor or by using the parameter names module for jackson. This is the only scalable and performant solution to this problem.
from databuilderframework.
Related Issues (19)
- Readme.md sample image
- EnhancementRequest - ReactiveExecutor HOT 4
- ProcessedBuilders check removal HOT 1
- DataBuilderClassInfo - customize Builder Name HOT 5
- Builder whose data is not consumed is left out of execution graph ( Because of bottom up building of graph) HOT 1
- Builder whose data is not consumed in is left out of execution graph ( Because of bottom up building of graph) HOT 3
- Making accesses mandatory for running a builder defeats purpose of statefulness of a builder HOT 3
- Making accesses mandatory for running a builder defeats purpose of statefulness of a builder HOT 1
- Accessible datas HOT 1
- Null returned from data builder is not nullifying the previous generated data.
- DataDelta content is getting changed if builder is producing the same data that is present in dataDelta. HOT 2
- Guice support HOT 1
- Proper way to access dataSet from DataBuilderContext HOT 3
- DataFlowExecutor's databuilderFactory is not used
- ConcurrentModificationExceptions when using Optimised Multithread Executors
- Builders of the same rank terminate when first one does not run HOT 3
- DataBuilderContext not accessible in DataBuilderExecutionListener
- MultiThreadedExecutor runs executor even when there is one builder in the respective rank. HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from databuilderframework.