Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Selecthiveql processor gives java.lang.NullPointerException

Selecthiveql processor gives java.lang.NullPointerException

New Contributor

Query- select `(processing_dttm)?+.+` from acme_inc_5.trialbalance2017_case_4_wrangler_1533643070304 fails due to null. But when I run the same query in hive, it executes successfully. I have added added the property hive.support.quoted.identifiers=processing_dttm in hive-site.xml

5 REPLIES 5

Re: Selecthiveql processor gives java.lang.NullPointerException

Super Guru

@Smita Malimath

Not able to reproduce the same issue with quoted identifiers,

select `(processing_dttm)?+.+` from acme_inc_5.trialbalance2017_case_4_wrangler_1533643070304 

Try configuring HiveConnection pool with the below parameter and execute the query again

<jdbc_url>?hive.support.quoted.identifiers=none

it worth to check with this property also in your hive connection pool

<jdbc_url>?hive.vectorized.execution.enabled=false

Re: Selecthiveql processor gives java.lang.NullPointerException

New Contributor

I still face the same error as attached selecthiveql-null-error.png

Re: Selecthiveql processor gives java.lang.NullPointerException

Super Guru
@Smita Malimath

Did you tried with CSV/Avro Output formats?

Please share Select HiveQL configs, HiveConnection pool configs and

hive> describe formatted acme_inc_5.trialbalance2017_case_4_wrangler_1533643070304;

Re: Selecthiveql processor gives java.lang.NullPointerException

New Contributor

@Shu

Im using CSV output format. Please find details attacedselecthiveql-configs.pnghiveconnectionpool-config.pngdescribe-table.png

Re: Selecthiveql processor gives java.lang.NullPointerException

New Contributor

@Shu

When I tried the same changes on selecthiveql processor 1.4.0, it works fine but I get null pointer exception in selecthiveql processor 1.6.0. Is there any specific change that needs to be done in 1.6.0 go get issue resolved?