Return-Path: X-Original-To: apmail-incubator-ambari-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ambari-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1AC87F8FF for ; Wed, 1 May 2013 22:42:19 +0000 (UTC) Received: (qmail 63526 invoked by uid 500); 1 May 2013 22:42:16 -0000 Delivered-To: apmail-incubator-ambari-dev-archive@incubator.apache.org Received: (qmail 63472 invoked by uid 500); 1 May 2013 22:42:16 -0000 Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ambari-dev@incubator.apache.org Delivered-To: mailing list ambari-dev@incubator.apache.org Received: (qmail 63188 invoked by uid 99); 1 May 2013 22:42:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 May 2013 22:42:15 +0000 Date: Wed, 1 May 2013 22:42:15 +0000 (UTC) From: "Sumit Mohanty (JIRA)" To: ambari-dev@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AMBARI-2066) HDFS shortcircuit skip checksum should be removed MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Sumit Mohanty created AMBARI-2066: ------------------------------------- Summary: HDFS shortcircuit skip checksum should be removed Key: AMBARI-2066 URL: https://issues.apache.org/jira/browse/AMBARI-2066 Project: Ambari Issue Type: Bug Affects Versions: 1.3.0 Reporter: Sumit Mohanty Assignee: Sumit Mohanty Fix For: 1.3.0 There is an HBase configuration called "HDFS shortcircuit skip checksum" in Ambari Hbase config page. It is almost never correct for the user to set this property, we should remove it. Note, it is different than the property called: HDFS Short-circuit read, which should stay the same. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira