Sean Owen

Here's a more direct version of your test: ``` int numEcBytes = 8; for (int totalBlockSizeBytes = 9; totalBlockSizeBytes

Hm, not quite; the failure occurs at 256 elements, not 257. I suspect my answer is still roughly correct, but the subtlety of why it works only at 255 elements...

I doubt it, or at least, I don't think I can make the change myself. If there's a good PR that fixes it I'll review it.

There aren't likely to be major updates here, but I wouldn't say deprecated. I'm not aware of anyone actively working on it. Within Databricks, the recommended parameter tuning framework going...

0.19.2 should work OK; what are you seeing?

I'm starting to look through the open PRs to see if we can merge them or whether they're stale -- @thunterdb is this one too old to resurrect?

Sure, yeah, I'm sure this could use some clarification. Feel free to open a PR.

Was this resolved? I see the test was un-skipped in https://github.com/databricks/spark-sklearn/commit/7583ee16958c90b683829416cb626a045843ab7a

Currently, this can be worked around by shading JPMML in the same way in the client app: ``` org.apache.maven.plugins maven-shade-plugin 3.0.0 shade package shade your.group:* org.jpmml oryx.org.jpmml org.jpmml.** org.dmg oryx.org.dmg...

Any solution I can think of ends up requiring an API change for MLUpdate, which is, while not a formal API, something that people might want to extend. However, it's...