[jira] [Created] (HIVE-2774) Message when trying to create a view from a view should give name of offending view
Message when trying to create a view from a view should give name of offending
view
---
Key: HIVE-2774
URL: https://issues.apache.org/jira/browse/HIVE-2774
Project: Hive
Issue Type: Improvement
Components: Query Processor
Affects Versions: 0.7.1
Reporter: Jakob Homan
Assignee: Jakob Homan
Fix For: 0.9.0
Attachments: HIVE-2774.patch
Currently when trying to create a view that contains another view (a prohibited
operation) the exception is:
{noformat}FAILED: Error in semantic analysis: Invalid Table Alias Referencing
view from foreign databases is not supported.{noformat}
'Twould be better if this message included the view that caused the error so
that when building views from lots of tables, one doesn't need to hunt to
figure out which one was the actual view.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-2705) SemanticAnalyzer twice swallows an exception it shouldn't
SemanticAnalyzer twice swallows an exception it shouldn't - Key: HIVE-2705 URL: https://issues.apache.org/jira/browse/HIVE-2705 Project: Hive Issue Type: Bug Components: Query Processor Affects Versions: 0.7.1 Reporter: Jakob Homan Assignee: Jakob Homan Fix For: 0.8.1 Twice SemanticAnalyzer catches an exception and drops it, just passing on the original message's in a new SemanticException. This means that those that see the message in the output cannot tell what generated the original exception. These original exceptions should be wrapped, as they are in other parts of the code. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-2677) Joins involving where statements with a partition do not prune correctly in left outer join
Joins involving where statements with a partition do not prune correctly in
left outer join
---
Key: HIVE-2677
URL: https://issues.apache.org/jira/browse/HIVE-2677
Project: Hive
Issue Type: Bug
Affects Versions: 0.7.0
Reporter: Jakob Homan
The following query:
{noformat}
select t1.id as m_id, count(t2.id) as totals
from table1 t1 left outer join table2 t2 on (t1.id = t2.id)
where (datepartition == '2011-11-08-00')
group by t1.id;{noformat}
should prune to just a single partition (datepartition == '2011-11-08-00') .
However, the filter is being applied in the reducer, so a full table scan is
being done as part of the map.
One can get the correct behavior by pushing the filter into a select statement
within the join itself:
{noformat}select t1.id as m_id, count(p.id) as totals
from table1 t1 left outer join (select * from table2 where datepartition ==
'2011-11-08-00') t2 on (t1.id = t2.id)
group by t1.id;{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (HIVE-2643) HIVE-2362 preventing Hadoop confs from loading in 0.20.204
HIVE-2362 preventing Hadoop confs from loading in 0.20.204
--
Key: HIVE-2643
URL: https://issues.apache.org/jira/browse/HIVE-2643
Project: Hive
Issue Type: Bug
Reporter: Jakob Homan
Priority: Blocker
After the application of HIVE-2362, we're unable to run queries against the
Hive cluster (RC2 and 3):
{noformat}java.io.IOException: Failed to set permissions of path:
/user/jhoman-667872320/.staging to 0700
at org.apache.hadoop.fs.FileUtil.checkReturnValue(FileUtil.java:680)
at org.apache.hadoop.fs.FileUtil.setPermission(FileUtil.java:653)
at
org.apache.hadoop.fs.RawLocalFileSystem.setPermission(RawLocalFileSystem.java:483)
at
org.apache.hadoop.fs.RawLocalFileSystem.mkdirs(RawLocalFileSystem.java:318)
at
org.apache.hadoop.fs.FilterFileSystem.mkdirs(FilterFileSystem.java:183)
at
org.apache.hadoop.mapreduce.JobSubmissionFiles.getStagingDir(JobSubmissionFiles.java:116){noformat}
this is due to all the hadoop confs not being loaded and the LocalJobRunner
(which builds staging directories in this manner) being used instead of the
regular one. It's also not possible to access the hdfs since no default fs is
specified.
Reverting 2362 fixes this, but I've not yet looked at that patch to see the
exact cause.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
