Return-Path: X-Original-To: apmail-clerezza-dev-archive@www.apache.org Delivered-To: apmail-clerezza-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E20EC100CA for ; Wed, 4 Dec 2013 20:32:12 +0000 (UTC) Received: (qmail 1495 invoked by uid 500); 4 Dec 2013 20:32:12 -0000 Delivered-To: apmail-clerezza-dev-archive@clerezza.apache.org Received: (qmail 1449 invoked by uid 500); 4 Dec 2013 20:32:12 -0000 Mailing-List: contact dev-help@clerezza.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@clerezza.apache.org Delivered-To: mailing list dev@clerezza.apache.org Received: (qmail 1441 invoked by uid 99); 4 Dec 2013 20:32:12 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Dec 2013 20:32:12 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of andy.seaborne.apache@gmail.com designates 209.85.212.181 as permitted sender) Received: from [209.85.212.181] (HELO mail-wi0-f181.google.com) (209.85.212.181) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Dec 2013 20:32:04 +0000 Received: by mail-wi0-f181.google.com with SMTP id hq4so8818630wib.14 for ; Wed, 04 Dec 2013 12:31:43 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=X+DcngGMh/T1UMAJ3EOMgtVGNycysiAiCsOLqdvvgRU=; b=Zc8Ngt0KoAYphkAIWRnc0sH9qcHSxukM6+ysAIKcu0vRu9WmEbfQUbt+0Mok3BrfBJ iMTEEWz8wa6LZSGQTPg9lAV+wRzZ00XoNYiA1xuAMRNASr2s/AS9Vw7bml1PbqdX8wFw xO1n7fYodbZjKjDLrHTy7+ezIL0VkxqRft5IRGQcYaVFE4IIX6ccttqmm06Msw0bPZMn B8BXqbzaqHtmSZLnxPlxLcQ5FtugpWGYgtws6lE/wjl+iq6TUq34j9tzAO7xHCOsVkvS 6HBfFS+sQb636fOqUF2+cnkWFc7h9ATYdVBkP8jBjEWaMc5rmoczSIlhz6qxj8pgzl/4 Mikw== X-Received: by 10.180.14.226 with SMTP id s2mr9027793wic.41.1386189103613; Wed, 04 Dec 2013 12:31:43 -0800 (PST) Received: from [192.168.0.114] (cpc37-aztw23-2-0-cust35.18-1.cable.virginm.net. [94.174.128.36]) by mx.google.com with ESMTPSA id ll10sm10149761wic.9.2013.12.04.12.31.42 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 04 Dec 2013 12:31:42 -0800 (PST) Message-ID: <529F912D.4020505@apache.org> Date: Wed, 04 Dec 2013 20:31:41 +0000 From: Andy Seaborne User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: dev@clerezza.apache.org Subject: Re: FROM clause ignored by QueryExceutionFactory References: <529DD1BF.8020800@apache.org> <529E265F.4050605@apache.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org On 03/12/13 21:22, Reto Bachmann-Gm�r wrote: > On Dec 3, 2013 7:44 PM, "Andy Seaborne" wrote: >> >> On 03/12/13 12:57, Reto Bachmann-Gm�r wrote: >>> >>> Hi Andy, >>> >>> >>> On Tue, Dec 3, 2013 at 1:42 PM, Andy Seaborne wrote: >>> >>>> On 03/12/13 12:27, Reto Bachmann-Gm�r wrote: >>>> >>>>> Hello >>>>> >>>>> Encountered an issue in clerezza of which the root cause seems to be in >>>>> Jena so forearding this here. The code is using jena-core and -arq > version >>>>> 2.11. >>>>> >>>> >>>> Work for me (using TDB which, from the way the question is asked is what >>>> you are doing else the thing is meaning less as it will deref >>>> ). >>>> >>> >>> Not using TDB just giving it what seems to be a minimalistic > implementation >>> of Dataset (TcDataset wrapping clerezza TcManager): >> >> >> QueryExecutionFactory.create(, ds) >> >> will use ds as the dataset regardless. The main query engine will http > GET any FROM if you use QueryExecutionFactory.create(query) > > Not sure I understand. So the above call with ds should use the dataset as > its universe? or should it use the web and ignore froms with non-http uris? An explicitly given dataset overrides the dataset description in the query when using the general query engine. The universe is not changed. The general query engine does not do what you want in a single line. See DatasetDescription DynamicDatasets to create a dataset and then use that to query. These are used by TDB's query engine internally, but not the general one. Andy