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