[MCOL-1129] Initialization of the Java Swig library within the parent class loader on package import Created: 2017-12-21 Updated: 2023-10-26 Resolved: 2017-12-23 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | None |
| Affects Version/s: | 1.1.2 |
| Fix Version/s: | 1.1.3 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Jens Röwekamp (Inactive) | Assignee: | David Thompson (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | relnote | ||
| Environment: |
ALL |
||
| Sprint: | 2017-25 |
| Description |
|
The initialization of the Java Swig library in the main Java class instead of the package causes errors if multiple class loaders are used. i.e. in jupyter notebooks. Fixed by loading the library while importing, in java/javamcsapi.i |
| Comments |
| Comment by Jens Röwekamp (Inactive) [ 2017-12-21 ] |
|
Similar to bug as described in [1] and similar solution. Entry in the Swig documentation [2]. [1] http://www.scala-lang.org/old/node/1043.html |
| Comment by David Thompson (Inactive) [ 2017-12-23 ] |
|
A nice general benefit of this is it's cleaner code not making the client code load the native library, we'll need to release note this though it appears existing code that loads in client still works. |