opensearch-project / opensearch-project/sql-jdbc
[FEATURE]Set additional params to server
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 28
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem?
We want JDBC driver to work with multitenant Opensearch and use api key distinguish between tenants.
What solution would you like?
We need one custom parameter to be sent in every request to the server and we will have multitenant (access rights) proxy before Opensearch. Is it possible now? How? When I set custom parameter in jdbc url I do not see it being sent to the server.
What alternatives have you considered?
Using some other parameter e.g. user. But I couldn't see it sent to the server even when I set it up in jdbc params after port or as user. Or we can use context-path it is working.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how JDBC URL parameters are parsed and how requests are constructed for the OpenSearch server. Determine whether a custom parameter, user value, or API-key-related value can be represented and forwarded on every request. Done means the chosen parameter is consistently sent through the driver and covered by verification that reflects the multitenant proxy use case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100