[ https://issues.apache.org/jira/browse/SPARK-7768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17270148#comment-17270148 ]
Simeon H.K. Fitch commented on SPARK-7768: ------------------------------------------ Not being familiar with the Spark issue triage and prioritization process, I'm wondering if there are other forums by which we might advocate for low level or extensibility features such as this. A chat session? A video meeting? Something else? Up to now RasterFrames and GeoMesa have been using backdoor techniques to work around the UDT restriction. However, this is no longer viable in modern (i.e. > 8) versions of the JVM with the new package/modules restrictions. Our users are eager for us to support > 8, but this ticket has left us in a bind as to how to serve them. I'd hate to see RasterFrames and GeoMesa (and others) die on the vine because we can no longer keep up with the JVM ecosystem. (Note: while I have been programming against the internals of Spark for over 4 years (c.f. RasterFrames), yet–likely due to my own fault–the feature advocacy process is still opaque to me. If there's another way, I'd appreciate some kind person pointing me in the right direction). > Make user-defined type (UDT) API public > --------------------------------------- > > Key: SPARK-7768 > URL: https://issues.apache.org/jira/browse/SPARK-7768 > Project: Spark > Issue Type: New Feature > Components: SQL > Reporter: Xiangrui Meng > Priority: Critical > > As the demand for UDTs increases beyond sparse/dense vectors in MLlib, it > would be nice to make the UDT API public in 1.5. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org