Return-Path: <user-return-12505-archive-asf-public=cust-asf.ponee.io@ignite.apache.org>
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 7D519200CA7
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Wed, 14 Jun 2017 19:53:11 +0200 (CEST)
Received: by cust-asf.ponee.io (Postfix)
	id 7C012160BDB; Wed, 14 Jun 2017 17:53:11 +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 C239E160BD6
	for <archive-asf-public@cust-asf.ponee.io>; Wed, 14 Jun 2017 19:53:10 +0200 (CEST)
Received: (qmail 98150 invoked by uid 500); 14 Jun 2017 17:53:09 -0000
Mailing-List: contact user-help@ignite.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@ignite.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@ignite.apache.org>
List-Post: <mailto:user@ignite.apache.org>
List-Id: <user.ignite.apache.org>
Reply-To: user@ignite.apache.org
Delivered-To: mailing list user@ignite.apache.org
Received: (qmail 98140 invoked by uid 99); 14 Jun 2017 17:53:09 -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; Wed, 14 Jun 2017 17:53:09 +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 6AB431AFCF1
	for <user@ignite.apache.org>; Wed, 14 Jun 2017 17:53:09 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: 0.972
X-Spam-Level: 
X-Spam-Status: No, score=0.972 tagged_above=-999 required=6.31
	tests=[RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972]
	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 6ALqLoX9FaLk for <user@ignite.apache.org>;
	Wed, 14 Jun 2017 17:53:08 +0000 (UTC)
Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43])
	by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 10DCD5F613
	for <user@ignite.apache.org>; Wed, 14 Jun 2017 17:53:08 +0000 (UTC)
Received: from static.162.255.23.37.macminivault.com (unknown [162.255.23.37])
	by mwork.nabble.com (Postfix) with ESMTP id 7B05E4A195DD2
	for <user@ignite.apache.org>; Wed, 14 Jun 2017 10:53:07 -0700 (MST)
Date: Wed, 14 Jun 2017 10:53:07 -0700 (MST)
From: amgad <amgad.madkour@outlook.com>
To: user@ignite.apache.org
Message-ID: <1497462787496-13711.post@n6.nabble.com>
Subject: IgniteRDD SQL query stalled or extremly slow on large input
 argument
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
archived-at: Wed, 14 Jun 2017 17:53:11 -0000

I have a query that stalls/hangs over large argument inputs. The same code
works well on smaller SQL argument input. The code is as follows: 

CODE:
------
*subEntries = dataRDD.sql("SELECT v.id,v.sub,v.obj FROM VPRow v JOIN
table(id bigint = ?) i ON v.id = i.id",new Object[]
{subKeyEntries.toArray()});
LOG.debug("Reading : "+subEntries.count());
*
Please note that the Ignite documentation mentions that the input argument
can be of any size - "Here you can provide object array (Object[]) of any
length as a parameter". The parameter passed to the query in the stalling
case was of size *23641 of long values*. 

My spring configuration file is as follows:

*<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="
        http://www.springframework.org/schema/beans
        http://www.springframework.org/schema/beans/spring-beans.xsd">

    <bean id="ignite.cfg"
class="org.apache.ignite.configuration.IgniteConfiguration">
        <property name="cacheConfiguration">
            <list>
                <bean
class="org.apache.ignite.configuration.CacheConfiguration">
                    
                    <property name="name" value="dataRDD"/>
                    
                    <property name="cacheMode" value="PARTITIONED"/>
                    
                    <property name="indexedTypes">
                        <list>
                            <value>java.lang.Long</value>
                            <value>sample.VPRow</value>
                        </list>
                    </property>
                    <property name="backups" value="0"/>
                </bean>
            </list>
        </property>
        
        <property name="discoverySpi">
            <bean
class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
                <property name="ipFinder">
                    <bean
class="org.apache.ignite.spi.discovery.tcp.ipfinder.multicast.TcpDiscoveryMulticastIpFinder">
                        <property name="addresses">
                            <list>
                                <value>[IP1]</value>
                                <value>[...]</value>
                                <value>[IP5]</value>
                            </list>
                        </property>
                    </bean>
                </property>
            </bean>
        </property>
    </bean>
</beans>
*
The VPRow class is defined as follows

*public class VPRow implements Serializable {

    @QuerySqlField
    private long id;
    @QuerySqlField
    private String sub;
    @QuerySqlField
    private String obj;

    public VPRow(long id,String sub, String obj) {
        this.id = id;
        this.sub = sub;
        this.obj = obj;
    }
    ...
}*



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/IgniteRDD-SQL-query-stalled-or-extremly-slow-on-large-input-argument-tp13711.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.