About Andrew_Sherman

Andrew_Sherman · ‎06-20-2019

I agree that is super confusing

Andrew_Sherman · ‎06-19-2019

Hi Mogiking, On the version I was testing (CDH 6.2) the duration looks correct, but the queries do not show up until they are completely closed. I was able to force this from the Impala Daemon Web UI, or by waiting, or by closing hue. -Andrew

Andrew_Sherman · ‎06-19-2019

If you want to use Statement then I think you just use simple: Statement statement = connection.createStatement(); statement.execute("drop table foo"); I know in other DBMS there is a lot of optimiazation around jdbc PreparedStatements and batches. There has not be a lot of emphasis on this in Impala. As I mention in my other reply there is a tendency to use other means of ingestion for optimal perforamance.

Andrew_Sherman · ‎06-17-2019

On that Cloudera Manager page, you can click 'Select Attributes' and check the box by 'Duration'. Now any queries that are displayed will show the query duration in milliseconds.

Andrew_Sherman · ‎02-08-2019

Hi Yasmin, there's not much information there but it does sound like your HS2 can't connect to the HMS. If you didn't fix the space issues for HMS then maybe HMS isn't running well. You may find useful information in the HMS logs -Andrew

Andrew_Sherman · ‎02-07-2019

It looks like the Postgres system used by HMS is out of disk space. -Andrew

Online	Offline
Last Visited	‎10-01-2024 03:36 PM

Member Since	‎07-25-2018 05:16 PM
Last Visited	‎10-01-2024 03:36 PM
Posts	17
Kudos received	4

Cloudera Community

Re: Impala JDBC executeBatch() doesn't work for St...

Re: Impala JDBC executeBatch() doesn't work for St...

Re: How can I check the Impala Query Execution Tim...

Re: Impala JDBC executeBatch() doesn't work for St...

Re: How can I check the Impala Query Execution Tim...

Re: ImpalaRuntimeException: Error making 'createTa...

Re: ImpalaRuntimeException: Error making 'createTa...