Member since
01-07-2016
26
Posts
8
Kudos Received
0
Solutions
02-22-2019
12:27 AM
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
06-07-2018
03:40 AM
Hi @Pettax Thanks, your solution work with me too.
... View more
01-10-2017
11:34 AM
Hi Tim, thank you for taking the time to look at this issue! Br, Petter
... View more
08-22-2016
11:32 AM
1 Kudo
Hi Pettax, I would say option 1 and option 3 would be very similar in performance and allow for the best distribution of data across the cluster. I wouldn't opt for option 2.
... View more
02-01-2016
09:57 AM
AFAIK starting in 5.5 you need to enable kerberos on the Web UI in any case, as a change in Yarn now requires it for kill/starting actions with Kerberos. The above caching issue might prevent the kill button to work in certain cases until 5.5.3: https://issues.cloudera.org/browse/HUE-3107 So to sum-up, maybe you were lucky if you were testing it on 5.5.1, as all should only work properly in 5.5.3 + checking the spnego for the Web UI (Yarn guys you fix their get delegation toekn API at some point instead) Romain
... View more
01-07-2016
05:23 PM
Yea :). Thanks everyone for your reports and JIRA contricutions!
... View more