ufukomer

@tiejian create a _command line app_ then use _impala-shell_ via this app. I have never tried in NodeJS but there are many in GitHub, e.g. [commander.js](https://github.com/tj/commander.js), [cli](https://github.com/node-js-libs/cli). I'm not sure...

@kwent we should make this library use HiveServer2 in a way that is similar to its [python client](https://github.com/cloudera/impyla) as I mentioned in the comment above.

Probably a bug. Can you fix it? You can easily understand the problem by inserting a console.log [here](https://github.com/ufukomer/node-impala/blob/master/src/node-impala.js#L171) to see what is wrong with the _result_.

@WangJiaoJo I think your port should be **21000** (#8). You don't need to include your username and password, no authentication is required (#14).

@WangJiaoJo Yes, probably. It does not support Kerberos. So, I should add an error to promise response. Let's keep this issue open.

@ZuluagaSD We are working on that. Can you provide a correctly configured remote Kerberized impala cluster or something like that? If you want to help... or anyone else? Then I...

@dhananjaymehta That did not worked for me. Does it require any additional configuration?

I'll do it if you wish.

I get the similar error when I update React from 14.0.0 to 15.0.0 and have no *require* in my code. Have an idea? (No changes on react.go)

Finally, I found the error. This is what happens when you update *React* and don't update *Helmet*. Goja does not show the error line in bundle.js which makes debugging process...