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

Add support for impala #23

Closed
Antwnis opened this issue Jan 28, 2016 · 4 comments
Closed

Add support for impala #23

Antwnis opened this issue Jan 28, 2016 · 4 comments

Comments

@Antwnis
Copy link

Antwnis commented Jan 28, 2016

By passing in authmech=3 and user/pass in the jdbc url you can interact with Impala even when Kerberos is enabled

@sksamuel
Copy link
Contributor

This can be done by changing the jdbc url ?

On 28 January 2016 at 20:44, Antonios Chalkiopoulos <
notifications@github.com> wrote:

By passing in authmech=3 and user/pass in the jdbc url you can interact
with Impala even when Kerberos is enabled


Reply to this email directly or view it on GitHub
#23.

@Antwnis
Copy link
Author

Antwnis commented Jan 29, 2016

Build two aliases ImpalaSource / ImpalaSink

JDBCDriver = "com.cloudera.impala.jdbc3.Driver"
jdbc:impala://host:21050;AuthMech=3;UID=UserName;PWD=Password

@sksamuel
Copy link
Contributor

Why can't you do JdbcSource("jdbc:impala://host:21050;
AuthMech=3;UID=UserName;PWD=Password") ?

On 29 January 2016 at 12:47, Antonios Chalkiopoulos <
notifications@github.com> wrote:

Build two aliases ImpalaSource / ImpalaSink

JDBCDriver = "com.cloudera.impala.jdbc3.Driver"
jdbc:impala://host:21050;AuthMech=3;UID=UserName;PWD=Password


Reply to this email directly or view it on GitHub
#23 (comment).

@sksamuel
Copy link
Contributor

This is a duplicate of functionality already present in jdbc source

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

No branches or pull requests

2 participants