About zegab

Meenambigai · ‎03-10-2025

Try query below and let us know if it solves the problem and any other issues you are facing related select id, st.value street, ph.value phone from table, table.result st, table.result ph where st.key=’street’ and st.value='abc' and ph.key=’phone’ and ph.value='123'

ChethanYM · ‎11-21-2024

Hi @mrblack To avoid full table scan you follow these tips: 1. Ensure proper partition pruning: https://impala.apache.org/docs/build/html/topics/impala_partitioning.html#:~:text=the%20impalad%20daemon.-,Partition%20Pruning%20for%20Queries,-Partition%20pruning%20refers 2. Re write the query with sub queries. 3. Add explicit hints for join behaviour. Impala supports join hints like brodcast and shuffle that can influence query planning. After optimising check the explain plan. Regards, Chethan YM

AKO · ‎10-15-2024

I know about CTE solution I was trying to find if the variable like SQL Server solution is there or not. I will use CTE. thanks

AyazHussain · ‎10-10-2024

Hi @evanle96 This error is not an issue. Usually in the HA setup the call goes to both the NN and the Active NN acknowledges the call but the standby NN will through this warning. So you can ignore this warning here.

disoardi · ‎10-07-2024

Sure, it’s the latest version available. We have opened a case to cloudera, but being Impala and python widely used together I am surprised not finding lots bug report about this.

Online	Offline
Last Visited	‎12-16-2024 10:35 AM

Member Since	‎12-10-2015 08:14 AM
Last Visited	‎12-16-2024 10:35 AM
Posts	27
Kudos received	6

Cloudera Community

Re: SQL SELECT into Variable

Re: Impala multiple Key values in where clause wit...

Re: impala forces full table scan

Re: SQL SELECT into Variable

Re: Operation category READ is not supported in st...

Re: Impala ODBC driver and python query with param...