Return-Path: X-Original-To: apmail-drill-dev-archive@www.apache.org Delivered-To: apmail-drill-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 72A9D1836D for ; Wed, 30 Sep 2015 00:01:18 +0000 (UTC) Received: (qmail 78307 invoked by uid 500); 30 Sep 2015 00:01:18 -0000 Delivered-To: apmail-drill-dev-archive@drill.apache.org Received: (qmail 78240 invoked by uid 500); 30 Sep 2015 00:01:18 -0000 Mailing-List: contact dev-help@drill.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@drill.apache.org Delivered-To: mailing list dev@drill.apache.org Received: (qmail 78227 invoked by uid 99); 30 Sep 2015 00:01:18 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Sep 2015 00:01:18 +0000 Date: Wed, 30 Sep 2015 00:01:18 +0000 (UTC) From: "Daniel Barclay (Drill) (JIRA)" To: dev@drill.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (DRILL-3864) TestBuilder "Unexpected column" message doesn't show records MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Daniel Barclay (Drill) created DRILL-3864: --------------------------------------------- Summary: TestBuilder "Unexpected column" message doesn't show records Key: DRILL-3864 URL: https://issues.apache.org/jira/browse/DRILL-3864 Project: Apache Drill Issue Type: Bug Components: Tools, Build & Test Reporter: Daniel Barclay (Drill) Assignee: Jason Altekruse When {{TestBuilder}} reports that the actual result set contains an unexpected column, it doesn't show any whole expected record (as it shows some expected record and some actual records for the "did not find expected record in result set" case). Showing a couple of whole expected records, rather than just reporting the unexpected column name(s), would speed up diagnosis of test failures. -- This message was sent by Atlassian JIRA (v6.3.4#6332)