Database Reference
In-Depth Information
- Time taken: 0.548 seconds
2013-11-15 11:56:49,874 INFO ql.Driver (PerfLogger.java:PerfLogBegin(100))
- <PERFLOG method=releaseLocks>
2013-11-15 11:56:49,874 INFO ql.Driver (PerfLogger.java:PerfLogEnd(127))
- </PERFLOG method=releaseLocks start=1384516609874 end=1384516609874 duration=0>
The highlighted entries in Listing 13-8 are the regions you should be looking at if you wish to see the chain of
events while executing your
CREATE DATABASE
Hive job.
Other entries are helpful in the event of an error. Say, for example, you try to create a database that already exists.
The attempt would fail. You would then look for entries in the log file such as those highlighted in Listing 13-9.
Listing 13-9.
hive.log file showing HQL errors
2013-11-15 13:37:11,432 INFO ql.Driver (PerfLogger.java:PerfLogBegin(100))
- <PERFLOG method=Driver.run>
2013-11-15 13:37:11,433 INFO ql.Driver (PerfLogger.java:PerfLogBegin(100))
- <PERFLOG method=TimeToSubmit>
2013-11-15 13:37:11,433 INFO ql.Driver (PerfLogger.java:PerfLogBegin(100))
- <PERFLOG method=compile>
2013-11-15 13:37:11,434 INFO parse.ParseDriver (ParseDriver.java:parse(179))
- Parsing command: create database test
2013-11-15 13:37:11,434 INFO parse.ParseDriver (ParseDriver.java:parse(197))
- Parse Completed
2013-11-15 13:37:11,435 INFO ql.Driver (Driver.java:compile(442))
- Semantic Analysis Completed
2013-11-15 13:37:11,436 INFO ql.Driver (Driver.java:getSchema(259))
- Returning Hive schema: Schema(fieldSchemas:null, properties:null)
2013-11-15 13:37:11,436 INFO ql.Driver (PerfLogger.java:PerfLogEnd(127))
- </PERFLOG method=compile start=1384522631433 end=1384522631436 duration=3>
2013-11-15 13:37:11,437 INFO ql.Driver (PerfLogger.java:PerfLogBegin(100))
- <PERFLOG method=Driver.execute>
2013-11-15 13:37:11,437 INFO ql.Driver (Driver.java:execute(1066))
-
Starting command: create database test
2013-11-15 13:37:11,437 INFO ql.Driver (PerfLogger.java:PerfLogEnd(127))
- </PERFLOG method=TimeToSubmit start=1384522631433 end=1384522631437 duration=4>
2013-11-15 13:37:11,508 ERROR exec.Task
(SessionState.java:printError(432))
- Database test already exists
2013-11-15 13:37:11,509 ERROR ql.Driver (SessionState.java:printError(432))
-
FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.DDLTask
2013-11-15 13:37:11,510 INFO ql.Driver (PerfLogger.java:PerfLogEnd(127))
- </PERFLOG method=Driver.execute start=1384522631437 end=1384522631510 duration=73>
2013-11-15 13:37:11,511 INFO ql.Driver (PerfLogger.java:PerfLogBegin(100))
- <PERFLOG method=releaseLocks>
2013-11-15 13:37:11,512 INFO ql.Driver (PerfLogger.java:PerfLogEnd(127))
- </PERFLOG method=releaseLocks start=1384522631511 end=1384522631512 duration=1>
2013-11-15 13:37:11,512 INFO ql.Driver (PerfLogger.java:PerfLogBegin(100))
- <PERFLOG method=releaseLocks>
2013-11-15 13:37:11,514 INFO ql.Driver (PerfLogger.java:PerfLogEnd(127))
- </PERFLOG method=releaseLocks start=1384522631512 end=1384522631513 duration=1>
Much the same way, if you try to drop a database that does not even exist, you would see errors logged like those
in Listing 13-10.
