[
https://issues.apache.org/jira/browse/SPARK-18134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15682855#comment-15682855
]
Christian Zorneck commented on SPARK-18134:
-------------------------------------------
I also do not see why this feature was removed, besides the performance issue.
So, to remove this feature, it is some how a political decision, so that spark
can say it is always fast.
Before 1.5 this feature worked fine. In 1.5 it was only be deactivated. I think
it should be activated again, and the performance issue should be addressed as
performance improvements for the future instead.
And as I mentioned before, one of the feature spark advertises, is the
compatibility to hive, not only performance.
[~hvanhovell] I think I'm not the right one, to activate this again. I don't
know spark under the hood, and its development processes.
> SQL: MapType in Group BY and Joins not working
> ----------------------------------------------
>
> Key: SPARK-18134
> URL: https://issues.apache.org/jira/browse/SPARK-18134
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0, 1.6.1, 1.6.2, 2.0.0, 2.0.1
> Reporter: Christian Zorneck
>
> Since version 1.5 and issue SPARK-9415, MapTypes can no longer be used in
> GROUP BY and join clauses. This makes it incompatible to HiveQL. So, a Hive
> feature was removed from Spark. This makes Spark incompatible to various
> HiveQL statements.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
