Return-Path: X-Original-To: apmail-hive-dev-archive@www.apache.org Delivered-To: apmail-hive-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 72C7417F5D for ; Thu, 23 Oct 2014 05:21:35 +0000 (UTC) Received: (qmail 69742 invoked by uid 500); 23 Oct 2014 05:21:34 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 69562 invoked by uid 500); 23 Oct 2014 05:21:34 -0000 Mailing-List: contact dev-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list dev@hive.apache.org Received: (qmail 69287 invoked by uid 500); 23 Oct 2014 05:21:34 -0000 Delivered-To: apmail-hadoop-hive-dev@hadoop.apache.org Received: (qmail 69243 invoked by uid 99); 23 Oct 2014 05:21:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Oct 2014 05:21:34 +0000 Date: Thu, 23 Oct 2014 05:21:34 +0000 (UTC) From: "Chao (JIRA)" To: hive-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HIVE-8545) Exception when casting Text to BytesWritable [Spark Branch] MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HIVE-8545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14181030#comment-14181030 ] Chao commented on HIVE-8545: ---------------------------- [~xuefuz] I agree. This indeed would be a better approach. Let me make the change and re-upload a patch. > Exception when casting Text to BytesWritable [Spark Branch] > ----------------------------------------------------------- > > Key: HIVE-8545 > URL: https://issues.apache.org/jira/browse/HIVE-8545 > Project: Hive > Issue Type: Bug > Components: Spark > Reporter: Chao > Assignee: Chao > Attachments: HIVE-8545.1-spark.patch, HIVE-8545.2-spark.patch, HIVE-8545.3-spark.patch, HIVE-8545.4-spark.patch, HIVE-8545.5-spark.patch > > > With the current multi-insertion implementation, when caching is enabled for input RDD, query may fail with the following exception: > {noformat} > 2014-10-21 13:57:34,742 WARN [task-result-getter-0]: scheduler.TaskSetManager (Logging.scala:logWarning(71)) - Lost task 0.0 in stage 1.0 (TID 1, localhost): java.lang.ClassCastException: org.apache.hadoop.io.Text cannot be cast to org.apache.hadoop.io.BytesWritable > org.apache.hadoop.hive.ql.exec.spark.MapInput$CopyFunction.call(MapInput.java:67) > org.apache.hadoop.hive.ql.exec.spark.MapInput$CopyFunction.call(MapInput.java:61) > org.apache.spark.api.java.JavaPairRDD$$anonfun$pairFunToScalaFun$1.apply(JavaPairRDD.scala:1002) > org.apache.spark.api.java.JavaPairRDD$$anonfun$pairFunToScalaFun$1.apply(JavaPairRDD.scala:1002) > scala.collection.Iterator$$anon$11.next(Iterator.scala:328) > org.apache.spark.storage.MemoryStore.unrollSafely(MemoryStore.scala:234) > org.apache.spark.CacheManager.putInBlockManager(CacheManager.scala:163) > org.apache.spark.CacheManager.getOrCompute(CacheManager.scala:70) > org.apache.spark.rdd.RDD.iterator(RDD.scala:227) > org.apache.spark.rdd.MapPartitionsRDD.compute(MapPartitionsRDD.scala:35) > org.apache.spark.rdd.RDD.computeOrReadCheckpoint(RDD.scala:262) > org.apache.spark.rdd.RDD.iterator(RDD.scala:229) > org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:68) > org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:41) > org.apache.spark.scheduler.Task.run(Task.scala:56) > org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:181) > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > java.lang.Thread.run(Thread.java:745) > {noformat} > The fix should be easy. However, interestingly, this error doesn't show up when the caching is turned off. We need to find out why. -- This message was sent by Atlassian JIRA (v6.3.4#6332)