Details
-
Bug
-
Status: Patch Available
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
Today we use a single class loader for both framework classes as well as user code (StreamTask implementations), which could result in conflicts of dependencies.
The approach is to use separate class loaders for framework classes and user instantiated classes. This approach has also been applied in Hadoop and Spark (MAPREDUCE-1700, SPARK-1870).
Attachments
Attachments
Issue Links
- duplicates
-
SAMZA-305 Isolate user library dependencies from framework dependencies
- Resolved