Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 8A4A9200D37 for ; Thu, 9 Nov 2017 17:53:12 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 88D52160BEF; Thu, 9 Nov 2017 16:53:12 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id CF29D1609C8 for ; Thu, 9 Nov 2017 17:53:11 +0100 (CET) Received: (qmail 53396 invoked by uid 500); 9 Nov 2017 16:53:11 -0000 Mailing-List: contact issues-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 issues@drill.apache.org Received: (qmail 53386 invoked by uid 99); 9 Nov 2017 16:53:11 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Nov 2017 16:53:11 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 526451A3BDD for ; Thu, 9 Nov 2017 16:53:10 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id A5G_DFAtjEM3 for ; Thu, 9 Nov 2017 16:53:09 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 28A2561174 for ; Thu, 9 Nov 2017 16:53:07 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 2B297E2597 for ; Thu, 9 Nov 2017 16:53:05 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id F00A324778 for ; Thu, 9 Nov 2017 16:53:01 +0000 (UTC) Date: Thu, 9 Nov 2017 16:53:01 +0000 (UTC) From: "Vlad (JIRA)" To: issues@drill.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (DRILL-5948) The wrong number of batches is displayed MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 09 Nov 2017 16:53:12 -0000 Vlad created DRILL-5948: --------------------------- Summary: The wrong number of batches is displayed Key: DRILL-5948 URL: https://issues.apache.org/jira/browse/DRILL-5948 Project: Apache Drill Issue Type: Bug Affects Versions: 1.11.0 Reporter: Vlad I suppose, when you execute a query with a small amount of data drill must create 1 batch, but here you can see that drill created 2 batches. I think it's a wrong behaviour for the drill. Full JSON file will be in the attachment. {code:html} "fragmentProfile": [ { "majorFragmentId": 0, "minorFragmentProfile": [ { "state": 3, "minorFragmentId": 0, "operatorProfile": [ { "inputProfile": [ { "records": 1, "batches": 2, "schemas": 1 } ], "operatorId": 2, "operatorType": 29, "setupNanos": 0, "processNanos": 1767363740, "peakLocalMemoryAllocated": 639120, "waitNanos": 25787 }, {code} Step to reproduce: # Create JSON file with 1 row # Execute star query whith this file, for example {code:sql} select * from dfs.`/path/to/your/file/example.json` {code} # Go to the Profile page on the UI, and open info about your query # Open JSON profile -- This message was sent by Atlassian JIRA (v6.4.14#64029)