Return-Path: X-Original-To: apmail-jena-users-archive@www.apache.org Delivered-To: apmail-jena-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EB92010CC4 for ; Fri, 7 Jun 2013 09:30:07 +0000 (UTC) Received: (qmail 67448 invoked by uid 500); 7 Jun 2013 09:30:07 -0000 Delivered-To: apmail-jena-users-archive@jena.apache.org Received: (qmail 67403 invoked by uid 500); 7 Jun 2013 09:30:03 -0000 Mailing-List: contact users-help@jena.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@jena.apache.org Delivered-To: mailing list users@jena.apache.org Received: (qmail 67395 invoked by uid 99); 7 Jun 2013 09:30:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Jun 2013 09:30:01 +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 (athena.apache.org: domain of andy.seaborne.apache@gmail.com designates 209.85.214.44 as permitted sender) Received: from [209.85.214.44] (HELO mail-bk0-f44.google.com) (209.85.214.44) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Jun 2013 09:29:55 +0000 Received: by mail-bk0-f44.google.com with SMTP id r7so2147445bkg.17 for ; Fri, 07 Jun 2013 02:29:34 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=H/VnQCmBeCmKn6vNz+Pw3rsCtC/5Y083NBv/lgEbMdA=; b=RbPHjgTY+XCLizyGiTZERKKUSZJUof61K35NDLFRRlYREFk9nc4rxtrDo8+1nvZjhT z3ctkIzgby+5ubma5a/5na/BQyIiGPn7ZE3z4Jn2baGdZMgYs2wuS5W8p/gRogAQtixx UIjtfh5DNJPDYA49ib+vu/9U9Y96xo5ANE/uJ+fKg3vKyRu8ZXOgeyMqjmdtk1q5Ie1b Pua7X0L+ZBU9Czxx4Yboe3jlyaYmHqFUxj230LBQLm6vlDyrqsE9Qzgo7w2oQHLc9RLS 2SidShXTEyqucy8o9Mp11ZGKQYJdZcJxYlJi93lmTwOt0A4ebBFIUdRvCC5sLqGjpU2V CBVw== X-Received: by 10.205.8.67 with SMTP id or3mr12312754bkb.172.1370597373904; Fri, 07 Jun 2013 02:29:33 -0700 (PDT) Received: from [192.168.0.72] (cpc37-aztw23-2-0-cust35.18-1.cable.virginmedia.com. [94.174.128.36]) by mx.google.com with ESMTPSA id hh3sm17306263bkc.5.2013.06.07.02.29.32 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 07 Jun 2013 02:29:33 -0700 (PDT) Message-ID: <51B1A7FB.4070601@apache.org> Date: Fri, 07 Jun 2013 10:29:31 +0100 From: Andy Seaborne User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6 MIME-Version: 1.0 To: "users@jena.apache.org" Subject: Future of Jena SDB Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org SDB is a Jena storage module that uses SQL databases for RDF storage. See [1] for documentation. It uses a custom database schema to store RDF; it is not a general SQL-to-RDF mapping layer. The supported databases are: Oracle, Microsoft SQL Server, DB2, PostgreSQL, MySQL, Apache Derby, H2, HSQLDB. Only Derby and HSQLDB are tested in the development build process. Both Oracle and IBM corporations provide commercial RDF solutions using Jena that are completely unrelated to SDB. TDB is faster, more scalable and better supported than SDB but there can be reasons why an SQL-backed solution is appropriate. There is no active development or maintenance of SDB from within the committer team; no committers use SDB and it imposes a cost to the team to generate separate releases. We're not receiving patches contributed to JIRA items for bugs. We are proposing: 1/ moving it into the main build so it will be part of the main distribution with limited testing. 2/ marking it as "under review / maintenance only". It will not be treated as something that can block a release, nor for any significant length of time, stop development builds. It may be pulled from the main build, and from a release, at very short notice. If moved out, the source code will still be available but no binaries (releases or development builds) will be produced. What would change SDB's status is care and attention. There are ways to enhance it, for example, pushing the work of filters into the SQL database, where possible, to improve query performance. Andy [1] http://jena.apache.org/documentation/sdb/index.html