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

Windows Kerberos Support #466

Open
ZeroCool2u opened this issue Aug 3, 2021 · 2 comments · May be fixed by #504
Open

Windows Kerberos Support #466

ZeroCool2u opened this issue Aug 3, 2021 · 2 comments · May be fixed by #504

Comments

@ZeroCool2u
Copy link

Right now, using impyla on Windows with kerberos is difficult. If you're running Python v3.6 or v3.7 you can go to the infamous Unofficial Windows Binaries for Python Extension Packages and install the binary version of the sasl package and somewhat successfully install an older version of impyla with kerberos support.

However, if you're forced to use a more recent version of Python say 3.8, you seem to be out of luck.

It seems like impyla could follow the popular pattern of using the winkerberos package based on the platform detected to mitigate the issue.

Would it be possible in the future to add support for this? Using CDH in a corporate environment is pretty painful without this feature.

@ZeroCool2u
Copy link
Author

Actually, this could probably be easily dealt with by clarifying things in the documentation and a small change to setup.py like:

 extras_require={
        "kerberos": [""] if platform.system() == 'Windows' else ['kerberos>=1.3.0'],
    },

Because the core dependencies will automatically handle kerberos support via winkerberos.

@attilajeges
Copy link
Contributor

@ZeroCool2u Could you do some basic testing with your suggested patch and then create a PR for it? Unfortunately I don't have access to a Windows box.

@jcrist jcrist linked a pull request Oct 18, 2022 that will close this issue
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 a pull request may close this issue.

2 participants