Try using length function where length(company name ) >1 ... View more

Also make sure that the HDFS Data Node is running on that server. ... View more

Hive is more adaptable as far as data arranges that it can check - You may see Hive as more component wealthy as far as SQL language support and inherent capacities - Hive will probably finish your inquiry regardless of whether there are hub disappointments (this makes it reasonable for long-running employments); this is valid for both Hive on MR and Hive on Spark - If Impala can run your ETL, at that point it will most likely be quicker - Impala will come up short/prematurely end a question if a hub goes down during inquiry execution - The last point may make Impala less reasonable for long-running occupations, obviously there is likewise a shorter disappointment window since questions are quicker, so Impala might just suit your ETL needs on the off chance that you can endure the faiure conduct ... View more

As it says in the documentation:    Because this option results in increased resource utilization on a single host, it could cause problems due to contention with other Impala statements or high resource usage. Symptoms could include queries running slowly, exceeding the memory limit, or appearing to hang. Use it only in a single-user development/test environment; do not use it in a production environment or in a cluster with a high-concurrency or high-volume or performance-critical workload.     ... View more

Hi vaccarinicarlo, In the hadoop world where different components may have different rules about  cases sensitivity, it may be best to do as Alex Behm said above: "It's just easier to accept one canonical casing". I agree with you that it might be better to issue more warnings when anythign other than lower case is used. ... View more

Hi,   I have not followed the development of Impala lateley.If this i still a limitation you might try the following approach.Design the schema with an additional column with information about which rows holds information for a particular struct column and then use this additional column in the WHERE clause. Something like: name complex1 complex2 complex3 complex1 content NULL NULL complex3 NULL NULL content and then:   SELECT complex1.* FROM myTable WHERE name = 'complex1' Br, Petter ... View more

Hi Alex,Ajay    Can you please help me here? im facing similar issue. I have atatched the query and error as well.   Please help  me out.   Thanks Yasmin ... View more

CDH5.10.2 should have the fix for that specific issue.   ... View more

Hi @scuffster   There are some interesting issues here with the different numeric data types here - INT, DOUBLE, DECIMAL, etc. The behaviour you're seeing is because the first input to round() is a DOUBLE expression, which cannot exactly represent all decimal values. Generally the output type of the round() function is the same as the input type.   Impala does support precise decimal arithmetic with the DECIMAL type. If you are operating on DECIMAL columns or you cast the input to a decimal type with the right precision and scale, you may get the behaviour you're hoping for. Here's a query showing the type of your expressions and an alternative version with a cast to DECIMAL:   > select typeof(269586/334026 * 100), typeof(round(269586/334026 * 100, 2)), round(269586/334026 * 100, 2), round(cast(269586/334026 * 100 as DECIMAL(20, 8)), 2); +-------------------------------+-----------------------------------------+---------------------------------+--------------------------------------------------------+ | typeof(269586 / 334026 * 100) | typeof(round(269586 / 334026 * 100, 2)) | round(269586 / 334026 * 100, 2) | round(cast(269586 / 334026 * 100 as decimal(20,8)), 2) | +-------------------------------+-----------------------------------------+---------------------------------+--------------------------------------------------------+ | DOUBLE | DOUBLE | 80.70999999999999 | 80.71 | +-------------------------------+-----------------------------------------+---------------------------------+--------------------------------------------------------+ ... View more

Is there a workaround for this as we are on Impala version 2.8.0.  We are always stuck with compute incremental stats queries that need tobe manually cancelled? ... View more