Skip to content

Conversation

@skandtandon
Copy link
Contributor

No description provided.

@sercanCyberVision
Copy link
Contributor

@skandtandon, can you share how you tested this patch?
If I understand correctly, with this patch, Livy will read some jars from user specific PVC. How do we add jars to the PVC in the first place? Are the jars replaced with new ones when we upgrade the app?

@skandtandon
Copy link
Contributor Author

skandtandon commented Mar 12, 2024

@skandtandon, can you share how you tested this patch? If I understand correctly, with this patch, Livy will read some jars from user specific PVC. How do we add jars to the PVC in the first place? Are the jars replaced with new ones when we upgrade the app?

@sercanCyberVision the PVC is a place holder which is auto populated by the Livy server, so as far as my understanding goes, we won't be needing to place the jars in the PVC at all.
Sanity test was done on dev1 cluster by creating a similar PVC manually in Spark Namespace, and then running the livy session in spark namespace. The session ran successfully with older Spark image without the need to upload or maintain the jars
image
image

Copy link
Contributor

@sercanCyberVision sercanCyberVision left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thank you @skandtandon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants