Menu
▾
▴
Re: [Bigdata-developers] Journal compatibility 1.5.3 vs 2.0.0
|
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 >>>>> >>>>> >>> >> > |
