This list is closed, nobody may subscribe to it.
2010 |
Jan
|
Feb
(19) |
Mar
(8) |
Apr
(25) |
May
(16) |
Jun
(77) |
Jul
(131) |
Aug
(76) |
Sep
(30) |
Oct
(7) |
Nov
(3) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
(2) |
Jul
(16) |
Aug
(3) |
Sep
(1) |
Oct
|
Nov
(7) |
Dec
(7) |
2012 |
Jan
(10) |
Feb
(1) |
Mar
(8) |
Apr
(6) |
May
(1) |
Jun
(3) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
(8) |
Dec
(2) |
2013 |
Jan
(5) |
Feb
(12) |
Mar
(2) |
Apr
(1) |
May
(1) |
Jun
(1) |
Jul
(22) |
Aug
(50) |
Sep
(31) |
Oct
(64) |
Nov
(83) |
Dec
(28) |
2014 |
Jan
(31) |
Feb
(18) |
Mar
(27) |
Apr
(39) |
May
(45) |
Jun
(15) |
Jul
(6) |
Aug
(27) |
Sep
(6) |
Oct
(67) |
Nov
(70) |
Dec
(1) |
2015 |
Jan
(3) |
Feb
(18) |
Mar
(22) |
Apr
(121) |
May
(42) |
Jun
(17) |
Jul
(8) |
Aug
(11) |
Sep
(26) |
Oct
(15) |
Nov
(66) |
Dec
(38) |
2016 |
Jan
(14) |
Feb
(59) |
Mar
(28) |
Apr
(44) |
May
(21) |
Jun
(12) |
Jul
(9) |
Aug
(11) |
Sep
(4) |
Oct
(2) |
Nov
(1) |
Dec
|
2017 |
Jan
(20) |
Feb
(7) |
Mar
(4) |
Apr
(18) |
May
(7) |
Jun
(3) |
Jul
(13) |
Aug
(2) |
Sep
(4) |
Oct
(9) |
Nov
(2) |
Dec
(5) |
2018 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Bryan T. <br...@sy...> - 2016-02-16 21:48:01
|
Great! Thanks, Bryan ---- Bryan Thompson Chief Scientist & Founder Blazegraph e: br...@bl... w: http://blazegraph.com Blazegraph products help to solve the Graph Cache Thrash to achieve large scale processing for graph and predictive analytics. Blazegraph is the creator of the industry’s first GPU-accelerated high-performance database for large graphs, has been named as one of the “10 Companies and Technologies to Watch in 2016” <http://insideanalysis.com/2016/01/20535/>. Blazegraph Database <https://www.blazegraph.com/> is our ultra-high performance graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints APIs. Blazegraph GPU <https://www.blazegraph.com/product/gpu-accelerated/> andBlazegraph DAS <https://www.blazegraph.com/product/gpu-accelerated/>L are disruptive new technologies that use GPUs to enable extreme scaling that is thousands of times faster and 40 times more affordable than CPU-based solutions. 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, LLC DBA Blazegraph. 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, Feb 16, 2016 at 4:42 PM, Edgar Rodriguez-Diaz <ed...@sy...> wrote: > > > On Tue, Feb 16, 2016 at 12:04 PM, Bryan Thompson <br...@sy...> wrote: > >> So it is looking for this class: com.bigdata.rdf.vocab.core. >> BigdataCoreVocabulary_v20151210 >> >> This class is in the 2.0 release. >> >> It should not have updated the definition of the vocabulary. That is a >> durable thing which is established when you first create a namespace. It is >> not modified after that. In fact, modifying this property would cause >> havoc for the namespace. >> >> Do you perhaps not have the default namespace (kb) in the journal before >> you start 2.0? It is possible that it is automatically creating that >> default namespace if none is found and then your 1.5.3 version is unable to >> resolve the newer vocabulary class. >> > > This is the case; I didn't have the kb namespace, since 1.5.3 does not > create it by default, but 2.0.0 does. Creating the kb namespace in 1.5.3 > seems to have done the trick and prevented 2.0.0 from writing into the > journal to create it. > > >> >> There is a web.xml property you can specify to have it NOT automatically >> create the default namespace. >> >> Thanks, >> Bryan >> >> >> ---- >> Bryan Thompson >> Chief Scientist & Founder >> Blazegraph >> e: br...@bl... >> w: http://blazegraph.com >> >> Blazegraph products help to solve the Graph Cache Thrash to achieve large >> scale processing for graph and predictive analytics. Blazegraph is the >> creator of the industry’s first GPU-accelerated high-performance database >> for large graphs, has been named as one of the “10 Companies and >> Technologies to Watch in 2016” <http://insideanalysis.com/2016/01/20535/>. >> >> >> Blazegraph Database <https://www.blazegraph.com/> is our ultra-high >> performance graph database that supports both RDF/SPARQL and >> Tinkerpop/Blueprints APIs. Blazegraph GPU >> <https://www.blazegraph.com/product/gpu-accelerated/> andBlazegraph DAS >> <https://www.blazegraph.com/product/gpu-accelerated/>L are disruptive >> new technologies that use GPUs to enable extreme scaling that is thousands >> of times faster and 40 times more affordable than CPU-based solutions. >> >> 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, LLC DBA Blazegraph. 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, Feb 16, 2016 at 3:00 PM, Edgar Rodriguez-Diaz <ed...@sy...> >> wrote: >> >>> This seems relevant from the log from my blazegraph 1.5.3 using the >>> Journal previously queried in 2.0.0: >>> >>> ``` >>> Feb 16,2016 11:09:30 PST - ERROR: 7822 qtp1935637221-32 >>> com.bigdata.rdf.sail.webapp.BigdataRDFServlet.launderThrowable(BigdataRDFServlet.java:214): >>> cause=java.lang.RuntimeException: off=0, len=339, >>> query=describeEachNamedGraph=false, describeDefaultNamespace=false >>> java.lang.RuntimeException: off=0, len=339 >>> at com.bigdata.io.SerializerUtil.deserialize(SerializerUtil.java:239) >>> at com.bigdata.io.SerializerUtil.deserialize(SerializerUtil.java:207) >>> at com.bigdata.sparse.ValueType.decode(ValueType.java:333) >>> at >>> com.bigdata.sparse.AtomicRowFilter$Transformerator.handleTuple(AtomicRowFilter.java:408) >>> at >>> com.bigdata.sparse.AtomicRowFilter$Transformerator.hasNext(AtomicRowFilter.java:290) >>> at >>> com.bigdata.btree.filter.WrappedTupleIterator.hasNext(WrappedTupleIterator.java:30) >>> at >>> cutthecrap.utils.striterators.Resolverator.hasNext(Resolverator.java:39) >>> at cutthecrap.utils.striterators.Striterator.hasNext(Striterator.java:89) >>> at >>> com.bigdata.rdf.sail.webapp.BigdataRDFContext.getNamespacesTx(BigdataRDFContext.java:2748) >>> at >>> com.bigdata.rdf.sail.webapp.MultiTenancyServlet.doDescribeNamespaces(MultiTenancyServlet.java:506) >>> at >>> com.bigdata.rdf.sail.webapp.MultiTenancyServlet.doGet(MultiTenancyServlet.java:199) >>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) >>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) >>> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:769) >>> at >>> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585) >>> at >>> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) >>> at >>> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577) >>> at >>> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223) >>> at >>> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1125) >>> at >>> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515) >>> at >>> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) >>> at >>> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1059) >>> at >>> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) >>> at >>> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215) >>> at >>> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:110) >>> at >>> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) >>> at org.eclipse.jetty.server.Server.handle(Server.java:497) >>> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:311) >>> at >>> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:248) >>> at >>> org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540) >>> at >>> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:610) >>> at >>> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:539) >>> at java.lang.Thread.run(Thread.java:745) >>> Caused by: java.lang.ClassNotFoundException: >>> com.bigdata.rdf.vocab.core.BigdataCoreVocabulary_v20151210 >>> at java.net.URLClassLoader.findClass(URLClassLoader.java:381) >>> at java.lang.ClassLoader.loadClass(ClassLoader.java:424) >>> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) >>> at java.lang.ClassLoader.loadClass(ClassLoader.java:357) >>> at java.lang.Class.forName0(Native Method) >>> at java.lang.Class.forName(Class.java:348) >>> at java.io.ObjectInputStream.resolveClass(ObjectInputStream.java:626) >>> at >>> java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1613) >>> at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1518) >>> at >>> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1774) >>> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351) >>> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:371) >>> at com.bigdata.io.SerializerUtil.deserialize(SerializerUtil.java:231) >>> ... 32 more >>> ``` >>> >>> Seems like still something is trying to use the vocabulary previously >>> mentioned. >>> >>> Cheers, >>> Edgar >>> >>> On Tue, Feb 16, 2016 at 11:41 AM, Bryan Thompson <br...@sy...> >>> wrote: >>> >>>> Does anything show up in the logs? The set of namespaces is stored in >>>> the __globalRowStore. Just querying the system should not cause anything >>>> to be written. This would be visible if you use DumpJournal (w/o -pages) >>>> and look at the commit counter. It should be unchanged. Queries are read >>>> only. >>>> >>>> Thanks, >>>> Bryan >>>> >>>> ---- >>>> Bryan Thompson >>>> Chief Scientist & Founder >>>> Blazegraph >>>> e: br...@bl... >>>> w: http://blazegraph.com >>>> >>>> Blazegraph products help to solve the Graph Cache Thrash to achieve >>>> large scale processing for graph and predictive analytics. Blazegraph is >>>> the creator of the industry’s first GPU-accelerated high-performance >>>> database for large graphs, has been named as one of the “10 Companies >>>> and Technologies to Watch in 2016” >>>> <http://insideanalysis.com/2016/01/20535/>. >>>> >>>> Blazegraph Database <https://www.blazegraph.com/> is our ultra-high >>>> performance graph database that supports both RDF/SPARQL and >>>> Tinkerpop/Blueprints APIs. Blazegraph GPU >>>> <https://www.blazegraph.com/product/gpu-accelerated/> andBlazegraph DAS >>>> <https://www.blazegraph.com/product/gpu-accelerated/>L are disruptive >>>> new technologies that use GPUs to enable extreme scaling that is thousands >>>> of times faster and 40 times more affordable than CPU-based solutions. >>>> >>>> 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, LLC DBA Blazegraph. 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, Feb 16, 2016 at 2:31 PM, Edgar Rodriguez-Diaz < >>>> ed...@sy...> wrote: >>>> >>>>> It would seem that just opening the 1.5.3 journal file in 2.0.0 makes >>>>> it unusable in 1.5.3. This is what I’m doing: >>>>> >>>>> 1. Start with an empty Journal from 1.5.3, in my blazegraph.properties >>>>> it’s defined: >>>>> >>>>> >>>>> com.bigdata.journal.AbstractJournal.file=/usr/local/var/blazegraph/blazegraph.jnl >>>>> >>>>> 2. Go to the workbench/namespaces and create a new NS, say `nstest`, >>>>> and select it >>>>> 2.1. Add some data ~1M triples. >>>>> 2.2. Execute a query to list just 100 triples >>>>> >>>>> 3. Stop blazegraph 1.5.3 >>>>> 4. Go to my properties file in blazegraph 2.0.0 (from the Github repo, >>>>> a copy of `bigdata-war-html/src/main/webapp/WEB-INF/RWStore.properties`), >>>>> set the Journal file to: >>>>> >>>>> >>>>> com.bigdata.journal.AbstractJournal.file=/usr/local/var/blazegraph/blazegraph.jnl >>>>> >>>>> 5. Start blazegraph 2.0.0, correctly pointing to my properties file in >>>>> `scripts/startBlazegraph.sh` >>>>> 6. Go to the workbench/namespaces. >>>>> 6.2. Select my namespaces created in 1.5.3 (`nstest`), which is listed >>>>> 6.1. Execute a query to list just 100 triples >>>>> >>>>> 7. Stop blazegraph 2.0.0 >>>>> 8. Start blazegraph 1.5.3 >>>>> 9. Go to namespaces; no namespaces are listed. >>>>> >>>>> I’m not modifying the 1.5.3 journal with 2.0.0 (or at least I don’t >>>>> think I’m modifying it), just opening it in 2.0.0 and executing a query, >>>>> which seems to be enough to make it not visible anymore back in 1.5.3. >>>>> >>>>> I’m I missing something? >>>>> >>>>> Thanks. >>>>> >>>>> Cheers, >>>>> Edgar >>>>> >>>>> On Tue, Feb 16, 2016 at 10:20 AM, Bryan Thompson <br...@sy...> >>>>> wrote: >>>>> >>>>>> Yes. It is actually if you create a namespace with a newer >>>>>> vocabulary, then you can not open it with a classpath that does not include >>>>>> that vocabulary. Since 2.0 uses a new vocabulary declaration by default, >>>>>> create your namespace in 1.5.3 if you want to use it in both 2.0 and 1.5.3. >>>>>> >>>>>> Thanks, >>>>>> Bryan >>>>>> >>>>>> ---- >>>>>> Bryan Thompson >>>>>> Chief Scientist & Founder >>>>>> Blazegraph >>>>>> e: br...@bl... >>>>>> w: http://blazegraph.com >>>>>> >>>>>> Blazegraph products help to solve the Graph Cache Thrash to achieve >>>>>> large scale processing for graph and predictive analytics. Blazegraph is >>>>>> the creator of the industry’s first GPU-accelerated high-performance >>>>>> database for large graphs, has been named as one of the “10 >>>>>> Companies and Technologies to Watch in 2016” >>>>>> <http://insideanalysis.com/2016/01/20535/>. >>>>>> >>>>>> Blazegraph Database <https://www.blazegraph.com/> is our ultra-high >>>>>> performance graph database that supports both RDF/SPARQL and >>>>>> Tinkerpop/Blueprints APIs. Blazegraph GPU >>>>>> <https://www.blazegraph.com/product/gpu-accelerated/> and >>>>>> Blazegraph DAS <https://www.blazegraph.com/product/gpu-accelerated/>L >>>>>> are disruptive new technologies that use GPUs to enable extreme scaling >>>>>> that is thousands of times faster and 40 times more affordable than >>>>>> CPU-based solutions. >>>>>> >>>>>> 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, LLC DBA Blazegraph. 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, Feb 16, 2016 at 1:18 PM, Brad Bebee <be...@bl...> >>>>>> wrote: >>>>>> >>>>>>> Edgar, >>>>>>> >>>>>>> 2.0.0 introduced a new versioned vocabulary class that is the >>>>>>> default for newly created namespaces. The vocabulary class must be in the >>>>>>> classpath. >>>>>>> >>>>>>> As such, if you create a journal with 1.5.3, you can open it in >>>>>>> 2.0.0. If You create a journal in 2.0.0, you would need to add the new >>>>>>> vocabulary class in the classpath to open it in 1.5.3. >>>>>>> >>>>>>> Thanks, Brad >>>>>>> >>>>>>> _______________ >>>>>>> Brad Bebee >>>>>>> CEO, Managing Partner >>>>>>> SYSTAP, LLC >>>>>>> e: be...@sy... >>>>>>> m: 202.642.7961 >>>>>>> f: 571.367.5000 >>>>>>> w: www.systap.com >>>>>>> >>>>>>> Blazegraph™ is our ultra high-performance graph database that >>>>>>> supports both RDF/SPARQL and Tinkerpop/Blueprints APIs. MapGraph™ is our >>>>>>> disruptive new technology to use GPUs to accelerate data-parallel graph >>>>>>> analytics. >>>>>>> >>>>>>> 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, LLC. 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 Feb 15, 2016 5:41 PM, "Bryan Thompson" <br...@sy...> wrote: >>>>>>> >>>>>>>> It should be compatible. Can you provide mode details. >>>>>>>> >>>>>>>> Bryan >>>>>>>> >>>>>>>> ---- >>>>>>>> Bryan Thompson >>>>>>>> Chief Scientist & Founder >>>>>>>> Blazegraph >>>>>>>> e: br...@bl... >>>>>>>> w: http://blazegraph.com >>>>>>>> >>>>>>>> Blazegraph products help to solve the Graph Cache Thrash to achieve >>>>>>>> large scale processing for graph and predictive analytics. Blazegraph is >>>>>>>> the creator of the industry’s first GPU-accelerated high-performance >>>>>>>> database for large graphs, has been named as one of the “10 >>>>>>>> Companies and Technologies to Watch in 2016” >>>>>>>> <http://insideanalysis.com/2016/01/20535/>. >>>>>>>> >>>>>>>> Blazegraph Database <https://www.blazegraph.com/> is our >>>>>>>> ultra-high performance graph database that supports both >>>>>>>> RDF/SPARQL and Tinkerpop/Blueprints APIs. Blazegraph GPU >>>>>>>> <https://www.blazegraph.com/product/gpu-accelerated/> and >>>>>>>> Blazegraph DAS >>>>>>>> <https://www.blazegraph.com/product/gpu-accelerated/>L are >>>>>>>> disruptive new technologies that use GPUs to enable extreme scaling that is >>>>>>>> thousands of times faster and 40 times more affordable than CPU-based >>>>>>>> solutions. >>>>>>>> >>>>>>>> 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, LLC DBA Blazegraph. 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, Feb 15, 2016 at 5:14 PM, Edgar Rodriguez-Diaz < >>>>>>>> ed...@sy...> wrote: >>>>>>>> >>>>>>>>> I was wondering what’s the level of compatibility for the Journal >>>>>>>>> file between 1.5.3 and 2.0.0. I did a small check and it seems like once a >>>>>>>>> journal is opened with 2.0.0 it’s no longer compatible with 1.5.3. >>>>>>>>> Is this correct? Thanks. >>>>>>>>> >>>>>>>>> Cheers, >>>>>>>>> - Edgar >>>>>>>>> >>>>>>>>> ------------------------------------------------------------------------------ >>>>>>>>> Site24x7 APM Insight: Get Deep Visibility into Application >>>>>>>>> Performance >>>>>>>>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >>>>>>>>> Monitor end-to-end web transactions and take corrective actions now >>>>>>>>> Troubleshoot faster and improve end-user experience. Signup Now! >>>>>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 >>>>>>>>> _______________________________________________ >>>>>>>>> Bigdata-developers mailing list >>>>>>>>> Big...@li... >>>>>>>>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> ------------------------------------------------------------------------------ >>>>>>>> Site24x7 APM Insight: Get Deep Visibility into Application >>>>>>>> Performance >>>>>>>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >>>>>>>> Monitor end-to-end web transactions and take corrective actions now >>>>>>>> Troubleshoot faster and improve end-user experience. Signup Now! >>>>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 >>>>>>>> _______________________________________________ >>>>>>>> Bigdata-developers mailing list >>>>>>>> Big...@li... >>>>>>>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers >>>>>>>> >>>>>>>> >>>>>> >>>>> >>>> >>> >> > |
From: Edgar Rodriguez-D. <ed...@sy...> - 2016-02-16 21:42:47
|
On Tue, Feb 16, 2016 at 12:04 PM, Bryan Thompson <br...@sy...> wrote: > So it is looking for this class: com.bigdata.rdf.vocab.core. > BigdataCoreVocabulary_v20151210 > > This class is in the 2.0 release. > > It should not have updated the definition of the vocabulary. That is a > durable thing which is established when you first create a namespace. It is > not modified after that. In fact, modifying this property would cause > havoc for the namespace. > > Do you perhaps not have the default namespace (kb) in the journal before > you start 2.0? It is possible that it is automatically creating that > default namespace if none is found and then your 1.5.3 version is unable to > resolve the newer vocabulary class. > This is the case; I didn't have the kb namespace, since 1.5.3 does not create it by default, but 2.0.0 does. Creating the kb namespace in 1.5.3 seems to have done the trick and prevented 2.0.0 from writing into the journal to create it. > > There is a web.xml property you can specify to have it NOT automatically > create the default namespace. > > Thanks, > Bryan > > > ---- > Bryan Thompson > Chief Scientist & Founder > Blazegraph > e: br...@bl... > w: http://blazegraph.com > > Blazegraph products help to solve the Graph Cache Thrash to achieve large > scale processing for graph and predictive analytics. Blazegraph is the > creator of the industry’s first GPU-accelerated high-performance database > for large graphs, has been named as one of the “10 Companies and > Technologies to Watch in 2016” <http://insideanalysis.com/2016/01/20535/>. > > > Blazegraph Database <https://www.blazegraph.com/> is our ultra-high > performance graph database that supports both RDF/SPARQL and > Tinkerpop/Blueprints APIs. Blazegraph GPU > <https://www.blazegraph.com/product/gpu-accelerated/> andBlazegraph DAS > <https://www.blazegraph.com/product/gpu-accelerated/>L are disruptive new > technologies that use GPUs to enable extreme scaling that is thousands of > times faster and 40 times more affordable than CPU-based solutions. > > 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, LLC DBA Blazegraph. 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, Feb 16, 2016 at 3:00 PM, Edgar Rodriguez-Diaz <ed...@sy...> > wrote: > >> This seems relevant from the log from my blazegraph 1.5.3 using the >> Journal previously queried in 2.0.0: >> >> ``` >> Feb 16,2016 11:09:30 PST - ERROR: 7822 qtp1935637221-32 >> com.bigdata.rdf.sail.webapp.BigdataRDFServlet.launderThrowable(BigdataRDFServlet.java:214): >> cause=java.lang.RuntimeException: off=0, len=339, >> query=describeEachNamedGraph=false, describeDefaultNamespace=false >> java.lang.RuntimeException: off=0, len=339 >> at com.bigdata.io.SerializerUtil.deserialize(SerializerUtil.java:239) >> at com.bigdata.io.SerializerUtil.deserialize(SerializerUtil.java:207) >> at com.bigdata.sparse.ValueType.decode(ValueType.java:333) >> at >> com.bigdata.sparse.AtomicRowFilter$Transformerator.handleTuple(AtomicRowFilter.java:408) >> at >> com.bigdata.sparse.AtomicRowFilter$Transformerator.hasNext(AtomicRowFilter.java:290) >> at >> com.bigdata.btree.filter.WrappedTupleIterator.hasNext(WrappedTupleIterator.java:30) >> at >> cutthecrap.utils.striterators.Resolverator.hasNext(Resolverator.java:39) >> at cutthecrap.utils.striterators.Striterator.hasNext(Striterator.java:89) >> at >> com.bigdata.rdf.sail.webapp.BigdataRDFContext.getNamespacesTx(BigdataRDFContext.java:2748) >> at >> com.bigdata.rdf.sail.webapp.MultiTenancyServlet.doDescribeNamespaces(MultiTenancyServlet.java:506) >> at >> com.bigdata.rdf.sail.webapp.MultiTenancyServlet.doGet(MultiTenancyServlet.java:199) >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) >> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:769) >> at >> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585) >> at >> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) >> at >> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577) >> at >> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223) >> at >> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1125) >> at >> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515) >> at >> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) >> at >> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1059) >> at >> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) >> at >> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215) >> at >> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:110) >> at >> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) >> at org.eclipse.jetty.server.Server.handle(Server.java:497) >> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:311) >> at >> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:248) >> at >> org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540) >> at >> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:610) >> at >> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:539) >> at java.lang.Thread.run(Thread.java:745) >> Caused by: java.lang.ClassNotFoundException: >> com.bigdata.rdf.vocab.core.BigdataCoreVocabulary_v20151210 >> at java.net.URLClassLoader.findClass(URLClassLoader.java:381) >> at java.lang.ClassLoader.loadClass(ClassLoader.java:424) >> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) >> at java.lang.ClassLoader.loadClass(ClassLoader.java:357) >> at java.lang.Class.forName0(Native Method) >> at java.lang.Class.forName(Class.java:348) >> at java.io.ObjectInputStream.resolveClass(ObjectInputStream.java:626) >> at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1613) >> at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1518) >> at >> java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1774) >> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351) >> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:371) >> at com.bigdata.io.SerializerUtil.deserialize(SerializerUtil.java:231) >> ... 32 more >> ``` >> >> Seems like still something is trying to use the vocabulary previously >> mentioned. >> >> Cheers, >> Edgar >> >> On Tue, Feb 16, 2016 at 11:41 AM, Bryan Thompson <br...@sy...> >> wrote: >> >>> Does anything show up in the logs? The set of namespaces is stored in >>> the __globalRowStore. Just querying the system should not cause anything >>> to be written. This would be visible if you use DumpJournal (w/o -pages) >>> and look at the commit counter. It should be unchanged. Queries are read >>> only. >>> >>> Thanks, >>> Bryan >>> >>> ---- >>> Bryan Thompson >>> Chief Scientist & Founder >>> Blazegraph >>> e: br...@bl... >>> w: http://blazegraph.com >>> >>> Blazegraph products help to solve the Graph Cache Thrash to achieve >>> large scale processing for graph and predictive analytics. Blazegraph is >>> the creator of the industry’s first GPU-accelerated high-performance >>> database for large graphs, has been named as one of the “10 Companies >>> and Technologies to Watch in 2016” >>> <http://insideanalysis.com/2016/01/20535/>. >>> >>> Blazegraph Database <https://www.blazegraph.com/> is our ultra-high >>> performance graph database that supports both RDF/SPARQL and >>> Tinkerpop/Blueprints APIs. Blazegraph GPU >>> <https://www.blazegraph.com/product/gpu-accelerated/> andBlazegraph DAS >>> <https://www.blazegraph.com/product/gpu-accelerated/>L are disruptive >>> new technologies that use GPUs to enable extreme scaling that is thousands >>> of times faster and 40 times more affordable than CPU-based solutions. >>> >>> 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, LLC DBA Blazegraph. 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, Feb 16, 2016 at 2:31 PM, Edgar Rodriguez-Diaz <ed...@sy... >>> > wrote: >>> >>>> It would seem that just opening the 1.5.3 journal file in 2.0.0 makes >>>> it unusable in 1.5.3. This is what I’m doing: >>>> >>>> 1. Start with an empty Journal from 1.5.3, in my blazegraph.properties >>>> it’s defined: >>>> >>>> >>>> com.bigdata.journal.AbstractJournal.file=/usr/local/var/blazegraph/blazegraph.jnl >>>> >>>> 2. Go to the workbench/namespaces and create a new NS, say `nstest`, >>>> and select it >>>> 2.1. Add some data ~1M triples. >>>> 2.2. Execute a query to list just 100 triples >>>> >>>> 3. Stop blazegraph 1.5.3 >>>> 4. Go to my properties file in blazegraph 2.0.0 (from the Github repo, >>>> a copy of `bigdata-war-html/src/main/webapp/WEB-INF/RWStore.properties`), >>>> set the Journal file to: >>>> >>>> >>>> com.bigdata.journal.AbstractJournal.file=/usr/local/var/blazegraph/blazegraph.jnl >>>> >>>> 5. Start blazegraph 2.0.0, correctly pointing to my properties file in >>>> `scripts/startBlazegraph.sh` >>>> 6. Go to the workbench/namespaces. >>>> 6.2. Select my namespaces created in 1.5.3 (`nstest`), which is listed >>>> 6.1. Execute a query to list just 100 triples >>>> >>>> 7. Stop blazegraph 2.0.0 >>>> 8. Start blazegraph 1.5.3 >>>> 9. Go to namespaces; no namespaces are listed. >>>> >>>> I’m not modifying the 1.5.3 journal with 2.0.0 (or at least I don’t >>>> think I’m modifying it), just opening it in 2.0.0 and executing a query, >>>> which seems to be enough to make it not visible anymore back in 1.5.3. >>>> >>>> I’m I missing something? >>>> >>>> Thanks. >>>> >>>> Cheers, >>>> Edgar >>>> >>>> On Tue, Feb 16, 2016 at 10:20 AM, Bryan Thompson <br...@sy...> >>>> wrote: >>>> >>>>> Yes. It is actually if you create a namespace with a newer >>>>> vocabulary, then you can not open it with a classpath that does not include >>>>> that vocabulary. Since 2.0 uses a new vocabulary declaration by default, >>>>> create your namespace in 1.5.3 if you want to use it in both 2.0 and 1.5.3. >>>>> >>>>> Thanks, >>>>> Bryan >>>>> >>>>> ---- >>>>> Bryan Thompson >>>>> Chief Scientist & Founder >>>>> Blazegraph >>>>> e: br...@bl... >>>>> w: http://blazegraph.com >>>>> >>>>> Blazegraph products help to solve the Graph Cache Thrash to achieve >>>>> large scale processing for graph and predictive analytics. Blazegraph is >>>>> the creator of the industry’s first GPU-accelerated high-performance >>>>> database for large graphs, has been named as one of the “10 Companies >>>>> and Technologies to Watch in 2016” >>>>> <http://insideanalysis.com/2016/01/20535/>. >>>>> >>>>> Blazegraph Database <https://www.blazegraph.com/> is our ultra-high >>>>> performance graph database that supports both RDF/SPARQL and >>>>> Tinkerpop/Blueprints APIs. Blazegraph GPU >>>>> <https://www.blazegraph.com/product/gpu-accelerated/> and >>>>> Blazegraph DAS <https://www.blazegraph.com/product/gpu-accelerated/>L >>>>> are disruptive new technologies that use GPUs to enable extreme scaling >>>>> that is thousands of times faster and 40 times more affordable than >>>>> CPU-based solutions. >>>>> >>>>> 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, LLC DBA Blazegraph. 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, Feb 16, 2016 at 1:18 PM, Brad Bebee <be...@bl...> >>>>> wrote: >>>>> >>>>>> Edgar, >>>>>> >>>>>> 2.0.0 introduced a new versioned vocabulary class that is the default >>>>>> for newly created namespaces. The vocabulary class must be in the >>>>>> classpath. >>>>>> >>>>>> As such, if you create a journal with 1.5.3, you can open it in >>>>>> 2.0.0. If You create a journal in 2.0.0, you would need to add the new >>>>>> vocabulary class in the classpath to open it in 1.5.3. >>>>>> >>>>>> Thanks, Brad >>>>>> >>>>>> _______________ >>>>>> Brad Bebee >>>>>> CEO, Managing Partner >>>>>> SYSTAP, LLC >>>>>> e: be...@sy... >>>>>> m: 202.642.7961 >>>>>> f: 571.367.5000 >>>>>> w: www.systap.com >>>>>> >>>>>> Blazegraph™ is our ultra high-performance graph database that >>>>>> supports both RDF/SPARQL and Tinkerpop/Blueprints APIs. MapGraph™ is our >>>>>> disruptive new technology to use GPUs to accelerate data-parallel graph >>>>>> analytics. >>>>>> >>>>>> 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, LLC. 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 Feb 15, 2016 5:41 PM, "Bryan Thompson" <br...@sy...> wrote: >>>>>> >>>>>>> It should be compatible. Can you provide mode details. >>>>>>> >>>>>>> Bryan >>>>>>> >>>>>>> ---- >>>>>>> Bryan Thompson >>>>>>> Chief Scientist & Founder >>>>>>> Blazegraph >>>>>>> e: br...@bl... >>>>>>> w: http://blazegraph.com >>>>>>> >>>>>>> Blazegraph products help to solve the Graph Cache Thrash to achieve >>>>>>> large scale processing for graph and predictive analytics. Blazegraph is >>>>>>> the creator of the industry’s first GPU-accelerated high-performance >>>>>>> database for large graphs, has been named as one of the “10 >>>>>>> Companies and Technologies to Watch in 2016” >>>>>>> <http://insideanalysis.com/2016/01/20535/>. >>>>>>> >>>>>>> Blazegraph Database <https://www.blazegraph.com/> is our ultra-high >>>>>>> performance graph database that supports both RDF/SPARQL and >>>>>>> Tinkerpop/Blueprints APIs. Blazegraph GPU >>>>>>> <https://www.blazegraph.com/product/gpu-accelerated/> and >>>>>>> Blazegraph DAS <https://www.blazegraph.com/product/gpu-accelerated/>L >>>>>>> are disruptive new technologies that use GPUs to enable extreme scaling >>>>>>> that is thousands of times faster and 40 times more affordable than >>>>>>> CPU-based solutions. >>>>>>> >>>>>>> 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, LLC DBA Blazegraph. 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, Feb 15, 2016 at 5:14 PM, Edgar Rodriguez-Diaz < >>>>>>> ed...@sy...> wrote: >>>>>>> >>>>>>>> I was wondering what’s the level of compatibility for the Journal >>>>>>>> file between 1.5.3 and 2.0.0. I did a small check and it seems like once a >>>>>>>> journal is opened with 2.0.0 it’s no longer compatible with 1.5.3. >>>>>>>> Is this correct? Thanks. >>>>>>>> >>>>>>>> Cheers, >>>>>>>> - Edgar >>>>>>>> >>>>>>>> ------------------------------------------------------------------------------ >>>>>>>> Site24x7 APM Insight: Get Deep Visibility into Application >>>>>>>> Performance >>>>>>>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >>>>>>>> Monitor end-to-end web transactions and take corrective actions now >>>>>>>> Troubleshoot faster and improve end-user experience. Signup Now! >>>>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 >>>>>>>> _______________________________________________ >>>>>>>> Bigdata-developers mailing list >>>>>>>> Big...@li... >>>>>>>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> ------------------------------------------------------------------------------ >>>>>>> Site24x7 APM Insight: Get Deep Visibility into Application >>>>>>> Performance >>>>>>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >>>>>>> Monitor end-to-end web transactions and take corrective actions now >>>>>>> Troubleshoot faster and improve end-user experience. Signup Now! >>>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 >>>>>>> _______________________________________________ >>>>>>> Bigdata-developers mailing list >>>>>>> Big...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers >>>>>>> >>>>>>> >>>>> >>>> >>> >> > |
From: Bryan T. <br...@sy...> - 2016-02-16 20:05:05
|
So it is looking for this class: com.bigdata.rdf.vocab.core. BigdataCoreVocabulary_v20151210 This class is in the 2.0 release. It should not have updated the definition of the vocabulary. That is a durable thing which is established when you first create a namespace. It is not modified after that. In fact, modifying this property would cause havoc for the namespace. Do you perhaps not have the default namespace (kb) in the journal before you start 2.0? It is possible that it is automatically creating that default namespace if none is found and then your 1.5.3 version is unable to resolve the newer vocabulary class. There is a web.xml property you can specify to have it NOT automatically create the default namespace. Thanks, Bryan ---- Bryan Thompson Chief Scientist & Founder Blazegraph e: br...@bl... w: http://blazegraph.com Blazegraph products help to solve the Graph Cache Thrash to achieve large scale processing for graph and predictive analytics. Blazegraph is the creator of the industry’s first GPU-accelerated high-performance database for large graphs, has been named as one of the “10 Companies and Technologies to Watch in 2016” <http://insideanalysis.com/2016/01/20535/>. Blazegraph Database <https://www.blazegraph.com/> is our ultra-high performance graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints APIs. Blazegraph GPU <https://www.blazegraph.com/product/gpu-accelerated/> andBlazegraph DAS <https://www.blazegraph.com/product/gpu-accelerated/>L are disruptive new technologies that use GPUs to enable extreme scaling that is thousands of times faster and 40 times more affordable than CPU-based solutions. 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, LLC DBA Blazegraph. 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, Feb 16, 2016 at 3:00 PM, Edgar Rodriguez-Diaz <ed...@sy...> wrote: > This seems relevant from the log from my blazegraph 1.5.3 using the > Journal previously queried in 2.0.0: > > ``` > Feb 16,2016 11:09:30 PST - ERROR: 7822 qtp1935637221-32 > com.bigdata.rdf.sail.webapp.BigdataRDFServlet.launderThrowable(BigdataRDFServlet.java:214): > cause=java.lang.RuntimeException: off=0, len=339, > query=describeEachNamedGraph=false, describeDefaultNamespace=false > java.lang.RuntimeException: off=0, len=339 > at com.bigdata.io.SerializerUtil.deserialize(SerializerUtil.java:239) > at com.bigdata.io.SerializerUtil.deserialize(SerializerUtil.java:207) > at com.bigdata.sparse.ValueType.decode(ValueType.java:333) > at > com.bigdata.sparse.AtomicRowFilter$Transformerator.handleTuple(AtomicRowFilter.java:408) > at > com.bigdata.sparse.AtomicRowFilter$Transformerator.hasNext(AtomicRowFilter.java:290) > at > com.bigdata.btree.filter.WrappedTupleIterator.hasNext(WrappedTupleIterator.java:30) > at cutthecrap.utils.striterators.Resolverator.hasNext(Resolverator.java:39) > at cutthecrap.utils.striterators.Striterator.hasNext(Striterator.java:89) > at > com.bigdata.rdf.sail.webapp.BigdataRDFContext.getNamespacesTx(BigdataRDFContext.java:2748) > at > com.bigdata.rdf.sail.webapp.MultiTenancyServlet.doDescribeNamespaces(MultiTenancyServlet.java:506) > at > com.bigdata.rdf.sail.webapp.MultiTenancyServlet.doGet(MultiTenancyServlet.java:199) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:769) > at > org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) > at > org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577) > at > org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223) > at > org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1125) > at > org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515) > at > org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) > at > org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1059) > at > org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) > at > org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215) > at > org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:110) > at > org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) > at org.eclipse.jetty.server.Server.handle(Server.java:497) > at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:311) > at > org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:248) > at > org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540) > at > org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:610) > at > org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:539) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.ClassNotFoundException: > com.bigdata.rdf.vocab.core.BigdataCoreVocabulary_v20151210 > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:348) > at java.io.ObjectInputStream.resolveClass(ObjectInputStream.java:626) > at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1613) > at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1518) > at > java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1774) > at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:371) > at com.bigdata.io.SerializerUtil.deserialize(SerializerUtil.java:231) > ... 32 more > ``` > > Seems like still something is trying to use the vocabulary previously > mentioned. > > Cheers, > Edgar > > On Tue, Feb 16, 2016 at 11:41 AM, Bryan Thompson <br...@sy...> wrote: > >> Does anything show up in the logs? The set of namespaces is stored in >> the __globalRowStore. Just querying the system should not cause anything >> to be written. This would be visible if you use DumpJournal (w/o -pages) >> and look at the commit counter. It should be unchanged. Queries are read >> only. >> >> Thanks, >> Bryan >> >> ---- >> Bryan Thompson >> Chief Scientist & Founder >> Blazegraph >> e: br...@bl... >> w: http://blazegraph.com >> >> Blazegraph products help to solve the Graph Cache Thrash to achieve large >> scale processing for graph and predictive analytics. Blazegraph is the >> creator of the industry’s first GPU-accelerated high-performance database >> for large graphs, has been named as one of the “10 Companies and >> Technologies to Watch in 2016” <http://insideanalysis.com/2016/01/20535/>. >> >> >> Blazegraph Database <https://www.blazegraph.com/> is our ultra-high >> performance graph database that supports both RDF/SPARQL and >> Tinkerpop/Blueprints APIs. Blazegraph GPU >> <https://www.blazegraph.com/product/gpu-accelerated/> andBlazegraph DAS >> <https://www.blazegraph.com/product/gpu-accelerated/>L are disruptive >> new technologies that use GPUs to enable extreme scaling that is thousands >> of times faster and 40 times more affordable than CPU-based solutions. >> >> 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, LLC DBA Blazegraph. 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, Feb 16, 2016 at 2:31 PM, Edgar Rodriguez-Diaz <ed...@sy...> >> wrote: >> >>> It would seem that just opening the 1.5.3 journal file in 2.0.0 makes it >>> unusable in 1.5.3. This is what I’m doing: >>> >>> 1. Start with an empty Journal from 1.5.3, in my blazegraph.properties >>> it’s defined: >>> >>> >>> com.bigdata.journal.AbstractJournal.file=/usr/local/var/blazegraph/blazegraph.jnl >>> >>> 2. Go to the workbench/namespaces and create a new NS, say `nstest`, and >>> select it >>> 2.1. Add some data ~1M triples. >>> 2.2. Execute a query to list just 100 triples >>> >>> 3. Stop blazegraph 1.5.3 >>> 4. Go to my properties file in blazegraph 2.0.0 (from the Github repo, a >>> copy of `bigdata-war-html/src/main/webapp/WEB-INF/RWStore.properties`), set >>> the Journal file to: >>> >>> >>> com.bigdata.journal.AbstractJournal.file=/usr/local/var/blazegraph/blazegraph.jnl >>> >>> 5. Start blazegraph 2.0.0, correctly pointing to my properties file in >>> `scripts/startBlazegraph.sh` >>> 6. Go to the workbench/namespaces. >>> 6.2. Select my namespaces created in 1.5.3 (`nstest`), which is listed >>> 6.1. Execute a query to list just 100 triples >>> >>> 7. Stop blazegraph 2.0.0 >>> 8. Start blazegraph 1.5.3 >>> 9. Go to namespaces; no namespaces are listed. >>> >>> I’m not modifying the 1.5.3 journal with 2.0.0 (or at least I don’t >>> think I’m modifying it), just opening it in 2.0.0 and executing a query, >>> which seems to be enough to make it not visible anymore back in 1.5.3. >>> >>> I’m I missing something? >>> >>> Thanks. >>> >>> Cheers, >>> Edgar >>> >>> On Tue, Feb 16, 2016 at 10:20 AM, Bryan Thompson <br...@sy...> >>> wrote: >>> >>>> Yes. It is actually if you create a namespace with a newer vocabulary, >>>> then you can not open it with a classpath that does not include that >>>> vocabulary. Since 2.0 uses a new vocabulary declaration by default, create >>>> your namespace in 1.5.3 if you want to use it in both 2.0 and 1.5.3. >>>> >>>> Thanks, >>>> Bryan >>>> >>>> ---- >>>> Bryan Thompson >>>> Chief Scientist & Founder >>>> Blazegraph >>>> e: br...@bl... >>>> w: http://blazegraph.com >>>> >>>> Blazegraph products help to solve the Graph Cache Thrash to achieve >>>> large scale processing for graph and predictive analytics. Blazegraph is >>>> the creator of the industry’s first GPU-accelerated high-performance >>>> database for large graphs, has been named as one of the “10 Companies >>>> and Technologies to Watch in 2016” >>>> <http://insideanalysis.com/2016/01/20535/>. >>>> >>>> Blazegraph Database <https://www.blazegraph.com/> is our ultra-high >>>> performance graph database that supports both RDF/SPARQL and >>>> Tinkerpop/Blueprints APIs. Blazegraph GPU >>>> <https://www.blazegraph.com/product/gpu-accelerated/> andBlazegraph DAS >>>> <https://www.blazegraph.com/product/gpu-accelerated/>L are disruptive >>>> new technologies that use GPUs to enable extreme scaling that is thousands >>>> of times faster and 40 times more affordable than CPU-based solutions. >>>> >>>> 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, LLC DBA Blazegraph. 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, Feb 16, 2016 at 1:18 PM, Brad Bebee <be...@bl...> >>>> wrote: >>>> >>>>> Edgar, >>>>> >>>>> 2.0.0 introduced a new versioned vocabulary class that is the default >>>>> for newly created namespaces. The vocabulary class must be in the >>>>> classpath. >>>>> >>>>> As such, if you create a journal with 1.5.3, you can open it in >>>>> 2.0.0. If You create a journal in 2.0.0, you would need to add the new >>>>> vocabulary class in the classpath to open it in 1.5.3. >>>>> >>>>> Thanks, Brad >>>>> >>>>> _______________ >>>>> Brad Bebee >>>>> CEO, Managing Partner >>>>> SYSTAP, LLC >>>>> e: be...@sy... >>>>> m: 202.642.7961 >>>>> f: 571.367.5000 >>>>> w: www.systap.com >>>>> >>>>> Blazegraph™ is our ultra high-performance graph database that supports >>>>> both RDF/SPARQL and Tinkerpop/Blueprints APIs. MapGraph™ is our disruptive >>>>> new technology to use GPUs to accelerate data-parallel graph analytics. >>>>> >>>>> 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, LLC. 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 Feb 15, 2016 5:41 PM, "Bryan Thompson" <br...@sy...> wrote: >>>>> >>>>>> It should be compatible. Can you provide mode details. >>>>>> >>>>>> Bryan >>>>>> >>>>>> ---- >>>>>> Bryan Thompson >>>>>> Chief Scientist & Founder >>>>>> Blazegraph >>>>>> e: br...@bl... >>>>>> w: http://blazegraph.com >>>>>> >>>>>> Blazegraph products help to solve the Graph Cache Thrash to achieve >>>>>> large scale processing for graph and predictive analytics. Blazegraph is >>>>>> the creator of the industry’s first GPU-accelerated high-performance >>>>>> database for large graphs, has been named as one of the “10 >>>>>> Companies and Technologies to Watch in 2016” >>>>>> <http://insideanalysis.com/2016/01/20535/>. >>>>>> >>>>>> Blazegraph Database <https://www.blazegraph.com/> is our ultra-high >>>>>> performance graph database that supports both RDF/SPARQL and >>>>>> Tinkerpop/Blueprints APIs. Blazegraph GPU >>>>>> <https://www.blazegraph.com/product/gpu-accelerated/> and >>>>>> Blazegraph DAS <https://www.blazegraph.com/product/gpu-accelerated/>L >>>>>> are disruptive new technologies that use GPUs to enable extreme scaling >>>>>> that is thousands of times faster and 40 times more affordable than >>>>>> CPU-based solutions. >>>>>> >>>>>> 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, LLC DBA Blazegraph. 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, Feb 15, 2016 at 5:14 PM, Edgar Rodriguez-Diaz < >>>>>> ed...@sy...> wrote: >>>>>> >>>>>>> I was wondering what’s the level of compatibility for the Journal >>>>>>> file between 1.5.3 and 2.0.0. I did a small check and it seems like once a >>>>>>> journal is opened with 2.0.0 it’s no longer compatible with 1.5.3. >>>>>>> Is this correct? Thanks. >>>>>>> >>>>>>> Cheers, >>>>>>> - Edgar >>>>>>> >>>>>>> ------------------------------------------------------------------------------ >>>>>>> Site24x7 APM Insight: Get Deep Visibility into Application >>>>>>> Performance >>>>>>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >>>>>>> Monitor end-to-end web transactions and take corrective actions now >>>>>>> Troubleshoot faster and improve end-user experience. Signup Now! >>>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 >>>>>>> _______________________________________________ >>>>>>> Bigdata-developers mailing list >>>>>>> Big...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> Site24x7 APM Insight: Get Deep Visibility into Application Performance >>>>>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >>>>>> Monitor end-to-end web transactions and take corrective actions now >>>>>> Troubleshoot faster and improve end-user experience. Signup Now! >>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 >>>>>> _______________________________________________ >>>>>> Bigdata-developers mailing list >>>>>> Big...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers >>>>>> >>>>>> >>>> >>> >> > |
From: Edgar Rodriguez-D. <ed...@sy...> - 2016-02-16 20:01:12
|
It would seem that just opening the 1.5.3 journal file in 2.0.0 makes it unusable in 1.5.3. This is what I’m doing: 1. Start with an empty Journal from 1.5.3, in my blazegraph.properties it’s defined: com.bigdata.journal.AbstractJournal.file=/usr/local/var/blazegraph/blazegraph.jnl 2. Go to the workbench/namespaces and create a new NS, say `nstest`, and select it 2.1. Add some data ~1M triples. 2.2. Execute a query to list just 100 triples 3. Stop blazegraph 1.5.3 4. Go to my properties file in blazegraph 2.0.0 (from the Github repo, a copy of `bigdata-war-html/src/main/webapp/WEB-INF/RWStore.properties`), set the Journal file to: com.bigdata.journal.AbstractJournal.file=/usr/local/var/blazegraph/blazegraph.jnl 5. Start blazegraph 2.0.0, correctly pointing to my properties file in `scripts/startBlazegraph.sh` 6. Go to the workbench/namespaces. 6.2. Select my namespaces created in 1.5.3 (`nstest`), which is listed 6.1. Execute a query to list just 100 triples 7. Stop blazegraph 2.0.0 8. Start blazegraph 1.5.3 9. Go to namespaces; no namespaces are listed. I’m not modifying the 1.5.3 journal with 2.0.0 (or at least I don’t think I’m modifying it), just opening it in 2.0.0 and executing a query, which seems to be enough to make it not visible anymore back in 1.5.3. I’m I missing something? Thanks. Cheers, Edgar On Tue, Feb 16, 2016 at 10:20 AM, Bryan Thompson <br...@sy...> wrote: > Yes. It is actually if you create a namespace with a newer vocabulary, > then you can not open it with a classpath that does not include that > vocabulary. Since 2.0 uses a new vocabulary declaration by default, create > your namespace in 1.5.3 if you want to use it in both 2.0 and 1.5.3. > > Thanks, > Bryan > > ---- > Bryan Thompson > Chief Scientist & Founder > Blazegraph > e: br...@bl... > w: http://blazegraph.com > > Blazegraph products help to solve the Graph Cache Thrash to achieve large > scale processing for graph and predictive analytics. Blazegraph is the > creator of the industry’s first GPU-accelerated high-performance database > for large graphs, has been named as one of the “10 Companies and > Technologies to Watch in 2016” <http://insideanalysis.com/2016/01/20535/>. > > > Blazegraph Database <https://www.blazegraph.com/> is our ultra-high > performance graph database that supports both RDF/SPARQL and > Tinkerpop/Blueprints APIs. Blazegraph GPU > <https://www.blazegraph.com/product/gpu-accelerated/> andBlazegraph DAS > <https://www.blazegraph.com/product/gpu-accelerated/>L are disruptive new > technologies that use GPUs to enable extreme scaling that is thousands of > times faster and 40 times more affordable than CPU-based solutions. > > 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, LLC DBA Blazegraph. 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, Feb 16, 2016 at 1:18 PM, Brad Bebee <be...@bl...> wrote: > >> Edgar, >> >> 2.0.0 introduced a new versioned vocabulary class that is the default for >> newly created namespaces. The vocabulary class must be in the classpath. >> >> As such, if you create a journal with 1.5.3, you can open it in 2.0.0. >> If You create a journal in 2.0.0, you would need to add the new vocabulary >> class in the classpath to open it in 1.5.3. >> >> Thanks, Brad >> >> _______________ >> Brad Bebee >> CEO, Managing Partner >> SYSTAP, LLC >> e: be...@sy... >> m: 202.642.7961 >> f: 571.367.5000 >> w: www.systap.com >> >> Blazegraph™ is our ultra high-performance graph database that supports >> both RDF/SPARQL and Tinkerpop/Blueprints APIs. MapGraph™ is our disruptive >> new technology to use GPUs to accelerate data-parallel graph analytics. >> >> 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, LLC. 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 Feb 15, 2016 5:41 PM, "Bryan Thompson" <br...@sy...> wrote: >> >>> It should be compatible. Can you provide mode details. >>> >>> Bryan >>> >>> ---- >>> Bryan Thompson >>> Chief Scientist & Founder >>> Blazegraph >>> e: br...@bl... >>> w: http://blazegraph.com >>> >>> Blazegraph products help to solve the Graph Cache Thrash to achieve >>> large scale processing for graph and predictive analytics. Blazegraph is >>> the creator of the industry’s first GPU-accelerated high-performance >>> database for large graphs, has been named as one of the “10 Companies >>> and Technologies to Watch in 2016” >>> <http://insideanalysis.com/2016/01/20535/>. >>> >>> Blazegraph Database <https://www.blazegraph.com/> is our ultra-high >>> performance graph database that supports both RDF/SPARQL and >>> Tinkerpop/Blueprints APIs. Blazegraph GPU >>> <https://www.blazegraph.com/product/gpu-accelerated/> andBlazegraph DAS >>> <https://www.blazegraph.com/product/gpu-accelerated/>L are disruptive >>> new technologies that use GPUs to enable extreme scaling that is thousands >>> of times faster and 40 times more affordable than CPU-based solutions. >>> >>> 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, LLC DBA Blazegraph. 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, Feb 15, 2016 at 5:14 PM, Edgar Rodriguez-Diaz <ed...@sy... >>> > wrote: >>> >>>> I was wondering what’s the level of compatibility for the Journal file >>>> between 1.5.3 and 2.0.0. I did a small check and it seems like once a >>>> journal is opened with 2.0.0 it’s no longer compatible with 1.5.3. >>>> Is this correct? Thanks. >>>> >>>> Cheers, >>>> - Edgar >>>> >>>> ------------------------------------------------------------------------------ >>>> Site24x7 APM Insight: Get Deep Visibility into Application Performance >>>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >>>> Monitor end-to-end web transactions and take corrective actions now >>>> Troubleshoot faster and improve end-user experience. Signup Now! >>>> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 >>>> _______________________________________________ >>>> Bigdata-developers mailing list >>>> Big...@li... >>>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers >>>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Site24x7 APM Insight: Get Deep Visibility into Application Performance >>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >>> Monitor end-to-end web transactions and take corrective actions now >>> Troubleshoot faster and improve end-user experience. Signup Now! >>> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 >>> _______________________________________________ >>> Bigdata-developers mailing list >>> Big...@li... >>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers >>> >>> > |
From: Edgar Rodriguez-D. <ed...@sy...> - 2016-02-16 20:00:40
|
This seems relevant from the log from my blazegraph 1.5.3 using the Journal previously queried in 2.0.0: ``` Feb 16,2016 11:09:30 PST - ERROR: 7822 qtp1935637221-32 com.bigdata.rdf.sail.webapp.BigdataRDFServlet.launderThrowable(BigdataRDFServlet.java:214): cause=java.lang.RuntimeException: off=0, len=339, query=describeEachNamedGraph=false, describeDefaultNamespace=false java.lang.RuntimeException: off=0, len=339 at com.bigdata.io.SerializerUtil.deserialize(SerializerUtil.java:239) at com.bigdata.io.SerializerUtil.deserialize(SerializerUtil.java:207) at com.bigdata.sparse.ValueType.decode(ValueType.java:333) at com.bigdata.sparse.AtomicRowFilter$Transformerator.handleTuple(AtomicRowFilter.java:408) at com.bigdata.sparse.AtomicRowFilter$Transformerator.hasNext(AtomicRowFilter.java:290) at com.bigdata.btree.filter.WrappedTupleIterator.hasNext(WrappedTupleIterator.java:30) at cutthecrap.utils.striterators.Resolverator.hasNext(Resolverator.java:39) at cutthecrap.utils.striterators.Striterator.hasNext(Striterator.java:89) at com.bigdata.rdf.sail.webapp.BigdataRDFContext.getNamespacesTx(BigdataRDFContext.java:2748) at com.bigdata.rdf.sail.webapp.MultiTenancyServlet.doDescribeNamespaces(MultiTenancyServlet.java:506) at com.bigdata.rdf.sail.webapp.MultiTenancyServlet.doGet(MultiTenancyServlet.java:199) at javax.servlet.http.HttpServlet.service(HttpServlet.java:687) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:769) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1125) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1059) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215) at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:110) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) at org.eclipse.jetty.server.Server.handle(Server.java:497) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:311) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:248) at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:610) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:539) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.ClassNotFoundException: com.bigdata.rdf.vocab.core.BigdataCoreVocabulary_v20151210 at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:348) at java.io.ObjectInputStream.resolveClass(ObjectInputStream.java:626) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1613) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1518) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1774) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1351) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:371) at com.bigdata.io.SerializerUtil.deserialize(SerializerUtil.java:231) ... 32 more ``` Seems like still something is trying to use the vocabulary previously mentioned. Cheers, Edgar On Tue, Feb 16, 2016 at 11:41 AM, Bryan Thompson <br...@sy...> wrote: > Does anything show up in the logs? The set of namespaces is stored in the > __globalRowStore. Just querying the system should not cause anything to be > written. This would be visible if you use DumpJournal (w/o -pages) and > look at the commit counter. It should be unchanged. Queries are read only. > > Thanks, > Bryan > > ---- > Bryan Thompson > Chief Scientist & Founder > Blazegraph > e: br...@bl... > w: http://blazegraph.com > > Blazegraph products help to solve the Graph Cache Thrash to achieve large > scale processing for graph and predictive analytics. Blazegraph is the > creator of the industry’s first GPU-accelerated high-performance database > for large graphs, has been named as one of the “10 Companies and > Technologies to Watch in 2016” <http://insideanalysis.com/2016/01/20535/>. > > > Blazegraph Database <https://www.blazegraph.com/> is our ultra-high > performance graph database that supports both RDF/SPARQL and > Tinkerpop/Blueprints APIs. Blazegraph GPU > <https://www.blazegraph.com/product/gpu-accelerated/> andBlazegraph DAS > <https://www.blazegraph.com/product/gpu-accelerated/>L are disruptive new > technologies that use GPUs to enable extreme scaling that is thousands of > times faster and 40 times more affordable than CPU-based solutions. > > 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, LLC DBA Blazegraph. 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, Feb 16, 2016 at 2:31 PM, Edgar Rodriguez-Diaz <ed...@sy...> > wrote: > >> It would seem that just opening the 1.5.3 journal file in 2.0.0 makes it >> unusable in 1.5.3. This is what I’m doing: >> >> 1. Start with an empty Journal from 1.5.3, in my blazegraph.properties >> it’s defined: >> >> >> com.bigdata.journal.AbstractJournal.file=/usr/local/var/blazegraph/blazegraph.jnl >> >> 2. Go to the workbench/namespaces and create a new NS, say `nstest`, and >> select it >> 2.1. Add some data ~1M triples. >> 2.2. Execute a query to list just 100 triples >> >> 3. Stop blazegraph 1.5.3 >> 4. Go to my properties file in blazegraph 2.0.0 (from the Github repo, a >> copy of `bigdata-war-html/src/main/webapp/WEB-INF/RWStore.properties`), set >> the Journal file to: >> >> >> com.bigdata.journal.AbstractJournal.file=/usr/local/var/blazegraph/blazegraph.jnl >> >> 5. Start blazegraph 2.0.0, correctly pointing to my properties file in >> `scripts/startBlazegraph.sh` >> 6. Go to the workbench/namespaces. >> 6.2. Select my namespaces created in 1.5.3 (`nstest`), which is listed >> 6.1. Execute a query to list just 100 triples >> >> 7. Stop blazegraph 2.0.0 >> 8. Start blazegraph 1.5.3 >> 9. Go to namespaces; no namespaces are listed. >> >> I’m not modifying the 1.5.3 journal with 2.0.0 (or at least I don’t think >> I’m modifying it), just opening it in 2.0.0 and executing a query, which >> seems to be enough to make it not visible anymore back in 1.5.3. >> >> I’m I missing something? >> >> Thanks. >> >> Cheers, >> Edgar >> >> On Tue, Feb 16, 2016 at 10:20 AM, Bryan Thompson <br...@sy...> >> wrote: >> >>> Yes. It is actually if you create a namespace with a newer vocabulary, >>> then you can not open it with a classpath that does not include that >>> vocabulary. Since 2.0 uses a new vocabulary declaration by default, create >>> your namespace in 1.5.3 if you want to use it in both 2.0 and 1.5.3. >>> >>> Thanks, >>> Bryan >>> >>> ---- >>> Bryan Thompson >>> Chief Scientist & Founder >>> Blazegraph >>> e: br...@bl... >>> w: http://blazegraph.com >>> >>> Blazegraph products help to solve the Graph Cache Thrash to achieve >>> large scale processing for graph and predictive analytics. Blazegraph is >>> the creator of the industry’s first GPU-accelerated high-performance >>> database for large graphs, has been named as one of the “10 Companies >>> and Technologies to Watch in 2016” >>> <http://insideanalysis.com/2016/01/20535/>. >>> >>> Blazegraph Database <https://www.blazegraph.com/> is our ultra-high >>> performance graph database that supports both RDF/SPARQL and >>> Tinkerpop/Blueprints APIs. Blazegraph GPU >>> <https://www.blazegraph.com/product/gpu-accelerated/> andBlazegraph DAS >>> <https://www.blazegraph.com/product/gpu-accelerated/>L are disruptive >>> new technologies that use GPUs to enable extreme scaling that is thousands >>> of times faster and 40 times more affordable than CPU-based solutions. >>> >>> 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, LLC DBA Blazegraph. 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, Feb 16, 2016 at 1:18 PM, Brad Bebee <be...@bl...> >>> wrote: >>> >>>> Edgar, >>>> >>>> 2.0.0 introduced a new versioned vocabulary class that is the default >>>> for newly created namespaces. The vocabulary class must be in the >>>> classpath. >>>> >>>> As such, if you create a journal with 1.5.3, you can open it in 2.0.0. >>>> If You create a journal in 2.0.0, you would need to add the new vocabulary >>>> class in the classpath to open it in 1.5.3. >>>> >>>> Thanks, Brad >>>> >>>> _______________ >>>> Brad Bebee >>>> CEO, Managing Partner >>>> SYSTAP, LLC >>>> e: be...@sy... >>>> m: 202.642.7961 >>>> f: 571.367.5000 >>>> w: www.systap.com >>>> >>>> Blazegraph™ is our ultra high-performance graph database that supports >>>> both RDF/SPARQL and Tinkerpop/Blueprints APIs. MapGraph™ is our disruptive >>>> new technology to use GPUs to accelerate data-parallel graph analytics. >>>> >>>> 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, LLC. 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 Feb 15, 2016 5:41 PM, "Bryan Thompson" <br...@sy...> wrote: >>>> >>>>> It should be compatible. Can you provide mode details. >>>>> >>>>> Bryan >>>>> >>>>> ---- >>>>> Bryan Thompson >>>>> Chief Scientist & Founder >>>>> Blazegraph >>>>> e: br...@bl... >>>>> w: http://blazegraph.com >>>>> >>>>> Blazegraph products help to solve the Graph Cache Thrash to achieve >>>>> large scale processing for graph and predictive analytics. Blazegraph is >>>>> the creator of the industry’s first GPU-accelerated high-performance >>>>> database for large graphs, has been named as one of the “10 Companies >>>>> and Technologies to Watch in 2016” >>>>> <http://insideanalysis.com/2016/01/20535/>. >>>>> >>>>> Blazegraph Database <https://www.blazegraph.com/> is our ultra-high >>>>> performance graph database that supports both RDF/SPARQL and >>>>> Tinkerpop/Blueprints APIs. Blazegraph GPU >>>>> <https://www.blazegraph.com/product/gpu-accelerated/> and >>>>> Blazegraph DAS <https://www.blazegraph.com/product/gpu-accelerated/>L >>>>> are disruptive new technologies that use GPUs to enable extreme scaling >>>>> that is thousands of times faster and 40 times more affordable than >>>>> CPU-based solutions. >>>>> >>>>> 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, LLC DBA Blazegraph. 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, Feb 15, 2016 at 5:14 PM, Edgar Rodriguez-Diaz < >>>>> ed...@sy...> wrote: >>>>> >>>>>> I was wondering what’s the level of compatibility for the Journal >>>>>> file between 1.5.3 and 2.0.0. I did a small check and it seems like once a >>>>>> journal is opened with 2.0.0 it’s no longer compatible with 1.5.3. >>>>>> Is this correct? Thanks. >>>>>> >>>>>> Cheers, >>>>>> - Edgar >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> Site24x7 APM Insight: Get Deep Visibility into Application Performance >>>>>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >>>>>> Monitor end-to-end web transactions and take corrective actions now >>>>>> Troubleshoot faster and improve end-user experience. Signup Now! >>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 >>>>>> _______________________________________________ >>>>>> Bigdata-developers mailing list >>>>>> Big...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers >>>>>> >>>>> >>>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Site24x7 APM Insight: Get Deep Visibility into Application Performance >>>>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >>>>> Monitor end-to-end web transactions and take corrective actions now >>>>> Troubleshoot faster and improve end-user experience. Signup Now! >>>>> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 >>>>> _______________________________________________ >>>>> Bigdata-developers mailing list >>>>> Big...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers >>>>> >>>>> >>> >> > |
From: Bryan T. <br...@sy...> - 2016-02-16 19:41:27
|
Does anything show up in the logs? The set of namespaces is stored in the __globalRowStore. Just querying the system should not cause anything to be written. This would be visible if you use DumpJournal (w/o -pages) and look at the commit counter. It should be unchanged. Queries are read only. Thanks, Bryan ---- Bryan Thompson Chief Scientist & Founder Blazegraph e: br...@bl... w: http://blazegraph.com Blazegraph products help to solve the Graph Cache Thrash to achieve large scale processing for graph and predictive analytics. Blazegraph is the creator of the industry’s first GPU-accelerated high-performance database for large graphs, has been named as one of the “10 Companies and Technologies to Watch in 2016” <http://insideanalysis.com/2016/01/20535/>. Blazegraph Database <https://www.blazegraph.com/> is our ultra-high performance graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints APIs. Blazegraph GPU <https://www.blazegraph.com/product/gpu-accelerated/> andBlazegraph DAS <https://www.blazegraph.com/product/gpu-accelerated/>L are disruptive new technologies that use GPUs to enable extreme scaling that is thousands of times faster and 40 times more affordable than CPU-based solutions. 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, LLC DBA Blazegraph. 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, Feb 16, 2016 at 2:31 PM, Edgar Rodriguez-Diaz <ed...@sy...> wrote: > It would seem that just opening the 1.5.3 journal file in 2.0.0 makes it > unusable in 1.5.3. This is what I’m doing: > > 1. Start with an empty Journal from 1.5.3, in my blazegraph.properties > it’s defined: > > > com.bigdata.journal.AbstractJournal.file=/usr/local/var/blazegraph/blazegraph.jnl > > 2. Go to the workbench/namespaces and create a new NS, say `nstest`, and > select it > 2.1. Add some data ~1M triples. > 2.2. Execute a query to list just 100 triples > > 3. Stop blazegraph 1.5.3 > 4. Go to my properties file in blazegraph 2.0.0 (from the Github repo, a > copy of `bigdata-war-html/src/main/webapp/WEB-INF/RWStore.properties`), set > the Journal file to: > > > com.bigdata.journal.AbstractJournal.file=/usr/local/var/blazegraph/blazegraph.jnl > > 5. Start blazegraph 2.0.0, correctly pointing to my properties file in > `scripts/startBlazegraph.sh` > 6. Go to the workbench/namespaces. > 6.2. Select my namespaces created in 1.5.3 (`nstest`), which is listed > 6.1. Execute a query to list just 100 triples > > 7. Stop blazegraph 2.0.0 > 8. Start blazegraph 1.5.3 > 9. Go to namespaces; no namespaces are listed. > > I’m not modifying the 1.5.3 journal with 2.0.0 (or at least I don’t think > I’m modifying it), just opening it in 2.0.0 and executing a query, which > seems to be enough to make it not visible anymore back in 1.5.3. > > I’m I missing something? > > Thanks. > > Cheers, > Edgar > > On Tue, Feb 16, 2016 at 10:20 AM, Bryan Thompson <br...@sy...> wrote: > >> Yes. It is actually if you create a namespace with a newer vocabulary, >> then you can not open it with a classpath that does not include that >> vocabulary. Since 2.0 uses a new vocabulary declaration by default, create >> your namespace in 1.5.3 if you want to use it in both 2.0 and 1.5.3. >> >> Thanks, >> Bryan >> >> ---- >> Bryan Thompson >> Chief Scientist & Founder >> Blazegraph >> e: br...@bl... >> w: http://blazegraph.com >> >> Blazegraph products help to solve the Graph Cache Thrash to achieve large >> scale processing for graph and predictive analytics. Blazegraph is the >> creator of the industry’s first GPU-accelerated high-performance database >> for large graphs, has been named as one of the “10 Companies and >> Technologies to Watch in 2016” <http://insideanalysis.com/2016/01/20535/>. >> >> >> Blazegraph Database <https://www.blazegraph.com/> is our ultra-high >> performance graph database that supports both RDF/SPARQL and >> Tinkerpop/Blueprints APIs. Blazegraph GPU >> <https://www.blazegraph.com/product/gpu-accelerated/> andBlazegraph DAS >> <https://www.blazegraph.com/product/gpu-accelerated/>L are disruptive >> new technologies that use GPUs to enable extreme scaling that is thousands >> of times faster and 40 times more affordable than CPU-based solutions. >> >> 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, LLC DBA Blazegraph. 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, Feb 16, 2016 at 1:18 PM, Brad Bebee <be...@bl...> wrote: >> >>> Edgar, >>> >>> 2.0.0 introduced a new versioned vocabulary class that is the default >>> for newly created namespaces. The vocabulary class must be in the >>> classpath. >>> >>> As such, if you create a journal with 1.5.3, you can open it in 2.0.0. >>> If You create a journal in 2.0.0, you would need to add the new vocabulary >>> class in the classpath to open it in 1.5.3. >>> >>> Thanks, Brad >>> >>> _______________ >>> Brad Bebee >>> CEO, Managing Partner >>> SYSTAP, LLC >>> e: be...@sy... >>> m: 202.642.7961 >>> f: 571.367.5000 >>> w: www.systap.com >>> >>> Blazegraph™ is our ultra high-performance graph database that supports >>> both RDF/SPARQL and Tinkerpop/Blueprints APIs. MapGraph™ is our disruptive >>> new technology to use GPUs to accelerate data-parallel graph analytics. >>> >>> 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, LLC. 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 Feb 15, 2016 5:41 PM, "Bryan Thompson" <br...@sy...> wrote: >>> >>>> It should be compatible. Can you provide mode details. >>>> >>>> Bryan >>>> >>>> ---- >>>> Bryan Thompson >>>> Chief Scientist & Founder >>>> Blazegraph >>>> e: br...@bl... >>>> w: http://blazegraph.com >>>> >>>> Blazegraph products help to solve the Graph Cache Thrash to achieve >>>> large scale processing for graph and predictive analytics. Blazegraph is >>>> the creator of the industry’s first GPU-accelerated high-performance >>>> database for large graphs, has been named as one of the “10 Companies >>>> and Technologies to Watch in 2016” >>>> <http://insideanalysis.com/2016/01/20535/>. >>>> >>>> Blazegraph Database <https://www.blazegraph.com/> is our ultra-high >>>> performance graph database that supports both RDF/SPARQL and >>>> Tinkerpop/Blueprints APIs. Blazegraph GPU >>>> <https://www.blazegraph.com/product/gpu-accelerated/> andBlazegraph DAS >>>> <https://www.blazegraph.com/product/gpu-accelerated/>L are disruptive >>>> new technologies that use GPUs to enable extreme scaling that is thousands >>>> of times faster and 40 times more affordable than CPU-based solutions. >>>> >>>> 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, LLC DBA Blazegraph. 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, Feb 15, 2016 at 5:14 PM, Edgar Rodriguez-Diaz < >>>> ed...@sy...> wrote: >>>> >>>>> I was wondering what’s the level of compatibility for the Journal file >>>>> between 1.5.3 and 2.0.0. I did a small check and it seems like once a >>>>> journal is opened with 2.0.0 it’s no longer compatible with 1.5.3. >>>>> Is this correct? Thanks. >>>>> >>>>> Cheers, >>>>> - Edgar >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Site24x7 APM Insight: Get Deep Visibility into Application Performance >>>>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >>>>> Monitor end-to-end web transactions and take corrective actions now >>>>> Troubleshoot faster and improve end-user experience. Signup Now! >>>>> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 >>>>> _______________________________________________ >>>>> Bigdata-developers mailing list >>>>> Big...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers >>>>> >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Site24x7 APM Insight: Get Deep Visibility into Application Performance >>>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >>>> Monitor end-to-end web transactions and take corrective actions now >>>> Troubleshoot faster and improve end-user experience. Signup Now! >>>> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 >>>> _______________________________________________ >>>> Bigdata-developers mailing list >>>> Big...@li... >>>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers >>>> >>>> >> > |
From: Bryan T. <br...@sy...> - 2016-02-16 18:20:47
|
Yes. It is actually if you create a namespace with a newer vocabulary, then you can not open it with a classpath that does not include that vocabulary. Since 2.0 uses a new vocabulary declaration by default, create your namespace in 1.5.3 if you want to use it in both 2.0 and 1.5.3. Thanks, Bryan ---- Bryan Thompson Chief Scientist & Founder Blazegraph e: br...@bl... w: http://blazegraph.com Blazegraph products help to solve the Graph Cache Thrash to achieve large scale processing for graph and predictive analytics. Blazegraph is the creator of the industry’s first GPU-accelerated high-performance database for large graphs, has been named as one of the “10 Companies and Technologies to Watch in 2016” <http://insideanalysis.com/2016/01/20535/>. Blazegraph Database <https://www.blazegraph.com/> is our ultra-high performance graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints APIs. Blazegraph GPU <https://www.blazegraph.com/product/gpu-accelerated/> andBlazegraph DAS <https://www.blazegraph.com/product/gpu-accelerated/>L are disruptive new technologies that use GPUs to enable extreme scaling that is thousands of times faster and 40 times more affordable than CPU-based solutions. 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, LLC DBA Blazegraph. 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, Feb 16, 2016 at 1:18 PM, Brad Bebee <be...@bl...> wrote: > Edgar, > > 2.0.0 introduced a new versioned vocabulary class that is the default for > newly created namespaces. The vocabulary class must be in the classpath. > > As such, if you create a journal with 1.5.3, you can open it in 2.0.0. If > You create a journal in 2.0.0, you would need to add the new vocabulary > class in the classpath to open it in 1.5.3. > > Thanks, Brad > > _______________ > Brad Bebee > CEO, Managing Partner > SYSTAP, LLC > e: be...@sy... > m: 202.642.7961 > f: 571.367.5000 > w: www.systap.com > > Blazegraph™ is our ultra high-performance graph database that supports > both RDF/SPARQL and Tinkerpop/Blueprints APIs. MapGraph™ is our disruptive > new technology to use GPUs to accelerate data-parallel graph analytics. > > 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, LLC. 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 Feb 15, 2016 5:41 PM, "Bryan Thompson" <br...@sy...> wrote: > >> It should be compatible. Can you provide mode details. >> >> Bryan >> >> ---- >> Bryan Thompson >> Chief Scientist & Founder >> Blazegraph >> e: br...@bl... >> w: http://blazegraph.com >> >> Blazegraph products help to solve the Graph Cache Thrash to achieve large >> scale processing for graph and predictive analytics. Blazegraph is the >> creator of the industry’s first GPU-accelerated high-performance database >> for large graphs, has been named as one of the “10 Companies and >> Technologies to Watch in 2016” <http://insideanalysis.com/2016/01/20535/>. >> >> >> Blazegraph Database <https://www.blazegraph.com/> is our ultra-high >> performance graph database that supports both RDF/SPARQL and >> Tinkerpop/Blueprints APIs. Blazegraph GPU >> <https://www.blazegraph.com/product/gpu-accelerated/> andBlazegraph DAS >> <https://www.blazegraph.com/product/gpu-accelerated/>L are disruptive >> new technologies that use GPUs to enable extreme scaling that is thousands >> of times faster and 40 times more affordable than CPU-based solutions. >> >> 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, LLC DBA Blazegraph. 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, Feb 15, 2016 at 5:14 PM, Edgar Rodriguez-Diaz <ed...@sy...> >> wrote: >> >>> I was wondering what’s the level of compatibility for the Journal file >>> between 1.5.3 and 2.0.0. I did a small check and it seems like once a >>> journal is opened with 2.0.0 it’s no longer compatible with 1.5.3. >>> Is this correct? Thanks. >>> >>> Cheers, >>> - Edgar >>> >>> ------------------------------------------------------------------------------ >>> Site24x7 APM Insight: Get Deep Visibility into Application Performance >>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >>> Monitor end-to-end web transactions and take corrective actions now >>> Troubleshoot faster and improve end-user experience. Signup Now! >>> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 >>> _______________________________________________ >>> Bigdata-developers mailing list >>> Big...@li... >>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers >>> >> >> >> >> ------------------------------------------------------------------------------ >> Site24x7 APM Insight: Get Deep Visibility into Application Performance >> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >> Monitor end-to-end web transactions and take corrective actions now >> Troubleshoot faster and improve end-user experience. Signup Now! >> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 >> _______________________________________________ >> Bigdata-developers mailing list >> Big...@li... >> https://lists.sourceforge.net/lists/listinfo/bigdata-developers >> >> |
From: Brad B. <be...@bl...> - 2016-02-16 18:18:13
|
Edgar, 2.0.0 introduced a new versioned vocabulary class that is the default for newly created namespaces. The vocabulary class must be in the classpath. As such, if you create a journal with 1.5.3, you can open it in 2.0.0. If You create a journal in 2.0.0, you would need to add the new vocabulary class in the classpath to open it in 1.5.3. Thanks, Brad _______________ Brad Bebee CEO, Managing Partner SYSTAP, LLC e: be...@sy... m: 202.642.7961 f: 571.367.5000 w: www.systap.com Blazegraph™ is our ultra high-performance graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints APIs. MapGraph™ is our disruptive new technology to use GPUs to accelerate data-parallel graph analytics. 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, LLC. 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 Feb 15, 2016 5:41 PM, "Bryan Thompson" <br...@sy...> wrote: > It should be compatible. Can you provide mode details. > > Bryan > > ---- > Bryan Thompson > Chief Scientist & Founder > Blazegraph > e: br...@bl... > w: http://blazegraph.com > > Blazegraph products help to solve the Graph Cache Thrash to achieve large > scale processing for graph and predictive analytics. Blazegraph is the > creator of the industry’s first GPU-accelerated high-performance database > for large graphs, has been named as one of the “10 Companies and > Technologies to Watch in 2016” <http://insideanalysis.com/2016/01/20535/>. > > > Blazegraph Database <https://www.blazegraph.com/> is our ultra-high > performance graph database that supports both RDF/SPARQL and > Tinkerpop/Blueprints APIs. Blazegraph GPU > <https://www.blazegraph.com/product/gpu-accelerated/> andBlazegraph DAS > <https://www.blazegraph.com/product/gpu-accelerated/>L are disruptive new > technologies that use GPUs to enable extreme scaling that is thousands of > times faster and 40 times more affordable than CPU-based solutions. > > 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, LLC DBA Blazegraph. 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, Feb 15, 2016 at 5:14 PM, Edgar Rodriguez-Diaz <ed...@sy...> > wrote: > >> I was wondering what’s the level of compatibility for the Journal file >> between 1.5.3 and 2.0.0. I did a small check and it seems like once a >> journal is opened with 2.0.0 it’s no longer compatible with 1.5.3. >> Is this correct? Thanks. >> >> Cheers, >> - Edgar >> >> ------------------------------------------------------------------------------ >> Site24x7 APM Insight: Get Deep Visibility into Application Performance >> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >> Monitor end-to-end web transactions and take corrective actions now >> Troubleshoot faster and improve end-user experience. Signup Now! >> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 >> _______________________________________________ >> Bigdata-developers mailing list >> Big...@li... >> https://lists.sourceforge.net/lists/listinfo/bigdata-developers >> > > > > ------------------------------------------------------------------------------ > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 > _______________________________________________ > Bigdata-developers mailing list > Big...@li... > https://lists.sourceforge.net/lists/listinfo/bigdata-developers > > |
From: Joakim S. <joa...@bl...> - 2016-02-16 16:36:06
|
I knew there is a DataLoader class, but I wasn’t aware it was available as a service in NanoSparql server. I will try it immediately Thanks Joakim > On Feb 16, 2016, at 8:09 AM, Jeremy J Carroll <jj...@sy...> wrote: > >> See https://wiki.blazegraph.com/wiki/index.php/REST_API#Bulk_Data_Load <https://wiki.blazegraph.com/wiki/index.php/REST_API#Bulk_Data_Load> > > > That looks very interesting: > > I read: > > "Parsing, insert, and removal on the database are now decoupled from the index writes” > > One behavior we have is that we have small inserts concurrent with other activity (typically but not exclusively read activity). Does the enhanced configurability in 2.0 give us options that may allow us to improve performance of these writes. > > E.g. this week we have many (millions? at least hundreds of thousands) of such small writes (10 - 100 quads) and we also are trying to delete 25 million quads using about 100 delete/insert requests (that I take to be not impacted by this change). I am currently suggesting we should do one or the other at any one time, and not try to mix: but frankly I am guessing, and guessing conservatively. We have to maintain an always-on read performance at the same time. Total store size approx 3billion. > > [Unfortunately this machine is still a 1.5.3 machine, but for future reference I am trying to have better sense of how to organize such activity] > > Jeremy > > > > > >> On Feb 16, 2016, at 7:55 AM, Bryan Thompson <br...@sy... <mailto:br...@sy...>> wrote: >> >> 2.0 includes support for bulk data load with a number of interesting features, including durable queue patterns, folders, etc. See https://wiki.blazegraph.com/wiki/index.php/REST_API#Bulk_Data_Load <https://wiki.blazegraph.com/wiki/index.php/REST_API#Bulk_Data_Load> >> >> ---- >> Bryan Thompson >> Chief Scientist & Founder >> Blazegraph >> e: br...@bl... <mailto:br...@bl...> >> w: http://blazegraph.com <http://blazegraph.com/> >> >> Blazegraph products help to solve the Graph Cache Thrash to achieve large scale processing for graph and predictive analytics. Blazegraph is the creator of the industry’s first GPU-accelerated high-performance database for large graphs, has been named as one of the “10 Companies and Technologies to Watch in 2016” <http://insideanalysis.com/2016/01/20535/>. >> >> Blazegraph Database <https://www.blazegraph.com/> is our ultra-high performance graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints APIs. Blazegraph GPU <https://www.blazegraph.com/product/gpu-accelerated/> andBlazegraph DAS <https://www.blazegraph.com/product/gpu-accelerated/>L are disruptive new technologies that use GPUs to enable extreme scaling that is thousands of times faster and 40 times more affordable than CPU-based solutions. >> >> 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, LLC DBA Blazegraph. 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, Feb 16, 2016 at 10:40 AM, Jeremy J Carroll <jj...@sy... <mailto:jj...@sy...>> wrote: >> >> >>> On Feb 15, 2016, at 10:42 PM, Joakim Soderberg <joa...@bl... <mailto:joa...@bl...>> wrote: >>> >>> Has anyone succeeded to load a folder of .nt files? I can load one by one: >>> >>> LOAD <file:///mydata/dbpedia2015/core/amsterdammuseum_links.nt <>> INTO GRAPH <http://dbpedia2015 <http://dbpedia2015/>> >>> >>> But it doesn’t like a folder name >>> LOAD <file:///mydata/dbpedia2015/core/ <>> INTO GRAPH <http://dbpedia2015 <http://dbpedia2015/>> >> >> >> That is correct. If you look at the spec for LOAD: >> https://www.w3.org/TR/sparql11-update/#load <https://www.w3.org/TR/sparql11-update/#load> >> then it takes an IRI as where you are loading from, and the concept of folder is simply not applicable. >> A few schemes such as file: and ftp: may have such a notion, but the operation you are looking for is local to your machine on the client and you should probably implement it yourself. >> >> In particular, do you want each file loaded into a different graph or the same graph: probably best for you to make up your own mind. >> >> I have had success loading trig files into multiple graphs, using a simple POST to the endpoint. >> >> >> Jeremy >> >> >> ------------------------------------------------------------------------------ >> Site24x7 APM Insight: Get Deep Visibility into Application Performance >> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >> Monitor end-to-end web transactions and take corrective actions now >> Troubleshoot faster and improve end-user experience. Signup Now! >> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 <http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140> >> _______________________________________________ >> Bigdata-developers mailing list >> Big...@li... <mailto:Big...@li...> >> https://lists.sourceforge.net/lists/listinfo/bigdata-developers <https://lists.sourceforge.net/lists/listinfo/bigdata-developers> >> >> > |
From: Bryan T. <br...@sy...> - 2016-02-16 16:17:55
|
Jeremy, The bulk data loader will not help with that scenario. It is desired for high throughput load. It can be used concurrent with query, but it can not really be mixed with concurrent small updates. In general, mixing concurrent small updates and large updates does not work well. Updates against a single graph must be serialized using the unisolated connection. So at some point the small updates will block for the large update. Thanks, Bryan ---- Bryan Thompson Chief Scientist & Founder Blazegraph e: br...@bl... w: http://blazegraph.com Blazegraph products help to solve the Graph Cache Thrash to achieve large scale processing for graph and predictive analytics. Blazegraph is the creator of the industry’s first GPU-accelerated high-performance database for large graphs, has been named as one of the “10 Companies and Technologies to Watch in 2016” <http://insideanalysis.com/2016/01/20535/>. Blazegraph Database <https://www.blazegraph.com/> is our ultra-high performance graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints APIs. Blazegraph GPU <https://www.blazegraph.com/product/gpu-accelerated/> andBlazegraph DAS <https://www.blazegraph.com/product/gpu-accelerated/>L are disruptive new technologies that use GPUs to enable extreme scaling that is thousands of times faster and 40 times more affordable than CPU-based solutions. 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, LLC DBA Blazegraph. 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, Feb 16, 2016 at 11:09 AM, Jeremy J Carroll <jj...@sy...> wrote: > See https://wiki.blazegraph.com/wiki/index.php/REST_API#Bulk_Data_Load > > > > That looks very interesting: > > I read: > > "Parsing, insert, and removal on the database are now decoupled from the > index writes” > > One behavior we have is that we have small inserts concurrent with other > activity (typically but not exclusively read activity). Does the > enhanced configurability in 2.0 give us options that may allow us to > improve performance of these writes. > > E.g. this week we have many (millions? at least hundreds of thousands) of > such small writes (10 - 100 quads) and we also are trying to delete 25 > million quads using about 100 delete/insert requests (that I take to be not > impacted by this change). I am currently suggesting we should do one or the > other at any one time, and not try to mix: but frankly I am guessing, and > guessing conservatively. We have to maintain an always-on read > performance at the same time. Total store size approx 3billion. > > [Unfortunately this machine is still a 1.5.3 machine, but for future > reference I am trying to have better sense of how to organize such activity] > > Jeremy > > > > > > On Feb 16, 2016, at 7:55 AM, Bryan Thompson <br...@sy...> wrote: > > 2.0 includes support for bulk data load with a number of interesting > features, including durable queue patterns, folders, etc. See > https://wiki.blazegraph.com/wiki/index.php/REST_API#Bulk_Data_Load > > ---- > Bryan Thompson > Chief Scientist & Founder > Blazegraph > e: br...@bl... > w: http://blazegraph.com > > Blazegraph products help to solve the Graph Cache Thrash to achieve large > scale processing for graph and predictive analytics. Blazegraph is the > creator of the industry’s first GPU-accelerated high-performance database > for large graphs, has been named as one of the “10 Companies and > Technologies to Watch in 2016” <http://insideanalysis.com/2016/01/20535/>. > > > Blazegraph Database <https://www.blazegraph.com/> is our ultra-high > performance graph database that supports both RDF/SPARQL and > Tinkerpop/Blueprints APIs. Blazegraph GPU > <https://www.blazegraph.com/product/gpu-accelerated/> andBlazegraph DAS > <https://www.blazegraph.com/product/gpu-accelerated/>L are disruptive new > technologies that use GPUs to enable extreme scaling that is thousands of > times faster and 40 times more affordable than CPU-based solutions. > > 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, LLC DBA Blazegraph. 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, Feb 16, 2016 at 10:40 AM, Jeremy J Carroll <jj...@sy...> wrote: > >> >> >> On Feb 15, 2016, at 10:42 PM, Joakim Soderberg < >> joa...@bl...> wrote: >> >> Has anyone succeeded to load a folder of .nt files? I can load one by one: >> >> LOAD <file:///mydata/dbpedia2015/core/amsterdammuseum_links.nt> INTO >> GRAPH <http://dbpedia2015> >> >> But it doesn’t like a folder name >> LOAD <file:///mydata/dbpedia2015/core/> INTO GRAPH <http://dbpedia2015> >> >> >> >> That is correct. If you look at the spec for LOAD: >> https://www.w3.org/TR/sparql11-update/#load >> then it takes an IRI as where you are loading from, and the concept of >> folder is simply not applicable. >> A few schemes such as file: and ftp: may have such a notion, but the >> operation you are looking for is local to your machine on the client and >> you should probably implement it yourself. >> >> In particular, do you want each file loaded into a different graph or the >> same graph: probably best for you to make up your own mind. >> >> I have had success loading trig files into multiple graphs, using a >> simple POST to the endpoint. >> >> >> Jeremy >> >> >> >> ------------------------------------------------------------------------------ >> Site24x7 APM Insight: Get Deep Visibility into Application Performance >> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >> Monitor end-to-end web transactions and take corrective actions now >> Troubleshoot faster and improve end-user experience. Signup Now! >> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 >> _______________________________________________ >> Bigdata-developers mailing list >> Big...@li... >> https://lists.sourceforge.net/lists/listinfo/bigdata-developers >> >> > > |
From: Jeremy J C. <jj...@sy...> - 2016-02-16 16:10:05
|
> See https://wiki.blazegraph.com/wiki/index.php/REST_API#Bulk_Data_Load <https://wiki.blazegraph.com/wiki/index.php/REST_API#Bulk_Data_Load> That looks very interesting: I read: "Parsing, insert, and removal on the database are now decoupled from the index writes” One behavior we have is that we have small inserts concurrent with other activity (typically but not exclusively read activity). Does the enhanced configurability in 2.0 give us options that may allow us to improve performance of these writes. E.g. this week we have many (millions? at least hundreds of thousands) of such small writes (10 - 100 quads) and we also are trying to delete 25 million quads using about 100 delete/insert requests (that I take to be not impacted by this change). I am currently suggesting we should do one or the other at any one time, and not try to mix: but frankly I am guessing, and guessing conservatively. We have to maintain an always-on read performance at the same time. Total store size approx 3billion. [Unfortunately this machine is still a 1.5.3 machine, but for future reference I am trying to have better sense of how to organize such activity] Jeremy > On Feb 16, 2016, at 7:55 AM, Bryan Thompson <br...@sy...> wrote: > > 2.0 includes support for bulk data load with a number of interesting features, including durable queue patterns, folders, etc. See https://wiki.blazegraph.com/wiki/index.php/REST_API#Bulk_Data_Load <https://wiki.blazegraph.com/wiki/index.php/REST_API#Bulk_Data_Load> > > ---- > Bryan Thompson > Chief Scientist & Founder > Blazegraph > e: br...@bl... <mailto:br...@bl...> > w: http://blazegraph.com <http://blazegraph.com/> > > Blazegraph products help to solve the Graph Cache Thrash to achieve large scale processing for graph and predictive analytics. Blazegraph is the creator of the industry’s first GPU-accelerated high-performance database for large graphs, has been named as one of the “10 Companies and Technologies to Watch in 2016” <http://insideanalysis.com/2016/01/20535/>. > > Blazegraph Database <https://www.blazegraph.com/> is our ultra-high performance graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints APIs. Blazegraph GPU <https://www.blazegraph.com/product/gpu-accelerated/> andBlazegraph DAS <https://www.blazegraph.com/product/gpu-accelerated/>L are disruptive new technologies that use GPUs to enable extreme scaling that is thousands of times faster and 40 times more affordable than CPU-based solutions. > > 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, LLC DBA Blazegraph. 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, Feb 16, 2016 at 10:40 AM, Jeremy J Carroll <jj...@sy... <mailto:jj...@sy...>> wrote: > > >> On Feb 15, 2016, at 10:42 PM, Joakim Soderberg <joa...@bl... <mailto:joa...@bl...>> wrote: >> >> Has anyone succeeded to load a folder of .nt files? I can load one by one: >> >> LOAD <file:///mydata/dbpedia2015/core/amsterdammuseum_links.nt <>> INTO GRAPH <http://dbpedia2015 <http://dbpedia2015/>> >> >> But it doesn’t like a folder name >> LOAD <file:///mydata/dbpedia2015/core/ <>> INTO GRAPH <http://dbpedia2015 <http://dbpedia2015/>> > > > That is correct. If you look at the spec for LOAD: > https://www.w3.org/TR/sparql11-update/#load <https://www.w3.org/TR/sparql11-update/#load> > then it takes an IRI as where you are loading from, and the concept of folder is simply not applicable. > A few schemes such as file: and ftp: may have such a notion, but the operation you are looking for is local to your machine on the client and you should probably implement it yourself. > > In particular, do you want each file loaded into a different graph or the same graph: probably best for you to make up your own mind. > > I have had success loading trig files into multiple graphs, using a simple POST to the endpoint. > > > Jeremy > > > ------------------------------------------------------------------------------ > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 <http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140> > _______________________________________________ > Bigdata-developers mailing list > Big...@li... <mailto:Big...@li...> > https://lists.sourceforge.net/lists/listinfo/bigdata-developers <https://lists.sourceforge.net/lists/listinfo/bigdata-developers> > > |
From: Bryan T. <br...@sy...> - 2016-02-16 15:55:17
|
2.0 includes support for bulk data load with a number of interesting features, including durable queue patterns, folders, etc. See https://wiki.blazegraph.com/wiki/index.php/REST_API#Bulk_Data_Load ---- Bryan Thompson Chief Scientist & Founder Blazegraph e: br...@bl... w: http://blazegraph.com Blazegraph products help to solve the Graph Cache Thrash to achieve large scale processing for graph and predictive analytics. Blazegraph is the creator of the industry’s first GPU-accelerated high-performance database for large graphs, has been named as one of the “10 Companies and Technologies to Watch in 2016” <http://insideanalysis.com/2016/01/20535/>. Blazegraph Database <https://www.blazegraph.com/> is our ultra-high performance graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints APIs. Blazegraph GPU <https://www.blazegraph.com/product/gpu-accelerated/> andBlazegraph DAS <https://www.blazegraph.com/product/gpu-accelerated/>L are disruptive new technologies that use GPUs to enable extreme scaling that is thousands of times faster and 40 times more affordable than CPU-based solutions. 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, LLC DBA Blazegraph. 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, Feb 16, 2016 at 10:40 AM, Jeremy J Carroll <jj...@sy...> wrote: > > > On Feb 15, 2016, at 10:42 PM, Joakim Soderberg < > joa...@bl...> wrote: > > Has anyone succeeded to load a folder of .nt files? I can load one by one: > > LOAD <file:///mydata/dbpedia2015/core/amsterdammuseum_links.nt> INTO > GRAPH <http://dbpedia2015> > > But it doesn’t like a folder name > LOAD <file:///mydata/dbpedia2015/core/> INTO GRAPH <http://dbpedia2015> > > > > That is correct. If you look at the spec for LOAD: > https://www.w3.org/TR/sparql11-update/#load > then it takes an IRI as where you are loading from, and the concept of > folder is simply not applicable. > A few schemes such as file: and ftp: may have such a notion, but the > operation you are looking for is local to your machine on the client and > you should probably implement it yourself. > > In particular, do you want each file loaded into a different graph or the > same graph: probably best for you to make up your own mind. > > I have had success loading trig files into multiple graphs, using a > simple POST to the endpoint. > > > Jeremy > > > > ------------------------------------------------------------------------------ > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 > _______________________________________________ > Bigdata-developers mailing list > Big...@li... > https://lists.sourceforge.net/lists/listinfo/bigdata-developers > > |
From: Jeremy J C. <jj...@sy...> - 2016-02-16 15:40:11
|
> On Feb 15, 2016, at 10:42 PM, Joakim Soderberg <joa...@bl...> wrote: > > Has anyone succeeded to load a folder of .nt files? I can load one by one: > > LOAD <file:///mydata/dbpedia2015/core/amsterdammuseum_links.nt <file:///mydata/dbpedia2015/core/amsterdammuseum_links.nt>> INTO GRAPH <http://dbpedia2015 <http://dbpedia2015/>> > > But it doesn’t like a folder name > LOAD <file:///mydata/dbpedia2015/core/ <file:///mydata/dbpedia2015/core/>> INTO GRAPH <http://dbpedia2015 <http://dbpedia2015/>> That is correct. If you look at the spec for LOAD: https://www.w3.org/TR/sparql11-update/#load <https://www.w3.org/TR/sparql11-update/#load> then it takes an IRI as where you are loading from, and the concept of folder is simply not applicable. A few schemes such as file: and ftp: may have such a notion, but the operation you are looking for is local to your machine on the client and you should probably implement it yourself. In particular, do you want each file loaded into a different graph or the same graph: probably best for you to make up your own mind. I have had success loading trig files into multiple graphs, using a simple POST to the endpoint. Jeremy |
From: Joakim S. <joa...@bl...> - 2016-02-16 06:42:47
|
Has anyone succeeded to load a folder of .nt files? I can load one by one: LOAD <file:///mydata/dbpedia2015/core/amsterdammuseum_links.nt> INTO GRAPH <http://dbpedia2015> But it doesn’t like a folder name LOAD <file:///mydata/dbpedia2015/core/> INTO GRAPH <http://dbpedia2015> |
From: Joakim S. <joa...@bl...> - 2016-02-16 06:13:47
|
Thanks, now it works just fine. > On Feb 15, 2016, at 3:34 PM, Bryan Thompson <br...@sy...> wrote: > > Blazegraph is configured using log4j, not java util logging. Do something like this: > > -Dlog4j.configuration=/Users/bryan/git/bigdata-gpu/src/main/resources/log4j.properties > > > ---- > Bryan Thompson > Chief Scientist & Founder > Blazegraph > e: br...@bl... <mailto:br...@bl...> > w: http://blazegraph.com <http://blazegraph.com/> > > Blazegraph products help to solve the Graph Cache Thrash to achieve large scale processing for graph and predictive analytics. Blazegraph is the creator of the industry’s first GPU-accelerated high-performance database for large graphs, has been named as one of the “10 Companies and Technologies to Watch in 2016” <http://insideanalysis.com/2016/01/20535/>. > > Blazegraph Database <https://www.blazegraph.com/> is our ultra-high performance graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints APIs. Blazegraph GPU <https://www.blazegraph.com/product/gpu-accelerated/> andBlazegraph DAS <https://www.blazegraph.com/product/gpu-accelerated/>L are disruptive new technologies that use GPUs to enable extreme scaling that is thousands of times faster and 40 times more affordable than CPU-based solutions. > > 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, LLC DBA Blazegraph. 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, Feb 15, 2016 at 5:18 PM, Joakim Soderberg <joa...@bl... <mailto:joa...@bl...>> wrote: > Hello, > > I am trying to set the logger from the command prompt like this without success: > > java -server -Xmx4g -Dbigdata.propertyFile=RWStore.properties -Djava.util.logging.config.file=log4j.properties -jar blazegraph.jar > > Does anyone know how configure the log util when running from the command line? > > > ------------------------------------------------------------------------------ > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 <http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140> > _______________________________________________ > Bigdata-developers mailing list > Big...@li... <mailto:Big...@li...> > https://lists.sourceforge.net/lists/listinfo/bigdata-developers <https://lists.sourceforge.net/lists/listinfo/bigdata-developers> > |
From: Bryan T. <br...@sy...> - 2016-02-15 23:59:11
|
Blazegraph is configured using log4j, not java util logging. Do something like this: -Dlog4j.configuration=/Users/bryan/git/bigdata-gpu/src/main/resources/log4j.properties ---- Bryan Thompson Chief Scientist & Founder Blazegraph e: br...@bl... w: http://blazegraph.com Blazegraph products help to solve the Graph Cache Thrash to achieve large scale processing for graph and predictive analytics. Blazegraph is the creator of the industry’s first GPU-accelerated high-performance database for large graphs, has been named as one of the “10 Companies and Technologies to Watch in 2016” <http://insideanalysis.com/2016/01/20535/>. Blazegraph Database <https://www.blazegraph.com/> is our ultra-high performance graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints APIs. Blazegraph GPU <https://www.blazegraph.com/product/gpu-accelerated/> andBlazegraph DAS <https://www.blazegraph.com/product/gpu-accelerated/>L are disruptive new technologies that use GPUs to enable extreme scaling that is thousands of times faster and 40 times more affordable than CPU-based solutions. 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, LLC DBA Blazegraph. 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, Feb 15, 2016 at 5:18 PM, Joakim Soderberg < joa...@bl...> wrote: > Hello, > > I am trying to set the logger from the command prompt like this without > success: > > java -server -Xmx4g -Dbigdata.propertyFile=RWStore.properties > -Djava.util.logging.config.file=log4j.properties -jar blazegraph.jar > > Does anyone know how configure the log util when running from the command > line? > > > > ------------------------------------------------------------------------------ > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 > _______________________________________________ > Bigdata-developers mailing list > Big...@li... > https://lists.sourceforge.net/lists/listinfo/bigdata-developers > |
From: Joakim S. <joa...@bl...> - 2016-02-15 22:47:19
|
Hello, I am trying to set the logger from the command prompt like this without success: java -server -Xmx4g -Dbigdata.propertyFile=RWStore.properties -Djava.util.logging.config.file=log4j.properties -jar blazegraph.jar Does anyone know how configure the log util when running from the command line? |
From: Bryan T. <br...@sy...> - 2016-02-15 22:41:08
|
It should be compatible. Can you provide mode details. Bryan ---- Bryan Thompson Chief Scientist & Founder Blazegraph e: br...@bl... w: http://blazegraph.com Blazegraph products help to solve the Graph Cache Thrash to achieve large scale processing for graph and predictive analytics. Blazegraph is the creator of the industry’s first GPU-accelerated high-performance database for large graphs, has been named as one of the “10 Companies and Technologies to Watch in 2016” <http://insideanalysis.com/2016/01/20535/>. Blazegraph Database <https://www.blazegraph.com/> is our ultra-high performance graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints APIs. Blazegraph GPU <https://www.blazegraph.com/product/gpu-accelerated/> andBlazegraph DAS <https://www.blazegraph.com/product/gpu-accelerated/>L are disruptive new technologies that use GPUs to enable extreme scaling that is thousands of times faster and 40 times more affordable than CPU-based solutions. 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, LLC DBA Blazegraph. 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, Feb 15, 2016 at 5:14 PM, Edgar Rodriguez-Diaz <ed...@sy...> wrote: > I was wondering what’s the level of compatibility for the Journal file > between 1.5.3 and 2.0.0. I did a small check and it seems like once a > journal is opened with 2.0.0 it’s no longer compatible with 1.5.3. > Is this correct? Thanks. > > Cheers, > - Edgar > > ------------------------------------------------------------------------------ > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 > _______________________________________________ > Bigdata-developers mailing list > Big...@li... > https://lists.sourceforge.net/lists/listinfo/bigdata-developers > |
From: Edgar Rodriguez-D. <ed...@sy...> - 2016-02-15 22:37:46
|
I was wondering what’s the level of compatibility for the Journal file between 1.5.3 and 2.0.0. I did a small check and it seems like once a journal is opened with 2.0.0 it’s no longer compatible with 1.5.3. Is this correct? Thanks. Cheers, - Edgar |
From: Bryan T. <br...@sy...> - 2016-02-11 17:49:40
|
Machine. The RAM is intended to provide a buffer for the disk. SSD fast. RAM faster. This reduces the IO latency associated with even SSD and allows continued scaling. Without this performance falls off more quickly. Bryan ---- Bryan Thompson Chief Scientist & Founder Blazegraph 4501 Tower Road Greensboro, NC 27410 br...@bl... http://blazegraph.com http://blog.blazegraph.com Blazegraph™ <http://www.blazegraph.com/> is our ultra high-performance graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints APIs. Blazegraph is now available with GPU acceleration using our disruptive technology to accelerate data-parallel graph analytics and graph query. 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, LLC DBA Blazegraph. 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 Thu, Feb 11, 2016 at 12:39 PM, Jim Balhoff <ba...@gm...> wrote: > I was looking through some of the newer content on the Blazegraph wiki and > had a question about the “RAM Sizing Guidance” here: > https://wiki.blazegraph.com/wiki/index.php/Hardware_Configuration#RAM_Sizing_Guidance > > Is the specified RAM a machine amount or JVM heap size? > > Thanks, > Jim > > > > ------------------------------------------------------------------------------ > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 > _______________________________________________ > Bigdata-developers mailing list > Big...@li... > https://lists.sourceforge.net/lists/listinfo/bigdata-developers > |
From: Jim B. <ba...@gm...> - 2016-02-11 17:39:26
|
I was looking through some of the newer content on the Blazegraph wiki and had a question about the “RAM Sizing Guidance” here: https://wiki.blazegraph.com/wiki/index.php/Hardware_Configuration#RAM_Sizing_Guidance Is the specified RAM a machine amount or JVM heap size? Thanks, Jim |
From: Brad B. <be...@bl...> - 2016-02-08 18:23:38
|
Mikel, It is -Djetty.port=8080. Thanks, --Brad On Mon, Feb 8, 2016 at 12:52 PM, Mikel Egaña Aranguren < mik...@gm...> wrote: > Hi; > > I need to use the NanoSparqlServer through the command line for a course > on Linked Data I'm teaching. I normally invoke it like this: > > java -server -Xmx4g -jar bigdata-bundled.jar > > > What is the argument for defining another port? (Not 9999) > > Thanks > > > -- > Mikel Egaña Aranguren, Ph.D. > > http://mikeleganaaranguren.com > > > > > ------------------------------------------------------------------------------ > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 > _______________________________________________ > Bigdata-developers mailing list > Big...@li... > https://lists.sourceforge.net/lists/listinfo/bigdata-developers > > -- _______________ Brad Bebee CEO Blazegraph e: be...@bl... m: 202.642.7961 w: www.blazegraph.com Blazegraph products help to solve the Graph Cache Thrash to achieve large scale processing for graph and predictive analytics. Blazegraph is the creator of the industry’s first GPU-accelerated high-performance database for large graphs, has been named as one of the “10 Companies and Technologies to Watch in 2016” <http://insideanalysis.com/2016/01/20535/>. Blazegraph Database <https://www.blazegraph.com/> is our ultra-high performance graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints APIs. Blazegraph GPU <https://www.blazegraph.com/product/gpu-accelerated/> andBlazegraph DAS <https://www.blazegraph.com/product/gpu-accelerated/>L are disruptive new technologies that use GPUs to enable extreme scaling that is thousands of times faster and 40 times more affordable than CPU-based solutions. 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, LLC DBA Blazegraph. 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. |
From: Mikel E. A. <mik...@gm...> - 2016-02-08 17:59:50
|
Yes, that worked, thanks 2016-02-08 18:56 GMT+01:00 Brad Bebee <be...@bl...>: > Mikel, > > It is -Djetty.port=8080. > > Thanks, --Brad > > On Mon, Feb 8, 2016 at 12:52 PM, Mikel Egaña Aranguren < > mik...@gm...> wrote: > >> Hi; >> >> I need to use the NanoSparqlServer through the command line for a course >> on Linked Data I'm teaching. I normally invoke it like this: >> >> java -server -Xmx4g -jar bigdata-bundled.jar >> >> >> What is the argument for defining another port? (Not 9999) >> >> Thanks >> >> >> -- >> Mikel Egaña Aranguren, Ph.D. >> >> http://mikeleganaaranguren.com >> >> >> >> >> ------------------------------------------------------------------------------ >> Site24x7 APM Insight: Get Deep Visibility into Application Performance >> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >> Monitor end-to-end web transactions and take corrective actions now >> Troubleshoot faster and improve end-user experience. Signup Now! >> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 >> _______________________________________________ >> Bigdata-developers mailing list >> Big...@li... >> https://lists.sourceforge.net/lists/listinfo/bigdata-developers >> >> > > > -- > _______________ > Brad Bebee > CEO > Blazegraph > e: be...@bl... > m: 202.642.7961 > w: www.blazegraph.com > > Blazegraph products help to solve the Graph Cache Thrash to achieve large > scale processing for graph and predictive analytics. Blazegraph is the > creator of the industry’s first GPU-accelerated high-performance database > for large graphs, has been named as one of the “10 Companies and > Technologies to Watch in 2016” <http://insideanalysis.com/2016/01/20535/>. > > > Blazegraph Database <https://www.blazegraph.com/> is our ultra-high > performance graph database that supports both RDF/SPARQL and > Tinkerpop/Blueprints APIs. Blazegraph GPU > <https://www.blazegraph.com/product/gpu-accelerated/> andBlazegraph DAS > <https://www.blazegraph.com/product/gpu-accelerated/>L are disruptive new > technologies that use GPUs to enable extreme scaling that is thousands of > times faster and 40 times more affordable than CPU-based solutions. > > 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, LLC DBA Blazegraph. 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. > -- Mikel Egaña Aranguren, Ph.D. http://mikeleganaaranguren.com |
From: Mikel E. A. <mik...@gm...> - 2016-02-08 17:53:03
|
Hi; I need to use the NanoSparqlServer through the command line for a course on Linked Data I'm teaching. I normally invoke it like this: java -server -Xmx4g -jar bigdata-bundled.jar What is the argument for defining another port? (Not 9999) Thanks -- Mikel Egaña Aranguren, Ph.D. http://mikeleganaaranguren.com |
From: Jeremy C. <jj...@gm...> - 2016-02-01 19:57:54
|
My experience is that blazegraph checks for disk integrity much more than most software, and after an error of this sort from blazegraph, sooner or later other things stop working too, because the h/w is defective. Jeremy > On Feb 1, 2016, at 9:48 AM, Matthew Roy <mr...@ca...> wrote: > > I saw this error this morning as well after testing against the 2.0.0 release code. Was running code from around 1.5.0 previously. > > Caused by: com.bigdata.util.ChecksumError: offset=18124800,nbytes=4044,expected=0,actual=1696870497 > at com.bigdata.io.writecache.WriteCacheService._readFromLocalDiskIntoNewHeapByteBuffer(WriteCacheService.java:3761) ~[bigdata-core-2.0.0.jar:na] > at com.bigdata.io.writecache.WriteCacheService._getRecord(WriteCacheService.java:3576) ~[bigdata-core-2.0.0.jar:na] > at com.bigdata.io.writecache.WriteCacheService.access$2500(WriteCacheService.java:200) ~[bigdata-core-2.0.0.jar:na] > at com.bigdata.io.writecache.WriteCacheService$1.compute(WriteCacheService.java:3413) ~[bigdata-core-2.0.0.jar:na] > at com.bigdata.io.writecache.WriteCacheService$1.compute(WriteCacheService.java:3397) ~[bigdata-core-2.0.0.jar:na] > at com.bigdata.util.concurrent.Memoizer$1.call(Memoizer.java:77) ~[bigdata-core-2.0.0.jar:na] > at java.util.concurrent.FutureTask.run(FutureTask.java:266) [na:1.8.0_60] > at com.bigdata.util.concurrent.Memoizer.compute(Memoizer.java:92) ~[bigdata-core-2.0.0.jar:na] > at com.bigdata.io.writecache.WriteCacheService.loadRecord(WriteCacheService.java:3518) ~[bigdata-core-2.0.0.jar:na] > at com.bigdata.io.writecache.WriteCacheService.read(WriteCacheService.java:3237) ~[bigdata-core-2.0.0.jar:na] > at com.bigdata.rwstore.RWStore.getData(RWStore.java:2052) ~[bigdata-core-2.0.0.jar:na] > ... 24 common frames omitted > and after reopening the journal file get: > > java.lang.Error: Two allocators at same address > at com.bigdata.rwstore.FixedAllocator.compareTo(FixedAllocator.java:102) > at java.util.ComparableTimSort.countRunAndMakeAscending(ComparableTimSort.java:295) > at java.util.ComparableTimSort.sort(ComparableTimSort.java:157) > at java.util.ComparableTimSort.sort(ComparableTimSort.java:146) > at java.util.Arrays.sort(Arrays.java:472) > at java.util.Collections.sort(Collections.java:155) > at com.bigdata.rwstore.RWStore.readAllocationBlocks(RWStore.java:1682) > at com.bigdata.rwstore.RWStore.initfromRootBlock(RWStore.java:1557) > at com.bigdata.rwstore.RWStore.<init>(RWStore.java:969) > at com.bigdata.journal.RWStrategy.<init>(RWStrategy.java:137) > Can't tell exactly what was going on query/update wise when the error occurred. > Will let you know if I can reproduce the error again. > Matt > > ------ Original Message ------ > From: "Bryan Thompson" <br...@sy... <mailto:br...@sy...>> > To: "Jeremy Carroll" <jj...@gm... <mailto:jj...@gm...>>; "Martyn Cutcher" <ma...@sy... <mailto:ma...@sy...>> > Cc: "Big...@li..." <Big...@li... <mailto:Big...@li...>> > Sent: 2/1/2016 10:43:04 AM > Subject: Re: [Bigdata-developers] " No WriteCache debug info" > >> Typically this indicates an actual disk error. It is attempting to read data from the backing file. The checksum that was stored is not matched by the data. The only time I have see this was when there was actually a bad disk. >> >> Caused by: com.bigdata.util.ChecksumError: offset=404849739776,nbytes=1156,expected=-402931822,actual=1830389633 >> at com.bigdata.io.writecache.WriteCacheService._readFromLocalDiskIntoNewHeapByteBuffer(WriteCacheService.java:3711) >> at com.bigdata.io.writecache.WriteCacheService._getRecord(WriteCacheService.java:3526) >> at com.bigdata.io.writecache.WriteCacheService.access$2500(WriteCacheService.java:200) >> at com.bigdata.io.writecache.WriteCacheService$1.compute(WriteCacheService.java:3363) >> at com.bigdata.io.writecache.WriteCacheService$1.compute(WriteCacheService.java:3347) >> >> Bryan >> >> ---- >> Bryan Thompson >> Chief Scientist & Founder >> SYSTAP, LLC >> 4501 Tower Road >> Greensboro, NC 27410 >> br...@sy... <mailto:br...@sy...> >> http://blazegraph.com/ <http://blazegraph.com/> >> http://blog.blazegraph.com <http://blog.blazegraph.com/> >> >> Blazegraph™ <http://www.blazegraph.com/> is our ultra high-performance graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints APIs. Blazegraph is now available with GPU acceleration using our disruptive technology to accelerate data-parallel graph analytics and graph query. >> 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, Feb 1, 2016 at 10:34 AM, Jeremy Carroll <jj...@gm... <mailto:jj...@gm...>> wrote: >> >> Also on 1.5.3, with %codes as a solution set with half million URIs binding ?x >> >> What does the error message mean? >> >> Jeremy >> >> >> Feb 01,2016 07:27:13 PST - ERROR: 73992665 qtp1401132667-16779 com.bigdata.rdf.sail.webapp.BigdataRDFServlet.launderThrowable(BigdataRDFServlet.java:214): cause=java.util.concurrent.ExecutionException: java.util.concurrent.ExecutionException: org.openrdf.query.QueryEvaluationException: java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.Exception: task=ChunkTask{query=57386638-1f48-4826-966a-84a6b36b5427,bopId=1,partitionId=-1,sinkId=2,altSinkId=null}, cause=java.util.concurrent.ExecutionException: java.lang.RuntimeException: addr=-403683228 : cause=java.lang.IllegalStateException: Error reading from WriteCache addr: 404849739776 length: 1152, writeCacheDebug: No WriteCache debug info, query=SPARQL-QUERY: queryStr=select (count(?x) as $cnt)^M >> { INCLUDE %codes^M >> } >> java.util.concurrent.ExecutionException: java.util.concurrent.ExecutionException: org.openrdf.query.QueryEvaluationException: java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.Exception: task=ChunkTask{query=57386638-1f48-4826-966a-84a6b36b5427,bopId=1,partitionId=-1,sinkId=2,altSinkId=null}, cause=java.util.concurrent.ExecutionException: java.lang.RuntimeException: addr=-403683228 : cause=java.lang.IllegalStateException: Error reading from WriteCache addr: 404849739776 length: 1152, writeCacheDebug: No WriteCache debug info >> at java.util.concurrent.FutureTask.report(FutureTask.java:122) >> at java.util.concurrent.FutureTask.get(FutureTask.java:192) >> at com.bigdata.rdf.sail.webapp.BigdataServlet.submitApiTask(BigdataServlet.java:281) >> at com.bigdata.rdf.sail.webapp.QueryServlet.doSparqlQuery(QueryServlet.java:636) >> at com.bigdata.rdf.sail.webapp.QueryServlet.doPost(QueryServlet.java:263) >> at com.bigdata.rdf.sail.webapp.RESTServlet.doPost(RESTServlet.java:248) >> at com.bigdata.rdf.sail.webapp.MultiTenancyServlet.doPost(MultiTenancyServlet.java:138) >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) >> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) >> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:769) >> at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585) >> at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) >> at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:577) >> at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223) >> at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1125) >> at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515) >> at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185) >> at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1059) >> at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141) >> at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:215) >> at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:110) >> at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97) >> at org.eclipse.jetty.server.Server.handle(Server.java:497) >> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:311) >> at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:248) >> at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:540) >> at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:610) >> at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:539) >> at java.lang.Thread.run(Thread.java:745) >> Caused by: java.util.concurrent.ExecutionException: org.openrdf.query.QueryEvaluationException: java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.Exception: task=ChunkTask{query=57386638-1f48-4826-966a-84a6b36b5427,bopId=1,partitionId=-1,sinkId=2,altSinkId=null}, cause=java.util.concurrent.ExecutionException: java.lang.RuntimeException: addr=-403683228 : cause=java.lang.IllegalStateException: Error reading from WriteCache addr: 404849739776 length: 1152, writeCacheDebug: No WriteCache debug info >> at java.util.concurrent.FutureTask.report(FutureTask.java:122) >> at java.util.concurrent.FutureTask.get(FutureTask.java:192) >> at com.bigdata.rdf.sail.webapp.QueryServlet$SparqlQueryTask.call(QueryServlet.java:834) >> at com.bigdata.rdf.sail.webapp.QueryServlet$SparqlQueryTask.call(QueryServlet.java:653) >> at com.bigdata.rdf.task.ApiTaskForIndexManager.call(ApiTaskForIndexManager.java:68) >> at java.util.concurrent.FutureTask.run(FutureTask.java:266) >> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) >> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) >> ... 1 more >> Caused by: org.openrdf.query.QueryEvaluationException: java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.Exception: task=ChunkTask{query=57386638-1f48-4826-966a-84a6b36b5427,bopId=1,partitionId=-1,sinkId=2,altSinkId=null}, cause=java.util.concurrent.ExecutionException: java.lang.RuntimeException: addr=-403683228 : cause=java.lang.IllegalStateException: Error reading from WriteCache addr: 404849739776 length: 1152, writeCacheDebug: No WriteCache debug info >> at com.bigdata.rdf.sail.Bigdata2Sesame2BindingSetIterator.hasNext(Bigdata2Sesame2BindingSetIterator.java:188) >> at info.aduna.iteration.IterationWrapper.hasNext(IterationWrapper.java:68) >> at org.openrdf.query.QueryResults.report(QueryResults.java:155) >> at org.openrdf.repository.sail.SailTupleQuery.evaluate(SailTupleQuery.java:76) >> at com.bigdata.rdf.sail.webapp.BigdataRDFContext$TupleQueryTask.doQuery(BigdataRDFContext.java:1710) >> at com.bigdata.rdf.sail.webapp.BigdataRDFContext$AbstractQueryTask.innerCall(BigdataRDFContext.java:1567) >> at com.bigdata.rdf.sail.webapp.BigdataRDFContext$AbstractQueryTask.call(BigdataRDFContext.java:1532) >> at com.bigdata.rdf.sail.webapp.BigdataRDFContext$AbstractQueryTask.call(BigdataRDFContext.java:704) >> ... 4 more >> Caused by: java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.Exception: task=ChunkTask{query=57386638-1f48-4826-966a-84a6b36b5427,bopId=1,partitionId=-1,sinkId=2,altSinkId=null}, cause=java.util.concurrent.ExecutionException: java.lang.RuntimeException: addr=-403683228 : cause=java.lang.IllegalStateException: Error reading from WriteCache addr: 404849739776 length: 1152, writeCacheDebug: No WriteCache debug info >> at com.bigdata.relation.accesspath.BlockingBuffer$BlockingIterator.checkFuture(BlockingBuffer.java:1523) >> at com.bigdata.relation.accesspath.BlockingBuffer$BlockingIterator._hasNext(BlockingBuffer.java:1710) >> at com.bigdata.relation.accesspath.BlockingBuffer$BlockingIterator.hasNext(BlockingBuffer.java:1563) >> at com.bigdata.striterator.AbstractChunkedResolverator._hasNext(AbstractChunkedResolverator.java:365) >> at com.bigdata.striterator.AbstractChunkedResolverator.hasNext(AbstractChunkedResolverator.java:341) >> at com.bigdata.rdf.sail.Bigdata2Sesame2BindingSetIterator.hasNext(Bigdata2Sesame2BindingSetIterator.java:134) >> ... 11 more >> Caused by: java.util.concurrent.ExecutionException: java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.Exception: task=ChunkTask{query=57386638-1f48-4826-966a-84a6b36b5427,bopId=1,partitionId=-1,sinkId=2,altSinkId=null}, cause=java.util.concurrent.ExecutionException: java.lang.RuntimeException: addr=-403683228 : cause=java.lang.IllegalStateException: Error reading from WriteCache addr: 404849739776 length: 1152, writeCacheDebug: No WriteCache debug info >> at java.util.concurrent.FutureTask.report(FutureTask.java:122) >> at java.util.concurrent.FutureTask.get(FutureTask.java:192) >> at com.bigdata.relation.accesspath.BlockingBuffer$BlockingIterator.checkFuture(BlockingBuffer.java:1454) >> ... 16 more >> Caused by: java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.Exception: task=ChunkTask{query=57386638-1f48-4826-966a-84a6b36b5427,bopId=1,partitionId=-1,sinkId=2,altSinkId=null}, cause=java.util.concurrent.ExecutionException: java.lang.RuntimeException: addr=-403683228 : cause=java.lang.IllegalStateException: Error reading from WriteCache addr: 404849739776 length: 1152, writeCacheDebug: No WriteCache debug info >> at com.bigdata.rdf.sail.RunningQueryCloseableIterator.checkFuture(RunningQueryCloseableIterator.java:59) >> at com.bigdata.rdf.sail.RunningQueryCloseableIterator.close(RunningQueryCloseableIterator.java:73) >> at com.bigdata.rdf.sail.RunningQueryCloseableIterator.hasNext(RunningQueryCloseableIterator.java:82) >> at com.bigdata.striterator.ChunkedWrappedIterator.hasNext(ChunkedWrappedIterator.java:197) >> at com.bigdata.striterator.AbstractChunkedResolverator$ChunkConsumerTask.call(AbstractChunkedResolverator.java:222) >> at com.bigdata.striterator.AbstractChunkedResolverator$ChunkConsumerTask.call(AbstractChunkedResolverator.java:197) >> ... 4 more >> Caused by: java.util.concurrent.ExecutionException: java.lang.Exception: task=ChunkTask{query=57386638-1f48-4826-966a-84a6b36b5427,bopId=1,partitionId=-1,sinkId=2,altSinkId=null}, cause=java.util.concurrent.ExecutionException: java.lang.RuntimeException: addr=-403683228 : cause=java.lang.IllegalStateException: Error reading from WriteCache addr: 404849739776 length: 1152, writeCacheDebug: No WriteCache debug info >> at com.bigdata.util.concurrent.Haltable.get(Haltable.java:273) >> at com.bigdata.bop.engine.AbstractRunningQuery.get(AbstractRunningQuery.java:1514) >> at com.bigdata.bop.engine.AbstractRunningQuery.get(AbstractRunningQuery.java:104) >> at com.bigdata.rdf.sail.RunningQueryCloseableIterator.checkFuture(RunningQueryCloseableIterator.java:46) >> ... 9 more >> Caused by: java.lang.Exception: task=ChunkTask{query=57386638-1f48-4826-966a-84a6b36b5427,bopId=1,partitionId=-1,sinkId=2,altSinkId=null}, cause=java.util.concurrent.ExecutionException: java.lang.RuntimeException: addr=-403683228 : cause=java.lang.IllegalStateException: Error reading from WriteCache addr: 404849739776 length: 1152, writeCacheDebug: No WriteCache debug info >> at com.bigdata.bop.engine.ChunkedRunningQuery$ChunkTask.call(ChunkedRunningQuery.java:1337) >> at com.bigdata.bop.engine.ChunkedRunningQuery$ChunkTaskWrapper.run(ChunkedRunningQuery.java:896) >> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) >> at java.util.concurrent.FutureTask.run(FutureTask.java:266) >> at com.bigdata.concurrent.FutureTaskMon.run(FutureTaskMon.java:63) >> at com.bigdata.bop.engine.ChunkedRunningQuery$ChunkFutureTask.run(ChunkedRunningQuery.java:791) >> ... 3 more >> Caused by: java.util.concurrent.ExecutionException: java.lang.RuntimeException: addr=-403683228 : cause=java.lang.IllegalStateException: Error reading from WriteCache addr: 404849739776 length: 1152, writeCacheDebug: No WriteCache debug info >> at java.util.concurrent.FutureTask.report(FutureTask.java:122) >> at java.util.concurrent.FutureTask.get(FutureTask.java:192) >> at com.bigdata.bop.engine.ChunkedRunningQuery$ChunkTask.call(ChunkedRunningQuery.java:1317) >> ... 8 more >> Caused by: java.lang.RuntimeException: addr=-403683228 : cause=java.lang.IllegalStateException: Error reading from WriteCache addr: 404849739776 length: 1152, writeCacheDebug: No WriteCache debug info >> at com.bigdata.rwstore.RWStore.getData(RWStore.java:2190) >> at com.bigdata.rwstore.RWStore.getData(RWStore.java:1989) >> at com.bigdata.rwstore.PSInputStream.<init>(PSInputStream.java:75) >> at com.bigdata.rwstore.RWStore.getInputStream(RWStore.java:6463) >> at com.bigdata.journal.RWStrategy.getInputStream(RWStrategy.java:846) >> at com.bigdata.bop.solutions.SolutionSetStream.get(SolutionSetStream.java:237) >> at com.bigdata.rdf.sparql.ast.ssets.SolutionSetManager.getSolutions(SolutionSetManager.java:556) >> at com.bigdata.bop.NamedSolutionSetRefUtility.getSolutionSet(NamedSolutionSetRefUtility.java:529) >> at com.bigdata.bop.BOpContext.getAlternateSource(BOpContext.java:752) >> at com.bigdata.bop.join.NestedLoopJoinOp$ChunkTask.getRightSolutions(NestedLoopJoinOp.java:263) >> at com.bigdata.bop.join.NestedLoopJoinOp$ChunkTask.call(NestedLoopJoinOp.java:200) >> at com.bigdata.bop.join.NestedLoopJoinOp$ChunkTask.call(NestedLoopJoinOp.java:166) >> at java.util.concurrent.FutureTask.run(FutureTask.java:266) >> at com.bigdata.bop.engine.ChunkedRunningQuery$ChunkTask.call(ChunkedRunningQuery.java:1316) >> ... 8 more >> Caused by: java.lang.IllegalStateException: Error reading from WriteCache addr: 404849739776 length: 1152, writeCacheDebug: No WriteCache debug info >> at com.bigdata.rwstore.RWStore.getData(RWStore.java:2112) >> ... 21 more >> Caused by: com.bigdata.util.ChecksumError: offset=404849739776,nbytes=1156,expected=-402931822,actual=1830389633 >> at com.bigdata.io.writecache.WriteCacheService._readFromLocalDiskIntoNewHeapByteBuffer(WriteCacheService.java:3711) >> at com.bigdata.io.writecache.WriteCacheService._getRecord(WriteCacheService.java:3526) >> at com.bigdata.io.writecache.WriteCacheService.access$2500(WriteCacheService.java:200) >> at com.bigdata.io.writecache.WriteCacheService$1.compute(WriteCacheService.java:3363) >> at com.bigdata.io.writecache.WriteCacheService$1.compute(WriteCacheService.java:3347) >> at com.bigdata.util.concurrent.Memoizer$1.call(Memoizer.java:77) >> at java.util.concurrent.FutureTask.run(FutureTask.java:266) >> at com.bigdata.util.concurrent.Memoizer.compute(Memoizer.java:92) >> at com.bigdata.io.writecache.WriteCacheService.loadRecord(WriteCacheService.java:3468) >> at com.bigdata.io.writecache.WriteCacheService.read(WriteCacheService.java:3187) >> at com.bigdata.rwstore.RWStore.getData(RWStore.java:2106) >> ... 21 more >> >> >> ------------------------------------------------------------------------------ >> Site24x7 APM Insight: Get Deep Visibility into Application Performance >> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >> Monitor end-to-end web transactions and take corrective actions now >> Troubleshoot faster and improve end-user experience. Signup Now! >> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 <http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140> >> _______________________________________________ >> Bigdata-developers mailing list >> Big...@li... <mailto:Big...@li...> >> https://lists.sourceforge.net/lists/listinfo/bigdata-developers <https://lists.sourceforge.net/lists/listinfo/bigdata-developers> >> >> |