You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by Andy Seaborne <an...@apache.org> on 2013/05/21 18:47:15 UTC

SDB future

SDB is getting some user attention but not much developer attention.  I 
was hoping that there would be a contribution to go with JENA-447 but 
nothing has come in.  I don't have the bandwidth to even answer 
questions about it properly, partly because I don't use it.  I guess 
others are in a similar position.

I do think we should be clear as to it's status.

In the future, I see these options:

1/ Add jena-sdb to the main distribution.
    (If it becomes a block on a release, remove it.)

2/ As is - release "sometimes".

3/ Dormant SDB.
    This is the last release unless some activity arises to maintain it.
    Keep the source around but move out of trunk.
    Can be built from source.

4/ Legacy SDB.
    More definite statement than (3) that it is dropped.
    Keep the source around.

For 3 and 4, where there are no plans to release again if nothing 
changes, the snapshot builds should be stopped.  Users can build from 
source if they want to but the current snapshot should not become a 
distribution-under-the-radar which I feel it becomes if there are no 
plans to make it a formal release.

Thoughts?

I'm tending towards doing this one last release then (3).

	Andy

Re: SDB future

Posted by Andy Seaborne <an...@apache.org>.
On 22/05/13 16:36, Charles Li wrote:
> Sure, Stephen.

301 Moved Permanently
Location: mailto:users@jena.a.o

> Does TDB require a relational database?

No.  It is a database, just not SQL.

	Andy

>
> Thanks!
> - Charles
>
>
> On Wed, May 22, 2013 at 5:47 AM, Stephen Owens <stephen.owens@thoughtwire.ca
>> wrote:
>
>> Charles,
>>
>> I think this query should really be on the user list rather than the dev
>> list so that other users can benefit from the answer. TDB is another good
>> option.
>>
>>
>> On Wed, May 22, 2013 at 5:35 AM, Charles Li <ch...@gmail.com>
>> wrote:
>>
>>> What are alternatives to SDB? I have a 4GB RDF/XML to load for later
>>> queries
>>>
>>> Thanks!
>>> - Charles
>>>
>>> On May 21, 2013, at 12:00 PM, Stephen Owens <
>> stephen.owens@thoughtwire.ca>
>>> wrote:
>>>
>>>> +1 for option 3 if no one currently is taking ownership of that
>> project.
>>> I think it's a useful signal to potential adopters about what they should
>>> expect.
>>>>
>>>> On 2013-05-21, at 12:47 PM, Andy Seaborne <an...@apache.org> wrote:
>>>>
>>>>> SDB is getting some user attention but not much developer attention.
>>   I
>>> was hoping that there would be a contribution to go with JENA-447 but
>>> nothing has come in.  I don't have the bandwidth to even answer questions
>>> about it properly, partly because I don't use it.  I guess others are in
>> a
>>> similar position.
>>>>>
>>>>> I do think we should be clear as to it's status.
>>>>>
>>>>> In the future, I see these options:
>>>>>
>>>>> 1/ Add jena-sdb to the main distribution.
>>>>>   (If it becomes a block on a release, remove it.)
>>>>>
>>>>> 2/ As is - release "sometimes".
>>>>>
>>>>> 3/ Dormant SDB.
>>>>>   This is the last release unless some activity arises to maintain it.
>>>>>   Keep the source around but move out of trunk.
>>>>>   Can be built from source.
>>>>>
>>>>> 4/ Legacy SDB.
>>>>>   More definite statement than (3) that it is dropped.
>>>>>   Keep the source around.
>>>>>
>>>>> For 3 and 4, where there are no plans to release again if nothing
>>> changes, the snapshot builds should be stopped.  Users can build from
>>> source if they want to but the current snapshot should not become a
>>> distribution-under-the-radar which I feel it becomes if there are no
>> plans
>>> to make it a formal release.
>>>>>
>>>>> Thoughts?
>>>>>
>>>>> I'm tending towards doing this one last release then (3).
>>>>>
>>>>>    Andy
>>>
>>
>>
>>
>> --
>> Regards,
>> *
>> *
>> *Stephen Owens*
>> CTO, ThoughtWire
>> t 647.351.9473 ext.104  I  m 416.697.3466
>>
>


Re: SDB future

Posted by Charles Li <ch...@gmail.com>.
Sure, Stephen.

Does TDB require a relational database?

Thanks!
- Charles


On Wed, May 22, 2013 at 5:47 AM, Stephen Owens <stephen.owens@thoughtwire.ca
> wrote:

> Charles,
>
> I think this query should really be on the user list rather than the dev
> list so that other users can benefit from the answer. TDB is another good
> option.
>
>
> On Wed, May 22, 2013 at 5:35 AM, Charles Li <ch...@gmail.com>
> wrote:
>
> > What are alternatives to SDB? I have a 4GB RDF/XML to load for later
> > queries
> >
> > Thanks!
> > - Charles
> >
> > On May 21, 2013, at 12:00 PM, Stephen Owens <
> stephen.owens@thoughtwire.ca>
> > wrote:
> >
> > > +1 for option 3 if no one currently is taking ownership of that
> project.
> > I think it's a useful signal to potential adopters about what they should
> > expect.
> > >
> > > On 2013-05-21, at 12:47 PM, Andy Seaborne <an...@apache.org> wrote:
> > >
> > >> SDB is getting some user attention but not much developer attention.
>  I
> > was hoping that there would be a contribution to go with JENA-447 but
> > nothing has come in.  I don't have the bandwidth to even answer questions
> > about it properly, partly because I don't use it.  I guess others are in
> a
> > similar position.
> > >>
> > >> I do think we should be clear as to it's status.
> > >>
> > >> In the future, I see these options:
> > >>
> > >> 1/ Add jena-sdb to the main distribution.
> > >>  (If it becomes a block on a release, remove it.)
> > >>
> > >> 2/ As is - release "sometimes".
> > >>
> > >> 3/ Dormant SDB.
> > >>  This is the last release unless some activity arises to maintain it.
> > >>  Keep the source around but move out of trunk.
> > >>  Can be built from source.
> > >>
> > >> 4/ Legacy SDB.
> > >>  More definite statement than (3) that it is dropped.
> > >>  Keep the source around.
> > >>
> > >> For 3 and 4, where there are no plans to release again if nothing
> > changes, the snapshot builds should be stopped.  Users can build from
> > source if they want to but the current snapshot should not become a
> > distribution-under-the-radar which I feel it becomes if there are no
> plans
> > to make it a formal release.
> > >>
> > >> Thoughts?
> > >>
> > >> I'm tending towards doing this one last release then (3).
> > >>
> > >>   Andy
> >
>
>
>
> --
> Regards,
> *
> *
> *Stephen Owens*
> CTO, ThoughtWire
> t 647.351.9473 ext.104  I  m 416.697.3466
>

Re: SDB future

Posted by Stephen Owens <st...@thoughtwire.ca>.
Charles,

I think this query should really be on the user list rather than the dev
list so that other users can benefit from the answer. TDB is another good
option.


On Wed, May 22, 2013 at 5:35 AM, Charles Li <ch...@gmail.com> wrote:

> What are alternatives to SDB? I have a 4GB RDF/XML to load for later
> queries
>
> Thanks!
> - Charles
>
> On May 21, 2013, at 12:00 PM, Stephen Owens <st...@thoughtwire.ca>
> wrote:
>
> > +1 for option 3 if no one currently is taking ownership of that project.
> I think it's a useful signal to potential adopters about what they should
> expect.
> >
> > On 2013-05-21, at 12:47 PM, Andy Seaborne <an...@apache.org> wrote:
> >
> >> SDB is getting some user attention but not much developer attention.  I
> was hoping that there would be a contribution to go with JENA-447 but
> nothing has come in.  I don't have the bandwidth to even answer questions
> about it properly, partly because I don't use it.  I guess others are in a
> similar position.
> >>
> >> I do think we should be clear as to it's status.
> >>
> >> In the future, I see these options:
> >>
> >> 1/ Add jena-sdb to the main distribution.
> >>  (If it becomes a block on a release, remove it.)
> >>
> >> 2/ As is - release "sometimes".
> >>
> >> 3/ Dormant SDB.
> >>  This is the last release unless some activity arises to maintain it.
> >>  Keep the source around but move out of trunk.
> >>  Can be built from source.
> >>
> >> 4/ Legacy SDB.
> >>  More definite statement than (3) that it is dropped.
> >>  Keep the source around.
> >>
> >> For 3 and 4, where there are no plans to release again if nothing
> changes, the snapshot builds should be stopped.  Users can build from
> source if they want to but the current snapshot should not become a
> distribution-under-the-radar which I feel it becomes if there are no plans
> to make it a formal release.
> >>
> >> Thoughts?
> >>
> >> I'm tending towards doing this one last release then (3).
> >>
> >>   Andy
>



-- 
Regards,
*
*
*Stephen Owens*
CTO, ThoughtWire
t 647.351.9473 ext.104  I  m 416.697.3466

Re: SDB future

Posted by Stephen Allen <sa...@apache.org>.
+1 for option 1.  I don't used SDB, but I think it is good to keep around
if the effort to maintain it is not too high (and I don't think that it
will).

Making it part of the release also will mean it will not suffer from
bit-rot.  Many of the times, changes are minor to port over as long as it
was the original developer doing it at the same time he makes changes
elsewhere.  Where it becomes difficult is when months go by since the
original change.

-Stephen

On Saturday, May 25, 2013, Andy Seaborne wrote:

> Yes - I'm conflicted as well, flip-flopping between opt1 and opt3.
>
> There is enough user@ traffic to suggest it's used.  I'm guessing it's
> the "SQL" part makes it easier in corp IT. TDB is faster, scales better and
> is better supported (and I'm not corp IT bound).
>
> There are ways to improve it's performance - pushing some filters into SQL
> for example - so theres scoep for development.
>
> Option 1 - add to the main distribution, remove if it becomes a block -
> means that there is no additional work on a release vote.
>
> Testing SDB using Derby only (that's what the junit does by default) is
> easy to setup because it's pulled in by maven.  It only runs embedded, not
> as a server but it does check the code generation.  Unliek other jjava SQL
> DBs, Derby implements tree join plans (the other onyl do linear join plans
> which makes some optional cases impossible - the code fall back to
> brute-force-and-ignorance in these cases). Derby is quite picky about it's
> SQL 92.  SDB tests without additional setup.
>
> We state on users@ this is the position as a indication that we stil have
> option 3 (retirement) available.  Unless we shake the tree a bit,
>
> Proposal: (option 1)
>
>   add to apache-jena, remove at the first sign of trouble.
>   make a clear statement of situation on users@ including
>     encouraging people to come forward
>   option 3 still on the cards.
>
> I've added DISCUSS to the subject line for now to leave open the
> possibility of a vote because it affects the whole project.
>
> But all PMC chipping in here is enough.
>
> I don't see a rush to make a choice just yet.
>
>         Andy
>
> On 22/05/13 11:47, Claude Warren wrote:
>
>> I am conflicted about this one.  I think we need SDB (or something
>> similar)
>> that will allow users to use standard infrastructure (shared/pooled DB is
>> fairly common).  But I don't have the bandwidth to support it.
>>
>> Is there a status where in we release SDB package with each release of
>> Jena
>> but only ensure that the current test cases work -- that is the latest
>> release doesn't break something?  Perhaps with a reduced set of supported
>> DBs (perhaps Derby & MySQL)
>>
>> If not then I think we take Andy's approach and release one more before
>> putting it on the shelf.
>>
>>
>> On Wed, May 22, 2013 at 10:35 AM, Charles Li <charlesquanli@gmail.com
>> >wrote:
>>
>>  What are alternatives to SDB? I have a 4GB RDF/XML to load for later
>>> queries
>>>
>>> Thanks!
>>> - Charles
>>>
>>> On May 21, 2013, at 12:00 PM, Stephen Owens <
>>> stephen.owens@thoughtwire.ca>
>>> wrote:
>>>
>>>  +1 for option 3 if no one currently is taking ownership of that project.
>>>>
>>> I think it's a useful signal to potential adopters about what they should
>>> expect.
>>>
>>>>
>>>> On 2013-05-21, at 12:47 PM, Andy Seaborne <an...@apache.org> wrote:
>>>>
>>>>  SDB is getting some user attention but not much developer attention.  I
>>>>>
>>>> was hoping that there would be a contribution to go with JENA-447 but
>>> nothing has come in.  I don't have the bandwidth to even answer questions
>>> about it properly, partly because I don't use it.  I guess others are in
>>> a
>>> similar position.
>>>
>>>>
>>>>> I do think we should be clear as to it's status.
>>>>>
>>>>> In the future, I see these options:
>>>>>
>>>>> 1/ Add jena-sdb to the main distribution.
>>>>>   (If it becomes a block on a release, remove it.)
>>>>>
>>>>> 2/ As is - release "sometimes".
>>>>>
>>>>> 3/ Dormant SDB.
>>>>>   This is the last release unless some activity arises to maintain it.
>>>>>   Keep the source around but move out of trunk.
>>>>>   Can be built from source.
>>>>>
>>>>> 4/ Legacy SDB.
>>>>>   More definite statement than (3) that it is dropped.
>>>>>   Keep the source around.
>>>>>
>>>>> For 3 and 4, where there are no plans to release again if nothing
>>>>>
>>>> changes, the snapshot builds should be stopped.  Users can build from
>>> source if they want to but the current snapshot should not become a
>>> distribution-under-the-radar which I feel it becomes if there are no
>>> plans
>>> to make it a formal release.
>>>
>>>>
>>>>> Thoughts?
>>>>>
>>>>> I'm tending towards doing this one last release then (3).
>>>>>
>>>>>    Andy
>>>>>
>>>>
>>>
>>
>>
>>
>

Re: [DISCUSS] SDB future

Posted by Claude Warren <cl...@xenei.com>.
+1 for option 1


On Sun, May 26, 2013 at 8:33 PM, Stephen Owens <stephen.owens@thoughtwire.ca
> wrote:

> Seems like a good alternative if it lowers the support cost enough that it
> doesn't take much to release it. It might bring an interested maintainer
> out of the woodwork if they don't want to see SDB support reduced further
> or vanish.
>
>
> On Sat, May 25, 2013 at 6:18 AM, Andy Seaborne <an...@apache.org> wrote:
>
> > Yes - I'm conflicted as well, flip-flopping between opt1 and opt3.
> >
> > There is enough user@ traffic to suggest it's used.  I'm guessing it's
> > the "SQL" part makes it easier in corp IT. TDB is faster, scales better
> and
> > is better supported (and I'm not corp IT bound).
> >
> > There are ways to improve it's performance - pushing some filters into
> SQL
> > for example - so theres scoep for development.
> >
> > Option 1 - add to the main distribution, remove if it becomes a block -
> > means that there is no additional work on a release vote.
> >
> > Testing SDB using Derby only (that's what the junit does by default) is
> > easy to setup because it's pulled in by maven.  It only runs embedded,
> not
> > as a server but it does check the code generation.  Unliek other jjava
> SQL
> > DBs, Derby implements tree join plans (the other onyl do linear join
> plans
> > which makes some optional cases impossible - the code fall back to
> > brute-force-and-ignorance in these cases). Derby is quite picky about
> it's
> > SQL 92.  SDB tests without additional setup.
> >
> > We state on users@ this is the position as a indication that we stil
> have
> > option 3 (retirement) available.  Unless we shake the tree a bit,
> >
> > Proposal: (option 1)
> >
> >   add to apache-jena, remove at the first sign of trouble.
> >   make a clear statement of situation on users@ including
> >     encouraging people to come forward
> >   option 3 still on the cards.
> >
> > I've added DISCUSS to the subject line for now to leave open the
> > possibility of a vote because it affects the whole project.
> >
> > But all PMC chipping in here is enough.
> >
> > I don't see a rush to make a choice just yet.
> >
> >         Andy
> >
> > On 22/05/13 11:47, Claude Warren wrote:
> >
> >> I am conflicted about this one.  I think we need SDB (or something
> >> similar)
> >> that will allow users to use standard infrastructure (shared/pooled DB
> is
> >> fairly common).  But I don't have the bandwidth to support it.
> >>
> >> Is there a status where in we release SDB package with each release of
> >> Jena
> >> but only ensure that the current test cases work -- that is the latest
> >> release doesn't break something?  Perhaps with a reduced set of
> supported
> >> DBs (perhaps Derby & MySQL)
> >>
> >> If not then I think we take Andy's approach and release one more before
> >> putting it on the shelf.
> >>
> >>
> >> On Wed, May 22, 2013 at 10:35 AM, Charles Li <charlesquanli@gmail.com
> >**
> >> wrote:
> >>
> >>  What are alternatives to SDB? I have a 4GB RDF/XML to load for later
> >>> queries
> >>>
> >>> Thanks!
> >>> - Charles
> >>>
> >>> On May 21, 2013, at 12:00 PM, Stephen Owens <
> >>> stephen.owens@thoughtwire.ca>
> >>> wrote:
> >>>
> >>>  +1 for option 3 if no one currently is taking ownership of that
> project.
> >>>>
> >>> I think it's a useful signal to potential adopters about what they
> should
> >>> expect.
> >>>
> >>>>
> >>>> On 2013-05-21, at 12:47 PM, Andy Seaborne <an...@apache.org> wrote:
> >>>>
> >>>>  SDB is getting some user attention but not much developer attention.
>  I
> >>>>>
> >>>> was hoping that there would be a contribution to go with JENA-447 but
> >>> nothing has come in.  I don't have the bandwidth to even answer
> questions
> >>> about it properly, partly because I don't use it.  I guess others are
> in
> >>> a
> >>> similar position.
> >>>
> >>>>
> >>>>> I do think we should be clear as to it's status.
> >>>>>
> >>>>> In the future, I see these options:
> >>>>>
> >>>>> 1/ Add jena-sdb to the main distribution.
> >>>>>   (If it becomes a block on a release, remove it.)
> >>>>>
> >>>>> 2/ As is - release "sometimes".
> >>>>>
> >>>>> 3/ Dormant SDB.
> >>>>>   This is the last release unless some activity arises to maintain
> it.
> >>>>>   Keep the source around but move out of trunk.
> >>>>>   Can be built from source.
> >>>>>
> >>>>> 4/ Legacy SDB.
> >>>>>   More definite statement than (3) that it is dropped.
> >>>>>   Keep the source around.
> >>>>>
> >>>>> For 3 and 4, where there are no plans to release again if nothing
> >>>>>
> >>>> changes, the snapshot builds should be stopped.  Users can build from
> >>> source if they want to but the current snapshot should not become a
> >>> distribution-under-the-radar which I feel it becomes if there are no
> >>> plans
> >>> to make it a formal release.
> >>>
> >>>>
> >>>>> Thoughts?
> >>>>>
> >>>>> I'm tending towards doing this one last release then (3).
> >>>>>
> >>>>>    Andy
> >>>>>
> >>>>
> >>>
> >>
> >>
> >>
> >
>
>
> --
> Regards,
> *
> *
> *Stephen Owens*
> CTO, ThoughtWire
> t 647.351.9473 ext.104  I  m 416.697.3466
>



-- 
I like: Like Like - The likeliest place on the web<http://like-like.xenei.com>
Identity: https://www.identify.nu/user.php?claude@xenei.com
LinkedIn: http://www.linkedin.com/in/claudewarren

Re: [DISCUSS] SDB future

Posted by Stephen Owens <st...@thoughtwire.ca>.
Seems like a good alternative if it lowers the support cost enough that it
doesn't take much to release it. It might bring an interested maintainer
out of the woodwork if they don't want to see SDB support reduced further
or vanish.


On Sat, May 25, 2013 at 6:18 AM, Andy Seaborne <an...@apache.org> wrote:

> Yes - I'm conflicted as well, flip-flopping between opt1 and opt3.
>
> There is enough user@ traffic to suggest it's used.  I'm guessing it's
> the "SQL" part makes it easier in corp IT. TDB is faster, scales better and
> is better supported (and I'm not corp IT bound).
>
> There are ways to improve it's performance - pushing some filters into SQL
> for example - so theres scoep for development.
>
> Option 1 - add to the main distribution, remove if it becomes a block -
> means that there is no additional work on a release vote.
>
> Testing SDB using Derby only (that's what the junit does by default) is
> easy to setup because it's pulled in by maven.  It only runs embedded, not
> as a server but it does check the code generation.  Unliek other jjava SQL
> DBs, Derby implements tree join plans (the other onyl do linear join plans
> which makes some optional cases impossible - the code fall back to
> brute-force-and-ignorance in these cases). Derby is quite picky about it's
> SQL 92.  SDB tests without additional setup.
>
> We state on users@ this is the position as a indication that we stil have
> option 3 (retirement) available.  Unless we shake the tree a bit,
>
> Proposal: (option 1)
>
>   add to apache-jena, remove at the first sign of trouble.
>   make a clear statement of situation on users@ including
>     encouraging people to come forward
>   option 3 still on the cards.
>
> I've added DISCUSS to the subject line for now to leave open the
> possibility of a vote because it affects the whole project.
>
> But all PMC chipping in here is enough.
>
> I don't see a rush to make a choice just yet.
>
>         Andy
>
> On 22/05/13 11:47, Claude Warren wrote:
>
>> I am conflicted about this one.  I think we need SDB (or something
>> similar)
>> that will allow users to use standard infrastructure (shared/pooled DB is
>> fairly common).  But I don't have the bandwidth to support it.
>>
>> Is there a status where in we release SDB package with each release of
>> Jena
>> but only ensure that the current test cases work -- that is the latest
>> release doesn't break something?  Perhaps with a reduced set of supported
>> DBs (perhaps Derby & MySQL)
>>
>> If not then I think we take Andy's approach and release one more before
>> putting it on the shelf.
>>
>>
>> On Wed, May 22, 2013 at 10:35 AM, Charles Li <ch...@gmail.com>**
>> wrote:
>>
>>  What are alternatives to SDB? I have a 4GB RDF/XML to load for later
>>> queries
>>>
>>> Thanks!
>>> - Charles
>>>
>>> On May 21, 2013, at 12:00 PM, Stephen Owens <
>>> stephen.owens@thoughtwire.ca>
>>> wrote:
>>>
>>>  +1 for option 3 if no one currently is taking ownership of that project.
>>>>
>>> I think it's a useful signal to potential adopters about what they should
>>> expect.
>>>
>>>>
>>>> On 2013-05-21, at 12:47 PM, Andy Seaborne <an...@apache.org> wrote:
>>>>
>>>>  SDB is getting some user attention but not much developer attention.  I
>>>>>
>>>> was hoping that there would be a contribution to go with JENA-447 but
>>> nothing has come in.  I don't have the bandwidth to even answer questions
>>> about it properly, partly because I don't use it.  I guess others are in
>>> a
>>> similar position.
>>>
>>>>
>>>>> I do think we should be clear as to it's status.
>>>>>
>>>>> In the future, I see these options:
>>>>>
>>>>> 1/ Add jena-sdb to the main distribution.
>>>>>   (If it becomes a block on a release, remove it.)
>>>>>
>>>>> 2/ As is - release "sometimes".
>>>>>
>>>>> 3/ Dormant SDB.
>>>>>   This is the last release unless some activity arises to maintain it.
>>>>>   Keep the source around but move out of trunk.
>>>>>   Can be built from source.
>>>>>
>>>>> 4/ Legacy SDB.
>>>>>   More definite statement than (3) that it is dropped.
>>>>>   Keep the source around.
>>>>>
>>>>> For 3 and 4, where there are no plans to release again if nothing
>>>>>
>>>> changes, the snapshot builds should be stopped.  Users can build from
>>> source if they want to but the current snapshot should not become a
>>> distribution-under-the-radar which I feel it becomes if there are no
>>> plans
>>> to make it a formal release.
>>>
>>>>
>>>>> Thoughts?
>>>>>
>>>>> I'm tending towards doing this one last release then (3).
>>>>>
>>>>>    Andy
>>>>>
>>>>
>>>
>>
>>
>>
>


-- 
Regards,
*
*
*Stephen Owens*
CTO, ThoughtWire
t 647.351.9473 ext.104  I  m 416.697.3466

Re: [DISCUSS] SDB future

Posted by Andy Seaborne <an...@apache.org>.
On 29/05/13 03:27, Holger Knublauch wrote:
> At TopQuadrant we do use and recommend SDB for enterprise solutions,
> mainly due to the fact that customers can rely on their existing SQL
> infrastructure. Performance is not a direct issue for us because we
> apply a caching layer on top of it (currently a home-grown in-memory
> cache, but in the future possibly TDB). We do have a growing
> installation base of successful deployments (TopBraid EVN) and customers
> seem to be happy. Having to rely on commercial alternatives would affect
> the overall price tag of our solutions, and having an open source
> solution that seamlessly works with Jena is a great asset.
>
> I have brought up the topic of this thread in our management to see
> whether we can allocate any resources to its future, but I cannot report
> any decision at this stage.
>
> Thanks,
> Holger
>

Ping?

	Andy


Re: [DISCUSS] SDB future

Posted by Andy Seaborne <an...@apache.org>.
On 06/06/13 08:25, Holger Knublauch wrote:
> On 6/5/2013 22:13, Andy Seaborne wrote:
>> On 29/05/13 03:27, Holger Knublauch wrote:
>>> At TopQuadrant we do use and recommend SDB for enterprise solutions,
>>> mainly due to the fact that customers can rely on their existing SQL
>>> infrastructure. Performance is not a direct issue for us because we
>>> apply a caching layer on top of it (currently a home-grown in-memory
>>> cache, but in the future possibly TDB). We do have a growing
>>> installation base of successful deployments (TopBraid EVN) and customers
>>> seem to be happy. Having to rely on commercial alternatives would affect
>>> the overall price tag of our solutions, and having an open source
>>> solution that seamlessly works with Jena is a great asset.
>>
>> What is cached?
>
> We put a GraphMem over each SDB, and this GraphMem remembers (i.e.
> copies) all triples that have already been queried. So if someone
> queried (ex:A ?p ?o) then we download all those triples. Then, more
> specific queries against (ex:A rdfs:label ?o) can already be answered by
> the cache alone. Writes are passed through into the SDB. In TopBraid
> EVN, where models are typically at most tens of millions of triple
> large, we just cache all at the start of the server, and use SDB as the
> master backup only. This works well for our use cases, and feels safer
> than TDB (where it used to be easy to corrupt data, at least in the
> older versions; we haven't upgraded for a while yet it's easier to
> convince IT departments of relying on their SQL infrastructure than some
> file drives).

When cached at the start, SDB is used a persistent copy of a graph held 
in memory.  That would be an interesting use case for the diff format - 
you could write deltas to disk as an in-memory graph changed then be 
able to get it again at start-up by applying the diff to the original. 
Periodically, out-of-band, read th graph and diff (the journal), write 
the up-to-date graph and remove the old version and the journal.

TDB has ACID transactions since 0.9.X

	Andy

>
> Holger
>


Re: [DISCUSS] SDB future

Posted by Holger Knublauch <ho...@knublauch.com>.
On 6/5/2013 22:13, Andy Seaborne wrote:
> On 29/05/13 03:27, Holger Knublauch wrote:
>> At TopQuadrant we do use and recommend SDB for enterprise solutions,
>> mainly due to the fact that customers can rely on their existing SQL
>> infrastructure. Performance is not a direct issue for us because we
>> apply a caching layer on top of it (currently a home-grown in-memory
>> cache, but in the future possibly TDB). We do have a growing
>> installation base of successful deployments (TopBraid EVN) and customers
>> seem to be happy. Having to rely on commercial alternatives would affect
>> the overall price tag of our solutions, and having an open source
>> solution that seamlessly works with Jena is a great asset.
>
> What is cached?

We put a GraphMem over each SDB, and this GraphMem remembers (i.e. 
copies) all triples that have already been queried. So if someone 
queried (ex:A ?p ?o) then we download all those triples. Then, more 
specific queries against (ex:A rdfs:label ?o) can already be answered by 
the cache alone. Writes are passed through into the SDB. In TopBraid 
EVN, where models are typically at most tens of millions of triple 
large, we just cache all at the start of the server, and use SDB as the 
master backup only. This works well for our use cases, and feels safer 
than TDB (where it used to be easy to corrupt data, at least in the 
older versions; we haven't upgraded for a while yet it's easier to 
convince IT departments of relying on their SQL infrastructure than some 
file drives).

Holger


Re: [DISCUSS] SDB future

Posted by Andy Seaborne <an...@apache.org>.
On 29/05/13 03:27, Holger Knublauch wrote:
> At TopQuadrant we do use and recommend SDB for enterprise solutions,
> mainly due to the fact that customers can rely on their existing SQL
> infrastructure. Performance is not a direct issue for us because we
> apply a caching layer on top of it (currently a home-grown in-memory
> cache, but in the future possibly TDB). We do have a growing
> installation base of successful deployments (TopBraid EVN) and customers
> seem to be happy. Having to rely on commercial alternatives would affect
> the overall price tag of our solutions, and having an open source
> solution that seamlessly works with Jena is a great asset.

What is cached?  Triples? or graphs? or parts of graphs?  (I'm wondering 
if GSP (SPARQL Graph Store Protocol) is an option - if graphs are the 
unit, and SDB is a graph date management layer,

GSP over SQL is really very simple and may be a useful tool in the toolbox.

(or indeed over NoSQL KV-store)

> I have brought up the topic of this thread in our management to see
> whether we can allocate any resources to its future, but I cannot report
> any decision at this stage.

Interesting - do let us know how that goes.  TQ have also mentioned 
extensions to SDB, for example multiple datasets in one SQL database.

	Andy

>
> Thanks,
> Holger
>
>
>
> On 5/28/2013 0:43, Simon Helsen wrote:
>> Andy, others,
>>
>> we do not use SDB because it is way too slow for us. Although I'm sure it
>> can be improved as you suggested below, we do not believe it will ever
>> come close to TDBs performance because of how SDB is designed. The
>> fact it
>> is used at all keeps surprising me, but it probably doesn't matter for
>> simple use cases especially if the dataset remains small. Btw, a little
>> while back we were reconsidering it because SDB supports multiple vendors
>> and our use-case was not very performance sensitive, but it turned out
>> that it was still too slow for our needs
>>
>> As for motivations why some people may prefer SDB over TDB, I don't think
>> it is just "SQL" and corporate acceptance. There are some very good
>> reasons why file-based systems like TDB are difficult to use in
>> commercial
>> deployments. Corporate Java-based server deployments are almost always
>> based on one or more app servers (JEE, but sometimes just a regular web
>> server) where *all* persisted state goes into a relational database.
>> Storing state on the file system is generally taboo for many reasons
>> including: The inability to cluster the app server - a critical step to
>> scale up beyond a few hundred users; the fact that organizations
>> generally
>> have a hard time understanding and managing file system state as opposed
>> to standard relational database management. For instance, how do you
>> perform online backups and when and how does the state corrupt. For
>> instance, on a DB server, admins are watchful for running out of disk
>> space. This sort of monitoring is usually less critical on the app
>> server,
>> but now, suddenly, there is this growing "thing" they have to backup
>> because it will corrupt if you run out of disk space. On top of that, DB
>> servers usually use very fast and expensive disk systems (RAIDs, SSDs,
>> etc.) This is usually not the case for the app server. On top of that,
>> when customers realize there is this large set of data on the file
>> system,
>> they have a tendency to put it on larger disks connected via NFS,
>> which is
>> unfortunately very dangerous because even short network glitches can
>> corrupt TDB. All of this is manageable if you carefully encapsulate TDB
>> and provide good administration tools on top of your system, but it is
>> not
>> trivial, and it doesn't come out of the box. Especially cluster
>> management
>> is quite tricky as you can imagine.
>>
>> Just wanted to set that out there as to why SQL-based systems remain
>> attractive. I would advise though to more clearly state on the SDB
>> download page that SDB is deprecated and no longer actively supported
>> (unless that changes of course)
>>
>> Simon
>>
>>
>>
>> From:
>> Andy Seaborne <an...@apache.org>
>> To:
>> dev@jena.apache.org,
>> Date:
>> 05/25/2013 06:19 AM
>> Subject:
>> [DISCUSS] SDB future
>>
>>
>>
>> Yes - I'm conflicted as well, flip-flopping between opt1 and opt3.
>>
>> There is enough user@ traffic to suggest it's used.  I'm guessing it's
>> the "SQL" part makes it easier in corp IT. TDB is faster, scales better
>> and is better supported (and I'm not corp IT bound).
>>
>> There are ways to improve it's performance - pushing some filters into
>> SQL for example - so theres scoep for development.
>>
>> Option 1 - add to the main distribution, remove if it becomes a block -
>> means that there is no additional work on a release vote.
>>
>> Testing SDB using Derby only (that's what the junit does by default) is
>> easy to setup because it's pulled in by maven.  It only runs embedded,
>> not as a server but it does check the code generation.  Unliek other
>> jjava SQL DBs, Derby implements tree join plans (the other onyl do
>> linear join plans which makes some optional cases impossible - the code
>> fall back to brute-force-and-ignorance in these cases). Derby is quite
>> picky about it's SQL 92.  SDB tests without additional setup.
>>
>> We state on users@ this is the position as a indication that we stil
>> have option 3 (retirement) available.  Unless we shake the tree a bit,
>>
>> Proposal: (option 1)
>>
>>     add to apache-jena, remove at the first sign of trouble.
>>     make a clear statement of situation on users@ including
>>       encouraging people to come forward
>>     option 3 still on the cards.
>>
>> I've added DISCUSS to the subject line for now to leave open the
>> possibility of a vote because it affects the whole project.
>>
>> But all PMC chipping in here is enough.
>>
>> I don't see a rush to make a choice just yet.
>>
>>                   Andy
>>
>> On 22/05/13 11:47, Claude Warren wrote:
>>> I am conflicted about this one.  I think we need SDB (or something
>> similar)
>>> that will allow users to use standard infrastructure (shared/pooled DB
>> is
>>> fairly common).  But I don't have the bandwidth to support it.
>>>
>>> Is there a status where in we release SDB package with each release of
>> Jena
>>> but only ensure that the current test cases work -- that is the latest
>>> release doesn't break something?  Perhaps with a reduced set of
>> supported
>>> DBs (perhaps Derby & MySQL)
>>>
>>> If not then I think we take Andy's approach and release one more before
>>> putting it on the shelf.
>>>
>>>
>>> On Wed, May 22, 2013 at 10:35 AM, Charles Li
>> <ch...@gmail.com>wrote:
>>>> What are alternatives to SDB? I have a 4GB RDF/XML to load for later
>>>> queries
>>>>
>>>> Thanks!
>>>> - Charles
>>>>
>>>> On May 21, 2013, at 12:00 PM, Stephen Owens
>> <st...@thoughtwire.ca>
>>>> wrote:
>>>>
>>>>> +1 for option 3 if no one currently is taking ownership of that
>> project.
>>>> I think it's a useful signal to potential adopters about what they
>> should
>>>> expect.
>>>>> On 2013-05-21, at 12:47 PM, Andy Seaborne <an...@apache.org> wrote:
>>>>>
>>>>>> SDB is getting some user attention but not much developer attention.
>> I
>>>> was hoping that there would be a contribution to go with JENA-447 but
>>>> nothing has come in.  I don't have the bandwidth to even answer
>> questions
>>>> about it properly, partly because I don't use it.  I guess others are
>> in a
>>>> similar position.
>>>>>> I do think we should be clear as to it's status.
>>>>>>
>>>>>> In the future, I see these options:
>>>>>>
>>>>>> 1/ Add jena-sdb to the main distribution.
>>>>>>    (If it becomes a block on a release, remove it.)
>>>>>>
>>>>>> 2/ As is - release "sometimes".
>>>>>>
>>>>>> 3/ Dormant SDB.
>>>>>>    This is the last release unless some activity arises to maintain
>> it.
>>>>>>    Keep the source around but move out of trunk.
>>>>>>    Can be built from source.
>>>>>>
>>>>>> 4/ Legacy SDB.
>>>>>>    More definite statement than (3) that it is dropped.
>>>>>>    Keep the source around.
>>>>>>
>>>>>> For 3 and 4, where there are no plans to release again if nothing
>>>> changes, the snapshot builds should be stopped.  Users can build from
>>>> source if they want to but the current snapshot should not become a
>>>> distribution-under-the-radar which I feel it becomes if there are no
>> plans
>>>> to make it a formal release.
>>>>>> Thoughts?
>>>>>>
>>>>>> I'm tending towards doing this one last release then (3).
>>>>>>
>>>>>>     Andy
>>>
>>>
>>
>>
>>
>


Re: [DISCUSS] SDB future

Posted by Holger Knublauch <ho...@knublauch.com>.
At TopQuadrant we do use and recommend SDB for enterprise solutions, 
mainly due to the fact that customers can rely on their existing SQL 
infrastructure. Performance is not a direct issue for us because we 
apply a caching layer on top of it (currently a home-grown in-memory 
cache, but in the future possibly TDB). We do have a growing 
installation base of successful deployments (TopBraid EVN) and customers 
seem to be happy. Having to rely on commercial alternatives would affect 
the overall price tag of our solutions, and having an open source 
solution that seamlessly works with Jena is a great asset.

I have brought up the topic of this thread in our management to see 
whether we can allocate any resources to its future, but I cannot report 
any decision at this stage.

Thanks,
Holger



On 5/28/2013 0:43, Simon Helsen wrote:
> Andy, others,
>
> we do not use SDB because it is way too slow for us. Although I'm sure it
> can be improved as you suggested below, we do not believe it will ever
> come close to TDBs performance because of how SDB is designed. The fact it
> is used at all keeps surprising me, but it probably doesn't matter for
> simple use cases especially if the dataset remains small. Btw, a little
> while back we were reconsidering it because SDB supports multiple vendors
> and our use-case was not very performance sensitive, but it turned out
> that it was still too slow for our needs
>
> As for motivations why some people may prefer SDB over TDB, I don't think
> it is just "SQL" and corporate acceptance. There are some very good
> reasons why file-based systems like TDB are difficult to use in commercial
> deployments. Corporate Java-based server deployments are almost always
> based on one or more app servers (JEE, but sometimes just a regular web
> server) where *all* persisted state goes into a relational database.
> Storing state on the file system is generally taboo for many reasons
> including: The inability to cluster the app server - a critical step to
> scale up beyond a few hundred users; the fact that organizations generally
> have a hard time understanding and managing file system state as opposed
> to standard relational database management. For instance, how do you
> perform online backups and when and how does the state corrupt. For
> instance, on a DB server, admins are watchful for running out of disk
> space. This sort of monitoring is usually less critical on the app server,
> but now, suddenly, there is this growing "thing" they have to backup
> because it will corrupt if you run out of disk space. On top of that, DB
> servers usually use very fast and expensive disk systems (RAIDs, SSDs,
> etc.) This is usually not the case for the app server. On top of that,
> when customers realize there is this large set of data on the file system,
> they have a tendency to put it on larger disks connected via NFS, which is
> unfortunately very dangerous because even short network glitches can
> corrupt TDB. All of this is manageable if you carefully encapsulate TDB
> and provide good administration tools on top of your system, but it is not
> trivial, and it doesn't come out of the box. Especially cluster management
> is quite tricky as you can imagine.
>
> Just wanted to set that out there as to why SQL-based systems remain
> attractive. I would advise though to more clearly state on the SDB
> download page that SDB is deprecated and no longer actively supported
> (unless that changes of course)
>
> Simon
>
>
>
> From:
> Andy Seaborne <an...@apache.org>
> To:
> dev@jena.apache.org,
> Date:
> 05/25/2013 06:19 AM
> Subject:
> [DISCUSS] SDB future
>
>
>
> Yes - I'm conflicted as well, flip-flopping between opt1 and opt3.
>
> There is enough user@ traffic to suggest it's used.  I'm guessing it's
> the "SQL" part makes it easier in corp IT. TDB is faster, scales better
> and is better supported (and I'm not corp IT bound).
>
> There are ways to improve it's performance - pushing some filters into
> SQL for example - so theres scoep for development.
>
> Option 1 - add to the main distribution, remove if it becomes a block -
> means that there is no additional work on a release vote.
>
> Testing SDB using Derby only (that's what the junit does by default) is
> easy to setup because it's pulled in by maven.  It only runs embedded,
> not as a server but it does check the code generation.  Unliek other
> jjava SQL DBs, Derby implements tree join plans (the other onyl do
> linear join plans which makes some optional cases impossible - the code
> fall back to brute-force-and-ignorance in these cases). Derby is quite
> picky about it's SQL 92.  SDB tests without additional setup.
>
> We state on users@ this is the position as a indication that we stil
> have option 3 (retirement) available.  Unless we shake the tree a bit,
>
> Proposal: (option 1)
>
>     add to apache-jena, remove at the first sign of trouble.
>     make a clear statement of situation on users@ including
>       encouraging people to come forward
>     option 3 still on the cards.
>
> I've added DISCUSS to the subject line for now to leave open the
> possibility of a vote because it affects the whole project.
>
> But all PMC chipping in here is enough.
>
> I don't see a rush to make a choice just yet.
>
>                   Andy
>
> On 22/05/13 11:47, Claude Warren wrote:
>> I am conflicted about this one.  I think we need SDB (or something
> similar)
>> that will allow users to use standard infrastructure (shared/pooled DB
> is
>> fairly common).  But I don't have the bandwidth to support it.
>>
>> Is there a status where in we release SDB package with each release of
> Jena
>> but only ensure that the current test cases work -- that is the latest
>> release doesn't break something?  Perhaps with a reduced set of
> supported
>> DBs (perhaps Derby & MySQL)
>>
>> If not then I think we take Andy's approach and release one more before
>> putting it on the shelf.
>>
>>
>> On Wed, May 22, 2013 at 10:35 AM, Charles Li
> <ch...@gmail.com>wrote:
>>> What are alternatives to SDB? I have a 4GB RDF/XML to load for later
>>> queries
>>>
>>> Thanks!
>>> - Charles
>>>
>>> On May 21, 2013, at 12:00 PM, Stephen Owens
> <st...@thoughtwire.ca>
>>> wrote:
>>>
>>>> +1 for option 3 if no one currently is taking ownership of that
> project.
>>> I think it's a useful signal to potential adopters about what they
> should
>>> expect.
>>>> On 2013-05-21, at 12:47 PM, Andy Seaborne <an...@apache.org> wrote:
>>>>
>>>>> SDB is getting some user attention but not much developer attention.
> I
>>> was hoping that there would be a contribution to go with JENA-447 but
>>> nothing has come in.  I don't have the bandwidth to even answer
> questions
>>> about it properly, partly because I don't use it.  I guess others are
> in a
>>> similar position.
>>>>> I do think we should be clear as to it's status.
>>>>>
>>>>> In the future, I see these options:
>>>>>
>>>>> 1/ Add jena-sdb to the main distribution.
>>>>>    (If it becomes a block on a release, remove it.)
>>>>>
>>>>> 2/ As is - release "sometimes".
>>>>>
>>>>> 3/ Dormant SDB.
>>>>>    This is the last release unless some activity arises to maintain
> it.
>>>>>    Keep the source around but move out of trunk.
>>>>>    Can be built from source.
>>>>>
>>>>> 4/ Legacy SDB.
>>>>>    More definite statement than (3) that it is dropped.
>>>>>    Keep the source around.
>>>>>
>>>>> For 3 and 4, where there are no plans to release again if nothing
>>> changes, the snapshot builds should be stopped.  Users can build from
>>> source if they want to but the current snapshot should not become a
>>> distribution-under-the-radar which I feel it becomes if there are no
> plans
>>> to make it a formal release.
>>>>> Thoughts?
>>>>>
>>>>> I'm tending towards doing this one last release then (3).
>>>>>
>>>>>     Andy
>>
>>
>
>
>


Re: [DISCUSS] SDB future

Posted by Dave Reynolds <da...@gmail.com>.
On 05/06/13 11:38, Andy Seaborne wrote:
> Proposal for next steps:
>
> 1/ Send message to users@j.a.o about the status of SDB - draft text below.
>
> 2/ Move jena-sdb to trunk, incorporate into build.
>     Remove if it causes trouble.
>
>
> Getting the tone of this right is important - I'd appreciate comments
> and fine tuning as much as possible here.
>
> -----------------
> Subject: Future of SDB
>
> 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 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

+1

Tone and content look just right to me.

Dave


Re: [DISCUSS] SDB future

Posted by Andy Seaborne <an...@apache.org>.
Proposal for next steps:

1/ Send message to users@j.a.o about the status of SDB - draft text below.

2/ Move jena-sdb to trunk, incorporate into build.
    Remove if it causes trouble.


Getting the tone of this right is important - I'd appreciate comments 
and fine tuning as much as possible here.

-----------------
Subject: Future of SDB

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 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

Re: [DISCUSS] SDB future

Posted by Andy Seaborne <an...@apache.org>.

On 28/05/13 18:22, Rob Vesse wrote:
> Personally I would vote for Option 3, none of us are maintaining it nor do
> we have the time/interest to do so.  To continue to put out releases
> implies a level of support that does not really exist.
>
> Over in dotNetRDF we long ago abandoned any use of SQL backed storage
> because it just doesn't scale as well as a native triple store.
>
> I understand the points about why people may prefer SDB over TDB but
> whatever we choose to do we should start making it clear to people that
> SDB is deprecated/dormant and we recommend they investigate other
> alternatives.
>
> Let's also be clear that TDB is not the only alternative it is just the
> one that comes with Jena.  Most of the big triple store vendors have Jena
> providers that will let you access commercially developed triple stores
> via Jena (e.g. Virtuoso, Stardog, OWLIM, Oracle, IBM DB2 etc).  Many of
> these commercial stores include the type of clustering, replication and
> failover capabilities that Simon is highlighting as being desirable in
> highly scalable production scenarios.

Good point that there is Jena-as-client, able to work with any SPARQL 
compliant system (that's what standards are for, right?!), 
Jena-as-framework (additional storage options) and 
Jena-as-database-provider + Jena-as-SPARQL server.  This may not come 
across clearly enough - if not, what can we do to fix that?

	Andy

>
> Rob
>
>
>
> On 5/27/13 7:43 AM, "Simon Helsen" <sh...@ca.ibm.com> wrote:
>
>> Andy, others,
>>
>> we do not use SDB because it is way too slow for us. Although I'm sure it
>> can be improved as you suggested below, we do not believe it will ever
>> come close to TDBs performance because of how SDB is designed. The fact
>> it
>> is used at all keeps surprising me, but it probably doesn't matter for
>> simple use cases especially if the dataset remains small. Btw, a little
>> while back we were reconsidering it because SDB supports multiple vendors
>> and our use-case was not very performance sensitive, but it turned out
>> that it was still too slow for our needs
>>
>> As for motivations why some people may prefer SDB over TDB, I don't think
>> it is just "SQL" and corporate acceptance. There are some very good
>> reasons why file-based systems like TDB are difficult to use in
>> commercial
>> deployments. Corporate Java-based server deployments are almost always
>> based on one or more app servers (JEE, but sometimes just a regular web
>> server) where *all* persisted state goes into a relational database.
>> Storing state on the file system is generally taboo for many reasons
>> including: The inability to cluster the app server - a critical step to
>> scale up beyond a few hundred users; the fact that organizations
>> generally
>> have a hard time understanding and managing file system state as opposed
>> to standard relational database management. For instance, how do you
>> perform online backups and when and how does the state corrupt. For
>> instance, on a DB server, admins are watchful for running out of disk
>> space. This sort of monitoring is usually less critical on the app
>> server,
>> but now, suddenly, there is this growing "thing" they have to backup
>> because it will corrupt if you run out of disk space. On top of that, DB
>> servers usually use very fast and expensive disk systems (RAIDs, SSDs,
>> etc.) This is usually not the case for the app server. On top of that,
>> when customers realize there is this large set of data on the file
>> system,
>> they have a tendency to put it on larger disks connected via NFS, which
>> is
>> unfortunately very dangerous because even short network glitches can
>> corrupt TDB. All of this is manageable if you carefully encapsulate TDB
>> and provide good administration tools on top of your system, but it is
>> not
>> trivial, and it doesn't come out of the box. Especially cluster
>> management
>> is quite tricky as you can imagine.
>>
>> Just wanted to set that out there as to why SQL-based systems remain
>> attractive. I would advise though to more clearly state on the SDB
>> download page that SDB is deprecated and no longer actively supported
>> (unless that changes of course)
>>
>> Simon
>>
>>
>>
>> From:
>> Andy Seaborne <an...@apache.org>
>> To:
>> dev@jena.apache.org,
>> Date:
>> 05/25/2013 06:19 AM
>> Subject:
>> [DISCUSS] SDB future
>>
>>
>>
>> Yes - I'm conflicted as well, flip-flopping between opt1 and opt3.
>>
>> There is enough user@ traffic to suggest it's used.  I'm guessing it's
>> the "SQL" part makes it easier in corp IT. TDB is faster, scales better
>> and is better supported (and I'm not corp IT bound).
>>
>> There are ways to improve it's performance - pushing some filters into
>> SQL for example - so theres scoep for development.
>>
>> Option 1 - add to the main distribution, remove if it becomes a block -
>> means that there is no additional work on a release vote.
>>
>> Testing SDB using Derby only (that's what the junit does by default) is
>> easy to setup because it's pulled in by maven.  It only runs embedded,
>> not as a server but it does check the code generation.  Unliek other
>> jjava SQL DBs, Derby implements tree join plans (the other onyl do
>> linear join plans which makes some optional cases impossible - the code
>> fall back to brute-force-and-ignorance in these cases). Derby is quite
>> picky about it's SQL 92.  SDB tests without additional setup.
>>
>> We state on users@ this is the position as a indication that we stil
>> have option 3 (retirement) available.  Unless we shake the tree a bit,
>>
>> Proposal: (option 1)
>>
>>    add to apache-jena, remove at the first sign of trouble.
>>    make a clear statement of situation on users@ including
>>      encouraging people to come forward
>>    option 3 still on the cards.
>>
>> I've added DISCUSS to the subject line for now to leave open the
>> possibility of a vote because it affects the whole project.
>>
>> But all PMC chipping in here is enough.
>>
>> I don't see a rush to make a choice just yet.
>>
>>                  Andy
>>
>> On 22/05/13 11:47, Claude Warren wrote:
>>> I am conflicted about this one.  I think we need SDB (or something
>> similar)
>>> that will allow users to use standard infrastructure (shared/pooled DB
>> is
>>> fairly common).  But I don't have the bandwidth to support it.
>>>
>>> Is there a status where in we release SDB package with each release of
>> Jena
>>> but only ensure that the current test cases work -- that is the latest
>>> release doesn't break something?  Perhaps with a reduced set of
>> supported
>>> DBs (perhaps Derby & MySQL)
>>>
>>> If not then I think we take Andy's approach and release one more before
>>> putting it on the shelf.
>>>
>>>
>>> On Wed, May 22, 2013 at 10:35 AM, Charles Li
>> <ch...@gmail.com>wrote:
>>>
>>>> What are alternatives to SDB? I have a 4GB RDF/XML to load for later
>>>> queries
>>>>
>>>> Thanks!
>>>> - Charles
>>>>
>>>> On May 21, 2013, at 12:00 PM, Stephen Owens
>> <st...@thoughtwire.ca>
>>>> wrote:
>>>>
>>>>> +1 for option 3 if no one currently is taking ownership of that
>> project.
>>>> I think it's a useful signal to potential adopters about what they
>> should
>>>> expect.
>>>>>
>>>>> On 2013-05-21, at 12:47 PM, Andy Seaborne <an...@apache.org> wrote:
>>>>>
>>>>>> SDB is getting some user attention but not much developer attention.
>> I
>>>> was hoping that there would be a contribution to go with JENA-447 but
>>>> nothing has come in.  I don't have the bandwidth to even answer
>> questions
>>>> about it properly, partly because I don't use it.  I guess others are
>> in a
>>>> similar position.
>>>>>>
>>>>>> I do think we should be clear as to it's status.
>>>>>>
>>>>>> In the future, I see these options:
>>>>>>
>>>>>> 1/ Add jena-sdb to the main distribution.
>>>>>>    (If it becomes a block on a release, remove it.)
>>>>>>
>>>>>> 2/ As is - release "sometimes".
>>>>>>
>>>>>> 3/ Dormant SDB.
>>>>>>    This is the last release unless some activity arises to maintain
>> it.
>>>>>>    Keep the source around but move out of trunk.
>>>>>>    Can be built from source.
>>>>>>
>>>>>> 4/ Legacy SDB.
>>>>>>    More definite statement than (3) that it is dropped.
>>>>>>    Keep the source around.
>>>>>>
>>>>>> For 3 and 4, where there are no plans to release again if nothing
>>>> changes, the snapshot builds should be stopped.  Users can build from
>>>> source if they want to but the current snapshot should not become a
>>>> distribution-under-the-radar which I feel it becomes if there are no
>> plans
>>>> to make it a formal release.
>>>>>>
>>>>>> Thoughts?
>>>>>>
>>>>>> I'm tending towards doing this one last release then (3).
>>>>>>
>>>>>>     Andy
>>>>
>>>
>>>
>>>
>>
>>
>>
>


Re: [DISCUSS] SDB future

Posted by Rob Vesse <rv...@yarcdata.com>.
Personally I would vote for Option 3, none of us are maintaining it nor do
we have the time/interest to do so.  To continue to put out releases
implies a level of support that does not really exist.

Over in dotNetRDF we long ago abandoned any use of SQL backed storage
because it just doesn't scale as well as a native triple store.

I understand the points about why people may prefer SDB over TDB but
whatever we choose to do we should start making it clear to people that
SDB is deprecated/dormant and we recommend they investigate other
alternatives.

Let's also be clear that TDB is not the only alternative it is just the
one that comes with Jena.  Most of the big triple store vendors have Jena
providers that will let you access commercially developed triple stores
via Jena (e.g. Virtuoso, Stardog, OWLIM, Oracle, IBM DB2 etc).  Many of
these commercial stores include the type of clustering, replication and
failover capabilities that Simon is highlighting as being desirable in
highly scalable production scenarios.

Rob



On 5/27/13 7:43 AM, "Simon Helsen" <sh...@ca.ibm.com> wrote:

>Andy, others,
>
>we do not use SDB because it is way too slow for us. Although I'm sure it
>can be improved as you suggested below, we do not believe it will ever
>come close to TDBs performance because of how SDB is designed. The fact
>it 
>is used at all keeps surprising me, but it probably doesn't matter for
>simple use cases especially if the dataset remains small. Btw, a little
>while back we were reconsidering it because SDB supports multiple vendors
>and our use-case was not very performance sensitive, but it turned out
>that it was still too slow for our needs
>
>As for motivations why some people may prefer SDB over TDB, I don't think
>it is just "SQL" and corporate acceptance. There are some very good
>reasons why file-based systems like TDB are difficult to use in
>commercial 
>deployments. Corporate Java-based server deployments are almost always
>based on one or more app servers (JEE, but sometimes just a regular web
>server) where *all* persisted state goes into a relational database.
>Storing state on the file system is generally taboo for many reasons
>including: The inability to cluster the app server - a critical step to
>scale up beyond a few hundred users; the fact that organizations
>generally 
>have a hard time understanding and managing file system state as opposed
>to standard relational database management. For instance, how do you
>perform online backups and when and how does the state corrupt. For
>instance, on a DB server, admins are watchful for running out of disk
>space. This sort of monitoring is usually less critical on the app
>server, 
>but now, suddenly, there is this growing "thing" they have to backup
>because it will corrupt if you run out of disk space. On top of that, DB
>servers usually use very fast and expensive disk systems (RAIDs, SSDs,
>etc.) This is usually not the case for the app server. On top of that,
>when customers realize there is this large set of data on the file
>system, 
>they have a tendency to put it on larger disks connected via NFS, which
>is 
>unfortunately very dangerous because even short network glitches can
>corrupt TDB. All of this is manageable if you carefully encapsulate TDB
>and provide good administration tools on top of your system, but it is
>not 
>trivial, and it doesn't come out of the box. Especially cluster
>management 
>is quite tricky as you can imagine.
>
>Just wanted to set that out there as to why SQL-based systems remain
>attractive. I would advise though to more clearly state on the SDB
>download page that SDB is deprecated and no longer actively supported
>(unless that changes of course)
>
>Simon
>
>
>
>From:
>Andy Seaborne <an...@apache.org>
>To:
>dev@jena.apache.org,
>Date:
>05/25/2013 06:19 AM
>Subject:
>[DISCUSS] SDB future
>
>
>
>Yes - I'm conflicted as well, flip-flopping between opt1 and opt3.
>
>There is enough user@ traffic to suggest it's used.  I'm guessing it's
>the "SQL" part makes it easier in corp IT. TDB is faster, scales better
>and is better supported (and I'm not corp IT bound).
>
>There are ways to improve it's performance - pushing some filters into
>SQL for example - so theres scoep for development.
>
>Option 1 - add to the main distribution, remove if it becomes a block -
>means that there is no additional work on a release vote.
>
>Testing SDB using Derby only (that's what the junit does by default) is
>easy to setup because it's pulled in by maven.  It only runs embedded,
>not as a server but it does check the code generation.  Unliek other
>jjava SQL DBs, Derby implements tree join plans (the other onyl do
>linear join plans which makes some optional cases impossible - the code
>fall back to brute-force-and-ignorance in these cases). Derby is quite
>picky about it's SQL 92.  SDB tests without additional setup.
>
>We state on users@ this is the position as a indication that we stil
>have option 3 (retirement) available.  Unless we shake the tree a bit,
>
>Proposal: (option 1)
>
>   add to apache-jena, remove at the first sign of trouble.
>   make a clear statement of situation on users@ including
>     encouraging people to come forward
>   option 3 still on the cards.
>
>I've added DISCUSS to the subject line for now to leave open the
>possibility of a vote because it affects the whole project.
>
>But all PMC chipping in here is enough.
>
>I don't see a rush to make a choice just yet.
>
>                 Andy
>
>On 22/05/13 11:47, Claude Warren wrote:
>> I am conflicted about this one.  I think we need SDB (or something
>similar)
>> that will allow users to use standard infrastructure (shared/pooled DB
>is
>> fairly common).  But I don't have the bandwidth to support it.
>>
>> Is there a status where in we release SDB package with each release of
>Jena
>> but only ensure that the current test cases work -- that is the latest
>> release doesn't break something?  Perhaps with a reduced set of
>supported
>> DBs (perhaps Derby & MySQL)
>>
>> If not then I think we take Andy's approach and release one more before
>> putting it on the shelf.
>>
>>
>> On Wed, May 22, 2013 at 10:35 AM, Charles Li
><ch...@gmail.com>wrote:
>>
>>> What are alternatives to SDB? I have a 4GB RDF/XML to load for later
>>> queries
>>>
>>> Thanks!
>>> - Charles
>>>
>>> On May 21, 2013, at 12:00 PM, Stephen Owens
><st...@thoughtwire.ca>
>>> wrote:
>>>
>>>> +1 for option 3 if no one currently is taking ownership of that
>project.
>>> I think it's a useful signal to potential adopters about what they
>should
>>> expect.
>>>>
>>>> On 2013-05-21, at 12:47 PM, Andy Seaborne <an...@apache.org> wrote:
>>>>
>>>>> SDB is getting some user attention but not much developer attention.
>I
>>> was hoping that there would be a contribution to go with JENA-447 but
>>> nothing has come in.  I don't have the bandwidth to even answer
>questions
>>> about it properly, partly because I don't use it.  I guess others are
>in a
>>> similar position.
>>>>>
>>>>> I do think we should be clear as to it's status.
>>>>>
>>>>> In the future, I see these options:
>>>>>
>>>>> 1/ Add jena-sdb to the main distribution.
>>>>>   (If it becomes a block on a release, remove it.)
>>>>>
>>>>> 2/ As is - release "sometimes".
>>>>>
>>>>> 3/ Dormant SDB.
>>>>>   This is the last release unless some activity arises to maintain
>it.
>>>>>   Keep the source around but move out of trunk.
>>>>>   Can be built from source.
>>>>>
>>>>> 4/ Legacy SDB.
>>>>>   More definite statement than (3) that it is dropped.
>>>>>   Keep the source around.
>>>>>
>>>>> For 3 and 4, where there are no plans to release again if nothing
>>> changes, the snapshot builds should be stopped.  Users can build from
>>> source if they want to but the current snapshot should not become a
>>> distribution-under-the-radar which I feel it becomes if there are no
>plans
>>> to make it a formal release.
>>>>>
>>>>> Thoughts?
>>>>>
>>>>> I'm tending towards doing this one last release then (3).
>>>>>
>>>>>    Andy
>>>
>>
>>
>>
>
>
>


Re: [DISCUSS] SDB future

Posted by Simon Helsen <sh...@ca.ibm.com>.
Andy, others,

we do not use SDB because it is way too slow for us. Although I'm sure it 
can be improved as you suggested below, we do not believe it will ever 
come close to TDBs performance because of how SDB is designed. The fact it 
is used at all keeps surprising me, but it probably doesn't matter for 
simple use cases especially if the dataset remains small. Btw, a little 
while back we were reconsidering it because SDB supports multiple vendors 
and our use-case was not very performance sensitive, but it turned out 
that it was still too slow for our needs

As for motivations why some people may prefer SDB over TDB, I don't think 
it is just "SQL" and corporate acceptance. There are some very good 
reasons why file-based systems like TDB are difficult to use in commercial 
deployments. Corporate Java-based server deployments are almost always 
based on one or more app servers (JEE, but sometimes just a regular web 
server) where *all* persisted state goes into a relational database. 
Storing state on the file system is generally taboo for many reasons 
including: The inability to cluster the app server - a critical step to 
scale up beyond a few hundred users; the fact that organizations generally 
have a hard time understanding and managing file system state as opposed 
to standard relational database management. For instance, how do you 
perform online backups and when and how does the state corrupt. For 
instance, on a DB server, admins are watchful for running out of disk 
space. This sort of monitoring is usually less critical on the app server, 
but now, suddenly, there is this growing "thing" they have to backup 
because it will corrupt if you run out of disk space. On top of that, DB 
servers usually use very fast and expensive disk systems (RAIDs, SSDs, 
etc.) This is usually not the case for the app server. On top of that, 
when customers realize there is this large set of data on the file system, 
they have a tendency to put it on larger disks connected via NFS, which is 
unfortunately very dangerous because even short network glitches can 
corrupt TDB. All of this is manageable if you carefully encapsulate TDB 
and provide good administration tools on top of your system, but it is not 
trivial, and it doesn't come out of the box. Especially cluster management 
is quite tricky as you can imagine.

Just wanted to set that out there as to why SQL-based systems remain 
attractive. I would advise though to more clearly state on the SDB 
download page that SDB is deprecated and no longer actively supported 
(unless that changes of course)

Simon



From:
Andy Seaborne <an...@apache.org>
To:
dev@jena.apache.org, 
Date:
05/25/2013 06:19 AM
Subject:
[DISCUSS] SDB future



Yes - I'm conflicted as well, flip-flopping between opt1 and opt3.

There is enough user@ traffic to suggest it's used.  I'm guessing it's 
the "SQL" part makes it easier in corp IT. TDB is faster, scales better 
and is better supported (and I'm not corp IT bound).

There are ways to improve it's performance - pushing some filters into 
SQL for example - so theres scoep for development.

Option 1 - add to the main distribution, remove if it becomes a block - 
means that there is no additional work on a release vote.

Testing SDB using Derby only (that's what the junit does by default) is 
easy to setup because it's pulled in by maven.  It only runs embedded, 
not as a server but it does check the code generation.  Unliek other 
jjava SQL DBs, Derby implements tree join plans (the other onyl do 
linear join plans which makes some optional cases impossible - the code 
fall back to brute-force-and-ignorance in these cases). Derby is quite 
picky about it's SQL 92.  SDB tests without additional setup.

We state on users@ this is the position as a indication that we stil 
have option 3 (retirement) available.  Unless we shake the tree a bit,

Proposal: (option 1)

   add to apache-jena, remove at the first sign of trouble.
   make a clear statement of situation on users@ including
     encouraging people to come forward
   option 3 still on the cards.

I've added DISCUSS to the subject line for now to leave open the 
possibility of a vote because it affects the whole project.

But all PMC chipping in here is enough.

I don't see a rush to make a choice just yet.

                 Andy

On 22/05/13 11:47, Claude Warren wrote:
> I am conflicted about this one.  I think we need SDB (or something 
similar)
> that will allow users to use standard infrastructure (shared/pooled DB 
is
> fairly common).  But I don't have the bandwidth to support it.
>
> Is there a status where in we release SDB package with each release of 
Jena
> but only ensure that the current test cases work -- that is the latest
> release doesn't break something?  Perhaps with a reduced set of 
supported
> DBs (perhaps Derby & MySQL)
>
> If not then I think we take Andy's approach and release one more before
> putting it on the shelf.
>
>
> On Wed, May 22, 2013 at 10:35 AM, Charles Li 
<ch...@gmail.com>wrote:
>
>> What are alternatives to SDB? I have a 4GB RDF/XML to load for later
>> queries
>>
>> Thanks!
>> - Charles
>>
>> On May 21, 2013, at 12:00 PM, Stephen Owens 
<st...@thoughtwire.ca>
>> wrote:
>>
>>> +1 for option 3 if no one currently is taking ownership of that 
project.
>> I think it's a useful signal to potential adopters about what they 
should
>> expect.
>>>
>>> On 2013-05-21, at 12:47 PM, Andy Seaborne <an...@apache.org> wrote:
>>>
>>>> SDB is getting some user attention but not much developer attention. 
I
>> was hoping that there would be a contribution to go with JENA-447 but
>> nothing has come in.  I don't have the bandwidth to even answer 
questions
>> about it properly, partly because I don't use it.  I guess others are 
in a
>> similar position.
>>>>
>>>> I do think we should be clear as to it's status.
>>>>
>>>> In the future, I see these options:
>>>>
>>>> 1/ Add jena-sdb to the main distribution.
>>>>   (If it becomes a block on a release, remove it.)
>>>>
>>>> 2/ As is - release "sometimes".
>>>>
>>>> 3/ Dormant SDB.
>>>>   This is the last release unless some activity arises to maintain 
it.
>>>>   Keep the source around but move out of trunk.
>>>>   Can be built from source.
>>>>
>>>> 4/ Legacy SDB.
>>>>   More definite statement than (3) that it is dropped.
>>>>   Keep the source around.
>>>>
>>>> For 3 and 4, where there are no plans to release again if nothing
>> changes, the snapshot builds should be stopped.  Users can build from
>> source if they want to but the current snapshot should not become a
>> distribution-under-the-radar which I feel it becomes if there are no 
plans
>> to make it a formal release.
>>>>
>>>> Thoughts?
>>>>
>>>> I'm tending towards doing this one last release then (3).
>>>>
>>>>    Andy
>>
>
>
>




[DISCUSS] SDB future

Posted by Andy Seaborne <an...@apache.org>.
Yes - I'm conflicted as well, flip-flopping between opt1 and opt3.

There is enough user@ traffic to suggest it's used.  I'm guessing it's 
the "SQL" part makes it easier in corp IT. TDB is faster, scales better 
and is better supported (and I'm not corp IT bound).

There are ways to improve it's performance - pushing some filters into 
SQL for example - so theres scoep for development.

Option 1 - add to the main distribution, remove if it becomes a block - 
means that there is no additional work on a release vote.

Testing SDB using Derby only (that's what the junit does by default) is 
easy to setup because it's pulled in by maven.  It only runs embedded, 
not as a server but it does check the code generation.  Unliek other 
jjava SQL DBs, Derby implements tree join plans (the other onyl do 
linear join plans which makes some optional cases impossible - the code 
fall back to brute-force-and-ignorance in these cases). Derby is quite 
picky about it's SQL 92.  SDB tests without additional setup.

We state on users@ this is the position as a indication that we stil 
have option 3 (retirement) available.  Unless we shake the tree a bit,

Proposal: (option 1)

   add to apache-jena, remove at the first sign of trouble.
   make a clear statement of situation on users@ including
     encouraging people to come forward
   option 3 still on the cards.

I've added DISCUSS to the subject line for now to leave open the 
possibility of a vote because it affects the whole project.

But all PMC chipping in here is enough.

I don't see a rush to make a choice just yet.

	Andy

On 22/05/13 11:47, Claude Warren wrote:
> I am conflicted about this one.  I think we need SDB (or something similar)
> that will allow users to use standard infrastructure (shared/pooled DB is
> fairly common).  But I don't have the bandwidth to support it.
>
> Is there a status where in we release SDB package with each release of Jena
> but only ensure that the current test cases work -- that is the latest
> release doesn't break something?  Perhaps with a reduced set of supported
> DBs (perhaps Derby & MySQL)
>
> If not then I think we take Andy's approach and release one more before
> putting it on the shelf.
>
>
> On Wed, May 22, 2013 at 10:35 AM, Charles Li <ch...@gmail.com>wrote:
>
>> What are alternatives to SDB? I have a 4GB RDF/XML to load for later
>> queries
>>
>> Thanks!
>> - Charles
>>
>> On May 21, 2013, at 12:00 PM, Stephen Owens <st...@thoughtwire.ca>
>> wrote:
>>
>>> +1 for option 3 if no one currently is taking ownership of that project.
>> I think it's a useful signal to potential adopters about what they should
>> expect.
>>>
>>> On 2013-05-21, at 12:47 PM, Andy Seaborne <an...@apache.org> wrote:
>>>
>>>> SDB is getting some user attention but not much developer attention.  I
>> was hoping that there would be a contribution to go with JENA-447 but
>> nothing has come in.  I don't have the bandwidth to even answer questions
>> about it properly, partly because I don't use it.  I guess others are in a
>> similar position.
>>>>
>>>> I do think we should be clear as to it's status.
>>>>
>>>> In the future, I see these options:
>>>>
>>>> 1/ Add jena-sdb to the main distribution.
>>>>   (If it becomes a block on a release, remove it.)
>>>>
>>>> 2/ As is - release "sometimes".
>>>>
>>>> 3/ Dormant SDB.
>>>>   This is the last release unless some activity arises to maintain it.
>>>>   Keep the source around but move out of trunk.
>>>>   Can be built from source.
>>>>
>>>> 4/ Legacy SDB.
>>>>   More definite statement than (3) that it is dropped.
>>>>   Keep the source around.
>>>>
>>>> For 3 and 4, where there are no plans to release again if nothing
>> changes, the snapshot builds should be stopped.  Users can build from
>> source if they want to but the current snapshot should not become a
>> distribution-under-the-radar which I feel it becomes if there are no plans
>> to make it a formal release.
>>>>
>>>> Thoughts?
>>>>
>>>> I'm tending towards doing this one last release then (3).
>>>>
>>>>    Andy
>>
>
>
>


Re: SDB future

Posted by Claude Warren <cl...@xenei.com>.
I am conflicted about this one.  I think we need SDB (or something similar)
that will allow users to use standard infrastructure (shared/pooled DB is
fairly common).  But I don't have the bandwidth to support it.

Is there a status where in we release SDB package with each release of Jena
but only ensure that the current test cases work -- that is the latest
release doesn't break something?  Perhaps with a reduced set of supported
DBs (perhaps Derby & MySQL)

If not then I think we take Andy's approach and release one more before
putting it on the shelf.


On Wed, May 22, 2013 at 10:35 AM, Charles Li <ch...@gmail.com>wrote:

> What are alternatives to SDB? I have a 4GB RDF/XML to load for later
> queries
>
> Thanks!
> - Charles
>
> On May 21, 2013, at 12:00 PM, Stephen Owens <st...@thoughtwire.ca>
> wrote:
>
> > +1 for option 3 if no one currently is taking ownership of that project.
> I think it's a useful signal to potential adopters about what they should
> expect.
> >
> > On 2013-05-21, at 12:47 PM, Andy Seaborne <an...@apache.org> wrote:
> >
> >> SDB is getting some user attention but not much developer attention.  I
> was hoping that there would be a contribution to go with JENA-447 but
> nothing has come in.  I don't have the bandwidth to even answer questions
> about it properly, partly because I don't use it.  I guess others are in a
> similar position.
> >>
> >> I do think we should be clear as to it's status.
> >>
> >> In the future, I see these options:
> >>
> >> 1/ Add jena-sdb to the main distribution.
> >>  (If it becomes a block on a release, remove it.)
> >>
> >> 2/ As is - release "sometimes".
> >>
> >> 3/ Dormant SDB.
> >>  This is the last release unless some activity arises to maintain it.
> >>  Keep the source around but move out of trunk.
> >>  Can be built from source.
> >>
> >> 4/ Legacy SDB.
> >>  More definite statement than (3) that it is dropped.
> >>  Keep the source around.
> >>
> >> For 3 and 4, where there are no plans to release again if nothing
> changes, the snapshot builds should be stopped.  Users can build from
> source if they want to but the current snapshot should not become a
> distribution-under-the-radar which I feel it becomes if there are no plans
> to make it a formal release.
> >>
> >> Thoughts?
> >>
> >> I'm tending towards doing this one last release then (3).
> >>
> >>   Andy
>



-- 
I like: Like Like - The likeliest place on the web<http://like-like.xenei.com>
Identity: https://www.identify.nu/user.php?claude@xenei.com
LinkedIn: http://www.linkedin.com/in/claudewarren

Re: SDB future

Posted by Charles Li <ch...@gmail.com>.
What are alternatives to SDB? I have a 4GB RDF/XML to load for later queries

Thanks!
- Charles

On May 21, 2013, at 12:00 PM, Stephen Owens <st...@thoughtwire.ca> wrote:

> +1 for option 3 if no one currently is taking ownership of that project. I think it's a useful signal to potential adopters about what they should expect. 
> 
> On 2013-05-21, at 12:47 PM, Andy Seaborne <an...@apache.org> wrote:
> 
>> SDB is getting some user attention but not much developer attention.  I was hoping that there would be a contribution to go with JENA-447 but nothing has come in.  I don't have the bandwidth to even answer questions about it properly, partly because I don't use it.  I guess others are in a similar position.
>> 
>> I do think we should be clear as to it's status.
>> 
>> In the future, I see these options:
>> 
>> 1/ Add jena-sdb to the main distribution.
>>  (If it becomes a block on a release, remove it.)
>> 
>> 2/ As is - release "sometimes".
>> 
>> 3/ Dormant SDB.
>>  This is the last release unless some activity arises to maintain it.
>>  Keep the source around but move out of trunk.
>>  Can be built from source.
>> 
>> 4/ Legacy SDB.
>>  More definite statement than (3) that it is dropped.
>>  Keep the source around.
>> 
>> For 3 and 4, where there are no plans to release again if nothing changes, the snapshot builds should be stopped.  Users can build from source if they want to but the current snapshot should not become a distribution-under-the-radar which I feel it becomes if there are no plans to make it a formal release.
>> 
>> Thoughts?
>> 
>> I'm tending towards doing this one last release then (3).
>> 
>>   Andy

Re: SDB future

Posted by Stephen Owens <st...@thoughtwire.ca>.
+1 for option 3 if no one currently is taking ownership of that project. I think it's a useful signal to potential adopters about what they should expect. 

On 2013-05-21, at 12:47 PM, Andy Seaborne <an...@apache.org> wrote:

> SDB is getting some user attention but not much developer attention.  I was hoping that there would be a contribution to go with JENA-447 but nothing has come in.  I don't have the bandwidth to even answer questions about it properly, partly because I don't use it.  I guess others are in a similar position.
> 
> I do think we should be clear as to it's status.
> 
> In the future, I see these options:
> 
> 1/ Add jena-sdb to the main distribution.
>   (If it becomes a block on a release, remove it.)
> 
> 2/ As is - release "sometimes".
> 
> 3/ Dormant SDB.
>   This is the last release unless some activity arises to maintain it.
>   Keep the source around but move out of trunk.
>   Can be built from source.
> 
> 4/ Legacy SDB.
>   More definite statement than (3) that it is dropped.
>   Keep the source around.
> 
> For 3 and 4, where there are no plans to release again if nothing changes, the snapshot builds should be stopped.  Users can build from source if they want to but the current snapshot should not become a distribution-under-the-radar which I feel it becomes if there are no plans to make it a formal release.
> 
> Thoughts?
> 
> I'm tending towards doing this one last release then (3).
> 
>    Andy

Re: SDB future

Posted by Charles Li <ch...@gmail.com>.
Hi, Andy:

I am just starting to develop a large model processing tool using SDB for
the initial load of model, so please do not make it go away. However, I
know very little so I don't know how to contribute. Maybe some testing
efforts to start with?

Thanks
- Charles


On Tue, May 21, 2013 at 11:47 AM, Andy Seaborne <an...@apache.org> wrote:

> SDB is getting some user attention but not much developer attention.  I
> was hoping that there would be a contribution to go with JENA-447 but
> nothing has come in.  I don't have the bandwidth to even answer questions
> about it properly, partly because I don't use it.  I guess others are in a
> similar position.
>
> I do think we should be clear as to it's status.
>
> In the future, I see these options:
>
> 1/ Add jena-sdb to the main distribution.
>    (If it becomes a block on a release, remove it.)
>
> 2/ As is - release "sometimes".
>
> 3/ Dormant SDB.
>    This is the last release unless some activity arises to maintain it.
>    Keep the source around but move out of trunk.
>    Can be built from source.
>
> 4/ Legacy SDB.
>    More definite statement than (3) that it is dropped.
>    Keep the source around.
>
> For 3 and 4, where there are no plans to release again if nothing changes,
> the snapshot builds should be stopped.  Users can build from source if they
> want to but the current snapshot should not become a
> distribution-under-the-radar which I feel it becomes if there are no plans
> to make it a formal release.
>
> Thoughts?
>
> I'm tending towards doing this one last release then (3).
>
>         Andy
>