[
https://issues.apache.org/jira/browse/IMPALA-12093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Smith resolved IMPALA-12093.
------------------------------------
Fix Version/s: Impala 4.5.0
Resolution: Fixed
> impala-shell should preserve all cookies by default
> ---------------------------------------------------
>
> Key: IMPALA-12093
> URL: https://issues.apache.org/jira/browse/IMPALA-12093
> Project: IMPALA
> Issue Type: Improvement
> Components: Clients
> Affects Versions: Impala 4.3.0
> Reporter: Joe McDonnell
> Assignee: Michael Smith
> Priority: Major
> Fix For: Impala 4.5.0
>
>
> Currently, impala-shell's http_cookie_names parameter specifies which cookies
> should be preserved and sent back with subsequent requests. This defaults to
> a couple well-known cookie names that Impala uses.
> In general, we don't know what proxies are between impala-shell and Impala,
> and we don't know what cookie name they rely on being preserved. As an
> example, Apache Knox can rely on a cookie it sets to route requests to the
> appropriate Impala coordinator. Limiting our cookie preservation to a small
> allow list makes this much more brittle and hard to use. Clients need to know
> the right list of cookies to put in http_cookie_names, and that is not
> obvious.
> It seems like the default behavior should be to preserve all cookies. We can
> keep a way to disallow or limit the cookies for unusual cases.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
