https://github.com/treeverse/lakeFS/issues/2810#issuecomment-999534511 has a reproduction of the content-length issue without loading any lakeFS libs into Spark. I know that yesterday we saw something else; perhaps some libraries are different inside your Spark cluster? @Daniel Satubi grateful if you could take a look; I give MD5s (and versions...) for the exact JARs for the reproduction, and would be happy for your sanity checking. Thanks!

Would you like to do it together later to verify it test it correctly?

Sorry, handling wet kids up until now.