Member since
10-16-2013
307
Posts
77
Kudos Received
59
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
11242 | 04-17-2018 04:59 PM | |
6189 | 04-11-2018 10:07 PM | |
3554 | 03-02-2018 09:13 AM | |
22282 | 03-01-2018 09:22 AM | |
2652 | 02-27-2018 08:06 AM |
07-13-2015
07:03 PM
1 Kudo
1) The Knuth variance is an Impala built-in. Internally, Impala can handle aggregate functions with different intermediate and output types. Basically, the only reason you are not allowed to create UDAs with different intermediate/output types is because we have not enabled the feature in sermantic analysis. For us, enabling the feature is the easy part. Adding extensive testing is the hard part. If you are curious, the check for preventing you from creating such UDAs is in: ./fe/src/main/java/com/cloudera/impala/analysis/CreateUdaStmt.java lines 137 following 2) Like I said, enabling the feature is not hard, but does involve a non-trivial QA effort, so I cannot promise a concrete release at this point. I'd recommend keeping an eye on that JIRA for updates to the target version.
... View more
07-03-2015
02:05 AM
This seems to be a bug and hope we get the fix included in cdh 5.4.3. one of the work arounds observed was to Have 2 hive table pointing to the same locationg nad have onle of the table accessed through Impala while thye other is accessed through Hive.
... View more
06-29-2015
10:48 AM
1 Kudo
Can you try enabling "use native query"? The driver will send the query to Impala verbatim (sometimes the driver may make some changes to the SQL). http://www.cloudera.com/content/cloudera/en/documentation/connectors/latest/PDF/Cloudera-JDBC-Driver-for-Impala-Install-Guide.pdf
... View more
06-25-2015
03:05 PM
Makes sense. I appreciate your thorough question, and I completely agree that we should point out this expression-substitution behavior in the performance guide. It's not the first time it has come, and I'd imagine it will not be the last 🙂 Btw, if you really really want to get the materialization behavior with an inline view without an ORDER BY, then you can apply the following terrible hack. Original query: select a, b, c from (select f(x) as a, f(y) as b, f(z) as c from mytable) v Modified query to force materialization of inline view: select a, b, c from (select f(x) as a, f(y) as b, f(z) as c from mytable union all select NULL, NULL, NULL from mytable where false) v The "union all" will force materialization, but the second union operand will be dropped due to the "false" predicate. Obviously, that behavior is implementation defined and subject to change any time, so it would be wise not to rely on it.
... View more
05-22-2015
02:09 PM
That change only affects values being parsed inside a scan node. In your example you are casting a literal - the query option will have no effect on that.
... View more
05-18-2015
11:55 AM
yes that's exactly my situation right now. i've only stored data for 1 server sofar. i will continue with my workaround, thx for confirming that this will work for this situation.
... View more
03-20-2015
05:29 PM
Thanks. Actually based on that very same paragraph I ended up integrating jinja2 in my pipeline and have now a very nice framework for generating dynamic workflows and make parameters available anywhere 🙂 Thanks once again.
... View more
02-11-2015
11:28 PM
Thanks for you kindly help, it works!
... View more
- « Previous
- Next »