srowen commented on pull request #31461: URL: https://github.com/apache/spark/pull/31461#issuecomment-773360047
It does sound like ideally the API would be refactored. @viirya I didn't see pushback on your redesign. We can just open this up, which at least re-enables the current 'hacky' but working path for third-party UDFs. The only downside is it exposes an API which _should_ change. If that refactoring is controversial (is it even?), there's an argument to open it up and caveat it: it may well change again. I expect third parties are expecting that (see above), and, if we refactor now it will already break the current unsupported integrations in Java 8 too. My motive is that geospatial use cases are relatively important, so want there to be at least any working path right now. To that end I'd still support opening this (this PR), but, still not sure we can't merge @viirya 's change as well? even also for 3.2? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
