spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dongjoon Hyun (Jira)" <j...@apache.org>
Subject [jira] [Resolved] (SPARK-30129) New auth engine does not keep client ID in TransportClient after auth
Date Thu, 05 Dec 2019 01:14:00 GMT

     [ https://issues.apache.org/jira/browse/SPARK-30129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dongjoon Hyun resolved SPARK-30129.
-----------------------------------
    Fix Version/s: 3.0.0
       Resolution: Fixed

This is resolved via https://github.com/apache/spark/pull/26760

> New auth engine does not keep client ID in TransportClient after auth
> ---------------------------------------------------------------------
>
>                 Key: SPARK-30129
>                 URL: https://issues.apache.org/jira/browse/SPARK-30129
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core
>    Affects Versions: 2.4.4, 3.0.0
>            Reporter: Marcelo Masiero Vanzin
>            Assignee: Marcelo Masiero Vanzin
>            Priority: Major
>             Fix For: 3.0.0
>
>
> Found a little bug when working on a feature; when auth is on, it's expected that the
{{TransportClient}} provides the authenticated ID of the client (generally the app ID), but
the new auth engine is not setting that information.



--
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


Mime
View raw message