bigdata-developers — List for bigdata developers

Re: [Bigdata-developers] IllegalMonitorStateException on close

[Bryan T. <br...@sy...>]

Ok. I am traveling for the next 2 days.  I will take a look at this soon.

Thanks,
Bryan

----
Bryan Thompson
Chief Scientist & Founder
SYSTAP, LLC
4501 Tower Road
Greensboro, NC 27410
br...@sy...
http://bigdata.com
http://mapgraph.io

CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
for the sole use of the intended recipient(s) and are confidential or
proprietary to SYSTAP. Any unauthorized review, use, disclosure,
dissemination or copying of this email or its contents or attachments is
prohibited. If you have received this communication in error, please notify
the sender by reply email and permanently delete all copies of the email
and its contents and attachments.

On Wed, Oct 8, 2014 at 8:36 AM, ryan <ry...@os...> wrote:

> Here's a simpler version of the code: just compile and run.
>
> The setup is one thread starts the repository, and another thread closes
> it.
> An exception is thrown.
>
> ry
>
> On Tuesday, October 07, 2014 05:31:28 PM Bryan Thompson wrote:
> > I still do not understand the setup you have going.  It sounds simple
> > enough, but what "app" are you clicking on? What list?
> >
> > Please reduce this to code so we can replicate the issue and then we can
> > take a look at it.
> >
> > For example, a unit test would be great.  That way we can get the test
> into
> > the regression suite as well.
> >
> > Thanks,
> > Bryan
> >
> > ----
> > Bryan Thompson
> > Chief Scientist & Founder
> > SYSTAP, LLC
> > 4501 Tower Road
> > Greensboro, NC 27410
> > br...@sy...
> > http://bigdata.com
> > http://mapgraph.io
> >
> > CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
> > for the sole use of the intended recipient(s) and are confidential or
> > proprietary to SYSTAP. Any unauthorized review, use, disclosure,
> > dissemination or copying of this email or its contents or attachments is
> > prohibited. If you have received this communication in error, please
> notify
> > the sender by reply email and permanently delete all copies of the email
> > and its contents and attachments.
> >
> > On Tue, Oct 7, 2014 at 5:13 PM, ryan <ry...@os...> wrote:
> > > With that example, I'm just starting and stopping a local journal file
> > > directly. No webserver involved.
> > >
> > >
> > > Bryan Thompson <br...@sy...> wrote:
> > >
> > > Are you running the NanoSparqlServer or the sesame workbench?
> > >
> > > Bryan
> > >
> > > ----
> > > Bryan Thompson
> > > Chief Scientist & Founder
> > > SYSTAP, LLC
> > > 4501 Tower Road
> > > Greensboro, NC 27410
> > > br...@sy...
> > > http://bigdata.com
> > > http://mapgraph.io
> > >
> > > CONFIDENTIALITY NOTICE:  This email and its contents and attachments
> are
> > > for the sole use of the intended recipient(s) and are confidential or
> > > proprietary to SYSTAP. Any unauthorized review, use, disclosure,
> > > dissemination or copying of this email or its contents or attachments
> is
> > > prohibited. If you have received this communication in error, please
> > > notify
> > > the sender by reply email and permanently delete all copies of the
> email
> > > and its contents and attachments.
> > >
> > > On Tue, Oct 7, 2014 at 4:29 PM, ryan <ry...@os...>
> wrote:
> > >> Here's a (non)working sample. I haven't included my RWStore.properties
> > >> file,
> > >> but I don't think it matters.
> > >>
> > >> Basically, start the app with a directory containing an
> > >> RWStore.properties
> > >> file, then click on it from the list. The repository gets created in
> one
> > >> thread, and closed in another, and it bombs.
> > >>
> > >> Thanks for your help,
> > >>
> > >> ry
> > >>
> > >> On Tuesday, October 07, 2014 10:00:29 AM Bryan Thompson wrote:
> > >> > Can you provide a simple Java class that illustrates the problem?
> The
> > >> > unisolated connection close logic is below.  If the connection is
> > >>
> > >> already
> > >>
> > >> > closed, it should return immediately.  I suspect that the problem is
> > >>
> > >> with
> > >>
> > >> > the invocation of
> > >> >
> > >> > >>> BigdataSail.*this*.connectionClosed(*this*);
> > >> >
> > >> > which notifies the base SAIL that the connection is closed.
> > >> >
> > >> > However, this problem does not show up in our tests so we would
> need an
> > >> > example in order to replicate it.
> > >> >
> > >> > Thanks,
> > >> > Bryan
> > >> >
> > >> >         *public* *synchronized* *void* close() *throws*
> SailException {
> > >> >
> > >> > //            assertOpen();
> > >> >
> > >> >             *if* (!openConn) {
> > >> >
> > >> >                 *return*;
> > >> >
> > >> >             }
> > >> >
> > >> >
> > >> >
> > >> >             *if* (*txLog*.isInfoEnabled())
> > >> >
> > >> >                 *txLog*.info("SAIL-CLOSE-CONN: conn=" + *this*);
> > >> >
> > >> >             *final* IIndexManager im =
> getDatabase().getIndexManager();
> > >> >
> > >> >
> > >> >             *if* (isDirty()) {
> > >> >
> > >> >                 /*
> > >> >
> > >> >                  * Do implicit rollback() of a dirty connection.
> > >> >
> > >> >                 */
> > >> >
> > >> >                 rollback();
> > >> >
> > >> >             }
> > >> >
> > >> >
> > >> >
> > >> >             *try* {
> > >> >
> > >> >                 // notify the SailBase that the connection is no
> longer
> > >>
> > >> in
> > >>
> > >> > use.
> > >> >
> > >> >                 BigdataSail.*this*.connectionClosed(*this*);
> > >> >
> > >> >             } *finally* {
> > >> >
> > >> >                 *if* (lock != *null*) {
> > >> >
> > >> >                     // release the reentrant lock
> > >> >
> > >> >                     lock.unlock();
> > >> >
> > >> >                 }
> > >> >
> > >> >                 *if* (unisolated && im *instanceof* Journal) {
> > >> >
> > >> >                     // release the permit.
> > >> >
> > >> >                     ((Journal) im).releaseUnisolatedConnection();
> > >> >
> > >> >                 }
> > >> >
> > >> >                 openConn = *false*;
> > >> >
> > >> >             }
> > >> >
> > >> >         }
> > >> >
> > >> > ----
> > >> > Bryan Thompson
> > >> > Chief Scientist & Founder
> > >> > SYSTAP, LLC
> > >> > 4501 Tower Road
> > >> > Greensboro, NC 27410
> > >> > br...@sy...
> > >> > http://bigdata.com
> > >> > http://mapgraph.io
> > >> >
> > >> > CONFIDENTIALITY NOTICE:  This email and its contents and attachments
> > >> > are
> > >> > for the sole use of the intended recipient(s) and are confidential
> or
> > >> > proprietary to SYSTAP. Any unauthorized review, use, disclosure,
> > >> > dissemination or copying of this email or its contents or
> attachments
> > >> > is
> > >> > prohibited. If you have received this communication in error, please
> > >>
> > >> notify
> > >>
> > >> > the sender by reply email and permanently delete all copies of the
> > >> > email
> > >> > and its contents and attachments.
> > >> >
> > >> > On Tue, Oct 7, 2014 at 9:36 AM, ryan <ry...@os...>
> > >>
> > >> wrote:
> > >> > > Hi All,
> > >> > > I'm trying to add a feature to my project that will allow a user
> to
> > >> > > disconnect
> > >> > > from a locally-connected BigData (1.3.1) engine, start up the
> network
> > >> > > server,
> > >> > > and reconnect to the now-networked repository.
> > >> > >
> > >> > > The problem is that every time I I try to close my local
> connection,
> > >>
> > >> I get
> > >>
> > >> > > an
> > >> > > IllegalMonitorStateException that appears to be preventing the
> > >> > > network
> > >> > > server
> > >> > > from working correctly.
> > >> > >
> > >> > > The pertinent stack trace is:
> > >> > > java.lang.IllegalMonitorStateException
> > >> > >
> > >> > >         at
> > >>
> > >>
> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryRelease(Reentra
> > >> n
> > >>
> > >> > > tReadWriteLock.java:374)>
> > >> > >
> > >> > >         at
> > >>
> > >>
> java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQue
> > >> u
> > >>
> > >> > > edSynchronizer.java:1260)>
> > >> > >
> > >> > >         at
> > >>
> > >>
> java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.unlock(Reentr
> > >> a
> > >>
> > >> > > ntReadWriteLock.java:1131)>
> > >> > >
> > >> > >         at
> > >>
> > >>
> com.bigdata.rdf.sail.BigdataSail$BigdataSailConnection.close(BigdataSail.
> > >> j
> > >>
> > >> > > ava:3349)>
> > >> > >
> > >> > >         at
> > >>
> > >>
> org.openrdf.repository.sail.SailRepositoryConnection.close(SailRepository
> > >> C
> > >>
> > >> > > onnection.java:109)
> > >> > >
> > >> > >
> > >> > > With the default OpenRDF backing store, the system will wait a
> little
> > >>
> > >> bit,
> > >>
> > >> > > and
> > >> > > then close connections for you if you don't close them first. I've
> > >>
> > >> tried
> > >>
> > >> > > both
> > >> > > ways (closing the connection first, then the repository, and just
> > >>
> > >> closing
> > >>
> > >> > > the
> > >> > > repository) with no difference.
> > >> > >
> > >> > > I'm running on java 1.7, bigdata 1.3.1, on a linux host.
> > >> > >
> > >> > > I'm at a loss for troubleshooting. I'd be grateful for any advice
> you
> > >> > > might
> > >> > > have.
> > >> > >
> > >> > > Thanks,
> > >> > > ry
> > >> > >
> > >> > > --
> > >> > > ...you can't have five wolves and one sheep voting on what to have
> > >> > > for
> > >> > > supper.
> > >> > >
> > >> > >         --Larry Flint
> > >>
> > >>
> -------------------------------------------------------------------------
> > >> -
> > >>
> > >> > > ---- Meet PCI DSS 3.0 Compliance Requirements with EventLog
> Analyzer
> > >> > > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS
> > >>
> > >> Reports
> > >>
> > >> > > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White
> paper
> > >> > > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog
> Analyzer
> > >>
> > >>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clk
> > >> t
> > >>
> > >> > > rk _______________________________________________
> > >> > > Bigdata-developers mailing list
> > >> > > Big...@li...
> > >> > > https://lists.sourceforge.net/lists/listinfo/bigdata-developers
> > >>
> > >> --
> > >> Four boxes to be used in defense of liberty: soap, ballot, jury, ammo
> -
> > >> use in
> > >> that order.
> > >>
> > >>         --Ed Howdershelt
>
> --
> Psychos don't burst into flames when sunlight hits them. I don't [care] how
> crazy they are.
>

Re: [Bigdata-developers] IllegalMonitorStateException on close

[ryan <ry...@os...>]

Here's a simpler version of the code: just compile and run.

The setup is one thread starts the repository, and another thread closes it. 
An exception is thrown.

ry

On Tuesday, October 07, 2014 05:31:28 PM Bryan Thompson wrote:
> I still do not understand the setup you have going.  It sounds simple
> enough, but what "app" are you clicking on? What list?
> 
> Please reduce this to code so we can replicate the issue and then we can
> take a look at it.
> 
> For example, a unit test would be great.  That way we can get the test into
> the regression suite as well.
> 
> Thanks,
> Bryan
> 
> ----
> Bryan Thompson
> Chief Scientist & Founder
> SYSTAP, LLC
> 4501 Tower Road
> Greensboro, NC 27410
> br...@sy...
> http://bigdata.com
> http://mapgraph.io
> 
> CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
> for the sole use of the intended recipient(s) and are confidential or
> proprietary to SYSTAP. Any unauthorized review, use, disclosure,
> dissemination or copying of this email or its contents or attachments is
> prohibited. If you have received this communication in error, please notify
> the sender by reply email and permanently delete all copies of the email
> and its contents and attachments.
> 
> On Tue, Oct 7, 2014 at 5:13 PM, ryan <ry...@os...> wrote:
> > With that example, I'm just starting and stopping a local journal file
> > directly. No webserver involved.
> > 
> > 
> > Bryan Thompson <br...@sy...> wrote:
> > 
> > Are you running the NanoSparqlServer or the sesame workbench?
> > 
> > Bryan
> > 
> > ----
> > Bryan Thompson
> > Chief Scientist & Founder
> > SYSTAP, LLC
> > 4501 Tower Road
> > Greensboro, NC 27410
> > br...@sy...
> > http://bigdata.com
> > http://mapgraph.io
> > 
> > CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
> > for the sole use of the intended recipient(s) and are confidential or
> > proprietary to SYSTAP. Any unauthorized review, use, disclosure,
> > dissemination or copying of this email or its contents or attachments is
> > prohibited. If you have received this communication in error, please
> > notify
> > the sender by reply email and permanently delete all copies of the email
> > and its contents and attachments.
> > 
> > On Tue, Oct 7, 2014 at 4:29 PM, ryan <ry...@os...> wrote:
> >> Here's a (non)working sample. I haven't included my RWStore.properties
> >> file,
> >> but I don't think it matters.
> >> 
> >> Basically, start the app with a directory containing an
> >> RWStore.properties
> >> file, then click on it from the list. The repository gets created in one
> >> thread, and closed in another, and it bombs.
> >> 
> >> Thanks for your help,
> >> 
> >> ry
> >> 
> >> On Tuesday, October 07, 2014 10:00:29 AM Bryan Thompson wrote:
> >> > Can you provide a simple Java class that illustrates the problem?  The
> >> > unisolated connection close logic is below.  If the connection is
> >> 
> >> already
> >> 
> >> > closed, it should return immediately.  I suspect that the problem is
> >> 
> >> with
> >> 
> >> > the invocation of
> >> > 
> >> > >>> BigdataSail.*this*.connectionClosed(*this*);
> >> > 
> >> > which notifies the base SAIL that the connection is closed.
> >> > 
> >> > However, this problem does not show up in our tests so we would need an
> >> > example in order to replicate it.
> >> > 
> >> > Thanks,
> >> > Bryan
> >> > 
> >> >         *public* *synchronized* *void* close() *throws* SailException {
> >> > 
> >> > //            assertOpen();
> >> > 
> >> >             *if* (!openConn) {
> >> >             
> >> >                 *return*;
> >> >             
> >> >             }
> >> >             
> >> >             
> >> >             
> >> >             *if* (*txLog*.isInfoEnabled())
> >> >             
> >> >                 *txLog*.info("SAIL-CLOSE-CONN: conn=" + *this*);
> >> >             
> >> >             *final* IIndexManager im = getDatabase().getIndexManager();
> >> >             
> >> >             
> >> >             *if* (isDirty()) {
> >> >             
> >> >                 /*
> >> >                 
> >> >                  * Do implicit rollback() of a dirty connection.
> >> >                 
> >> >                 */
> >> >                 
> >> >                 rollback();
> >> >             
> >> >             }
> >> >             
> >> >             
> >> >             
> >> >             *try* {
> >> >             
> >> >                 // notify the SailBase that the connection is no longer
> >> 
> >> in
> >> 
> >> > use.
> >> > 
> >> >                 BigdataSail.*this*.connectionClosed(*this*);
> >> >             
> >> >             } *finally* {
> >> >             
> >> >                 *if* (lock != *null*) {
> >> >                 
> >> >                     // release the reentrant lock
> >> >                     
> >> >                     lock.unlock();
> >> >                 
> >> >                 }
> >> >                 
> >> >                 *if* (unisolated && im *instanceof* Journal) {
> >> >                 
> >> >                     // release the permit.
> >> >                     
> >> >                     ((Journal) im).releaseUnisolatedConnection();
> >> >                 
> >> >                 }
> >> >                 
> >> >                 openConn = *false*;
> >> >             
> >> >             }
> >> >         
> >> >         }
> >> > 
> >> > ----
> >> > Bryan Thompson
> >> > Chief Scientist & Founder
> >> > SYSTAP, LLC
> >> > 4501 Tower Road
> >> > Greensboro, NC 27410
> >> > br...@sy...
> >> > http://bigdata.com
> >> > http://mapgraph.io
> >> > 
> >> > CONFIDENTIALITY NOTICE:  This email and its contents and attachments
> >> > are
> >> > for the sole use of the intended recipient(s) and are confidential or
> >> > proprietary to SYSTAP. Any unauthorized review, use, disclosure,
> >> > dissemination or copying of this email or its contents or attachments
> >> > is
> >> > prohibited. If you have received this communication in error, please
> >> 
> >> notify
> >> 
> >> > the sender by reply email and permanently delete all copies of the
> >> > email
> >> > and its contents and attachments.
> >> > 
> >> > On Tue, Oct 7, 2014 at 9:36 AM, ryan <ry...@os...>
> >> 
> >> wrote:
> >> > > Hi All,
> >> > > I'm trying to add a feature to my project that will allow a user to
> >> > > disconnect
> >> > > from a locally-connected BigData (1.3.1) engine, start up the network
> >> > > server,
> >> > > and reconnect to the now-networked repository.
> >> > > 
> >> > > The problem is that every time I I try to close my local connection,
> >> 
> >> I get
> >> 
> >> > > an
> >> > > IllegalMonitorStateException that appears to be preventing the
> >> > > network
> >> > > server
> >> > > from working correctly.
> >> > > 
> >> > > The pertinent stack trace is:
> >> > > java.lang.IllegalMonitorStateException
> >> > > 
> >> > >         at
> >> 
> >> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryRelease(Reentra
> >> n
> >> 
> >> > > tReadWriteLock.java:374)>
> >> > > 
> >> > >         at
> >> 
> >> java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQue
> >> u
> >> 
> >> > > edSynchronizer.java:1260)>
> >> > > 
> >> > >         at
> >> 
> >> java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.unlock(Reentr
> >> a
> >> 
> >> > > ntReadWriteLock.java:1131)>
> >> > > 
> >> > >         at
> >> 
> >> com.bigdata.rdf.sail.BigdataSail$BigdataSailConnection.close(BigdataSail.
> >> j
> >> 
> >> > > ava:3349)>
> >> > > 
> >> > >         at
> >> 
> >> org.openrdf.repository.sail.SailRepositoryConnection.close(SailRepository
> >> C
> >> 
> >> > > onnection.java:109)
> >> > > 
> >> > > 
> >> > > With the default OpenRDF backing store, the system will wait a little
> >> 
> >> bit,
> >> 
> >> > > and
> >> > > then close connections for you if you don't close them first. I've
> >> 
> >> tried
> >> 
> >> > > both
> >> > > ways (closing the connection first, then the repository, and just
> >> 
> >> closing
> >> 
> >> > > the
> >> > > repository) with no difference.
> >> > > 
> >> > > I'm running on java 1.7, bigdata 1.3.1, on a linux host.
> >> > > 
> >> > > I'm at a loss for troubleshooting. I'd be grateful for any advice you
> >> > > might
> >> > > have.
> >> > > 
> >> > > Thanks,
> >> > > ry
> >> > > 
> >> > > --
> >> > > ...you can't have five wolves and one sheep voting on what to have
> >> > > for
> >> > > supper.
> >> > > 
> >> > >         --Larry Flint
> >> 
> >> -------------------------------------------------------------------------
> >> -
> >> 
> >> > > ---- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> >> > > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS
> >> 
> >> Reports
> >> 
> >> > > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> >> > > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> >> 
> >> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clk
> >> t
> >> 
> >> > > rk _______________________________________________
> >> > > Bigdata-developers mailing list
> >> > > Big...@li...
> >> > > https://lists.sourceforge.net/lists/listinfo/bigdata-developers
> >> 
> >> --
> >> Four boxes to be used in defense of liberty: soap, ballot, jury, ammo -
> >> use in
> >> that order.
> >> 
> >>         --Ed Howdershelt

-- 
Psychos don't burst into flames when sunlight hits them. I don't [care] how 
crazy they are.

Re: [Bigdata-developers] IllegalMonitorStateException on close

[Bryan T. <br...@sy...>]

I still do not understand the setup you have going.  It sounds simple
enough, but what "app" are you clicking on? What list?

Please reduce this to code so we can replicate the issue and then we can
take a look at it.

For example, a unit test would be great.  That way we can get the test into
the regression suite as well.

Thanks,
Bryan

----
Bryan Thompson
Chief Scientist & Founder
SYSTAP, LLC
4501 Tower Road
Greensboro, NC 27410
br...@sy...
http://bigdata.com
http://mapgraph.io

CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
for the sole use of the intended recipient(s) and are confidential or
proprietary to SYSTAP. Any unauthorized review, use, disclosure,
dissemination or copying of this email or its contents or attachments is
prohibited. If you have received this communication in error, please notify
the sender by reply email and permanently delete all copies of the email
and its contents and attachments.

On Tue, Oct 7, 2014 at 5:13 PM, ryan <ry...@os...> wrote:

> With that example, I'm just starting and stopping a local journal file
> directly. No webserver involved.
>
>
> Bryan Thompson <br...@sy...> wrote:
>
> Are you running the NanoSparqlServer or the sesame workbench?
>
> Bryan
>
> ----
> Bryan Thompson
> Chief Scientist & Founder
> SYSTAP, LLC
> 4501 Tower Road
> Greensboro, NC 27410
> br...@sy...
> http://bigdata.com
> http://mapgraph.io
>
> CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
> for the sole use of the intended recipient(s) and are confidential or
> proprietary to SYSTAP. Any unauthorized review, use, disclosure,
> dissemination or copying of this email or its contents or attachments is
> prohibited. If you have received this communication in error, please notify
> the sender by reply email and permanently delete all copies of the email
> and its contents and attachments.
>
> On Tue, Oct 7, 2014 at 4:29 PM, ryan <ry...@os...> wrote:
>
>> Here's a (non)working sample. I haven't included my RWStore.properties
>> file,
>> but I don't think it matters.
>>
>> Basically, start the app with a directory containing an RWStore.properties
>> file, then click on it from the list. The repository gets created in one
>> thread, and closed in another, and it bombs.
>>
>> Thanks for your help,
>>
>> ry
>>
>> On Tuesday, October 07, 2014 10:00:29 AM Bryan Thompson wrote:
>> > Can you provide a simple Java class that illustrates the problem?  The
>> > unisolated connection close logic is below.  If the connection is
>> already
>> > closed, it should return immediately.  I suspect that the problem is
>> with
>> > the invocation of
>> >
>> > >>> BigdataSail.*this*.connectionClosed(*this*);
>> >
>> > which notifies the base SAIL that the connection is closed.
>> >
>> > However, this problem does not show up in our tests so we would need an
>> > example in order to replicate it.
>> >
>> > Thanks,
>> > Bryan
>> >
>> >         *public* *synchronized* *void* close() *throws* SailException {
>> >
>> >
>> > //            assertOpen();
>> >
>> >
>> >             *if* (!openConn) {
>> >
>> >
>> >
>> >                 *return*;
>> >
>> >
>> >
>> >             }
>> >
>> >
>> >
>> >             *if* (*txLog*.isInfoEnabled())
>> >
>> >                 *txLog*.info("SAIL-CLOSE-CONN: conn=" + *this*);
>> >
>> >
>> >             *final* IIndexManager im = getDatabase().getIndexManager();
>> >
>> >
>> >             *if* (isDirty()) {
>> >
>> >                 /*
>> >
>> >                  * Do implicit rollback() of a dirty connection.
>> >
>> >                 */
>> >
>> >                 rollback();
>> >
>> >             }
>> >
>> >
>> >
>> >             *try* {
>> >
>> >                 // notify the SailBase that the connection is no longer
>> in
>> > use.
>> >
>> >                 BigdataSail.*this*.connectionClosed(*this*);
>> >
>> >             } *finally* {
>> >
>> >                 *if* (lock != *null*) {
>> >
>> >                     // release the reentrant lock
>> >
>> >                     lock.unlock();
>> >
>> >                 }
>> >
>> >                 *if* (unisolated && im *instanceof* Journal) {
>> >
>> >                     // release the permit.
>> >
>> >                     ((Journal) im).releaseUnisolatedConnection();
>> >
>> >                 }
>> >
>> >                 openConn = *false*;
>> >
>> >             }
>> >
>> >
>> >
>> >         }
>> >
>> > ----
>> > Bryan Thompson
>> > Chief Scientist & Founder
>> > SYSTAP, LLC
>> > 4501 Tower Road
>> > Greensboro, NC 27410
>> > br...@sy...
>> > http://bigdata.com
>> > http://mapgraph.io
>> >
>> > CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
>> > for the sole use of the intended recipient(s) and are confidential or
>> > proprietary to SYSTAP. Any unauthorized review, use, disclosure,
>> > dissemination or copying of this email or its contents or attachments is
>> > prohibited. If you have received this communication in error, please
>> notify
>> > the sender by reply email and permanently delete all copies of the email
>> > and its contents and attachments.
>> >
>> > On Tue, Oct 7, 2014 at 9:36 AM, ryan <ry...@os...>
>> wrote:
>> > > Hi All,
>> > > I'm trying to add a feature to my project that will allow a user to
>> > > disconnect
>> > > from a locally-connected BigData (1.3.1) engine, start up the network
>> > > server,
>> > > and reconnect to the now-networked repository.
>> > >
>> > > The problem is that every time I I try to close my local connection,
>> I get
>> > > an
>> > > IllegalMonitorStateException that appears to be preventing the network
>> > > server
>> > > from working correctly.
>> > >
>> > > The pertinent stack trace is:
>> > > java.lang.IllegalMonitorStateException
>> > >
>> > >         at
>> > >
>> > >
>> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryRelease(Reentran
>> > > tReadWriteLock.java:374)>
>> > >         at
>> > >
>> > >
>> java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueu
>> > > edSynchronizer.java:1260)>
>> > >         at
>> > >
>> > >
>> java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.unlock(Reentra
>> > > ntReadWriteLock.java:1131)>
>> > >         at
>> > >
>> > >
>> com.bigdata.rdf.sail.BigdataSail$BigdataSailConnection.close(BigdataSail.j
>> > > ava:3349)>
>> > >         at
>> > >
>> > >
>> org.openrdf.repository.sail.SailRepositoryConnection.close(SailRepositoryC
>> > > onnection.java:109)
>> > >
>> > >
>> > > With the default OpenRDF backing store, the system will wait a little
>> bit,
>> > > and
>> > > then close connections for you if you don't close them first. I've
>> tried
>> > > both
>> > > ways (closing the connection first, then the repository, and just
>> closing
>> > > the
>> > > repository) with no difference.
>> > >
>> > > I'm running on java 1.7, bigdata 1.3.1, on a linux host.
>> > >
>> > > I'm at a loss for troubleshooting. I'd be grateful for any advice you
>> > > might
>> > > have.
>> > >
>> > > Thanks,
>> > > ry
>> > >
>> > > --
>> > > ...you can't have five wolves and one sheep voting on what to have for
>> > > supper.
>> > >
>> > >         --Larry Flint
>> > >
>> > >
>> --------------------------------------------------------------------------
>> > > ---- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>> > > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS
>> Reports
>> > > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>> > > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>> > >
>> > >
>> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clkt
>> > > rk _______________________________________________
>> > > Bigdata-developers mailing list
>> > > Big...@li...
>> > > https://lists.sourceforge.net/lists/listinfo/bigdata-developers
>>
>> --
>> Four boxes to be used in defense of liberty: soap, ballot, jury, ammo -
>> use in
>> that order.
>>         --Ed Howdershelt
>>
>
>

Re: [Bigdata-developers] IllegalMonitorStateException on close

[ryan <ry...@os...>]

With that example, I'm just starting and stopping a local journal file directly. No webserver involved.

Bryan Thompson <br...@sy...> wrote:

>Are you running the NanoSparqlServer or the sesame workbench?
>
>
>Bryan
>
>
>----
>Bryan Thompson
>
>Chief Scientist & Founder
>SYSTAP, LLC
>
>4501 Tower Road
>Greensboro, NC 27410
>
>br...@sy...
>
>http://bigdata.com
>
>http://mapgraph.io
>
>CONFIDENTIALITY NOTICE:  This email and its contents and attachments are for the sole use of the intended recipient(s) and are confidential or proprietary to SYSTAP. Any unauthorized review, use, disclosure, dissemination or copying of this email or its contents or attachments is prohibited. If you have received this communication in error, please notify the sender by reply email and permanently delete all copies of the email and its contents and attachments.
>
>
>
>On Tue, Oct 7, 2014 at 4:29 PM, ryan <ry...@os...> wrote:
>
>Here's a (non)working sample. I haven't included my RWStore.properties file,
>but I don't think it matters.
>
>Basically, start the app with a directory containing an RWStore.properties
>file, then click on it from the list. The repository gets created in one
>thread, and closed in another, and it bombs.
>
>Thanks for your help,
>
>ry
>
>On Tuesday, October 07, 2014 10:00:29 AM Bryan Thompson wrote:
>> Can you provide a simple Java class that illustrates the problem?  The
>> unisolated connection close logic is below.  If the connection is already
>> closed, it should return immediately.  I suspect that the problem is with
>> the invocation of
>>
>> >>> BigdataSail.*this*.connectionClosed(*this*);
>>
>> which notifies the base SAIL that the connection is closed.
>>
>> However, this problem does not show up in our tests so we would need an
>> example in order to replicate it.
>>
>> Thanks,
>> Bryan
>>
>>         *public* *synchronized* *void* close() *throws* SailException {
>>
>>
>> //            assertOpen();
>>
>>
>>             *if* (!openConn) {
>>
>>
>>
>>                 *return*;
>>
>>
>>
>>             }
>>
>>
>>
>>             *if* (*txLog*.isInfoEnabled())
>>
>>                 *txLog*.info("SAIL-CLOSE-CONN: conn=" + *this*);
>>
>>
>>             *final* IIndexManager im = getDatabase().getIndexManager();
>>
>>
>>             *if* (isDirty()) {
>>
>>                 /*
>>
>>                  * Do implicit rollback() of a dirty connection.
>>
>>                 */
>>
>>                 rollback();
>>
>>             }
>>
>>
>>
>>             *try* {
>>
>>                 // notify the SailBase that the connection is no longer in
>> use.
>>
>>                 BigdataSail.*this*.connectionClosed(*this*);
>>
>>             } *finally* {
>>
>>                 *if* (lock != *null*) {
>>
>>                     // release the reentrant lock
>>
>>                     lock.unlock();
>>
>>                 }
>>
>>                 *if* (unisolated && im *instanceof* Journal) {
>>
>>                     // release the permit.
>>
>>                     ((Journal) im).releaseUnisolatedConnection();
>>
>>                 }
>>
>>                 openConn = *false*;
>>
>>             }
>>
>>
>>
>>         }
>>
>> ----
>> Bryan Thompson
>> Chief Scientist & Founder
>> SYSTAP, LLC
>> 4501 Tower Road
>> Greensboro, NC 27410
>> br...@sy...
>> http://bigdata.com
>> http://mapgraph.io
>>
>> CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
>> for the sole use of the intended recipient(s) and are confidential or
>> proprietary to SYSTAP. Any unauthorized review, use, disclosure,
>> dissemination or copying of this email or its contents or attachments is
>> prohibited. If you have received this communication in error, please notify
>> the sender by reply email and permanently delete all copies of the email
>> and its contents and attachments.
>>
>> On Tue, Oct 7, 2014 at 9:36 AM, ryan <ry...@os...> wrote:
>> > Hi All,
>> > I'm trying to add a feature to my project that will allow a user to
>> > disconnect
>> > from a locally-connected BigData (1.3.1) engine, start up the network
>> > server,
>> > and reconnect to the now-networked repository.
>> >
>> > The problem is that every time I I try to close my local connection, I get
>> > an
>> > IllegalMonitorStateException that appears to be preventing the network
>> > server
>> > from working correctly.
>> >
>> > The pertinent stack trace is:
>> > java.lang.IllegalMonitorStateException
>> >
>> >         at
>> >
>> > java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryRelease(Reentran
>> > tReadWriteLock.java:374)>
>> >         at
>> >
>> > java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueu
>> > edSynchronizer.java:1260)>
>> >         at
>> >
>> > java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.unlock(Reentra
>> > ntReadWriteLock.java:1131)>
>> >         at
>> >
>> > com.bigdata.rdf.sail.BigdataSail$BigdataSailConnection.close(BigdataSail.j
>> > ava:3349)>
>> >         at
>> >
>> > org.openrdf.repository.sail.SailRepositoryConnection.close(SailRepositoryC
>> > onnection.java:109)
>> >
>> >
>> > With the default OpenRDF backing store, the system will wait a little bit,
>> > and
>> > then close connections for you if you don't close them first. I've tried
>> > both
>> > ways (closing the connection first, then the repository, and just closing
>> > the
>> > repository) with no difference.
>> >
>> > I'm running on java 1.7, bigdata 1.3.1, on a linux host.
>> >
>> > I'm at a loss for troubleshooting. I'd be grateful for any advice you
>> > might
>> > have.
>> >
>> > Thanks,
>> > ry
>> >
>> > --
>> > ...you can't have five wolves and one sheep voting on what to have for
>> > supper.
>> >
>> >         --Larry Flint
>> >
>> > --------------------------------------------------------------------------
>> > ---- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>> > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
>> > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>> > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>> >
>> > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clkt
>> > rk _______________________________________________
>> > Bigdata-developers mailing list
>> > Big...@li...
>> > https://lists.sourceforge.net/lists/listinfo/bigdata-developers
>
>--
>Four boxes to be used in defense of liberty: soap, ballot, jury, ammo - use in
>that order.
>        --Ed Howdershelt
>
>

Re: [Bigdata-developers] IllegalMonitorStateException on close

[Bryan T. <br...@sy...>]

Are you running the NanoSparqlServer or the sesame workbench?

Bryan

----
Bryan Thompson
Chief Scientist & Founder
SYSTAP, LLC
4501 Tower Road
Greensboro, NC 27410
br...@sy...
http://bigdata.com
http://mapgraph.io

CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
for the sole use of the intended recipient(s) and are confidential or
proprietary to SYSTAP. Any unauthorized review, use, disclosure,
dissemination or copying of this email or its contents or attachments is
prohibited. If you have received this communication in error, please notify
the sender by reply email and permanently delete all copies of the email
and its contents and attachments.

On Tue, Oct 7, 2014 at 4:29 PM, ryan <ry...@os...> wrote:

> Here's a (non)working sample. I haven't included my RWStore.properties
> file,
> but I don't think it matters.
>
> Basically, start the app with a directory containing an RWStore.properties
> file, then click on it from the list. The repository gets created in one
> thread, and closed in another, and it bombs.
>
> Thanks for your help,
>
> ry
>
> On Tuesday, October 07, 2014 10:00:29 AM Bryan Thompson wrote:
> > Can you provide a simple Java class that illustrates the problem?  The
> > unisolated connection close logic is below.  If the connection is already
> > closed, it should return immediately.  I suspect that the problem is with
> > the invocation of
> >
> > >>> BigdataSail.*this*.connectionClosed(*this*);
> >
> > which notifies the base SAIL that the connection is closed.
> >
> > However, this problem does not show up in our tests so we would need an
> > example in order to replicate it.
> >
> > Thanks,
> > Bryan
> >
> >         *public* *synchronized* *void* close() *throws* SailException {
> >
> >
> > //            assertOpen();
> >
> >
> >             *if* (!openConn) {
> >
> >
> >
> >                 *return*;
> >
> >
> >
> >             }
> >
> >
> >
> >             *if* (*txLog*.isInfoEnabled())
> >
> >                 *txLog*.info("SAIL-CLOSE-CONN: conn=" + *this*);
> >
> >
> >             *final* IIndexManager im = getDatabase().getIndexManager();
> >
> >
> >             *if* (isDirty()) {
> >
> >                 /*
> >
> >                  * Do implicit rollback() of a dirty connection.
> >
> >                 */
> >
> >                 rollback();
> >
> >             }
> >
> >
> >
> >             *try* {
> >
> >                 // notify the SailBase that the connection is no longer
> in
> > use.
> >
> >                 BigdataSail.*this*.connectionClosed(*this*);
> >
> >             } *finally* {
> >
> >                 *if* (lock != *null*) {
> >
> >                     // release the reentrant lock
> >
> >                     lock.unlock();
> >
> >                 }
> >
> >                 *if* (unisolated && im *instanceof* Journal) {
> >
> >                     // release the permit.
> >
> >                     ((Journal) im).releaseUnisolatedConnection();
> >
> >                 }
> >
> >                 openConn = *false*;
> >
> >             }
> >
> >
> >
> >         }
> >
> > ----
> > Bryan Thompson
> > Chief Scientist & Founder
> > SYSTAP, LLC
> > 4501 Tower Road
> > Greensboro, NC 27410
> > br...@sy...
> > http://bigdata.com
> > http://mapgraph.io
> >
> > CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
> > for the sole use of the intended recipient(s) and are confidential or
> > proprietary to SYSTAP. Any unauthorized review, use, disclosure,
> > dissemination or copying of this email or its contents or attachments is
> > prohibited. If you have received this communication in error, please
> notify
> > the sender by reply email and permanently delete all copies of the email
> > and its contents and attachments.
> >
> > On Tue, Oct 7, 2014 at 9:36 AM, ryan <ry...@os...> wrote:
> > > Hi All,
> > > I'm trying to add a feature to my project that will allow a user to
> > > disconnect
> > > from a locally-connected BigData (1.3.1) engine, start up the network
> > > server,
> > > and reconnect to the now-networked repository.
> > >
> > > The problem is that every time I I try to close my local connection, I
> get
> > > an
> > > IllegalMonitorStateException that appears to be preventing the network
> > > server
> > > from working correctly.
> > >
> > > The pertinent stack trace is:
> > > java.lang.IllegalMonitorStateException
> > >
> > >         at
> > >
> > >
> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryRelease(Reentran
> > > tReadWriteLock.java:374)>
> > >         at
> > >
> > >
> java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueu
> > > edSynchronizer.java:1260)>
> > >         at
> > >
> > >
> java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.unlock(Reentra
> > > ntReadWriteLock.java:1131)>
> > >         at
> > >
> > >
> com.bigdata.rdf.sail.BigdataSail$BigdataSailConnection.close(BigdataSail.j
> > > ava:3349)>
> > >         at
> > >
> > >
> org.openrdf.repository.sail.SailRepositoryConnection.close(SailRepositoryC
> > > onnection.java:109)
> > >
> > >
> > > With the default OpenRDF backing store, the system will wait a little
> bit,
> > > and
> > > then close connections for you if you don't close them first. I've
> tried
> > > both
> > > ways (closing the connection first, then the repository, and just
> closing
> > > the
> > > repository) with no difference.
> > >
> > > I'm running on java 1.7, bigdata 1.3.1, on a linux host.
> > >
> > > I'm at a loss for troubleshooting. I'd be grateful for any advice you
> > > might
> > > have.
> > >
> > > Thanks,
> > > ry
> > >
> > > --
> > > ...you can't have five wolves and one sheep voting on what to have for
> > > supper.
> > >
> > >         --Larry Flint
> > >
> > >
> --------------------------------------------------------------------------
> > > ---- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> > > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS
> Reports
> > > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> > > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> > >
> > >
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clkt
> > > rk _______________________________________________
> > > Bigdata-developers mailing list
> > > Big...@li...
> > > https://lists.sourceforge.net/lists/listinfo/bigdata-developers
>
> --
> Four boxes to be used in defense of liberty: soap, ballot, jury, ammo -
> use in
> that order.
>         --Ed Howdershelt
>

Re: [Bigdata-developers] IllegalMonitorStateException on close

[ryan <ry...@os...>]

Here's a (non)working sample. I haven't included my RWStore.properties file, 
but I don't think it matters.

Basically, start the app with a directory containing an RWStore.properties 
file, then click on it from the list. The repository gets created in one 
thread, and closed in another, and it bombs.

Thanks for your help,

ry

On Tuesday, October 07, 2014 10:00:29 AM Bryan Thompson wrote:
> Can you provide a simple Java class that illustrates the problem?  The
> unisolated connection close logic is below.  If the connection is already
> closed, it should return immediately.  I suspect that the problem is with
> the invocation of
> 
> >>> BigdataSail.*this*.connectionClosed(*this*);
> 
> which notifies the base SAIL that the connection is closed.
> 
> However, this problem does not show up in our tests so we would need an
> example in order to replicate it.
> 
> Thanks,
> Bryan
> 
>         *public* *synchronized* *void* close() *throws* SailException {
> 
> 
> //            assertOpen();
> 
> 
>             *if* (!openConn) {
> 
> 
> 
>                 *return*;
> 
> 
> 
>             }
> 
> 
> 
>             *if* (*txLog*.isInfoEnabled())
> 
>                 *txLog*.info("SAIL-CLOSE-CONN: conn=" + *this*);
> 
> 
>             *final* IIndexManager im = getDatabase().getIndexManager();
> 
> 
>             *if* (isDirty()) {
> 
>                 /*
> 
>                  * Do implicit rollback() of a dirty connection.
> 
>                 */
> 
>                 rollback();
> 
>             }
> 
> 
> 
>             *try* {
> 
>                 // notify the SailBase that the connection is no longer in
> use.
> 
>                 BigdataSail.*this*.connectionClosed(*this*);
> 
>             } *finally* {
> 
>                 *if* (lock != *null*) {
> 
>                     // release the reentrant lock
> 
>                     lock.unlock();
> 
>                 }
> 
>                 *if* (unisolated && im *instanceof* Journal) {
> 
>                     // release the permit.
> 
>                     ((Journal) im).releaseUnisolatedConnection();
> 
>                 }
> 
>                 openConn = *false*;
> 
>             }
> 
> 
> 
>         }
> 
> ----
> Bryan Thompson
> Chief Scientist & Founder
> SYSTAP, LLC
> 4501 Tower Road
> Greensboro, NC 27410
> br...@sy...
> http://bigdata.com
> http://mapgraph.io
> 
> CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
> for the sole use of the intended recipient(s) and are confidential or
> proprietary to SYSTAP. Any unauthorized review, use, disclosure,
> dissemination or copying of this email or its contents or attachments is
> prohibited. If you have received this communication in error, please notify
> the sender by reply email and permanently delete all copies of the email
> and its contents and attachments.
> 
> On Tue, Oct 7, 2014 at 9:36 AM, ryan <ry...@os...> wrote:
> > Hi All,
> > I'm trying to add a feature to my project that will allow a user to
> > disconnect
> > from a locally-connected BigData (1.3.1) engine, start up the network
> > server,
> > and reconnect to the now-networked repository.
> > 
> > The problem is that every time I I try to close my local connection, I get
> > an
> > IllegalMonitorStateException that appears to be preventing the network
> > server
> > from working correctly.
> > 
> > The pertinent stack trace is:
> > java.lang.IllegalMonitorStateException
> > 
> >         at
> > 
> > java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryRelease(Reentran
> > tReadWriteLock.java:374)> 
> >         at
> > 
> > java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueu
> > edSynchronizer.java:1260)> 
> >         at
> > 
> > java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.unlock(Reentra
> > ntReadWriteLock.java:1131)> 
> >         at
> > 
> > com.bigdata.rdf.sail.BigdataSail$BigdataSailConnection.close(BigdataSail.j
> > ava:3349)> 
> >         at
> > 
> > org.openrdf.repository.sail.SailRepositoryConnection.close(SailRepositoryC
> > onnection.java:109)
> > 
> > 
> > With the default OpenRDF backing store, the system will wait a little bit,
> > and
> > then close connections for you if you don't close them first. I've tried
> > both
> > ways (closing the connection first, then the repository, and just closing
> > the
> > repository) with no difference.
> > 
> > I'm running on java 1.7, bigdata 1.3.1, on a linux host.
> > 
> > I'm at a loss for troubleshooting. I'd be grateful for any advice you
> > might
> > have.
> > 
> > Thanks,
> > ry
> > 
> > --
> > ...you can't have five wolves and one sheep voting on what to have for
> > supper.
> > 
> >         --Larry Flint
> > 
> > --------------------------------------------------------------------------
> > ---- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> > 
> > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clkt
> > rk _______________________________________________
> > Bigdata-developers mailing list
> > Big...@li...
> > https://lists.sourceforge.net/lists/listinfo/bigdata-developers

-- 
Four boxes to be used in defense of liberty: soap, ballot, jury, ammo - use in 
that order.
	--Ed Howdershelt

Re: [Bigdata-developers] IllegalMonitorStateException on close

[Bryan T. <br...@sy...>]

Can you provide a simple Java class that illustrates the problem?  The
unisolated connection close logic is below.  If the connection is already
closed, it should return immediately.  I suspect that the problem is with
the invocation of

>>> BigdataSail.*this*.connectionClosed(*this*);

which notifies the base SAIL that the connection is closed.

However, this problem does not show up in our tests so we would need an
example in order to replicate it.

Thanks,
Bryan

        *public* *synchronized* *void* close() *throws* SailException {


//            assertOpen();


            *if* (!openConn) {



                *return*;



            }



            *if* (*txLog*.isInfoEnabled())

                *txLog*.info("SAIL-CLOSE-CONN: conn=" + *this*);


            *final* IIndexManager im = getDatabase().getIndexManager();


            *if* (isDirty()) {

                /*

                 * Do implicit rollback() of a dirty connection.

                */

                rollback();

            }



            *try* {

                // notify the SailBase that the connection is no longer in
use.

                BigdataSail.*this*.connectionClosed(*this*);

            } *finally* {

                *if* (lock != *null*) {

                    // release the reentrant lock

                    lock.unlock();

                }

                *if* (unisolated && im *instanceof* Journal) {

                    // release the permit.

                    ((Journal) im).releaseUnisolatedConnection();

                }

                openConn = *false*;

            }



        }

----
Bryan Thompson
Chief Scientist & Founder
SYSTAP, LLC
4501 Tower Road
Greensboro, NC 27410
br...@sy...
http://bigdata.com
http://mapgraph.io

CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
for the sole use of the intended recipient(s) and are confidential or
proprietary to SYSTAP. Any unauthorized review, use, disclosure,
dissemination or copying of this email or its contents or attachments is
prohibited. If you have received this communication in error, please notify
the sender by reply email and permanently delete all copies of the email
and its contents and attachments.

On Tue, Oct 7, 2014 at 9:36 AM, ryan <ry...@os...> wrote:

> Hi All,
> I'm trying to add a feature to my project that will allow a user to
> disconnect
> from a locally-connected BigData (1.3.1) engine, start up the network
> server,
> and reconnect to the now-networked repository.
>
> The problem is that every time I I try to close my local connection, I get
> an
> IllegalMonitorStateException that appears to be preventing the network
> server
> from working correctly.
>
> The pertinent stack trace is:
> java.lang.IllegalMonitorStateException
>         at
>
> java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryRelease(ReentrantReadWriteLock.java:374)
>         at
>
> java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueuedSynchronizer.java:1260)
>         at
>
> java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.unlock(ReentrantReadWriteLock.java:1131)
>         at
>
> com.bigdata.rdf.sail.BigdataSail$BigdataSailConnection.close(BigdataSail.java:3349)
>         at
>
> org.openrdf.repository.sail.SailRepositoryConnection.close(SailRepositoryConnection.java:109)
>
>
> With the default OpenRDF backing store, the system will wait a little bit,
> and
> then close connections for you if you don't close them first. I've tried
> both
> ways (closing the connection first, then the repository, and just closing
> the
> repository) with no difference.
>
> I'm running on java 1.7, bigdata 1.3.1, on a linux host.
>
> I'm at a loss for troubleshooting. I'd be grateful for any advice you might
> have.
>
> Thanks,
> ry
>
> --
> ...you can't have five wolves and one sheep voting on what to have for
> supper.
>         --Larry Flint
>
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Bigdata-developers mailing list
> Big...@li...
> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
>

[Bigdata-developers] IllegalMonitorStateException on close

[ryan <ry...@os...>]

Hi All,
I'm trying to add a feature to my project that will allow a user to disconnect 
from a locally-connected BigData (1.3.1) engine, start up the network server, 
and reconnect to the now-networked repository.

The problem is that every time I I try to close my local connection, I get an 
IllegalMonitorStateException that appears to be preventing the network server 
from working correctly.

The pertinent stack trace is: 
java.lang.IllegalMonitorStateException
	at 
java.util.concurrent.locks.ReentrantReadWriteLock$Sync.tryRelease(ReentrantReadWriteLock.java:374)
	at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueuedSynchronizer.java:1260)
	at 
java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.unlock(ReentrantReadWriteLock.java:1131)
	at 
com.bigdata.rdf.sail.BigdataSail$BigdataSailConnection.close(BigdataSail.java:3349)
	at 
org.openrdf.repository.sail.SailRepositoryConnection.close(SailRepositoryConnection.java:109)


With the default OpenRDF backing store, the system will wait a little bit, and 
then close connections for you if you don't close them first. I've tried both 
ways (closing the connection first, then the repository, and just closing the 
repository) with no difference. 

I'm running on java 1.7, bigdata 1.3.1, on a linux host.

I'm at a loss for troubleshooting. I'd be grateful for any advice you might 
have.

Thanks,
ry

-- 
...you can't have five wolves and one sheep voting on what to have for supper.
	--Larry Flint

Re: [Bigdata-developers] Bulk loading into bigdata

[Bryan T. <br...@sy...>]

Rose,

The trunk is no longer used for bigdata.

You can checkout the 1.3.2 release from:
https://svn.code.sf.net/p/bigdata/code/tags/BIGDATA_RELEASE_1_3_2

The 1.3.x maintenance and development branch is:
https://svn.code.sf.net/p/bigdata/code/branches/BIGDATA_RELEASE_1_3_0

You can also download bigdata from our web site:
http://www.bigdata.com/download.

Be sure to given the Java platform sufficient resources if you are loading
large files (-server, -Xmx16G or better, etc.).  See wiki.bigdata.com for
various information on how to obtain, build, configure, and use the bigdata
platform.

Thanks,
Bryan

----
Bryan Thompson
Chief Scientist & Founder
SYSTAP, LLC
4501 Tower Road
Greensboro, NC 27410
br...@sy...
http://bigdata.com
http://mapgraph.io

CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
for the sole use of the intended recipient(s) and are confidential or
proprietary to SYSTAP. Any unauthorized review, use, disclosure,
dissemination or copying of this email or its contents or attachments is
prohibited. If you have received this communication in error, please notify
the sender by reply email and permanently delete all copies of the email
and its contents and attachments.

On Mon, Oct 6, 2014 at 1:09 PM, Rose Beck <ros...@gm...> wrote:

> Dear Bryan,
>
> I have Uniprot data in turse triple form (ttl) and I want to load it
> in bigdata and I want to query it using bigdata. On the web page
> http://wiki.bigdata.com/wiki/index.php/NanoSparqlServer it is
> mentioned that I should look at the example:  NSSEmbeddedExample.java.
> However when I check out the code:
> svn checkout svn://svn.code.sf.net/p/bigdata/code/trunk bigdata-code
>
> I am unable to find this example.
>
> Can you please help me with this. I am a complete novice at Java
> (Although I work on C/C++ and Python extensively), therefore I am not
> able to understand as to how should I load large datasets into Bigdata
> and how should I query them. Perhaps a step-by-step guide for users
> like me who are not familiar with Java will be of great help.
>
> Thanks & Regards,
> Jyoti
>

Re: [Bigdata-developers] Bulk loading into bigdata

[Rose B. <ros...@gm...>]

Dear Bryan,

I have Uniprot data in turse triple form (ttl) and I want to load it
in bigdata and I want to query it using bigdata. On the web page
http://wiki.bigdata.com/wiki/index.php/NanoSparqlServer it is
mentioned that I should look at the example:  NSSEmbeddedExample.java.
However when I check out the code:
svn checkout svn://svn.code.sf.net/p/bigdata/code/trunk bigdata-code

I am unable to find this example.

Can you please help me with this. I am a complete novice at Java
(Although I work on C/C++ and Python extensively), therefore I am not
able to understand as to how should I load large datasets into Bigdata
and how should I query them. Perhaps a step-by-step guide for users
like me who are not familiar with Java will be of great help.

Thanks & Regards,
Jyoti

On Mon, Oct 6, 2014 at 8:40 PM, Bryan Thompson <br...@sy...> wrote:
> Certainly.  There are a number of resources at http://blog.bigdata.com.
> There is a chapter length paper on the bigdata architecture at [1].  This is
> also linked from that blog page.  You might also be interested in our other
> project, which is http://mapgraph.io.
>
> If you are only storing the source of a triple, then the named graphs
> mechanism is sufficient since the URI of the named graph can be used for the
> source URI.
>
> However, if you want to associate more metadata with each triple then RDR is
> the way to go.
>
> Thanks,
> Bryan
>
> [1] http://www.bigdata.com/whitepapers/bigdata_architecture_whitepaper.pdf
>
> ----
> Bryan Thompson
> Chief Scientist & Founder
> SYSTAP, LLC
> 4501 Tower Road
> Greensboro, NC 27410
> br...@sy...
> http://bigdata.com
> http://mapgraph.io
>
> CONFIDENTIALITY NOTICE:  This email and its contents and attachments are for
> the sole use of the intended recipient(s) and are confidential or
> proprietary to SYSTAP. Any unauthorized review, use, disclosure,
> dissemination or copying of this email or its contents or attachments is
> prohibited. If you have received this communication in error, please notify
> the sender by reply email and permanently delete all copies of the email and
> its contents and attachments.
>
>
> On Mon, Oct 6, 2014 at 11:05 AM, Rose Beck <ros...@gm...> wrote:
>>
>> Dear Bryan,
>>
>> For now we are just using RDR for storing provenance or source of
>> triples. All these questions arise in my mind out of curiosity :)
>>
>> I saw bigdata slides at
>> http://www.cse.unsw.edu.au/~iwgdm/2012/Slides/bigdata.pdf. And I am
>> pretty curious to read more about:  how Bigdata implements vectored
>> query execution and what engineering goes behind its analytic mode of
>> execution. If possible, can you please point me to resources from
>> which I learn more about the same?
>>
>>
>> Thanks & Regards,
>> Rose
>>
>>
>> On Mon, Oct 6, 2014 at 8:15 PM, Bryan Thompson <br...@sy...> wrote:
>> > Rose,
>> >
>> > I think that the requirement for statement level metadata should be
>> > orthogonal to the decision to use named graphs.  Statement level
>> > metadata
>> > can be used for a variety of purposes.  For example, it can be used for
>> > security, it can be used to provide the source of the statement (which
>> > is
>> > often the use case for named graphs), to associate an author with a
>> > statement, to associate a creation time with a statement, to associate a
>> > weight with an edge of a graph, etc.
>> >
>> > What is the use case that motivates the RDR mechanisms for you?  Perhaps
>> > if
>> > you can explain that I can provide an example of how this might be
>> > relevant
>> > in the context of named graphs for your application.  However, the
>> > feature
>> > is not currently supported for the quads mode of the bigdata database,
>> > so
>> > this is a somewhat academic question.
>> >
>> > Thanks,
>> > Bryan
>> >
>> > ----
>> > Bryan Thompson
>> > Chief Scientist & Founder
>> > SYSTAP, LLC
>> > 4501 Tower Road
>> > Greensboro, NC 27410
>> > br...@sy...
>> > http://bigdata.com
>> > http://mapgraph.io
>> >
>> > CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
>> > for
>> > the sole use of the intended recipient(s) and are confidential or
>> > proprietary to SYSTAP. Any unauthorized review, use, disclosure,
>> > dissemination or copying of this email or its contents or attachments is
>> > prohibited. If you have received this communication in error, please
>> > notify
>> > the sender by reply email and permanently delete all copies of the email
>> > and
>> > its contents and attachments.
>> >
>> >
>> > On Mon, Oct 6, 2014 at 10:40 AM, Rose Beck <ros...@gm...>
>> > wrote:
>> >>
>> >> Dear Bryan,
>> >>
>> >> Probably I am new to the field. But since you are an experienced
>> >> person in the field, therefore can you please help me understand that:
>> >> when we apply RDR mechanism to triples, then what is the practical
>> >> use-case application of using named graph mechanism? I mean I
>> >> understand intuitively but I still am not able to get the practical
>> >> significance of using named graphs.
>> >>
>> >>
>> >> Thanks & Regards,
>> >> Rose
>> >>
>> >> On Mon, Oct 6, 2014 at 8:02 PM, Bryan Thompson <br...@sy...>
>> >> wrote:
>> >> > The purpose of RDR is to permit statements about statements.
>> >> >
>> >> > The purpose of named graphs is to allow statements to be collected
>> >> > into
>> >> > containers.
>> >> >
>> >> > With RDF* support for named graphs, you could do both.
>> >> >
>> >> > Whether or not this is a good idea is an interesting question.
>> >> > Consider,
>> >> > that named graphs could be interpreted as just a special case of a
>> >> > statement
>> >> > about a statement where the database then applies special indexing
>> >> > (typically by maintaining additional indices for fast access by the
>> >> > named
>> >> > graph).
>> >> >
>> >> > For example, given:
>> >> >
>> >> > <<:a :b :c> :namedGraph :d>
>> >> >
>> >> > If we assume that ":namedGraph" has the semantics of the SPARQL named
>> >> > graphs
>> >> > mechanism, then this RDR assertion says that the statement :a :b :c
>> >> > exists
>> >> > in the named graph :d.
>> >> >
>> >> > If so, then the RDR mechanisms always apply to triples and the named
>> >> > graphs
>> >> > mechanism just specifies the containers within which a given triple
>> >> > (including an RDR triple) is visible.
>> >> >
>> >> > Thanks,
>> >> > Bryan
>> >> >
>> >> > ----
>> >> > Bryan Thompson
>> >> > Chief Scientist & Founder
>> >> > SYSTAP, LLC
>> >> > 4501 Tower Road
>> >> > Greensboro, NC 27410
>> >> > br...@sy...
>> >> > http://bigdata.com
>> >> > http://mapgraph.io
>> >> >
>> >> > CONFIDENTIALITY NOTICE:  This email and its contents and attachments
>> >> > are
>> >> > for
>> >> > the sole use of the intended recipient(s) and are confidential or
>> >> > proprietary to SYSTAP. Any unauthorized review, use, disclosure,
>> >> > dissemination or copying of this email or its contents or attachments
>> >> > is
>> >> > prohibited. If you have received this communication in error, please
>> >> > notify
>> >> > the sender by reply email and permanently delete all copies of the
>> >> > email
>> >> > and
>> >> > its contents and attachments.
>> >> >
>> >> >
>> >> > On Mon, Oct 6, 2014 at 10:19 AM, Rose Beck <ros...@gm...>
>> >> > wrote:
>> >> >>
>> >> >> Dear Bryan,
>> >> >>
>> >> >> Thanks for the enlightening write-up about RDR. But I have a
>> >> >> question
>> >> >> in the write-up you wrote "In the future, we plan to add support for
>> >> >> RDF* and SPARQL* to the quads mode of the platform as well. This
>> >> >> will
>> >> >> allow statement level metadata to co-exist seamlessly with the named
>> >> >> graphs model." But I dont understand the need for supporting RDF*
>> >> >> and
>> >> >> SPARQL* in quads mode. I mean I dont understand as to why do we need
>> >> >> to allow statement level metadata to co-exist with named graph
>> >> >> model.
>> >> >> Can you please explain this with an example.
>> >> >>
>> >> >>
>> >> >> Thanks & Regards,
>> >> >> Rose.
>> >> >>
>> >> >> On Mon, Oct 6, 2014 at 5:59 PM, Bryan Thompson <br...@sy...>
>> >> >> wrote:
>> >> >> > I've added a page to the wiki based on that blog post:
>> >> >> >
>> >> >> > wiki.bigdata.com/wiki/index.php/Reification_Done_Right
>> >> >> >
>> >> >> > Thanks,
>> >> >> > Bryan
>> >> >> >
>> >> >> > ----
>> >> >> > Bryan Thompson
>> >> >> > Chief Scientist & Founder
>> >> >> > SYSTAP, LLC
>> >> >> > 4501 Tower Road
>> >> >> > Greensboro, NC 27410
>> >> >> > br...@sy...
>> >> >> > http://bigdata.com
>> >> >> > http://mapgraph.io
>> >> >> >
>> >> >> > CONFIDENTIALITY NOTICE:  This email and its contents and
>> >> >> > attachments
>> >> >> > are
>> >> >> > for
>> >> >> > the sole use of the intended recipient(s) and are confidential or
>> >> >> > proprietary to SYSTAP. Any unauthorized review, use, disclosure,
>> >> >> > dissemination or copying of this email or its contents or
>> >> >> > attachments
>> >> >> > is
>> >> >> > prohibited. If you have received this communication in error,
>> >> >> > please
>> >> >> > notify
>> >> >> > the sender by reply email and permanently delete all copies of the
>> >> >> > email
>> >> >> > and
>> >> >> > its contents and attachments.
>> >> >> >
>> >> >> >
>> >> >> > On Sun, Oct 5, 2014 at 5:27 PM, Rose Beck <ros...@gm...>
>> >> >> > wrote:
>> >> >> >>
>> >> >> >> Dear all,
>> >> >> >>
>> >> >> >> I have downloaded bigdata.war and have deployed it using sesame
>> >> >> >> HTTP
>> >> >> >> API. Now I am not getting as to how should I load rdf
>> >> >> >> triples/provenance with triples to bigdata using
>> >> >> >> nanosparqlserver? I
>> >> >> >> am using sesame HTTP API (using apache tomcat). Can someone
>> >> >> >> please
>> >> >> >> help.
>> >> >> >>
>> >> >> >> I intend to use mysql, native java and postgres with sesame. Any
>> >> >> >> help
>> >> >> >> will be deeply appreciated.
>> >> >> >>
>> >> >> >> Regards,
>> >> >> >> Rose
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> ------------------------------------------------------------------------------
>> >> >> >> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>> >> >> >> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS
>> >> >> >> Reports
>> >> >> >> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White
>> >> >> >> paper
>> >> >> >> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog
>> >> >> >> Analyzer
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>> >> >> >> _______________________________________________
>> >> >> >> Bigdata-developers mailing list
>> >> >> >> Big...@li...
>> >> >> >> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
>> >> >> >
>> >> >> >
>> >> >
>> >> >
>> >
>> >
>
>

Re: [Bigdata-developers] Bulk loading into bigdata

[Bryan T. <br...@sy...>]

Certainly.  There are a number of resources at http://blog.bigdata.com.
There is a chapter length paper on the bigdata architecture at [1].  This
is also linked from that blog page.  You might also be interested in our
other project, which is http://mapgraph.io.

If you are only storing the source of a triple, then the named graphs
mechanism is sufficient since the URI of the named graph can be used for
the source URI.

However, if you want to associate more metadata with each triple then RDR
is the way to go.

Thanks,
Bryan

[1] http://www.bigdata.com/whitepapers/bigdata_architecture_whitepaper.pdf

----
Bryan Thompson
Chief Scientist & Founder
SYSTAP, LLC
4501 Tower Road
Greensboro, NC 27410
br...@sy...
http://bigdata.com
http://mapgraph.io

CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
for the sole use of the intended recipient(s) and are confidential or
proprietary to SYSTAP. Any unauthorized review, use, disclosure,
dissemination or copying of this email or its contents or attachments is
prohibited. If you have received this communication in error, please notify
the sender by reply email and permanently delete all copies of the email
and its contents and attachments.

On Mon, Oct 6, 2014 at 11:05 AM, Rose Beck <ros...@gm...> wrote:

> Dear Bryan,
>
> For now we are just using RDR for storing provenance or source of
> triples. All these questions arise in my mind out of curiosity :)
>
> I saw bigdata slides at
> http://www.cse.unsw.edu.au/~iwgdm/2012/Slides/bigdata.pdf. And I am
> pretty curious to read more about:  how Bigdata implements vectored
> query execution and what engineering goes behind its analytic mode of
> execution. If possible, can you please point me to resources from
> which I learn more about the same?
>
>
> Thanks & Regards,
> Rose
>
>
> On Mon, Oct 6, 2014 at 8:15 PM, Bryan Thompson <br...@sy...> wrote:
> > Rose,
> >
> > I think that the requirement for statement level metadata should be
> > orthogonal to the decision to use named graphs.  Statement level metadata
> > can be used for a variety of purposes.  For example, it can be used for
> > security, it can be used to provide the source of the statement (which is
> > often the use case for named graphs), to associate an author with a
> > statement, to associate a creation time with a statement, to associate a
> > weight with an edge of a graph, etc.
> >
> > What is the use case that motivates the RDR mechanisms for you?  Perhaps
> if
> > you can explain that I can provide an example of how this might be
> relevant
> > in the context of named graphs for your application.  However, the
> feature
> > is not currently supported for the quads mode of the bigdata database, so
> > this is a somewhat academic question.
> >
> > Thanks,
> > Bryan
> >
> > ----
> > Bryan Thompson
> > Chief Scientist & Founder
> > SYSTAP, LLC
> > 4501 Tower Road
> > Greensboro, NC 27410
> > br...@sy...
> > http://bigdata.com
> > http://mapgraph.io
> >
> > CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
> for
> > the sole use of the intended recipient(s) and are confidential or
> > proprietary to SYSTAP. Any unauthorized review, use, disclosure,
> > dissemination or copying of this email or its contents or attachments is
> > prohibited. If you have received this communication in error, please
> notify
> > the sender by reply email and permanently delete all copies of the email
> and
> > its contents and attachments.
> >
> >
> > On Mon, Oct 6, 2014 at 10:40 AM, Rose Beck <ros...@gm...>
> wrote:
> >>
> >> Dear Bryan,
> >>
> >> Probably I am new to the field. But since you are an experienced
> >> person in the field, therefore can you please help me understand that:
> >> when we apply RDR mechanism to triples, then what is the practical
> >> use-case application of using named graph mechanism? I mean I
> >> understand intuitively but I still am not able to get the practical
> >> significance of using named graphs.
> >>
> >>
> >> Thanks & Regards,
> >> Rose
> >>
> >> On Mon, Oct 6, 2014 at 8:02 PM, Bryan Thompson <br...@sy...>
> wrote:
> >> > The purpose of RDR is to permit statements about statements.
> >> >
> >> > The purpose of named graphs is to allow statements to be collected
> into
> >> > containers.
> >> >
> >> > With RDF* support for named graphs, you could do both.
> >> >
> >> > Whether or not this is a good idea is an interesting question.
> >> > Consider,
> >> > that named graphs could be interpreted as just a special case of a
> >> > statement
> >> > about a statement where the database then applies special indexing
> >> > (typically by maintaining additional indices for fast access by the
> >> > named
> >> > graph).
> >> >
> >> > For example, given:
> >> >
> >> > <<:a :b :c> :namedGraph :d>
> >> >
> >> > If we assume that ":namedGraph" has the semantics of the SPARQL named
> >> > graphs
> >> > mechanism, then this RDR assertion says that the statement :a :b :c
> >> > exists
> >> > in the named graph :d.
> >> >
> >> > If so, then the RDR mechanisms always apply to triples and the named
> >> > graphs
> >> > mechanism just specifies the containers within which a given triple
> >> > (including an RDR triple) is visible.
> >> >
> >> > Thanks,
> >> > Bryan
> >> >
> >> > ----
> >> > Bryan Thompson
> >> > Chief Scientist & Founder
> >> > SYSTAP, LLC
> >> > 4501 Tower Road
> >> > Greensboro, NC 27410
> >> > br...@sy...
> >> > http://bigdata.com
> >> > http://mapgraph.io
> >> >
> >> > CONFIDENTIALITY NOTICE:  This email and its contents and attachments
> are
> >> > for
> >> > the sole use of the intended recipient(s) and are confidential or
> >> > proprietary to SYSTAP. Any unauthorized review, use, disclosure,
> >> > dissemination or copying of this email or its contents or attachments
> is
> >> > prohibited. If you have received this communication in error, please
> >> > notify
> >> > the sender by reply email and permanently delete all copies of the
> email
> >> > and
> >> > its contents and attachments.
> >> >
> >> >
> >> > On Mon, Oct 6, 2014 at 10:19 AM, Rose Beck <ros...@gm...>
> >> > wrote:
> >> >>
> >> >> Dear Bryan,
> >> >>
> >> >> Thanks for the enlightening write-up about RDR. But I have a question
> >> >> in the write-up you wrote "In the future, we plan to add support for
> >> >> RDF* and SPARQL* to the quads mode of the platform as well. This will
> >> >> allow statement level metadata to co-exist seamlessly with the named
> >> >> graphs model." But I dont understand the need for supporting RDF* and
> >> >> SPARQL* in quads mode. I mean I dont understand as to why do we need
> >> >> to allow statement level metadata to co-exist with named graph model.
> >> >> Can you please explain this with an example.
> >> >>
> >> >>
> >> >> Thanks & Regards,
> >> >> Rose.
> >> >>
> >> >> On Mon, Oct 6, 2014 at 5:59 PM, Bryan Thompson <br...@sy...>
> >> >> wrote:
> >> >> > I've added a page to the wiki based on that blog post:
> >> >> >
> >> >> > wiki.bigdata.com/wiki/index.php/Reification_Done_Right
> >> >> >
> >> >> > Thanks,
> >> >> > Bryan
> >> >> >
> >> >> > ----
> >> >> > Bryan Thompson
> >> >> > Chief Scientist & Founder
> >> >> > SYSTAP, LLC
> >> >> > 4501 Tower Road
> >> >> > Greensboro, NC 27410
> >> >> > br...@sy...
> >> >> > http://bigdata.com
> >> >> > http://mapgraph.io
> >> >> >
> >> >> > CONFIDENTIALITY NOTICE:  This email and its contents and
> attachments
> >> >> > are
> >> >> > for
> >> >> > the sole use of the intended recipient(s) and are confidential or
> >> >> > proprietary to SYSTAP. Any unauthorized review, use, disclosure,
> >> >> > dissemination or copying of this email or its contents or
> attachments
> >> >> > is
> >> >> > prohibited. If you have received this communication in error,
> please
> >> >> > notify
> >> >> > the sender by reply email and permanently delete all copies of the
> >> >> > email
> >> >> > and
> >> >> > its contents and attachments.
> >> >> >
> >> >> >
> >> >> > On Sun, Oct 5, 2014 at 5:27 PM, Rose Beck <ros...@gm...>
> >> >> > wrote:
> >> >> >>
> >> >> >> Dear all,
> >> >> >>
> >> >> >> I have downloaded bigdata.war and have deployed it using sesame
> HTTP
> >> >> >> API. Now I am not getting as to how should I load rdf
> >> >> >> triples/provenance with triples to bigdata using
> nanosparqlserver? I
> >> >> >> am using sesame HTTP API (using apache tomcat). Can someone please
> >> >> >> help.
> >> >> >>
> >> >> >> I intend to use mysql, native java and postgres with sesame. Any
> >> >> >> help
> >> >> >> will be deeply appreciated.
> >> >> >>
> >> >> >> Regards,
> >> >> >> Rose
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> ------------------------------------------------------------------------------
> >> >> >> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> >> >> >> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS
> >> >> >> Reports
> >> >> >> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White
> paper
> >> >> >> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog
> Analyzer
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> >> >> >> _______________________________________________
> >> >> >> Bigdata-developers mailing list
> >> >> >> Big...@li...
> >> >> >> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
> >> >> >
> >> >> >
> >> >
> >> >
> >
> >
>

Re: [Bigdata-developers] Bulk loading into bigdata

[Rose B. <ros...@gm...>]

Dear Bryan,

For now we are just using RDR for storing provenance or source of
triples. All these questions arise in my mind out of curiosity :)

I saw bigdata slides at
http://www.cse.unsw.edu.au/~iwgdm/2012/Slides/bigdata.pdf. And I am
pretty curious to read more about:  how Bigdata implements vectored
query execution and what engineering goes behind its analytic mode of
execution. If possible, can you please point me to resources from
which I learn more about the same?


Thanks & Regards,
Rose


On Mon, Oct 6, 2014 at 8:15 PM, Bryan Thompson <br...@sy...> wrote:
> Rose,
>
> I think that the requirement for statement level metadata should be
> orthogonal to the decision to use named graphs.  Statement level metadata
> can be used for a variety of purposes.  For example, it can be used for
> security, it can be used to provide the source of the statement (which is
> often the use case for named graphs), to associate an author with a
> statement, to associate a creation time with a statement, to associate a
> weight with an edge of a graph, etc.
>
> What is the use case that motivates the RDR mechanisms for you?  Perhaps if
> you can explain that I can provide an example of how this might be relevant
> in the context of named graphs for your application.  However, the feature
> is not currently supported for the quads mode of the bigdata database, so
> this is a somewhat academic question.
>
> Thanks,
> Bryan
>
> ----
> Bryan Thompson
> Chief Scientist & Founder
> SYSTAP, LLC
> 4501 Tower Road
> Greensboro, NC 27410
> br...@sy...
> http://bigdata.com
> http://mapgraph.io
>
> CONFIDENTIALITY NOTICE:  This email and its contents and attachments are for
> the sole use of the intended recipient(s) and are confidential or
> proprietary to SYSTAP. Any unauthorized review, use, disclosure,
> dissemination or copying of this email or its contents or attachments is
> prohibited. If you have received this communication in error, please notify
> the sender by reply email and permanently delete all copies of the email and
> its contents and attachments.
>
>
> On Mon, Oct 6, 2014 at 10:40 AM, Rose Beck <ros...@gm...> wrote:
>>
>> Dear Bryan,
>>
>> Probably I am new to the field. But since you are an experienced
>> person in the field, therefore can you please help me understand that:
>> when we apply RDR mechanism to triples, then what is the practical
>> use-case application of using named graph mechanism? I mean I
>> understand intuitively but I still am not able to get the practical
>> significance of using named graphs.
>>
>>
>> Thanks & Regards,
>> Rose
>>
>> On Mon, Oct 6, 2014 at 8:02 PM, Bryan Thompson <br...@sy...> wrote:
>> > The purpose of RDR is to permit statements about statements.
>> >
>> > The purpose of named graphs is to allow statements to be collected into
>> > containers.
>> >
>> > With RDF* support for named graphs, you could do both.
>> >
>> > Whether or not this is a good idea is an interesting question.
>> > Consider,
>> > that named graphs could be interpreted as just a special case of a
>> > statement
>> > about a statement where the database then applies special indexing
>> > (typically by maintaining additional indices for fast access by the
>> > named
>> > graph).
>> >
>> > For example, given:
>> >
>> > <<:a :b :c> :namedGraph :d>
>> >
>> > If we assume that ":namedGraph" has the semantics of the SPARQL named
>> > graphs
>> > mechanism, then this RDR assertion says that the statement :a :b :c
>> > exists
>> > in the named graph :d.
>> >
>> > If so, then the RDR mechanisms always apply to triples and the named
>> > graphs
>> > mechanism just specifies the containers within which a given triple
>> > (including an RDR triple) is visible.
>> >
>> > Thanks,
>> > Bryan
>> >
>> > ----
>> > Bryan Thompson
>> > Chief Scientist & Founder
>> > SYSTAP, LLC
>> > 4501 Tower Road
>> > Greensboro, NC 27410
>> > br...@sy...
>> > http://bigdata.com
>> > http://mapgraph.io
>> >
>> > CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
>> > for
>> > the sole use of the intended recipient(s) and are confidential or
>> > proprietary to SYSTAP. Any unauthorized review, use, disclosure,
>> > dissemination or copying of this email or its contents or attachments is
>> > prohibited. If you have received this communication in error, please
>> > notify
>> > the sender by reply email and permanently delete all copies of the email
>> > and
>> > its contents and attachments.
>> >
>> >
>> > On Mon, Oct 6, 2014 at 10:19 AM, Rose Beck <ros...@gm...>
>> > wrote:
>> >>
>> >> Dear Bryan,
>> >>
>> >> Thanks for the enlightening write-up about RDR. But I have a question
>> >> in the write-up you wrote "In the future, we plan to add support for
>> >> RDF* and SPARQL* to the quads mode of the platform as well. This will
>> >> allow statement level metadata to co-exist seamlessly with the named
>> >> graphs model." But I dont understand the need for supporting RDF* and
>> >> SPARQL* in quads mode. I mean I dont understand as to why do we need
>> >> to allow statement level metadata to co-exist with named graph model.
>> >> Can you please explain this with an example.
>> >>
>> >>
>> >> Thanks & Regards,
>> >> Rose.
>> >>
>> >> On Mon, Oct 6, 2014 at 5:59 PM, Bryan Thompson <br...@sy...>
>> >> wrote:
>> >> > I've added a page to the wiki based on that blog post:
>> >> >
>> >> > wiki.bigdata.com/wiki/index.php/Reification_Done_Right
>> >> >
>> >> > Thanks,
>> >> > Bryan
>> >> >
>> >> > ----
>> >> > Bryan Thompson
>> >> > Chief Scientist & Founder
>> >> > SYSTAP, LLC
>> >> > 4501 Tower Road
>> >> > Greensboro, NC 27410
>> >> > br...@sy...
>> >> > http://bigdata.com
>> >> > http://mapgraph.io
>> >> >
>> >> > CONFIDENTIALITY NOTICE:  This email and its contents and attachments
>> >> > are
>> >> > for
>> >> > the sole use of the intended recipient(s) and are confidential or
>> >> > proprietary to SYSTAP. Any unauthorized review, use, disclosure,
>> >> > dissemination or copying of this email or its contents or attachments
>> >> > is
>> >> > prohibited. If you have received this communication in error, please
>> >> > notify
>> >> > the sender by reply email and permanently delete all copies of the
>> >> > email
>> >> > and
>> >> > its contents and attachments.
>> >> >
>> >> >
>> >> > On Sun, Oct 5, 2014 at 5:27 PM, Rose Beck <ros...@gm...>
>> >> > wrote:
>> >> >>
>> >> >> Dear all,
>> >> >>
>> >> >> I have downloaded bigdata.war and have deployed it using sesame HTTP
>> >> >> API. Now I am not getting as to how should I load rdf
>> >> >> triples/provenance with triples to bigdata using nanosparqlserver? I
>> >> >> am using sesame HTTP API (using apache tomcat). Can someone please
>> >> >> help.
>> >> >>
>> >> >> I intend to use mysql, native java and postgres with sesame. Any
>> >> >> help
>> >> >> will be deeply appreciated.
>> >> >>
>> >> >> Regards,
>> >> >> Rose
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> ------------------------------------------------------------------------------
>> >> >> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>> >> >> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS
>> >> >> Reports
>> >> >> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>> >> >> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>> >> >>
>> >> >>
>> >> >>
>> >> >> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>> >> >> _______________________________________________
>> >> >> Bigdata-developers mailing list
>> >> >> Big...@li...
>> >> >> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
>> >> >
>> >> >
>> >
>> >
>
>

Re: [Bigdata-developers] Bulk loading into bigdata

[Bryan T. <br...@sy...>]

Rose,

I think that the requirement for statement level metadata should be
orthogonal to the decision to use named graphs.  Statement level metadata
can be used for a variety of purposes.  For example, it can be used for
security, it can be used to provide the source of the statement (which is
often the use case for named graphs), to associate an author with a
statement, to associate a creation time with a statement, to associate a
weight with an edge of a graph, etc.

What is the use case that motivates the RDR mechanisms for you?  Perhaps if
you can explain that I can provide an example of how this might be relevant
in the context of named graphs for your application.  However, the feature
is not currently supported for the quads mode of the bigdata database, so
this is a somewhat academic question.

Thanks,
Bryan

----
Bryan Thompson
Chief Scientist & Founder
SYSTAP, LLC
4501 Tower Road
Greensboro, NC 27410
br...@sy...
http://bigdata.com
http://mapgraph.io

CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
for the sole use of the intended recipient(s) and are confidential or
proprietary to SYSTAP. Any unauthorized review, use, disclosure,
dissemination or copying of this email or its contents or attachments is
prohibited. If you have received this communication in error, please notify
the sender by reply email and permanently delete all copies of the email
and its contents and attachments.

On Mon, Oct 6, 2014 at 10:40 AM, Rose Beck <ros...@gm...> wrote:

> Dear Bryan,
>
> Probably I am new to the field. But since you are an experienced
> person in the field, therefore can you please help me understand that:
> when we apply RDR mechanism to triples, then what is the practical
> use-case application of using named graph mechanism? I mean I
> understand intuitively but I still am not able to get the practical
> significance of using named graphs.
>
>
> Thanks & Regards,
> Rose
>
> On Mon, Oct 6, 2014 at 8:02 PM, Bryan Thompson <br...@sy...> wrote:
> > The purpose of RDR is to permit statements about statements.
> >
> > The purpose of named graphs is to allow statements to be collected into
> > containers.
> >
> > With RDF* support for named graphs, you could do both.
> >
> > Whether or not this is a good idea is an interesting question.  Consider,
> > that named graphs could be interpreted as just a special case of a
> statement
> > about a statement where the database then applies special indexing
> > (typically by maintaining additional indices for fast access by the named
> > graph).
> >
> > For example, given:
> >
> > <<:a :b :c> :namedGraph :d>
> >
> > If we assume that ":namedGraph" has the semantics of the SPARQL named
> graphs
> > mechanism, then this RDR assertion says that the statement :a :b :c
> exists
> > in the named graph :d.
> >
> > If so, then the RDR mechanisms always apply to triples and the named
> graphs
> > mechanism just specifies the containers within which a given triple
> > (including an RDR triple) is visible.
> >
> > Thanks,
> > Bryan
> >
> > ----
> > Bryan Thompson
> > Chief Scientist & Founder
> > SYSTAP, LLC
> > 4501 Tower Road
> > Greensboro, NC 27410
> > br...@sy...
> > http://bigdata.com
> > http://mapgraph.io
> >
> > CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
> for
> > the sole use of the intended recipient(s) and are confidential or
> > proprietary to SYSTAP. Any unauthorized review, use, disclosure,
> > dissemination or copying of this email or its contents or attachments is
> > prohibited. If you have received this communication in error, please
> notify
> > the sender by reply email and permanently delete all copies of the email
> and
> > its contents and attachments.
> >
> >
> > On Mon, Oct 6, 2014 at 10:19 AM, Rose Beck <ros...@gm...>
> wrote:
> >>
> >> Dear Bryan,
> >>
> >> Thanks for the enlightening write-up about RDR. But I have a question
> >> in the write-up you wrote "In the future, we plan to add support for
> >> RDF* and SPARQL* to the quads mode of the platform as well. This will
> >> allow statement level metadata to co-exist seamlessly with the named
> >> graphs model." But I dont understand the need for supporting RDF* and
> >> SPARQL* in quads mode. I mean I dont understand as to why do we need
> >> to allow statement level metadata to co-exist with named graph model.
> >> Can you please explain this with an example.
> >>
> >>
> >> Thanks & Regards,
> >> Rose.
> >>
> >> On Mon, Oct 6, 2014 at 5:59 PM, Bryan Thompson <br...@sy...>
> wrote:
> >> > I've added a page to the wiki based on that blog post:
> >> >
> >> > wiki.bigdata.com/wiki/index.php/Reification_Done_Right
> >> >
> >> > Thanks,
> >> > Bryan
> >> >
> >> > ----
> >> > Bryan Thompson
> >> > Chief Scientist & Founder
> >> > SYSTAP, LLC
> >> > 4501 Tower Road
> >> > Greensboro, NC 27410
> >> > br...@sy...
> >> > http://bigdata.com
> >> > http://mapgraph.io
> >> >
> >> > CONFIDENTIALITY NOTICE:  This email and its contents and attachments
> are
> >> > for
> >> > the sole use of the intended recipient(s) and are confidential or
> >> > proprietary to SYSTAP. Any unauthorized review, use, disclosure,
> >> > dissemination or copying of this email or its contents or attachments
> is
> >> > prohibited. If you have received this communication in error, please
> >> > notify
> >> > the sender by reply email and permanently delete all copies of the
> email
> >> > and
> >> > its contents and attachments.
> >> >
> >> >
> >> > On Sun, Oct 5, 2014 at 5:27 PM, Rose Beck <ros...@gm...>
> wrote:
> >> >>
> >> >> Dear all,
> >> >>
> >> >> I have downloaded bigdata.war and have deployed it using sesame HTTP
> >> >> API. Now I am not getting as to how should I load rdf
> >> >> triples/provenance with triples to bigdata using nanosparqlserver? I
> >> >> am using sesame HTTP API (using apache tomcat). Can someone please
> >> >> help.
> >> >>
> >> >> I intend to use mysql, native java and postgres with sesame. Any help
> >> >> will be deeply appreciated.
> >> >>
> >> >> Regards,
> >> >> Rose
> >> >>
> >> >>
> >> >>
> >> >>
> ------------------------------------------------------------------------------
> >> >> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> >> >> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS
> >> >> Reports
> >> >> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> >> >> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> >> >>
> >> >>
> >> >>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> >> >> _______________________________________________
> >> >> Bigdata-developers mailing list
> >> >> Big...@li...
> >> >> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
> >> >
> >> >
> >
> >
>

Re: [Bigdata-developers] Bulk loading into bigdata

[Rose B. <ros...@gm...>]

Dear Bryan,

Probably I am new to the field. But since you are an experienced
person in the field, therefore can you please help me understand that:
when we apply RDR mechanism to triples, then what is the practical
use-case application of using named graph mechanism? I mean I
understand intuitively but I still am not able to get the practical
significance of using named graphs.


Thanks & Regards,
Rose

On Mon, Oct 6, 2014 at 8:02 PM, Bryan Thompson <br...@sy...> wrote:
> The purpose of RDR is to permit statements about statements.
>
> The purpose of named graphs is to allow statements to be collected into
> containers.
>
> With RDF* support for named graphs, you could do both.
>
> Whether or not this is a good idea is an interesting question.  Consider,
> that named graphs could be interpreted as just a special case of a statement
> about a statement where the database then applies special indexing
> (typically by maintaining additional indices for fast access by the named
> graph).
>
> For example, given:
>
> <<:a :b :c> :namedGraph :d>
>
> If we assume that ":namedGraph" has the semantics of the SPARQL named graphs
> mechanism, then this RDR assertion says that the statement :a :b :c exists
> in the named graph :d.
>
> If so, then the RDR mechanisms always apply to triples and the named graphs
> mechanism just specifies the containers within which a given triple
> (including an RDR triple) is visible.
>
> Thanks,
> Bryan
>
> ----
> Bryan Thompson
> Chief Scientist & Founder
> SYSTAP, LLC
> 4501 Tower Road
> Greensboro, NC 27410
> br...@sy...
> http://bigdata.com
> http://mapgraph.io
>
> CONFIDENTIALITY NOTICE:  This email and its contents and attachments are for
> the sole use of the intended recipient(s) and are confidential or
> proprietary to SYSTAP. Any unauthorized review, use, disclosure,
> dissemination or copying of this email or its contents or attachments is
> prohibited. If you have received this communication in error, please notify
> the sender by reply email and permanently delete all copies of the email and
> its contents and attachments.
>
>
> On Mon, Oct 6, 2014 at 10:19 AM, Rose Beck <ros...@gm...> wrote:
>>
>> Dear Bryan,
>>
>> Thanks for the enlightening write-up about RDR. But I have a question
>> in the write-up you wrote "In the future, we plan to add support for
>> RDF* and SPARQL* to the quads mode of the platform as well. This will
>> allow statement level metadata to co-exist seamlessly with the named
>> graphs model." But I dont understand the need for supporting RDF* and
>> SPARQL* in quads mode. I mean I dont understand as to why do we need
>> to allow statement level metadata to co-exist with named graph model.
>> Can you please explain this with an example.
>>
>>
>> Thanks & Regards,
>> Rose.
>>
>> On Mon, Oct 6, 2014 at 5:59 PM, Bryan Thompson <br...@sy...> wrote:
>> > I've added a page to the wiki based on that blog post:
>> >
>> > wiki.bigdata.com/wiki/index.php/Reification_Done_Right
>> >
>> > Thanks,
>> > Bryan
>> >
>> > ----
>> > Bryan Thompson
>> > Chief Scientist & Founder
>> > SYSTAP, LLC
>> > 4501 Tower Road
>> > Greensboro, NC 27410
>> > br...@sy...
>> > http://bigdata.com
>> > http://mapgraph.io
>> >
>> > CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
>> > for
>> > the sole use of the intended recipient(s) and are confidential or
>> > proprietary to SYSTAP. Any unauthorized review, use, disclosure,
>> > dissemination or copying of this email or its contents or attachments is
>> > prohibited. If you have received this communication in error, please
>> > notify
>> > the sender by reply email and permanently delete all copies of the email
>> > and
>> > its contents and attachments.
>> >
>> >
>> > On Sun, Oct 5, 2014 at 5:27 PM, Rose Beck <ros...@gm...> wrote:
>> >>
>> >> Dear all,
>> >>
>> >> I have downloaded bigdata.war and have deployed it using sesame HTTP
>> >> API. Now I am not getting as to how should I load rdf
>> >> triples/provenance with triples to bigdata using nanosparqlserver? I
>> >> am using sesame HTTP API (using apache tomcat). Can someone please
>> >> help.
>> >>
>> >> I intend to use mysql, native java and postgres with sesame. Any help
>> >> will be deeply appreciated.
>> >>
>> >> Regards,
>> >> Rose
>> >>
>> >>
>> >>
>> >> ------------------------------------------------------------------------------
>> >> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>> >> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS
>> >> Reports
>> >> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>> >> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>> >>
>> >>
>> >> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>> >> _______________________________________________
>> >> Bigdata-developers mailing list
>> >> Big...@li...
>> >> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
>> >
>> >
>
>

Re: [Bigdata-developers] Bulk loading into bigdata

[Bryan T. <br...@sy...>]

The purpose of RDR is to permit statements about statements.

The purpose of named graphs is to allow statements to be collected into
containers.

With RDF* support for named graphs, you could do both.

Whether or not this is a good idea is an interesting question.  Consider,
that named graphs could be interpreted as just a special case of a
statement about a statement where the database then applies special
indexing (typically by maintaining additional indices for fast access by
the named graph).

For example, given:

<<:a :b :c> :namedGraph :d>

If we assume that ":namedGraph" has the semantics of the SPARQL named
graphs mechanism, then this RDR assertion says that the statement :a :b :c
exists in the named graph :d.

If so, then the RDR mechanisms always apply to triples and the named graphs
mechanism just specifies the containers within which a given triple
(including an RDR triple) is visible.

Thanks,
Bryan

----
Bryan Thompson
Chief Scientist & Founder
SYSTAP, LLC
4501 Tower Road
Greensboro, NC 27410
br...@sy...
http://bigdata.com
http://mapgraph.io

CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
for the sole use of the intended recipient(s) and are confidential or
proprietary to SYSTAP. Any unauthorized review, use, disclosure,
dissemination or copying of this email or its contents or attachments is
prohibited. If you have received this communication in error, please notify
the sender by reply email and permanently delete all copies of the email
and its contents and attachments.

On Mon, Oct 6, 2014 at 10:19 AM, Rose Beck <ros...@gm...> wrote:

> Dear Bryan,
>
> Thanks for the enlightening write-up about RDR. But I have a question
> in the write-up you wrote "In the future, we plan to add support for
> RDF* and SPARQL* to the quads mode of the platform as well. This will
> allow statement level metadata to co-exist seamlessly with the named
> graphs model." But I dont understand the need for supporting RDF* and
> SPARQL* in quads mode. I mean I dont understand as to why do we need
> to allow statement level metadata to co-exist with named graph model.
> Can you please explain this with an example.
>
>
> Thanks & Regards,
> Rose.
>
> On Mon, Oct 6, 2014 at 5:59 PM, Bryan Thompson <br...@sy...> wrote:
> > I've added a page to the wiki based on that blog post:
> >
> > wiki.bigdata.com/wiki/index.php/Reification_Done_Right
> >
> > Thanks,
> > Bryan
> >
> > ----
> > Bryan Thompson
> > Chief Scientist & Founder
> > SYSTAP, LLC
> > 4501 Tower Road
> > Greensboro, NC 27410
> > br...@sy...
> > http://bigdata.com
> > http://mapgraph.io
> >
> > CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
> for
> > the sole use of the intended recipient(s) and are confidential or
> > proprietary to SYSTAP. Any unauthorized review, use, disclosure,
> > dissemination or copying of this email or its contents or attachments is
> > prohibited. If you have received this communication in error, please
> notify
> > the sender by reply email and permanently delete all copies of the email
> and
> > its contents and attachments.
> >
> >
> > On Sun, Oct 5, 2014 at 5:27 PM, Rose Beck <ros...@gm...> wrote:
> >>
> >> Dear all,
> >>
> >> I have downloaded bigdata.war and have deployed it using sesame HTTP
> >> API. Now I am not getting as to how should I load rdf
> >> triples/provenance with triples to bigdata using nanosparqlserver? I
> >> am using sesame HTTP API (using apache tomcat). Can someone please
> >> help.
> >>
> >> I intend to use mysql, native java and postgres with sesame. Any help
> >> will be deeply appreciated.
> >>
> >> Regards,
> >> Rose
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> >> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> >> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> >> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> >>
> >>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> >> _______________________________________________
> >> Bigdata-developers mailing list
> >> Big...@li...
> >> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
> >
> >
>

Re: [Bigdata-developers] Bulk loading into bigdata

[Rose B. <ros...@gm...>]

Dear Bryan,

Thanks for the enlightening write-up about RDR. But I have a question
in the write-up you wrote "In the future, we plan to add support for
RDF* and SPARQL* to the quads mode of the platform as well. This will
allow statement level metadata to co-exist seamlessly with the named
graphs model." But I dont understand the need for supporting RDF* and
SPARQL* in quads mode. I mean I dont understand as to why do we need
to allow statement level metadata to co-exist with named graph model.
Can you please explain this with an example.


Thanks & Regards,
Rose.

On Mon, Oct 6, 2014 at 5:59 PM, Bryan Thompson <br...@sy...> wrote:
> I've added a page to the wiki based on that blog post:
>
> wiki.bigdata.com/wiki/index.php/Reification_Done_Right
>
> Thanks,
> Bryan
>
> ----
> Bryan Thompson
> Chief Scientist & Founder
> SYSTAP, LLC
> 4501 Tower Road
> Greensboro, NC 27410
> br...@sy...
> http://bigdata.com
> http://mapgraph.io
>
> CONFIDENTIALITY NOTICE:  This email and its contents and attachments are for
> the sole use of the intended recipient(s) and are confidential or
> proprietary to SYSTAP. Any unauthorized review, use, disclosure,
> dissemination or copying of this email or its contents or attachments is
> prohibited. If you have received this communication in error, please notify
> the sender by reply email and permanently delete all copies of the email and
> its contents and attachments.
>
>
> On Sun, Oct 5, 2014 at 5:27 PM, Rose Beck <ros...@gm...> wrote:
>>
>> Dear all,
>>
>> I have downloaded bigdata.war and have deployed it using sesame HTTP
>> API. Now I am not getting as to how should I load rdf
>> triples/provenance with triples to bigdata using nanosparqlserver? I
>> am using sesame HTTP API (using apache tomcat). Can someone please
>> help.
>>
>> I intend to use mysql, native java and postgres with sesame. Any help
>> will be deeply appreciated.
>>
>> Regards,
>> Rose
>>
>>
>> ------------------------------------------------------------------------------
>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Bigdata-developers mailing list
>> Big...@li...
>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
>
>

Re: [Bigdata-developers] Bulk loading into bigdata

[Bryan T. <br...@sy...>]

I've added a page to the wiki based on that blog post:

wiki.bigdata.com/wiki/index.php/Reification_Done_Right

Thanks,
Bryan

----
Bryan Thompson
Chief Scientist & Founder
SYSTAP, LLC
4501 Tower Road
Greensboro, NC 27410
br...@sy...
http://bigdata.com
http://mapgraph.io

CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
for the sole use of the intended recipient(s) and are confidential or
proprietary to SYSTAP. Any unauthorized review, use, disclosure,
dissemination or copying of this email or its contents or attachments is
prohibited. If you have received this communication in error, please notify
the sender by reply email and permanently delete all copies of the email
and its contents and attachments.

On Sun, Oct 5, 2014 at 5:27 PM, Rose Beck <ros...@gm...> wrote:

> Dear all,
>
> I have downloaded bigdata.war and have deployed it using sesame HTTP
> API. Now I am not getting as to how should I load rdf
> triples/provenance with triples to bigdata using nanosparqlserver? I
> am using sesame HTTP API (using apache tomcat). Can someone please
> help.
>
> I intend to use mysql, native java and postgres with sesame. Any help
> will be deeply appreciated.
>
> Regards,
> Rose
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Bigdata-developers mailing list
> Big...@li...
> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
>

Re: [Bigdata-developers] [Bigdata-commit] Bulk loading into bigdata

[Bryan T. <br...@sy...>]

Rose,

You can use either the syntax extension described in the the following
links or you can just load data with reified statements. If the database
mode to support RDR is enabled, then the reified statements will be
automatically interpreted as RDR assertions.

See http://blog.bigdata.com/?p=716
See http://www.bigdata.com/whitepapers/reifSPARQL.pdf
See http://arxiv.org/pdf/1406.3399.pdf

Please note that concurrent query against the sesame http interface
wrapping the bigdata sail is much less efficient than using the
nanoSparqlServer.  This is because the openrdf semantics for a connection
are always read/write.  Bigdata uses read-only connections as well that are
non-blocking and which offer substantially higher throughput for concurrent
query. The nanoSparqlServer supports these non-blocking connections
automatically.

Thanks,
Bryan

On Sunday, October 5, 2014, Rose Beck <ros...@gm...> wrote:

> Dear all,
>
> I have downloaded bigdata.war and have deployed it using sesame HTTP
> API. Now I am not getting as to how should I load rdf
> triples/provenance with triples to bigdata using nanosparqlserver? I
> am using sesame HTTP API (using apache tomcat). Can someone please
> help.
>
> I intend to use mysql, native java and postgres with sesame. Any help
> will be deeply appreciated.
>
> Regards,
> Rose
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Bigdata-developers mailing list
> Big...@li... <javascript:;>
> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
>


-- 
----
Bryan Thompson
Chief Scientist & Founder
SYSTAP, LLC
4501 Tower Road
Greensboro, NC 27410
br...@sy...
http://bigdata.com
http://mapgraph.io

CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
for the sole use of the intended recipient(s) and are confidential or
proprietary to SYSTAP. Any unauthorized review, use, disclosure,
dissemination or copying of this email or its contents or attachments is
prohibited. If you have received this communication in error, please notify
the sender by reply email and permanently delete all copies of the email
and its contents and attachments.

[Bigdata-developers] Bulk loading into bigdata

[Rose B. <ros...@gm...>]

Dear all,

I have downloaded bigdata.war and have deployed it using sesame HTTP
API. Now I am not getting as to how should I load rdf
triples/provenance with triples to bigdata using nanosparqlserver? I
am using sesame HTTP API (using apache tomcat). Can someone please
help.

I intend to use mysql, native java and postgres with sesame. Any help
will be deeply appreciated.

Regards,
Rose

Re: [Bigdata-developers] on test protocol memory leaks trac 1015

[Bryan T. <br...@sy...>]

Jeremy,

I commented out the line to clear the standalone query engine cache and
forced a clean checkout from SVN to see if that will clear up the failed CI
builds.

If you are seeing a leak in that cache, it probably means that you have a
hard reference to the QueryEngine. That might occur if you do not shutdown
the Journals such that they can be finalized.  Without that, the
QueryEngine might be left running.

Ah. Look at this line in BigdataSail:

      queryEngine = QueryEngineFactory.*getQueryController*(mainDatabase

              .getIndexManager());

A hard reference to a BigdataSail pins both the Journal

    *final* *protected* AbstractTripleStore database;

and the QueryEngine:

    *final* *private* QueryEngine queryEngine;

I would look for Test member fields that were references to BigdataSail
objects (or BigdataSailConnection objects, etc.). That is probably the
source of the leak.
Bryan

----
Bryan Thompson
Chief Scientist & Founder
SYSTAP, LLC
4501 Tower Road
Greensboro, NC 27410
br...@sy...
http://bigdata.com
http://mapgraph.io

CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
for the sole use of the intended recipient(s) and are confidential or
proprietary to SYSTAP. Any unauthorized review, use, disclosure,
dissemination or copying of this email or its contents or attachments is
prohibited. If you have received this communication in error, please notify
the sender by reply email and permanently delete all copies of the email
and its contents and attachments.

On Mon, Sep 29, 2014 at 5:53 PM, Bryan Thompson <br...@sy...> wrote:

> The code there has not been changed in quite a while.
>
>     private static ConcurrentWeakValueCache<IBTreeManager, QueryEngine>
> standaloneQECache = new ConcurrentWeakValueCache<IBTreeManager,
> QueryEngine>(
>             0/* queueCapacity */
>     );
>
> The IBTreeManager is a Journal.  Tthe QueryEngine becomes only weakly
> reachable and gets queued for finalization.  When the reference queue
> receives that notice, the entry in the ConcurrentWeakValueMap is removed.
> That causes the Journal to no longer be strongly reachable, at which point
> the Journal is also available for GC.
>
> ConcurrentWeakValueMap::
>
> protected void removeClearedEntries()
>     {
>
>         if (referenceQueue == null)
>             return;
>
>         int counter = 0;
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *        for (Reference<? extends V> ref = referenceQueue.poll(); ref !=
> null; ref = referenceQueue                .poll()) {            final K k =
> ((WeakRef<K, V>) ref).k;            if (map.get(k) == ref) {
> if (DEBUG) {                    log.debug("Removing cleared reference:
> key=" + k);                }
> removeMapEntry(k);                                counter++;
> *            }
>
>         }
>
>         if( counter > 1 ) {
>
>             if( INFO ) {
>
>                 log.info("Removed " + counter + " cleared references");
>
>             }
>
>         }
>
>     }
>
>
> Bryan
>
> ----
> Bryan Thompson
> Chief Scientist & Founder
> SYSTAP, LLC
> 4501 Tower Road
> Greensboro, NC 27410
> br...@sy...
> http://bigdata.com
> http://mapgraph.io
>
> CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
> for the sole use of the intended recipient(s) and are confidential or
> proprietary to SYSTAP. Any unauthorized review, use, disclosure,
> dissemination or copying of this email or its contents or attachments is
> prohibited. If you have received this communication in error, please notify
> the sender by reply email and permanently delete all copies of the email
> and its contents and attachments.
>
> On Mon, Sep 29, 2014 at 4:01 PM, Jeremy J Carroll <jj...@sy...> wrote:
>
>> What about the com.bigdata.bop.fed.QueryEngineFactory.standaloneQECache ?
>>
>> Was I mistaken to read that as a real leak? The code would be cleaner to
>> not have that method and its call, maybe the destroy and the nulling out is
>> sufficient?
>>
>> Jeremy J Carroll
>> Principal Architect
>> Syapse, Inc.
>>
>>
>>
>> On Sep 29, 2014, at 12:12 PM, Bryan Thompson <br...@sy...> wrote:
>>
>> I have looked through those issues and verified that (a) the references
>> are eventually released; and (b) you can force yourkit to take them through
>> a GC and release many of them.  There is a
>> ConcurrentWeakValueHashMapWithTimeout that has a ring buffer which gets
>> cleared down as things age out. Until that happens some kinds of references
>> will remain in CI, but they do get cleared out eventually.
>>
>> ----
>> Bryan Thompson
>> Chief Scientist & Founder
>> SYSTAP, LLC
>> 4501 Tower Road
>> Greensboro, NC 27410
>> br...@sy...
>> http://bigdata.com
>> http://mapgraph.io
>>
>> CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
>> for the sole use of the intended recipient(s) and are confidential or
>> proprietary to SYSTAP. Any unauthorized review, use, disclosure,
>> dissemination or copying of this email or its contents or attachments is
>> prohibited. If you have received this communication in error, please notify
>> the sender by reply email and permanently delete all copies of the email
>> and its contents and attachments.
>>
>> On Mon, Sep 29, 2014 at 3:03 PM, Jeremy J Carroll <jj...@sy...> wrote:
>>
>>>
>>>
>>> Congrats on getting latest release out.
>>>
>>> Better late than never, I got to looking once more at the memory leaks
>>> in TestProtocolAll and have made commit r8670 which I believe addresses
>>> them.
>>>
>>> This adds a method to tear down the 'mode' quads/triples/sids and its
>>> related index etc at the right point.
>>>
>>> Some concerns:
>>> - yourkit was suggesting leaks through
>>> com.bigdata.bop.fed.QueryEngineFactory.standaloneQECache
>>>
>>> and I somewhat inelegantly added a method:
>>>
>>> com.bigdata.bop.fed.QueryEngineFactory.clearStandAloneQECacheDuringTesting()
>>> which I call again at the end of each mode of the protocol tests
>>>
>>> However, the test issue in this area may be indicative of a real memory
>>> leak here (which i believe is fairly new code).
>>> My own, fairly casual assessment, is that the strong reference to the
>>> key in this cache may well be problematic. If so, fixing that and removing
>>> my clearStandAloneQECacheDuringTesting() would be better.
>>>
>>> Further I was having some issues with clearing references through the
>>> WeakHashMap at
>>>
>>> com.bigdata.btree.ReadWriteLockManager.locks
>>>
>>> I slightly convinced myself that these were artifacts of my test runs,
>>> and that the finalizers would eventually run and the memory would
>>> eventually be released. That is certainly the theory, but I have had bad
>>> experiences with finalizers and the finalizer queue in the past, and I am
>>> pretty suspicious of WeakHashMaps as a result. However, despite these
>>> concerns, I made no code changes in this area.
>>>
>>> Jeremy
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Slashdot TV.  Videos for Nerds.  Stuff that Matters.
>>>
>>> http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk
>>> _______________________________________________
>>> Bigdata-developers mailing list
>>> Big...@li...
>>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
>>>
>>
>>
>>
>

Re: [Bigdata-developers] on test protocol memory leaks trac 1015

[Bryan T. <br...@sy...>]

The code there has not been changed in quite a while.

    private static ConcurrentWeakValueCache<IBTreeManager, QueryEngine>
standaloneQECache = new ConcurrentWeakValueCache<IBTreeManager,
QueryEngine>(
            0/* queueCapacity */
    );

The IBTreeManager is a Journal.  Tthe QueryEngine becomes only weakly
reachable and gets queued for finalization.  When the reference queue
receives that notice, the entry in the ConcurrentWeakValueMap is removed.
That causes the Journal to no longer be strongly reachable, at which point
the Journal is also available for GC.

ConcurrentWeakValueMap::

protected void removeClearedEntries()
    {

        if (referenceQueue == null)
            return;

        int counter = 0;


















*        for (Reference<? extends V> ref = referenceQueue.poll(); ref !=
null; ref = referenceQueue                .poll()) {            final K k =
((WeakRef<K, V>) ref).k;            if (map.get(k) == ref) {
if (DEBUG) {                    log.debug("Removing cleared reference:
key=" + k);                }
removeMapEntry(k);                                counter++;
*            }

        }

        if( counter > 1 ) {

            if( INFO ) {

                log.info("Removed " + counter + " cleared references");

            }

        }

    }


Bryan

----
Bryan Thompson
Chief Scientist & Founder
SYSTAP, LLC
4501 Tower Road
Greensboro, NC 27410
br...@sy...
http://bigdata.com
http://mapgraph.io

CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
for the sole use of the intended recipient(s) and are confidential or
proprietary to SYSTAP. Any unauthorized review, use, disclosure,
dissemination or copying of this email or its contents or attachments is
prohibited. If you have received this communication in error, please notify
the sender by reply email and permanently delete all copies of the email
and its contents and attachments.

On Mon, Sep 29, 2014 at 4:01 PM, Jeremy J Carroll <jj...@sy...> wrote:

> What about the com.bigdata.bop.fed.QueryEngineFactory.standaloneQECache ?
>
> Was I mistaken to read that as a real leak? The code would be cleaner to
> not have that method and its call, maybe the destroy and the nulling out is
> sufficient?
>
> Jeremy J Carroll
> Principal Architect
> Syapse, Inc.
>
>
>
> On Sep 29, 2014, at 12:12 PM, Bryan Thompson <br...@sy...> wrote:
>
> I have looked through those issues and verified that (a) the references
> are eventually released; and (b) you can force yourkit to take them through
> a GC and release many of them.  There is a
> ConcurrentWeakValueHashMapWithTimeout that has a ring buffer which gets
> cleared down as things age out. Until that happens some kinds of references
> will remain in CI, but they do get cleared out eventually.
>
> ----
> Bryan Thompson
> Chief Scientist & Founder
> SYSTAP, LLC
> 4501 Tower Road
> Greensboro, NC 27410
> br...@sy...
> http://bigdata.com
> http://mapgraph.io
>
> CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
> for the sole use of the intended recipient(s) and are confidential or
> proprietary to SYSTAP. Any unauthorized review, use, disclosure,
> dissemination or copying of this email or its contents or attachments is
> prohibited. If you have received this communication in error, please notify
> the sender by reply email and permanently delete all copies of the email
> and its contents and attachments.
>
> On Mon, Sep 29, 2014 at 3:03 PM, Jeremy J Carroll <jj...@sy...> wrote:
>
>>
>>
>> Congrats on getting latest release out.
>>
>> Better late than never, I got to looking once more at the memory leaks in
>> TestProtocolAll and have made commit r8670 which I believe addresses them.
>>
>> This adds a method to tear down the 'mode' quads/triples/sids and its
>> related index etc at the right point.
>>
>> Some concerns:
>> - yourkit was suggesting leaks through
>> com.bigdata.bop.fed.QueryEngineFactory.standaloneQECache
>>
>> and I somewhat inelegantly added a method:
>>
>> com.bigdata.bop.fed.QueryEngineFactory.clearStandAloneQECacheDuringTesting()
>> which I call again at the end of each mode of the protocol tests
>>
>> However, the test issue in this area may be indicative of a real memory
>> leak here (which i believe is fairly new code).
>> My own, fairly casual assessment, is that the strong reference to the key
>> in this cache may well be problematic. If so, fixing that and removing my
>> clearStandAloneQECacheDuringTesting() would be better.
>>
>> Further I was having some issues with clearing references through the
>> WeakHashMap at
>>
>> com.bigdata.btree.ReadWriteLockManager.locks
>>
>> I slightly convinced myself that these were artifacts of my test runs,
>> and that the finalizers would eventually run and the memory would
>> eventually be released. That is certainly the theory, but I have had bad
>> experiences with finalizers and the finalizer queue in the past, and I am
>> pretty suspicious of WeakHashMaps as a result. However, despite these
>> concerns, I made no code changes in this area.
>>
>> Jeremy
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Slashdot TV.  Videos for Nerds.  Stuff that Matters.
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Bigdata-developers mailing list
>> Big...@li...
>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
>>
>
>
>

Re: [Bigdata-developers] on test protocol memory leaks trac 1015

[Jeremy J C. <jj...@sy...>]

What about the com.bigdata.bop.fed.QueryEngineFactory.standaloneQECache ?

Was I mistaken to read that as a real leak? The code would be cleaner to not have that method and its call, maybe the destroy and the nulling out is sufficient?

Jeremy J Carroll
Principal Architect
Syapse, Inc.



On Sep 29, 2014, at 12:12 PM, Bryan Thompson <br...@sy...> wrote:

> I have looked through those issues and verified that (a) the references are eventually released; and (b) you can force yourkit to take them through a GC and release many of them.  There is a ConcurrentWeakValueHashMapWithTimeout that has a ring buffer which gets cleared down as things age out. Until that happens some kinds of references will remain in CI, but they do get cleared out eventually.
> 
> ----
> Bryan Thompson
> Chief Scientist & Founder
> SYSTAP, LLC
> 4501 Tower Road
> Greensboro, NC 27410
> br...@sy...
> http://bigdata.com
> http://mapgraph.io
> CONFIDENTIALITY NOTICE:  This email and its contents and attachments are for the sole use of the intended recipient(s) and are confidential or proprietary to SYSTAP. Any unauthorized review, use, disclosure, dissemination or copying of this email or its contents or attachments is prohibited. If you have received this communication in error, please notify the sender by reply email and permanently delete all copies of the email and its contents and attachments.
> 
> 
> 
> On Mon, Sep 29, 2014 at 3:03 PM, Jeremy J Carroll <jj...@sy...> wrote:
> 
> 
> Congrats on getting latest release out.
> 
> Better late than never, I got to looking once more at the memory leaks in TestProtocolAll and have made commit r8670 which I believe addresses them.
> 
> This adds a method to tear down the 'mode' quads/triples/sids and its related index etc at the right point.
> 
> Some concerns:
> - yourkit was suggesting leaks through
> com.bigdata.bop.fed.QueryEngineFactory.standaloneQECache
> 
> and I somewhat inelegantly added a method:
> com.bigdata.bop.fed.QueryEngineFactory.clearStandAloneQECacheDuringTesting()
> which I call again at the end of each mode of the protocol tests
> 
> However, the test issue in this area may be indicative of a real memory leak here (which i believe is fairly new code).
> My own, fairly casual assessment, is that the strong reference to the key in this cache may well be problematic. If so, fixing that and removing my clearStandAloneQECacheDuringTesting() would be better.
> 
> Further I was having some issues with clearing references through the WeakHashMap at
> 
> com.bigdata.btree.ReadWriteLockManager.locks
> 
> I slightly convinced myself that these were artifacts of my test runs, and that the finalizers would eventually run and the memory would eventually be released. That is certainly the theory, but I have had bad experiences with finalizers and the finalizer queue in the past, and I am pretty suspicious of WeakHashMaps as a result. However, despite these concerns, I made no code changes in this area.
> 
> Jeremy
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> Slashdot TV.  Videos for Nerds.  Stuff that Matters.
> http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk
> _______________________________________________
> Bigdata-developers mailing list
> Big...@li...
> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
> 

Re: [Bigdata-developers] on test protocol memory leaks trac 1015

[Bryan T. <br...@sy...>]

I have looked through those issues and verified that (a) the references are
eventually released; and (b) you can force yourkit to take them through a
GC and release many of them.  There is a
ConcurrentWeakValueHashMapWithTimeout that has a ring buffer which gets
cleared down as things age out. Until that happens some kinds of references
will remain in CI, but they do get cleared out eventually.

----
Bryan Thompson
Chief Scientist & Founder
SYSTAP, LLC
4501 Tower Road
Greensboro, NC 27410
br...@sy...
http://bigdata.com
http://mapgraph.io

CONFIDENTIALITY NOTICE:  This email and its contents and attachments are
for the sole use of the intended recipient(s) and are confidential or
proprietary to SYSTAP. Any unauthorized review, use, disclosure,
dissemination or copying of this email or its contents or attachments is
prohibited. If you have received this communication in error, please notify
the sender by reply email and permanently delete all copies of the email
and its contents and attachments.

On Mon, Sep 29, 2014 at 3:03 PM, Jeremy J Carroll <jj...@sy...> wrote:

>
>
> Congrats on getting latest release out.
>
> Better late than never, I got to looking once more at the memory leaks in
> TestProtocolAll and have made commit r8670 which I believe addresses them.
>
> This adds a method to tear down the 'mode' quads/triples/sids and its
> related index etc at the right point.
>
> Some concerns:
> - yourkit was suggesting leaks through
> com.bigdata.bop.fed.QueryEngineFactory.standaloneQECache
>
> and I somewhat inelegantly added a method:
>
> com.bigdata.bop.fed.QueryEngineFactory.clearStandAloneQECacheDuringTesting()
> which I call again at the end of each mode of the protocol tests
>
> However, the test issue in this area may be indicative of a real memory
> leak here (which i believe is fairly new code).
> My own, fairly casual assessment, is that the strong reference to the key
> in this cache may well be problematic. If so, fixing that and removing my
> clearStandAloneQECacheDuringTesting() would be better.
>
> Further I was having some issues with clearing references through the
> WeakHashMap at
>
> com.bigdata.btree.ReadWriteLockManager.locks
>
> I slightly convinced myself that these were artifacts of my test runs, and
> that the finalizers would eventually run and the memory would eventually be
> released. That is certainly the theory, but I have had bad experiences with
> finalizers and the finalizer queue in the past, and I am pretty suspicious
> of WeakHashMaps as a result. However, despite these concerns, I made no
> code changes in this area.
>
> Jeremy
>
>
>
>
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Slashdot TV.  Videos for Nerds.  Stuff that Matters.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk
> _______________________________________________
> Bigdata-developers mailing list
> Big...@li...
> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
>

[Bigdata-developers] on test protocol memory leaks trac 1015

[Jeremy J C. <jj...@sy...>]

Congrats on getting latest release out.

Better late than never, I got to looking once more at the memory leaks in TestProtocolAll and have made commit r8670 which I believe addresses them.

This adds a method to tear down the 'mode' quads/triples/sids and its related index etc at the right point.

Some concerns:
- yourkit was suggesting leaks through 
com.bigdata.bop.fed.QueryEngineFactory.standaloneQECache

and I somewhat inelegantly added a method:
com.bigdata.bop.fed.QueryEngineFactory.clearStandAloneQECacheDuringTesting()
which I call again at the end of each mode of the protocol tests

However, the test issue in this area may be indicative of a real memory leak here (which i believe is fairly new code).
My own, fairly casual assessment, is that the strong reference to the key in this cache may well be problematic. If so, fixing that and removing my clearStandAloneQECacheDuringTesting() would be better.

Further I was having some issues with clearing references through the WeakHashMap at 

com.bigdata.btree.ReadWriteLockManager.locks

I slightly convinced myself that these were artifacts of my test runs, and that the finalizers would eventually run and the memory would eventually be released. That is certainly the theory, but I have had bad experiences with finalizers and the finalizer queue in the past, and I am pretty suspicious of WeakHashMaps as a result. However, despite these concerns, I made no code changes in this area.

Jeremy

[Bigdata-developers] Posts from bigdata for 09/29/2014

[Bigdata by S. L. <bi...@sy...>]

Checkout the latest Blog post on Bigdata by SYSTAP, LLC.

View this email in your browser (http://us8.campaign-archive2.com/?u=807fe42a6d19f97994387207d&id=f8ea694e93&e=085d8ae40c)

Updates from


** bigdata
------------------------------------------------------------
bigdata(R) is a scale-out storage and computing fabric supporting optional transactions, very high concurrency, and very high aggregate IO rates.

In the 09/29/2014 edition:
* Bigdata Release 1.3.2 (HA Load Balancer, Blueprints, RDR, new Workbench)




** Bigdata Release 1.3.2 (HA Load Balancer, Blueprints, RDR, new Workbench) (http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=a5c39c88bb&e=085d8ae40c)
------------------------------------------------------------
By Bryan Thompson on Sep 26, 2014 08:34 am
This is a minor release of bigdata(R) with critical security and bug fixes.

Bigdata is a horizontally-scaled, open-source architecture for indexed data with an emphasis on RDF capable of loading 1B triples in under one hour on a 15 node cluster. Bigdata operates in both a single machine mode (Journal), highly available replication cluster mode (HAJournalServer), and a horizontally sharded cluster mode (BigdataFederation). The Journal provides fast scalable ACID indexed storage for very large data sets, up to 50 billion triples / quads. The HAJournalServer adds replication, online backup, horizontal scaling of query, and high availability. The federation provides fast scalable shard-wise parallel indexed storage using dynamic sharding and shard-wise ACID updates and incremental cluster size growth. Both platforms support fully concurrent readers with snapshot isolation.

Distributed processing offers greater throughput but does not reduce query or update latency. Choose the Journal when the anticipated scale and throughput requirements permit. Choose the HAJournalServer for high availability and linear scaling in query throughput. Choose the BigdataFederation when the administrative and machine overhead associated with operating a cluster is an acceptable tradeoff to have essentially unlimited data scaling and throughput.

See [1,2,8] for instructions on installing bigdata(R), [4] for the javadoc, and [3,5,6] for news, questions, and the latest developments. For more information about SYSTAP, LLC and bigdata, see [7].

Starting with the 1.0.0 release, we offer a WAR artifact [8] for easy installation of the single machine RDF database. For custom development and cluster installations we recommend checking out the code from SVN using the tag for this release. The code will build automatically under eclipse. You can also build the code using the ant script. The cluster installer requires the use of the ant script.

Starting with the 1.3.0 release, we offer a tarball artifact [10] for easy installation of the HA replication cluster.

You can download the WAR (standalone) or HA artifacts from:

http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=aad24c0d06&e=085d8ae40c

You can checkout this release from:

http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=9318262cf7&e=085d8ae40c

Critical or otherwise of note in this minor release:

- Stored query facility (#989).
- Improved locality for small allocation slots (#986).
- Improved scalability for RWStore (#936).
- Various improvements for the workbench.
- Various improvements for property graphs.
- Critical bug fix for hasStatements() for unisolated indices (#855, #1005).
- Critical bug fix for ConcurrentWeakValueHashMap (#1004).
- Critical bug fix for query timeouts (#772, #865).
- Critical bug fix for RWStore (#973).
- Security fix for Apache commons-fileupload (#1010).

New features in 1.3.x:

- Java 7 is now required.
- High availability [10].
- High availability load balancer.
- New RDF/SPARQL workbench.
- Blueprints API.
- RDF Graph Mining Service (GASService) [12].
- Reification Done Right (RDR) support [11].
- Property Path performance enhancements.
- Plus numerous other bug fixes and performance enhancements.

Feature summary:

- Highly Available Replication Clusters (HAJournalServer [10])
- Single machine data storage to ~50B triples/quads (RWStore);
- Clustered data storage is essentially unlimited (BigdataFederation);
- Simple embedded and/or webapp deployment (NanoSparqlServer);
- Triples, quads, or triples with provenance (SIDs);
- Fast RDFS+ inference and truth maintenance;
- Fast 100% native SPARQL 1.1 evaluation;
- Integrated “analytic” query package;
- %100 Java memory manager leverages the JVM native heap (no GC);

Road map [3]:

- Column-wise indexing;
- Runtime Query Optimizer for quads;
- Performance optimization for scale-out clusters; and
- Simplified deployment, configuration, and administration for scale-out clusters.

Change log:

Note: Versions with (*) MAY require data migration. For details, see [9].

1.3.2:

- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=dd31972edd&e=085d8ae40c (Jetty/LBS issues when deployed as WAR under tomcat)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=7208015df1&e=085d8ae40c (Upgrade apache http components to 1.3.1 (security))
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=0f8ccb93e0&e=085d8ae40c (Invalidate BTree objects if error occurs during eviction)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=21d735666f&e=085d8ae40c (Concurrent binding problem)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=e65a94da80&e=085d8ae40c (Concurrency issues in JVMHashJoinUtility caused by MAX_PARALLEL query hint override)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=e303c1b6bc&e=085d8ae40c (Add configuration option to turn off bottom-up evaluation)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=e177ac287d&e=085d8ae40c (Extend BigdataSailFactory to take arbitrary properties)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=efc5f48fae&e=085d8ae40c (SPARQL Update through BigdataGraph)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=e05b03d3a5&e=085d8ae40c (Add custom prefix support for query results)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=c7b2b883df&e=085d8ae40c (Allow general purpose SPARQL queries through BigdataGraph)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=e2fdbd3537&e=085d8ae40c (Deadlock between AbstractRunningQuery.cancel(), QueryLog.log(), and ArbitraryLengthPathTask)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=577e60ba12&e=085d8ae40c (Query hints not recognized in FILTERs)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=53478aaeeb&e=085d8ae40c (Stored query service)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=1109321a4e&e=085d8ae40c (Bad performance for FILTER EXISTS)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=967dc30305&e=085d8ae40c (maven build is broken)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=7f00526b02&e=085d8ae40c (Improve locality for small allocation slots)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=778770c85b&e=085d8ae40c (Deadlock in BigdataTriplePatternMaterializer)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=9102cf633f&e=085d8ae40c (HA Health Status Page)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=88c0363391&e=085d8ae40c (Name2Addr.indexNameScan(prefix) uses scan + filter)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=ee8d5c581e&e=085d8ae40c (RWStore.commit() should be more defensive)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=80f4a6a754&e=085d8ae40c (Clarify HTTP Status codes for CREATE NAMESPACE operation)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=53405aec89&e=085d8ae40c (no link to wiki from workbench)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=fde1cb4fa5&e=085d8ae40c (Failed to get namespace under concurrent update)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=76e270b40b&e=085d8ae40c (Can not run LBS mode with HA1 setup)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=9a849d63d6&e=085d8ae40c (Clone/modify namespace to create a new one)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=c74400ac24&e=085d8ae40c (Export namespace properties in XML/Java properties text format)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=4130cc849f&e=085d8ae40c (HA Load Balancer)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=f45258921e&e=085d8ae40c (Support larger metabits allocations)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=7ed2773402&e=085d8ae40c (Bigdata/Rexster integration)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=c01d2988ba&e=085d8ae40c (Formatted Layout for Status pages)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=b4cd1fe92e&e=085d8ae40c (REST API Query Cancellation)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=36020cd7de&e=085d8ae40c (Panels do not appear on startup in Firefox)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=c7c14d2ada&e=085d8ae40c (Executing a new query should clear the old query results from the console)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=1c800697d0&e=085d8ae40c (Abbreviate URIs that can be namespaced with one of the defined common namespaces)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=35054efe9c&e=085d8ae40c (Can’t explore an absolute URI with < >)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=57a9e696d6&e=085d8ae40c (Explore page looks weird when empty)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=f7cacbd532&e=085d8ae40c (Allow user to go use browser back & forward buttons to view explore history)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=e48050cead&e=085d8ae40c (OutOfMemoryError instead of Timeout for SPARQL Property Paths)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=62b7e184d6&e=085d8ae40c (Change explore URLs to include URI being clicked so user can see what they’ve clicked on before)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=fe24f082c0&e=085d8ae40c (AssertionError: Child does not have persistent identity)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=53169eb79d&e=085d8ae40c (Search functionality in workbench)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=2f692f05ef&e=085d8ae40c (Query results panel should recognize well known namespaces for easier reading)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=9eeacfe516&e=085d8ae40c (Display the properties for a namespace)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=c833627b41&e=085d8ae40c (Create new tabs for status & performance counters, and add per namespace service/VoID description links)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=e04469b6e7&e=085d8ae40c (Configurator for new namespaces)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=da7adf8c0d&e=085d8ae40c (Allow user to create namespace in the workbench)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=8911a8470e&e=085d8ae40c (Output RDF data from queries in table format)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=47de8c5c5c&e=085d8ae40c (Export query results)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=0775ad9689&e=085d8ae40c (Save selected namespace in browser)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=c80b268615&e=085d8ae40c (Explore tab in workbench)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=7ac308f440&e=085d8ae40c (Create shortcut to execute load/query)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=d301e057e3&e=085d8ae40c (Disable textarea when a large file is selected)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=68b4faa05d&e=085d8ae40c (Allow non-file:// URLs to be loaded)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=9bbdc03bf3&e=085d8ae40c (Retrieve default namespace on page load)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=61444cdae7&e=085d8ae40c (Query timeout only checked at operator start/stop)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=15549e7961&e=085d8ae40c (order by expr skips invalid expressions)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=5378bb6807&e=085d8ae40c (JSP page to configure KBs)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=137495eb03&e=085d8ae40c (Stochastic assert in AbstractBTree#writeNodeOrLeaf() in CI)

1.3.1:

- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=76f15ec021&e=085d8ae40c (Deadlines do not play well with GROUP_BY, ORDER_BY, etc.)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=4b35a5ff38&e=085d8ae40c (Amortize RTO cost)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=300ec6d9e9&e=085d8ae40c (Support BOP fragments in the RTO.)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=5654116fb1&e=085d8ae40c (Integrate RTO into SAIL)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=20da1bdb46&e=085d8ae40c (Dynamically increase RTO sampling limit.)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=caddf9b612&e=085d8ae40c (Reification done right)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=722072ac58&e=085d8ae40c (Problem with the bigdata RDF/XML parser with sids)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=62e2225e0c&e=085d8ae40c (NSS using jetty+windows can lose connections (windows only; jdk 6/7 bug))
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=2ceb14fa52&e=085d8ae40c (HA Load Balancer)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=5f105618b9&e=085d8ae40c (Graph processing API)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=c06a1be79f&e=085d8ae40c (Support HA1 configurations)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=de686abd8f&e=085d8ae40c (Allow configuration of embedded NSS jetty server using jetty-web.xml)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=78f29a6ac8&e=085d8ae40c (multiple filters interfere)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=74ba64364c&e=085d8ae40c (Stochastic results with Analytic Query Mode)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=3d83e40698&e=085d8ae40c (Converge on Java 7.)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=1733a71b5b&e=085d8ae40c (Resynchronization of socket level write replication protocol (HA))
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=9e8a16ea50&e=085d8ae40c (Incremental or asynchronous purge of HALog files)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=900e71bf56&e=085d8ae40c (Wrong serialization version)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=e2f1f52682&e=085d8ae40c (Describe Limit/offset don’t work as expected)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=c60ec2132a&e=085d8ae40c (Update documentations and samples, they are OUTDATED)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=bbeb49119c&e=085d8ae40c (Name2Addr does not report all root causes if the commit fails.)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=247bda3289&e=085d8ae40c (ant task to build sesame fails, docs for setting up bigdata for sesame are ancient)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=a658afa11b&e=085d8ae40c (should not be pruning any children)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=009ffc32b6&e=085d8ae40c (Clean up query hints)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=71a5e41f85&e=085d8ae40c (Explain reports incorrect value for opCount)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=ff96c44b76&e=085d8ae40c (Filter assigned to sub-query by query generator is dropped from evaluation)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=043898af05&e=085d8ae40c (add sbt setup to getting started wiki)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=a506a63024&e=085d8ae40c (Solution order not always preserved)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=c59b68e500&e=085d8ae40c (mis-optimation of quad pattern vs triple pattern)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=d28ece3707&e=085d8ae40c (Optimize DatatypeFactory instantiation in DateTimeExtension)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=0a50588922&e=085d8ae40c (prefixMatch does not work in full text search)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=463fc11219&e=085d8ae40c (update bug deleting quads)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=77d8365979&e=085d8ae40c (Incorrect AST generated for OPTIONAL { SELECT })
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=e460839860&e=085d8ae40c (Wildcard search in bigdata for type suggessions)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=fece94e3c9&e=085d8ae40c (Expose GAS API as SPARQL SERVICE)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=6038866b37&e=085d8ae40c (RDR query does too much work)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=b15172802f&e=085d8ae40c (Wildcard projection ignores variables inside a SERVICE call.)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=786c370948&e=085d8ae40c (Unexplained increase in journal size)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=89aa6f699f&e=085d8ae40c (Reject large files, rather then storing them in a hidden variable)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=9eeac35d00&e=085d8ae40c (UNION with filter issue)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=d2d78b974e&e=085d8ae40c (Using “VALUES” in a query returns lexical error)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=cd9e907eec&e=085d8ae40c (Fix SPARQL Results JSON writer to write the RDR syntax)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=3769920d18&e=085d8ae40c (Create writers that support the RDR syntax)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=845ac08f0a&e=085d8ae40c (RDR GAS interface)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=fa71e6791f&e=085d8ae40c (RemoteRepository.cancel() does not consume the HTTP response entity.)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=512e2e6df6&e=085d8ae40c (Follower does not accept POST of idempotent operations (HA))
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=0431f17e93&e=085d8ae40c (Allow override of maximum length before converting an HTTP GET to an HTTP POST)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=63b3bb25ec&e=085d8ae40c (AssertionError: Child does not have persistent identity)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=9d53427755&e=085d8ae40c (Create parser for JSON SPARQL Results)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=67db391003&e=085d8ae40c (HA1 commit failure)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=df980f5505&e=085d8ae40c (Batch remove API for the SAIL)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=b897717b4e&e=085d8ae40c (NSS concurrency problem with list namespaces and create namespace)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=ab02837d18&e=085d8ae40c (HA5 test suite)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=b04b382c06&e=085d8ae40c (Full text index range count optimization)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=8f1514c046&e=085d8ae40c (FILTER not applied when there is UNION in the same join group)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=0e927ef1bc&e=085d8ae40c (When I upload a file I want to see the filename.)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=57b9592c2f&e=085d8ae40c (RDF Format selector is invisible)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=9a879379e6&e=085d8ae40c (CANCEL Query fails on non-default kb namespace on HA follower.)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=fe27eea5f4&e=085d8ae40c (Provide workaround for bad reverse DNS setups.)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=8709db1f63&e=085d8ae40c (BIND is leaving a variable unbound)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=0ee7a86429&e=085d8ae40c (HAJournalServer does not die if zookeeper is not running)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=fbf86c3d38&e=085d8ae40c (large sparql insert optimization slow?)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=db2882b812&e=085d8ae40c (unnecessary synchronization)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=789b40b045&e=085d8ae40c (stack overflow in populateStatsMap)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=927c3b7b66&e=085d8ae40c (Update Basic Bigdata Chef Cookbook)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=43e1e1135d&e=085d8ae40c (AssertionError: PropertyPathNode got to ASTJoinOrderByType.optimizeJoinGroup)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=925291d23a&e=085d8ae40c (unsound combo query optimization: union + filter)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=a6150edf95&e=085d8ae40c (DC Prefix Button Appends “

“)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=2c45465d9e&e=085d8ae40c (Add a quick-start ant task for the BD Server “ant start”)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=91ca9b7d60&e=085d8ae40c (Provide a configurable IAnalyzerFactory)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=cf946322ac&e=085d8ae40c (Blueprints API Implementation)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=32ef88e7ff&e=085d8ae40c (Settable timeout on SPARQL Query (REST API))
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=6d76f72e2e&e=085d8ae40c (DefaultAnalyzerFactory issues)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=c18865bb46&e=085d8ae40c (Content negotiation orders accept header scores in reverse)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=4e74225e31&e=085d8ae40c (NSS does not start from command line: bigdata-war/src not found.)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=df2de2f9f3&e=085d8ae40c (ProxyServlet in web.xml breaks tomcat WAR (HA LBS)

1.3.0:

- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=2ded5e374e&e=085d8ae40c (Journal HA)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=e72b11decd&e=085d8ae40c (Coalesce write cache records and install reads in cache)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=325e31417f&e=085d8ae40c (HA TXS)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=5d78f8b012&e=085d8ae40c (Remove triple-buffering in RWStore)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=f5156329e9&e=085d8ae40c (HA backup)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=38b9ea2bca&e=085d8ae40c (River not compatible with newer 1.6.0 and 1.7.0 JVMs)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=e794944126&e=085d8ae40c (Add a custom function to use full text index for filtering.)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=020bac84ff&e=085d8ae40c (RWS test failure)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=b5d289ba80&e=085d8ae40c (Compress write cache blocks for replication and in HALogs)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=6cbfbdd612&e=085d8ae40c (Latency on followers during commit on leader)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=c6aa56936d&e=085d8ae40c (Issue with OPTIONAL blocks)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=fbc135d0b3&e=085d8ae40c (RWStore needs post-commit protocol)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=0972d3a893&e=085d8ae40c (HA3 LOAD non-responsive with node failure)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=f1297c7d4c&e=085d8ae40c (Occasional CI deadlock in HALogWriter testConcurrentRWWriterReader)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=53dd02f8f9&e=085d8ae40c (Accumulating HALog files cause latency for HA commit)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=7c54825c08&e=085d8ae40c (Query on follower fails during UPDATE on leader)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=214e29b3ab&e=085d8ae40c (DGC in release time consensus protocol causes native thread leak in HAJournalServer at each commit)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=eea45217ff&e=085d8ae40c (WCS write cache compaction causes errors in RWS postHACommit())
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=5e14b51e77&e=085d8ae40c (Bad patterns for timeout computations)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=776d80bd0e&e=085d8ae40c (HA deadlock under UPDATE + QUERY)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=0a9ad63791&e=085d8ae40c (DGC Thread and Open File Leaks: sendHALogForWriteSet())
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=f8c8e91876&e=085d8ae40c (HAJournalServer can not restart due to logically empty log file)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=2457a6dc4f&e=085d8ae40c (HAJournalServer deadlock: pipelineRemove() and getLeaderId())
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=b70c9544b3&e=085d8ae40c (Optimization with skos altLabel)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=4ff991d9b9&e=085d8ae40c (Consensus protocol does not detect clock skew correctly)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=4c9a22fd42&e=085d8ae40c (HAJournalServer Cache not populated)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=8cd185a8d7&e=085d8ae40c (Missing URL encoding in RemoteRepositoryManager)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=729e64f78b&e=085d8ae40c (Error when using the alias “a” instead of rdf:type for a multipart insert)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=c3fb39f498&e=085d8ae40c (Failed to re-interrupt thread in HAJournalServer)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=1847e2b997&e=085d8ae40c (Failed to re-interrupt thread)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=e77f07df31&e=085d8ae40c (OneOrMorePath SPARQL property path expression ignored)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=3b1493420e&e=085d8ae40c (Transparently cancel update/query in RemoteRepository)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=b98c7af21d&e=085d8ae40c (HAJournalServer reports “follower” but is in SeekConsensus and is not participating in commits.)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=1f281712bf&e=085d8ae40c (Problems in BackgroundTupleResult)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=7187d17ec1&e=085d8ae40c (InvocationTargetException on /namespace call)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=ba725d28dc&e=085d8ae40c (ask does not return json)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=ec6eee2f02&e=085d8ae40c (Race between QueryEngine.putIfAbsent() and shutdownNow())
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=7f7f14620f&e=085d8ae40c (MultiSourceSequentialCloseableIterator.nextSource() can throw NPE)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=c87dbe83fd&e=085d8ae40c (BlockingBuffer.close() does not unblock threads)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=39f003871c&e=085d8ae40c (BIND heisenbug – race condition on select query with BIND)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=069645a5a1&e=085d8ae40c (sparql protocol: mime type application/sparql-query)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=b3bce558c1&e=085d8ae40c (SELECT ?x { OPTIONAL { ?x eg:doesNotExist eg:doesNotExist } } incorrect)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=764b7a0314&e=085d8ae40c (Interrupt of thread submitting a query for evaluation does not always terminate the AbstractRunningQuery)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=3ff57cfd25&e=085d8ae40c (Verify that IRunningQuery instances (and nested queries) are correctly cancelled when interrupted)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=846bcc7963&e=085d8ae40c (HAJournalServer needs to handle ZK client connection loss)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=b4b319c334&e=085d8ae40c (HA3 simultaneous service start failure)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=b466a45c25&e=085d8ae40c (HA asynchronous tasks must be canceled when invariants are changed)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=8312a04ac9&e=085d8ae40c (FILTER EXISTS in subselect)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=05f6f4ba4a&e=085d8ae40c (Logically empty HALog for committed transaction)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=c47851dccb&e=085d8ae40c (DELETE/INSERT fails with OPTIONAL non-matching WHERE)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=09c4ec8611&e=085d8ae40c (Refactor to create HAClient)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=50e4240063&e=085d8ae40c (ant bundleJar not working)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=937e89f6ad&e=085d8ae40c (CBD and Update leads to 500 status code)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=db09dc1775&e=085d8ae40c (describe statement limit does not work)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=cf5c4a50a2&e=085d8ae40c (Range optimizer not optimizing Slice service)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=41a5256d5c&e=085d8ae40c (two property paths interfere)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=3cccc36dc6&e=085d8ae40c (MIN() malfunction)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=c3e25f0b5f&e=085d8ae40c (class cast exception)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=b36d31e6f2&e=085d8ae40c (Inconsistent treatment of bind and optional property path)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=f4bf21ead0&e=085d8ae40c (ctc-striterators should build as independent top-level project (Apache2))
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=6e45e9a139&e=085d8ae40c (AbstractTripleStore.destroy() does not filter for correct prefix)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=5c26c9ff3d&e=085d8ae40c (Assertion error)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=d9e3a20ab2&e=085d8ae40c (BOUND bug)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=8c848398e0&e=085d8ae40c (incorrect join with subselect renaming vars)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=da23523e5a&e=085d8ae40c (Failure to setup SERVICE hook and changeLog for Unisolated and Read/Write connections)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=110f1ca5ec&e=085d8ae40c (Concurrent QuorumActors can interfere leading to failure to progress)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=57dc68e641&e=085d8ae40c (order by and group_concat)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=8be690c0bd&e=085d8ae40c (Code review on 2-phase commit protocol)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=f2b842ee93&e=085d8ae40c (RESYNC failure (HA))
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=d5cf0e1f08&e=085d8ae40c (alpp ordering)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=13b3b8c27b&e=085d8ae40c (Query timeout only checked at operator start/stop.)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=e4e9cfbbc9&e=085d8ae40c (Closed as duplicate of #490)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=87924a8c49&e=085d8ae40c (HA Leader fail results in transient problem with allocations on other services)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=a76b30b4cd&e=085d8ae40c (Operator Alerts (HA))

1.2.4:

- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=6dd8445171&e=085d8ae40c (ConcurrentModificationException in ASTComplexOptionalOptimizer)

1.2.3:

- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=b63c71c9f4&e=085d8ae40c (Maven Build)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=7553db19c8&e=085d8ae40c (Journal leaks memory).
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=78d28472de&e=085d8ae40c (Occasional deadlock in CI runs in com.bigdata.io.writecache.TestAll)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=0822171bc0&e=085d8ae40c (CI (mock) quorums deadlock)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=1b99e9aab7&e=085d8ae40c (Optimize hash join for subgroups with no incoming bound vars.)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=5e27c560d8&e=085d8ae40c (StaticAnalysis#getDefinitelyBound() ignores exogenous variables.)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=8f47a28b0c&e=085d8ae40c (RDFS Plus Profile)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=3680792b3c&e=085d8ae40c (SPARQL 1.1 Property Paths)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=27d9839700&e=085d8ae40c (Negative parser tests)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=84f83d1060&e=085d8ae40c (SPARQL UPDATE for SOLUTION SETS)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=3228d79537&e=085d8ae40c (Optimize JOIN VARS for Sub-Selects)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=32286dab5d&e=085d8ae40c (Support PSOutputStream/InputStream at IRawStore)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=dcdce2665c&e=085d8ae40c (Use RDFFormat.NQUADS as the format identifier for the NQuads parser)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=704925192a&e=085d8ae40c (MemoryManager Journal does not implement all methods).
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=abe0222c98&e=085d8ae40c (NSS Admin API)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=36f9107a98&e=085d8ae40c (DESCRIBE with OFFSET/LIMIT needs to use sub-select)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=5e3ef39cbf&e=085d8ae40c (Concise Bounded Description (CBD))
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=7438badf9d&e=085d8ae40c (CONSTRUCT should use distinct SPO filter)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=d8a713bc72&e=085d8ae40c (VoID in ServiceDescription)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=e1628b8656&e=085d8ae40c (RWStore immedateFree() not removing Checkpoint addresses from the historical index cache.)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=76202ba0b7&e=085d8ae40c (nxparser fails with uppercase language tag)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=6f2896029a&e=085d8ae40c (Optimize RWStore allocator sizes)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=d1f0808bca&e=085d8ae40c (Ugrade to Sesame 2.6.10)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=61c23fd9a5&e=085d8ae40c (WAR was deployed using TRIPLES rather than QUADS by default)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=2d2170a9b0&e=085d8ae40c (Change web.xml parameter names to be consistent with Jini/River)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=8a677439ae&e=085d8ae40c (SPARQL UPDATE LISTENER)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=5a6e700058&e=085d8ae40c (B+Tree branching factor and HTree addressBits are confused in their NodeSerializer implementations)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=08da83d5c9&e=085d8ae40c (BlobIV for blank node : NotMaterializedException)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=5a388b8715&e=085d8ae40c (BlobIV collision counter hits false limit.)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=5ba35955b4&e=085d8ae40c (Log uncaught exceptions)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=bfc09065d7&e=085d8ae40c (RWStore does not discard logged deletes on reset())
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=e87b5ff98e&e=085d8ae40c (History service / index)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=e33dad5a1e&e=085d8ae40c (LOG BlockingBuffer not progressing at INFO or lower level)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=87d0c00986&e=085d8ae40c (bigdata-ganglia is required dependency for Journal)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=c5f6caab6d&e=085d8ae40c (The code that processes SPARQL Update has a typo)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=4b000c1364&e=085d8ae40c (Bigdata scale-up depends on zookeper)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=eb7db02368&e=085d8ae40c (SPARQL UPDATE response inlines large DELETE or INSERT triple graphs)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=2593abbbb0&e=085d8ae40c (static join optimizer does not get ordering right when multiple tails share vars with ancestry)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=c699991a73&e=085d8ae40c (AST2BOpUtility wraps UNION with an unnecessary hash join)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=2ce35cb687&e=085d8ae40c (Row store read/update not isolated on Journal)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=7708d8a2b2&e=085d8ae40c (Concurrent KB create fails with “No axioms defined?”)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=ad0a33efac&e=085d8ae40c (DirectBufferPool.poolCapacity maximum of 2GB)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=adda5e1bbd&e=085d8ae40c (RemoteRepository class should use application/x-www-form-urlencoded for large POST requests)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=551a4c9719&e=085d8ae40c (UpdateServlet fails to parse MIMEType when doing conneg.)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=453837d11b&e=085d8ae40c (Expose performance counters for read-only indices)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=27e9c69f35&e=085d8ae40c (Environment variable override for NSS properties file)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=a5f1d2c983&e=085d8ae40c (Create a bigdata-client jar for the NSS REST API)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=4447b74b20&e=085d8ae40c (ClassCastException in SIDs mode query)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=d9b57f3f96&e=085d8ae40c (NotMaterializedException when a SERVICE call needs variables that are provided as query input bindings)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=6fdcd60178&e=085d8ae40c (ClassCastException when binding non-uri values to a variable that occurs in predicate position)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=edbfd102e1&e=085d8ae40c (Change DEFAULT_MIN_RELEASE_AGE to 1ms)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=9ed2b8be9a&e=085d8ae40c (Conditionally rollback() BigdataSailConnection if dirty)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=b753118597&e=085d8ae40c (Property paths do not work inside of exists/not exists filters)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=98936979b2&e=085d8ae40c (Add web.xml parameters to lock down public NSS end points)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=685894b6a1&e=085d8ae40c (Bigdata2Sesame2BindingSetIterator can fail to notice asynchronous close())
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=5b756e0273&e=085d8ae40c (Can not POST RDF to a graph using REST API)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=1bde0773f9&e=085d8ae40c (Rare AssertionError in WriteCache.clearAddrMap())
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=4f3a482067&e=085d8ae40c (SPARQL REGEX operator does not perform case-folding correctly for Unicode data)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=d529fb44e8&e=085d8ae40c (InFactory bug when IN args consist of a single literal)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=ba2711d844&e=085d8ae40c (SIDs mode creates unnecessary hash join for GRAPH group patterns)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=31aec2781d&e=085d8ae40c (Provide NanoSparqlServer initialization hook)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=c2e6195bab&e=085d8ae40c (Doubly nested subqueries yield no results with LIMIT)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=6419b26eb1&e=085d8ae40c (Flush indices in parallel during checkpoint to reduce IO latency)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=3c0fbaf2a7&e=085d8ae40c (AtomicRowFilter UnsupportedOperationException)

1.2.2:

- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=6d579c0fbc&e=085d8ae40c (RWStore immedateFree() not removing Checkpoint addresses from the historical index cache.)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=d61c778070&e=085d8ae40c (RWStore does not discard logged deletes on reset())
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=1cb898b8b0&e=085d8ae40c (Prepare critical maintenance release as branch of 1.2.1)

1.2.1:

- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=ca1b81904f&e=085d8ae40c (Review materialization for inline IVs)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=62191435ec&e=085d8ae40c (NotMaterializedException with REGEX and Vocab)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=110fd93e7e&e=085d8ae40c (SPARQL UPDATE using NSS via index.html)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=ce4f9cf04e&e=085d8ae40c (MemoryManaged backed Journal mode)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=088bdd950f&e=085d8ae40c (Index cache for Journal)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=4042843398&e=085d8ae40c (BTree can not be cast to Name2Addr (MemStore recycler))
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=4638d83a97&e=085d8ae40c (NPE in Leaf.getKey() : root cause was user error)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=cd34bd42d5&e=085d8ae40c (SPARQL INSERT not working in same request after INSERT DATA)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=cd96415307&e=085d8ae40c (Sub-select in INSERT cause NPE in UpdateExprBuilder)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=e78466ba41&e=085d8ae40c (DISTINCT ORDER BY)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=fb0fbbcc5e&e=085d8ae40c (Failure to set cached value on IV results in incorrect behavior for complex UPDATE operation)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=9d67c49a0b&e=085d8ae40c (DELETE WHERE fails with Java AssertionError)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=7809b8616f&e=085d8ae40c (LOAD-CREATE-LOAD using virgin journal fails with “Graph exists” exception)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=9f4511f5d2&e=085d8ae40c (DELETE/INSERT WHERE handling of blank nodes)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=174cb2fb26&e=085d8ae40c (NullPointerException when attempting to INSERT DATA containing a blank node)

1.2.0: (*)

- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=9eb18841b2&e=085d8ae40c (Monitoring webapp)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=6066059e63&e=085d8ae40c (Support evaluation of 3rd party operators)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=d86d2c99e1&e=085d8ae40c (Compact and efficient movement of binding sets between nodes.)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=4ecfa81e49&e=085d8ae40c (Cluster leaks threads under read-only index operations: DGC thread leak)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=b723259e13&e=085d8ae40c (Thread-local cache combined with unbounded thread pools causes effective memory leak: termCache memory leak & thread-local buffers)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=61e7c3cbac&e=085d8ae40c (KeyBeforePartitionException on cluster)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=893a1c0549&e=085d8ae40c (Class loader problem)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=ff3bd41d1f&e=085d8ae40c (Ganglia integration)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=7fe580a6d7&e=085d8ae40c (Logger for RWStore transaction service and recycler)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=5e824d074a&e=085d8ae40c (SPARQL query can fail to notice when IRunningQuery.isDone() on cluster)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=8bb1bfd060&e=085d8ae40c (RWStore does not track tx release correctly)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=9154079f95&e=085d8ae40c (HTTP Repostory broken with bigdata 1.1.0)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=bfd894c9bf&e=085d8ae40c (SPARQL 1.1 UPDATE)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=d9846c753d&e=085d8ae40c (SPARQL 1.1 Federation extension)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=7c4bdab0bf&e=085d8ae40c (Serialization error in SIDs mode on cluster)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=6719ff9414&e=085d8ae40c (Global Row Store Read on Cluster uses Tx)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=5707ce408e&e=085d8ae40c (IExtension implementations do point lookups on lexicon)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=23fc176964&e=085d8ae40c (“No such index” on cluster under concurrent query workload)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=727eba37ee&e=085d8ae40c (Java level deadlock in DS)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=7e938b132b&e=085d8ae40c (Uncaught interrupt resolving RDF terms)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=1f7bed1a8b&e=085d8ae40c (KeyAfterPartitionException / KeyBeforePartitionException on cluster)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=ada8b7d6bc&e=085d8ae40c (NoSuchVocabularyItem with LUBMVocabulary for DerivedNumericsExtension)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=ef9bcf6cf5&e=085d8ae40c (Query statistics do not update correctly on cluster)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=ad657b23c8&e=085d8ae40c (Too many GRS reads on cluster)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=7f14dcebe1&e=085d8ae40c (Sail does not flush assertion buffers before query)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=c75e0d8988&e=085d8ae40c (acceptTaskService pool size on cluster)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=4b1e7a9055&e=085d8ae40c (Optimize serialization for query messages on cluster)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=a8ba25fd60&e=085d8ae40c (Test suite for writeCheckpoint() and recycling for BTree/HTree)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=37c57b4fbb&e=085d8ae40c (Cluster does not map input solution(s) across shards)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=a64831f52b&e=085d8ae40c (Error releasing deferred frees using 1.0.6 against a 1.0.4 journal)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=ea3986d39f&e=085d8ae40c (PhysicalAddressResolutionException against 1.0.6)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=2c1853fdc8&e=085d8ae40c (RWStore reset() should be thread-safe for concurrent readers)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=64732f0015&e=085d8ae40c (Java API for NanoSparqlServer REST API)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=ffc8ef13a5&e=085d8ae40c (AbstractTripleStore.destroy() does not clear the locator cache)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=9bc4deea5f&e=085d8ae40c (Empty chunk in ThickChunkMessage (cluster))
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=d04a93e986&e=085d8ae40c (Virtual Graphs)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=1d914d3162&e=085d8ae40c (Sesame 2.6.3)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=67d3f1b675&e=085d8ae40c (Implement STRBEFORE, STRAFTER, and REPLACE)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=e05f3a6032&e=085d8ae40c (Bring bigdata RDF/XML parser up to openrdf 2.6.3.)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=bce9b6035e&e=085d8ae40c (SPARQL 1.1 Service Description)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=1ea9fef3d8&e=085d8ae40c (Aggregation with an solution set as input should produce an empty solution as output)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=9333f31566&e=085d8ae40c (Incorrect error handling for SPARQL aggregation; fix in 2.6.1)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=eddca7e021&e=085d8ae40c (Order the same Blank Nodes together in ORDER BY)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=a233a83f31&e=085d8ae40c (SPARQL 1.1 BINDINGS are ignored)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=33df637e3d&e=085d8ae40c (Bigdata2Sesame2BindingSetIterator throws QueryEvaluationException were it should throw NoSuchElementException)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=ace893eb0f&e=085d8ae40c (UNION with Empty Group Pattern)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=ecf069046b&e=085d8ae40c (Exception when using SPARQL sort & statement identifiers)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=e841d31457&e=085d8ae40c (Load, closure and query performance in 1.1.x versus 1.0.x)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=94bb1cf4eb&e=085d8ae40c (LIMIT causes hash join utility to log errors)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=582a4e8331&e=085d8ae40c (Expose the LexiconConfiguration to Function BOPs)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=e218985d13&e=085d8ae40c (Query with two “FILTER NOT EXISTS” expressions returns no results)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=cbc35789ea&e=085d8ae40c (REGEXBOp should cache the Pattern when it is a constant)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=bb9cf4a8ca&e=085d8ae40c (Java 7 Compiler Compatibility)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=05b5df68e7&e=085d8ae40c (Review function bop subclass hierarchy, optimize datatype bop, etc.)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=5fd3ec61ac&e=085d8ae40c (CONSTRUCT WHERE shortcut)
- http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=2c7c4c4ebd&e=085d8ae40c (Incremental materialization of Tuple and Graph query results)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=55bc9f2a6c&e=085d8ae40c (Modify the IChangeLog interface to support multiple agents)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=69bc33d164&e=085d8ae40c (Expose timestamp of LexiconRelation to function bops)
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=feeec54f17&e=085d8ae40c (ClassCastException during hash join (can not be cast to TermId))
- http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=99e3cf9df2&e=085d8ae40c (Review materialization for inline IVs)
- http://bigdata.us8.list-manage1.com/track/click?u=807fe42a6d19f97994387207d&id=032edb3294&e=085d8ae40c (BSBM BI Q5 error using MERGE JOIN)

1.1.0 (*)

– http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=6b992ba191&e=085d8ae40c (Lexicon joins)
– http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=d123a41d48&e=085d8ae40c (Store large literals as “blobs”)
– http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=189bf1418f&e=085d8ae40c (Scale-out LUBM “how to” in wiki and build.xml are out of date.)
– http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=fffaf6412f&e=085d8ae40c (Implement an persistence capable hash table to support analytic query)
– http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=22319b4f48&e=085d8ae40c (AccessPath should visit binding sets rather than elements for high level query.)
– http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=3db133f755&e=085d8ae40c (SliceOp appears to be necessary when operator plan should suffice without)
– http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=2be621398b&e=085d8ae40c (Bottom-up evaluation semantics).
– http://bigdata.us8.list-manage2.com/track/click?u=807fe42a6d19f97994387207d&id=14c3a0ff91&e=085d8ae40c (Derived xsd numeric data types must be inlined as extension types.)
– http://bigdata.us8.list-manage.com/track/click?u=807fe42a6d19f97994387207d&id=7b9ea679d5&e=085d8ae40c (Revisit pruning of intermediate variable bindings during query execution)
– http://bigdata.us8.list-ma...
 
[truncated message content]