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.

Sign up for GitHub

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

Jump to bottom

Don't physically patch pyspark files #11

Open
abronte opened this issue Jun 11, 2019 · 1 comment
Open

Don't physically patch pyspark files #11

abronte opened this issue Jun 11, 2019 · 1 comment
Labels
enhancement New feature or request

Comments

@abronte
Copy link
Owner

abronte commented Jun 11, 2019

Because of issues trying to patch a function within a module in python, the gateway gets around this by physically patching the necessary pyspark files with our own custom code.

This is prone to breaking your local pyspark installation and probably shouldn't do it.
@abronte abronte added the enhancement New feature or request label Jun 11, 2019
@abronte abronte mentioned this issue Jul 14, 2019
Merged
abronte added a commit that referenced this issue Jul 15, 2019
@abronte
#11 Patch pyspark within python (#14)
7a781e0 
patch local_connect_and_auth in python rather than the file
@abronte abronte closed this as completed Jul 15, 2019
abronte pushed a commit that referenced this issue Jul 16, 2019
Revert "#11 Patch pyspark within python (#14)"
a2f5c0d 
This reverts commit 7a781e0.
@abronte abronte reopened this Jul 16, 2019
@abronte
Copy link
Owner Author

abronte commented Jul 16, 2019 •
edited
Loading

Came into a use case where this didn't work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@abronte