Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/12076#issuecomment-204503015
Grepping `sql/hive` for `kryo` turns up one explicit usage in HiveShim's
`HivefunctionWrapper` where it looks like we take an instance of `Kryo`
provided by Hive and use that instance to deserialize things:
https://github.com/apache/spark/blob/8ba2b7f28fee39c4839e5ea125bd25f5091a3a1e/sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveShim.scala#L171.
Assuming that we use a shaded Kryo in Hive, I think we could just import the
shaded Kryo here and use that import in our `[de]serializeObjectByKryo`
methods' signatures.
I don't spot any other Hive-specific uses of Kryo which look problematic,
so it seems plausible that we can shade without major problems. Am I
overlooking other uses of Kryo to exchange data between Spark and Hive
internals?
---
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]
