Hi,
thank you all for your replies.
I switched to using 'hive.io.filter.text' inline with Peters reply. I also
applied the filter negotiation mechanism (HiveStoragePredicateHandler) in
my storage handler. It works very well (so far) even though the filter
negotiation mechanism is a bit limited in
Hi,
Sorry for the late reply.
Maybe the property 'hive.io.filter.expr.serialized' is something that can help?
It works for me, and it certainly works in the case where the query does not
result in a Map/Reduce (which is something that I rely on).
(If you google you should be able to find out abou
Looks like a bug. I've booked this on
https://issues.apache.org/jira/browse/HIVE-5935.
2013/12/4 Adam Kawa
> Maybe you can parse the output of EXPLAIN operator applied on your query
> https://cwiki.apache.org/confluence/display/Hive/LanguageManual+Explain
> or look for other configuration prope
Maybe you can parse the output of EXPLAIN operator applied on your query
https://cwiki.apache.org/confluence/display/Hive/LanguageManual+Explain or
look for other configuration property (e.g. saying that number of map and
reduce tasks is equal to 0, or something).
2013/12/3 Petter von Dolwitz (H
Yes, it seems related. I think the query string is not refreshed when hive
decides to run without a map reduce job. Problem is that I try to interact
with the query string to apply an early filter in the record reader. Any
other known way to detect that a map reduce job is not spawned so that I
can
Hmmm?
Maybe it is related to the fact, that a query:
> select * from mytable limit 100;
does not start any MapReduce job. It is starts a reading operation from
HDFS (and a communication with MetaStore to know what is the schema and how
to parse the data using InputFormat and SerDe).
For example,
