Skip to content
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

Document driver installation for Hive metastore backend database #416

Closed
2 tasks done
Jimvin opened this issue Feb 19, 2024 · 9 comments · Fixed by #449
Closed
2 tasks done

Document driver installation for Hive metastore backend database #416

Jimvin opened this issue Feb 19, 2024 · 9 comments · Fixed by #449

Comments

@Jimvin
Copy link
Member

Jimvin commented Feb 19, 2024

Certain databases (Oracle, MySQL) do not allow shipping their database driver, and so as a user of that database with Hive, I have to manually provide the driver to Hive. As a user, I want to find instructions in the Stackable documentation on how to install and configure such a driver with a Stackable-deployed Hive instance, so I can use Hive with my proprietary database.

Suggested steps to document

Also: we should update the "required external components" page to note that some drivers have to be installed manually.

Considered alternatives

  • building a custom image (quite a bit of overhead, also requires a registry/way to deploy the image)
  • copy the driver from s3 or another place to curl from

Tasks

Tasks

Preview Give feedback

Open Questions

  • Should we have an integration test for this? Should it be somehow entirely coded so we can test if it keeps working?

Acceptance criteria

  • The "Usage guide" for the Hive operator contains a document that explains how to install custom drivers
  • The guide is mentioned in relevant places to make it easy to find for users
@lfrancke
Copy link
Member

The follow up for this would be #415

@lfrancke
Copy link
Member

lfrancke commented Apr 3, 2024

Refinement by Malte, Felix

@fhennig
Copy link
Contributor

fhennig commented Apr 4, 2024

Refinement notes

Due to licensing issues certain drivers cannot be shipped, and customers have to deploy them on their own.

Suggested steps

Considered alternatives

  • building a custom image (quite a bit of overhead, also requires a registry/way to deploy the image)
  • copy the driver from s3 or another place to curl from

Misc.

we should also update the "required external components" page to note that some drivers have to be installed manually.

A common way to add volumes to product images would be good. We have something in Druid in Airflow, but no standardized way: stackabletech/issues#471

Maybe we can also write a generic tutorial about how to get arbitrary files into Pods

@lfrancke
Copy link
Member

lfrancke commented Apr 4, 2024

We can't ship certain drivers for licensing reasons. So we'll need a documented way to include new ones either way.

@lfrancke lfrancke moved this to Refinement: In Progress in Stackable Engineering Apr 4, 2024
@fhennig fhennig moved this from Refinement: In Progress to Refinement Acceptance: Waiting for in Stackable Engineering Apr 4, 2024
@fhennig fhennig moved this from Refinement Acceptance: Waiting for to Refinement: In Progress in Stackable Engineering Apr 4, 2024
@fhennig fhennig moved this from Refinement: In Progress to Refinement Acceptance: Waiting for in Stackable Engineering Apr 8, 2024
@soenkeliebau
Copy link
Member

looks good to me, just to double check, are the "considered alternatives" planned to include as an "honorable mention" in the docs?

@soenkeliebau soenkeliebau moved this from Refinement Acceptance: Waiting for to Ready for Development in Stackable Engineering Apr 15, 2024
@fhennig
Copy link
Contributor

fhennig commented Apr 17, 2024

I think they weren't, but good idea!

@adwk67
Copy link
Member

adwk67 commented Apr 19, 2024

Another alternative might be to use git-sync in "one-off" mode to download external resources. This would involve more work/code changes, but would be more robust than using PVCs (we got rid of our PVC-based external-resources-tests because they only worked on certain clusters) and is something we were looking at using for e.g. spark anyway.

@lfrancke lfrancke moved this from Proposed to Next in Stackable End-to-End Coordination Apr 22, 2024
@lfrancke lfrancke moved this from Next to In Progress in Stackable End-to-End Coordination Apr 22, 2024
@adwk67 adwk67 moved this from Ready for Development to Development: In Progress in Stackable Engineering Apr 22, 2024
@adwk67 adwk67 assigned adwk67 and unassigned fhennig and maltesander Apr 22, 2024
@adwk67 adwk67 moved this from Development: In Progress to Development: Waiting for Review in Stackable Engineering Apr 23, 2024
@maltesander maltesander moved this from Development: Waiting for Review to Development: In Review in Stackable Engineering Apr 23, 2024
@adwk67 adwk67 moved this from Development: In Review to Development: Done in Stackable Engineering Apr 25, 2024
@adwk67 adwk67 moved this from In Progress to Done in Stackable End-to-End Coordination Apr 25, 2024
@lfrancke lfrancke moved this from Development: Done to Acceptance: In Progress in Stackable Engineering Apr 30, 2024
@lfrancke
Copy link
Member

Could you please add a link to the documentation? (can be nightly)

@lfrancke lfrancke moved this from Acceptance: In Progress to Done in Stackable Engineering Apr 30, 2024
@lfrancke lfrancke moved this from Done to Acceptance: In Progress in Stackable Engineering Apr 30, 2024
@adwk67
Copy link
Member

adwk67 commented Apr 30, 2024

Docs are here: https://docs.stackable.tech/home/nightly/hive/usage-guide/database-driver

@lfrancke lfrancke moved this from Acceptance: In Progress to Done in Stackable Engineering May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

7 participants