You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Sebastien Binet (Jira)" <ji...@apache.org> on 2020/10/26 15:35:00 UTC

[jira] [Resolved] (ARROW-10319) [Flight][Go] Add Context to Client Auth Handler functions for Flight

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

Sebastien Binet resolved ARROW-10319.
-------------------------------------
    Fix Version/s: 3.0.0
       Resolution: Fixed

Issue resolved by pull request 8471
[https://github.com/apache/arrow/pull/8471]

> [Flight][Go] Add Context to Client Auth Handler functions for Flight
> --------------------------------------------------------------------
>
>                 Key: ARROW-10319
>                 URL: https://issues.apache.org/jira/browse/ARROW-10319
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: FlightRPC, Go
>            Reporter: Matt Topol
>            Assignee: Matt Topol
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 3.0.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> During my usage I found that if i wanted to reuse an existing flight client that required authentication, it was difficult to reuse the auth handler since there wasn't a way to tell which goroutine / which auth made a particular request. By passing the context to the client auth handler it allows passing information to the auth handler via the context which could then be utilized by consumers in order to reuse a auth handler so that an entire flight client could be shared across multiple goroutines if desired.



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