Return-Path: Delivered-To: apmail-hadoop-hive-user-archive@minotaur.apache.org Received: (qmail 70775 invoked from network); 19 Feb 2009 09:07:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Feb 2009 09:07:04 -0000 Received: (qmail 12739 invoked by uid 500); 19 Feb 2009 09:07:04 -0000 Delivered-To: apmail-hadoop-hive-user-archive@hadoop.apache.org Received: (qmail 12725 invoked by uid 500); 19 Feb 2009 09:07:04 -0000 Mailing-List: contact hive-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hive-user@hadoop.apache.org Delivered-To: mailing list hive-user@hadoop.apache.org Received: (qmail 12716 invoked by uid 99); 19 Feb 2009 09:07:04 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Feb 2009 01:07:04 -0800 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of qingyan@gmail.com designates 209.85.217.170 as permitted sender) Received: from [209.85.217.170] (HELO mail-gx0-f170.google.com) (209.85.217.170) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Feb 2009 09:06:57 +0000 Received: by gxk18 with SMTP id 18so802430gxk.5 for ; Thu, 19 Feb 2009 01:06:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=yROWJWRLjq33xzIdCOjNK4gj3n8hCNLNYrYRH8eRJdI=; b=s0R/eWm9MLu5EB9J2bv3Ba4mvyHjEdX9Aa/s3OFxLWZSbbGQS/EkXS2SrJOC2vOSQy aRJIvcq0TwaPxeu+TnO+mjtTxFrnWmN2q5qXc8zm1fkUOapWbn/4jqsR2BkUCIXL04bB tWcCG/yLg7MNfrqcIcrKItyyCS38qJ6/VTtCA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=va9AdDcuvihQStyqvIy1PuPPhLNeeFqsL9HkpnHO2eRWfSRUC+kP0pg2ujEdw5s4lN nVTkiaImAFFrOQmMdJmc8NfII6JOk4Z+nNSUQq5idUbMe6Zxcv0fkans8UdPE5fW/6Uc uozEdr8GmY7rThXpqQCsJ2qCvFyg5QXyVvt7E= MIME-Version: 1.0 Received: by 10.64.184.18 with SMTP id h18mr5096409qbf.27.1235034396594; Thu, 19 Feb 2009 01:06:36 -0800 (PST) Date: Thu, 19 Feb 2009 17:06:36 +0800 Message-ID: Subject: Error input handling in Hive From: Qing Yan To: hive-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=00c09f90f97b7e9475046341da5b X-Virus-Checked: Checked by ClamAV on apache.org --00c09f90f97b7e9475046341da5b Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Say I have some bad/ill-formatted records in the input, is there a way to configure the default Hive parser to discard those records directly(e.g. when a integer column get a string)? Besides, is the new skip-bad-records feature in 0.19 accessible in Hive? It is a quite handy feature in the real world. What I see so far is the Hive parser throws exception and cause the whole job to fail ultimately. Thanks for the help! Qing --00c09f90f97b7e9475046341da5b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Say I have some bad/ill-formatted records in the input, is there a way to configure the default Hive parser to discard those records directly(e.g. when a integer column get a string)?
 
Besides, is the new skip-bad-records feature in 0.19 accessible in Hive? It is a quite handy feature in the real world.
 
What I see so far is the Hive parser throws exception and cause the whole job to fail ultimately.
 
Thanks for the help!
 
Qing
 
 
 
--00c09f90f97b7e9475046341da5b--