Return-Path: Delivered-To: apmail-incubator-jackrabbit-dev-archive@www.apache.org Received: (qmail 82281 invoked from network); 15 Aug 2005 12:13:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 15 Aug 2005 12:13:57 -0000 Received: (qmail 71101 invoked by uid 500); 15 Aug 2005 12:13:55 -0000 Mailing-List: contact jackrabbit-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jackrabbit-dev@incubator.apache.org Delivered-To: mailing list jackrabbit-dev@incubator.apache.org Received: (qmail 71068 invoked by uid 99); 15 Aug 2005 12:13:55 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Aug 2005 05:13:55 -0700 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 55407EB for ; Mon, 15 Aug 2005 14:13:54 +0200 (CEST) Message-ID: <617822765.1124108034347.JavaMail.jira@ajax.apache.org> Date: Mon, 15 Aug 2005 14:13:54 +0200 (CEST) From: "Marcel Reutegger (JIRA)" To: jackrabbit-dev@incubator.apache.org Subject: [jira] Closed: (JCR-178) Allow concurrent index updates and queries In-Reply-To: <1662528573.1123577795147.JavaMail.jira@ajax.apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/JCR-178?page=all ] Marcel Reutegger closed JCR-178: -------------------------------- > Allow concurrent index updates and queries > ------------------------------------------ > > Key: JCR-178 > URL: http://issues.apache.org/jira/browse/JCR-178 > Project: Jackrabbit > Type: Improvement > Components: query > Environment: svn revision: 231015 > Reporter: Marcel Reutegger > Assignee: Marcel Reutegger > Priority: Minor > > Currently the query handler either allows one modification or multiple queries at a time. That is, write operations are separated from read operations. With this synchronization scheme multiple queries may run concurrently, but only in the absence of a write operation. > There is one major drawback with this synchronization: a single long running query is able to block the whole workspace from committing changes. Because the query handler is coupled to the Workspace via a synchronous event listener, further processing is blocked until the query handler has finished its event processing (reflecting the changes in the index). > Instead, each index modification should be non-blocking, in the sense that an index modification should not have to wait for any queries to complete. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira