Github user a-roberts commented on the issue:
https://github.com/apache/spark/pull/14958
I'm almost done with adding in the test case anyway, involved a quick
rewrite to use Scala code, had fun rewriting the for loop for the test into a
while, I _think_ it would manifest itself if your very first byte happened to
be -126 and you're using Snappy.
At the very least I brushed up on my Scala skills and I think it's good
practice to add a test with an implementation change so I'll update the PR once
it's done. If Snappy were to change (e.g. 1.1.3 were to be released but the
magic header logic changes) we'd at least be another project that picks up the
problem.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
