FYI, I created a bug report and it's been already fixed on master:
https://issues.apache.org/jira/browse/HIVE-9347. Thanks for your help.
On Wed, Oct 22, 2014 at 9:39 AM, Michal Krawczyk
wrote:
> Not sure. The issue you mentioned requires specifying additional columns,
> whereas the one I mentio
Not sure. The issue you mentioned requires specifying additional columns,
whereas the one I mentioned return obviously incorrect results, which seems
to be much more severe issue.
Can anybody try to replicate this? If it's really the case on non Amazon
Hive I'll send a bug report on Jira.
On Tue,
Perhaps related to https://issues.apache.org/jira/browse/HIVE-4663
I ran across similar issues in .11 not sure if that above ticket affects .13
On Tue, Oct 21, 2014 at 8:21 AM, Michal Krawczyk
wrote:
> Hi all,
>
> Recently I've run into a problem with incorrect results in one of the
> queries o
Hi all,
Recently I've run into a problem with incorrect results in one of the
queries on our system after upgrade from Hive 0.8.1.4 to 0.13.1. We use
Amazon Elastic Map Reduce servivce on Amazon. I tried to simplify the
original query and replicate this issue on a small dataset. Please take a
look
