-
Notifications
You must be signed in to change notification settings - Fork 19
feat: extra headers during client initialization #666
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: aderihoilya.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @aderihoJD Thanks for this.
Can you add a test for it?
|
@aderihoJD please provide a signed CLA as well |
i had to create a new one, as i did whole flow from another email #668 |
Your CLA probably still has to be processed. Stay tuned. Also if you rebase your commit you can change author as well so theoretically you dont need a new PR. But either is fine and we need to wait until CLA is processed. Your github username will show up in https://github.com/trinodb/cla/blob/master/contributors |
@mosabua i appeared in this list https://github.com/trinodb/cla/blob/master/contributors |
@cla-bot check |
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: aderihoilya.
|
The cla-bot has been summoned, and re-checked this pull request! |
There's an open discussion in trinodb/trino#15826 about allowing clients to send any HTTP headers. It would be better to discuss specific use cases. Similar changes were suggested in both the Trino Go client, and the Python client, and both were rejected, because no sufficient use case was provided. |
BTW the CLA bot check is not passing, because the commit is authored by |
@nineinchnick i created a new MR with correct user #668 - it's not a duplicate |
So can this one be closed then? |
Unfortunately, this feature #568 not fully provide possibility to apply extra headers for each request to Trino. They apply only for the first one (query) and we lose them later, in next() method. If we'll add extraHeaders during client initialization, they will apply for each request.
p.s. pretty urgent, if possible