Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Wed, 11 Nov 2015 02:37:11 +0000 (UTC)
From: "Andrey Novikov (JIRA)" <jira@apache.org>
To: dev@ignite.apache.org
Message-ID: <JIRA.12912059.1447209384000.35757.1447209431013@Atlassian.JIRA>
In-Reply-To: <JIRA.12912059.1447209384000@Atlassian.JIRA>
References: <JIRA.12912059.1447209384000@Atlassian.JIRA>
 <JIRA.12912059.1447209384818@arcas>
Subject: [jira] [Created] (IGNITE-1887) REST-HTTP change queryId generation
 from sequence to random.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Andrey Novikov created IGNITE-1887:
--------------------------------------

             Summary: REST-HTTP change queryId generation from sequence to random.
                 Key: IGNITE-1887
                 URL: https://issues.apache.org/jira/browse/IGNITE-1887
             Project: Ignite
          Issue Type: Bug
            Reporter: Andrey Novikov
            Assignee: Andrey Novikov
            Priority: Minor


First problem:
 1. client1 execute query and get queryId = 1.
 2. node where query was executed is restarted (queryId generator
initialized to zero).
 3. client2 execute some query and also get queryId=1.
 4. client1 fetch next page for queryId=1 and GETS results of client2.

Second problem:
 As queryId is generated sequentially it is very easy to brute force and
some client could get data of other clients too easy.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)