From issues-return-6262-archive-asf-public=cust-asf.ponee.io@phoenix.apache.org Thu Apr 25 05:05:05 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id E7A69180668 for ; Thu, 25 Apr 2019 07:05:04 +0200 (CEST) Received: (qmail 63263 invoked by uid 500); 25 Apr 2019 05:05:01 -0000 Mailing-List: contact issues-help@phoenix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@phoenix.apache.org Delivered-To: mailing list issues@phoenix.apache.org Received: (qmail 63175 invoked by uid 99); 25 Apr 2019 05:05:01 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Apr 2019 05:05:01 +0000 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 973FFE2B24 for ; Thu, 25 Apr 2019 05:05:00 +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 1D15D256C1 for ; Thu, 25 Apr 2019 05:05:00 +0000 (UTC) Date: Thu, 25 Apr 2019 05:05:00 +0000 (UTC) From: "Karan Mehta (JIRA)" To: issues@phoenix.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (PHOENIX-5236) Multiple dynamic columns in WHERE clause is not working MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/PHOENIX-5236?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16= 825717#comment-16825717 ]=20 Karan Mehta commented on PHOENIX-5236: -------------------------------------- [~ckulkarni] Any idea why this is happening here? > Multiple dynamic columns in WHERE clause is not working > ------------------------------------------------------- > > Key: PHOENIX-5236 > URL: https://issues.apache.org/jira/browse/PHOENIX-5236 > Project: Phoenix > Issue Type: Bug > Affects Versions: 4.14.0 > Reporter: Chandrasekar > Priority: Major > > When the query uses multiple dynamic columns in the WHERE clause it's fai= ling. Consider the following example: > =C2=A0 > CREATE TABLE CITY (ID INTEGER, NAME VARCHAR CONSTRAINT PK PRIMARY KEY (ID= )) > And the following upserts: > UPSERT INTO CITY (ID, NAME, POPULATION INTEGER, DISTRICT VARCHAR) VALUES = (1, 'XYZ', 1000, 'XYZ') > UPSERT INTO CITY (ID, NAME, POPULATION INTEGER) VALUES (2, 'ABC', 2000) > =C2=A0 > And now when the following query is executed: > SELECT ID, NAME FROM CITY (POPULATION INTEGER, DISTRICT VARCHAR) WHERE=C2= =A0 DISTRICT IS NULL AND POPULATION > 1000 > It throws the following exception: > org.apache.phoenix.schema.PTable$QualifierEncodingScheme$InvalidQualifier= BytesException: Invalid number of qualifier bytes. Expected length: 2. Actu= al: 8 > =C2=A0Even comparing different dynamic columns is not working. For exampl= e in the same table, following upsert is executed: > UPSERT INTO CITY (ID, NAME, CURRENT_POPULATION INTEGER) VALUES (2, 'ABC',= 2000) > And when the following query is executed: > SELECT ID, NAME FROM CITY (POPULATION INTEGER, CURRENT_POPULATION INTEGER= ) WHERE POPULATION !=3D CURRENT_POPULATION > It again throws the same error ( > org.apache.phoenix.schema.PTable$QualifierEncodingScheme$InvalidQualifier= BytesException: Invalid number of qualifier bytes. Expected length: 2. Actu= al: 10) > Does phoenix allows querying by conditions on multiple dynamic columns? T= he phoenix version used is 4.14.0 and HBase version is 1.4.8. -- This message was sent by Atlassian JIRA (v7.6.3#76005)