hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-1841) datanucleus.fixedDatastore should be true in hive-default.xml
Date Sat, 14 Nov 2015 16:06:10 GMT

    [ https://issues.apache.org/jira/browse/HIVE-1841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15005451#comment-15005451
] 

Hive QA commented on HIVE-1841:
-------------------------------



Here are the results of testing the latest attachment:
https://issues.apache.org/jira/secure/attachment/12772273/HIVE-1841.2.patch

{color:green}SUCCESS:{color} +1 due to 1 test(s) being added or modified.

{color:red}ERROR:{color} -1 due to 4 failed/errored test(s), 9782 tests executed
*Failed tests:*
{noformat}
TestHWISessionManager - did not produce a TEST-*.xml file
org.apache.hadoop.hive.cli.TestCliDriver.testCliDriver_cbo_rp_annotate_stats_groupby
org.apache.hadoop.hive.cli.TestNegativeCliDriver.testNegativeCliDriver_authorization_uri_import
org.apache.hive.jdbc.TestSSL.testSSLVersion
{noformat}

Test results: http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/6036/testReport
Console output: http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/PreCommit-HIVE-TRUNK-Build/6036/console
Test logs: http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-6036/

Messages:
{noformat}
Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase
Tests exited with: TestsFailedException: 4 tests failed
{noformat}

This message is automatically generated.

ATTACHMENT ID: 12772273 - PreCommit-HIVE-TRUNK-Build

>  datanucleus.fixedDatastore should be true in hive-default.xml
> --------------------------------------------------------------
>
>                 Key: HIVE-1841
>                 URL: https://issues.apache.org/jira/browse/HIVE-1841
>             Project: Hive
>          Issue Type: Improvement
>          Components: Configuration, Metastore
>    Affects Versions: 0.6.0
>            Reporter: Edward Capriolo
>            Assignee: Ashutosh Chauhan
>            Priority: Minor
>         Attachments: HIVE-1841.1.patch.txt, HIVE-1841.2.patch, HIVE-1841.patch
>
>
> Two datanucleus variables:
> {noformat}
> <property>
>  <name>datanucleus.autoCreateSchema</name>
>  <value>false</value>
> </property>
> <property>
>  <name>datanucleus.fixedDatastore</name>
>  <value>true</value>
> </property>
> {noformat}
> are dangerous.  We do want the schema to auto-create itself, but we do not want the schema
to auto update itself. 
> Someone might accidentally point a trunk at the wrong meta-store and unknowingly update.
I believe we should set this to false and possibly trap exceptions stemming from hive wanting
to do any update. This way someone has to actively acknowledge the update, by setting this
to true and then starting up hive, or leaving it false, removing schema modifies for the user
that hive usages, and doing all the time and doing the updates by hand. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message