Return-Path: X-Original-To: apmail-drill-issues-archive@minotaur.apache.org Delivered-To: apmail-drill-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 157F2109D0 for ; Tue, 8 Sep 2015 18:32:47 +0000 (UTC) Received: (qmail 61343 invoked by uid 500); 8 Sep 2015 18:32:46 -0000 Delivered-To: apmail-drill-issues-archive@drill.apache.org Received: (qmail 61270 invoked by uid 500); 8 Sep 2015 18:32:46 -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 61195 invoked by uid 99); 8 Sep 2015 18:32:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Sep 2015 18:32:46 +0000 Date: Tue, 8 Sep 2015 18:32:46 +0000 (UTC) From: "Sean Hsuan-Yi Chu (JIRA)" To: issues@drill.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (DRILL-3597) Disable RESPECT NULLS, IGNORE NULLS option for LEAD, LAG window functions 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/DRILL-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Hsuan-Yi Chu updated DRILL-3597: ------------------------------------- Fix Version/s: 1.2.0 > Disable RESPECT NULLS, IGNORE NULLS option for LEAD, LAG window functions > ------------------------------------------------------------------------- > > Key: DRILL-3597 > URL: https://issues.apache.org/jira/browse/DRILL-3597 > Project: Apache Drill > Issue Type: Bug > Components: Execution - Relational Operators > Affects Versions: 1.2.0 > Reporter: Khurram Faraaz > Assignee: Sean Hsuan-Yi Chu > Fix For: 1.2.0 > > > The SQL standard defines a RESPECT NULLS or IGNORE NULLS option for lead, lag, first_value, and last_value window functions. We need to (disable it) and report a meaningful message to user if either of these two options is used in a query, with any of those functions. > Currently we throw parse errors when these options are used in query. > {code} > 0: jdbc:drill:schema=dfs.tmp> select lead(c1,2) respect nulls over w from union_01 window w as (partition by c3 order by c1); > Error: PARSE ERROR: Encountered "nulls" at line 1, column 27. > Was expecting one of: > "FROM" ... > "," ... > > [Error Id: 73d09692-6374-41a2-bce0-db73d2828f1f on centos-04.qa.lab:31010] (state=,code=0) > {code} > {code} > 0: jdbc:drill:schema=dfs.tmp> select lead(c1,2) ignore nulls over w from union_01 window w as (partition by c3 order by c1); > Error: PARSE ERROR: Encountered "nulls" at line 1, column 26. > Was expecting one of: > "FROM" ... > "," ... > > [Error Id: a7bd21b3-b46c-417d-a9d9-aa6d0378b0fc on centos-04.qa.lab:31010] (state=,code=0) > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)