You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (Jira)" <ji...@apache.org> on 2020/09/20 01:56:00 UTC

[jira] [Commented] (SPARK-32912) Sparksql authentication

    [ https://issues.apache.org/jira/browse/SPARK-32912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17198857#comment-17198857 ] 

Hyukjin Kwon commented on SPARK-32912:
--------------------------------------

Let's discuss this in the mailing list instead of filing an issue. Looks like it's vague about what action should be taken and more appropriate as a discussion.

> Sparksql authentication
> -----------------------
>
>                 Key: SPARK-32912
>                 URL: https://issues.apache.org/jira/browse/SPARK-32912
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 2.3.0
>            Reporter: fengchunfeng
>            Priority: Major
>
> At present, we want to implement the same authentication module as hive, mainly to realize the blood relationship between table and column (field name). According to the survey, spark is used to resolve the corresponding relationship based on antrl4. However, the test shows that it does not support multi-layer nested query well, and can not accurately locate the corresponding relationship between table and column. We hope that the predecessors can provide help and relative Should the reference material, I will be very grateful, thank you



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org