You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "BELUGA BEHR (JIRA)" <ji...@apache.org> on 2018/02/09 16:29:00 UTC
[jira] [Updated] (HIVE-18669) Deprecate hive.mapred.mode For New
Name
[ https://issues.apache.org/jira/browse/HIVE-18669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
BELUGA BEHR updated HIVE-18669:
-------------------------------
Description:
The configuration {{hive.mapred.mode}} should have its name changed to reflect the fact that 'mapred' isn't the only game in town anymore when we're talking about "Hive operations."
https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties
{quote}
The mode in which the Hive operations are being performed. In strict mode, some risky queries are not allowed to run. For example, full table scans are prevented (see HIVE-10454) and ORDER BY requires a LIMIT clause.
{quote}
was:
The configuration {{hive.mapred.mode}} should be changed to reflect the fact that 'mapred' isn't the only game in town anymore when we're talking about "Hive operations."
https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties
{quote}
The mode in which the Hive operations are being performed. In strict mode, some risky queries are not allowed to run. For example, full table scans are prevented (see HIVE-10454) and ORDER BY requires a LIMIT clause.
{quote}
> Deprecate hive.mapred.mode For New Name
> ---------------------------------------
>
> Key: HIVE-18669
> URL: https://issues.apache.org/jira/browse/HIVE-18669
> Project: Hive
> Issue Type: Improvement
> Components: HiveServer2
> Affects Versions: 3.0.0, 2.3.2
> Reporter: BELUGA BEHR
> Priority: Minor
>
> The configuration {{hive.mapred.mode}} should have its name changed to reflect the fact that 'mapred' isn't the only game in town anymore when we're talking about "Hive operations."
> https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties
> {quote}
> The mode in which the Hive operations are being performed. In strict mode, some risky queries are not allowed to run. For example, full table scans are prevented (see HIVE-10454) and ORDER BY requires a LIMIT clause.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)