Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D6DE910721 for ; Sun, 7 Dec 2014 16:12:12 +0000 (UTC) Received: (qmail 36422 invoked by uid 500); 7 Dec 2014 16:12:12 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 36379 invoked by uid 500); 7 Dec 2014 16:12:12 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 36367 invoked by uid 99); 7 Dec 2014 16:12:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 Dec 2014 16:12:12 +0000 Date: Sun, 7 Dec 2014 16:12:12 +0000 (UTC) From: "Philip Thompson (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-8421) Cassandra 2.1.1 UDT not returning value for LIST type as UDT 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/CASSANDRA-8421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14237189#comment-14237189 ] Philip Thompson commented on CASSANDRA-8421: -------------------------------------------- [~madheswaran] I was able to reproduce your issue on 2.1.2. I have found that if there is an index on field_values, but not on status_key, your problem reproduces exactly as described. If there is an index on both field_values and on status_key, the correct data is returned every time. I am not sure if the index is supposed to be required, so I am reassigning to someone more familiar with secondary indexes. > Cassandra 2.1.1 UDT not returning value for LIST type as UDT > ------------------------------------------------------------ > > Key: CASSANDRA-8421 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8421 > Project: Cassandra > Issue Type: Bug > Components: API > Environment: single node cassandra > Reporter: madheswaran > Assignee: Philip Thompson > Fix For: 3.0, 2.1.3 > > > I using List and its data type is UDT. > UDT: > {code} > CREATE TYPE > fieldmap ( > key text, > value text > ); > {code} > TABLE: > {code} > CREATE TABLE entity ( > entity_id uuid PRIMARY KEY, > begining int, > domain text, > domain_type text, > entity_template_name text, > field_values list, > global_entity_type text, > revision_time timeuuid, > status_key int, > status_name text, > uuid timeuuid > ) {code} > INDEX: > {code} > CREATE INDEX entity_domain_idx_1 ON galaxy_dev.entity (domain); > CREATE INDEX entity_field_values_idx_1 ON galaxy_dev.entity (field_values); > CREATE INDEX entity_global_entity_type_idx_1 ON galaxy_dev.entity (gen_type ); > {code} > QUERY > {code} > SELECT * FROM entity WHERE status_key < 3 and field_values contains {key: 'userName', value: 'Sprint5_200002'} and gen_type = 'USER' and domain = 'S4_1017.abc.com' allow filtering; > {code} > The above query return value for some row and not for many rows but those rows and data's are exist. > Observation: > If I execute query with other than field_maps, then it returns value. I suspect the problem with LIST with UDT. > I have single node cassadra DB. Please let me know why this strange behavior from cassandra. -- This message was sent by Atlassian JIRA (v6.3.4#6332)