[
https://issues.apache.org/jira/browse/SPARK-7275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14532159#comment-14532159
]
Santiago M. Mola commented on SPARK-7275:
-----------------------------------------
[~gweidner] I work on a project that extends Spark SQL with a richer data
sources API. One of such extensions is the ability to push down a subtree of
the logical plan in full to a data source. Data sources implementing this API
must be able to inspect the LogicalPlan they're given, and that includes
matching LogicalRelation. If a data source is in its own Java package (i.e. not
org.apache.spark.sql) which is the usual case, it will not be able to match a
LogicalRelation out of the box. Currently, I implemented a workaround by adding
a public extractor IsLogicalRelation in org.apache.spark.sql package that
proxies LogicalRelation to outsider packages... which is, of course, a ugly
hack.
Note that LogicalRelation is the only element of the logical plan which is not
public.
> Make LogicalRelation public
> ---------------------------
>
> Key: SPARK-7275
> URL: https://issues.apache.org/jira/browse/SPARK-7275
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Reporter: Santiago M. Mola
> Priority: Minor
>
> It seems LogicalRelation is the only part of the LogicalPlan that is not
> public. This makes it harder to work with full logical plans from third party
> packages.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
