Menu
▾
▴
bigdata-developers — List for bigdata developers
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: Joakim S. <joa...@bl...> - 2015-12-22 19:23:45
|
NIce, so no vacation for you guys? :-) > On Dec 22, 2015, at 11:22 AM, Brad Bebee <be...@sy...> wrote: > > Joakim, > > The release candidate 2.0 release should be out very soon. > > Thanks, --Brad > > On Tue, Dec 22, 2015 at 2:21 PM, Joakim Soderberg <joa...@bl... <mailto:joa...@bl...>> wrote: > There is a ticket for this bug: > Test case for service whitelist: https://jira.blazegraph.com/browse/BLZG-1609 <https://jira.blazegraph.com/browse/BLZG-1609> > > Is the update released? > > >> On Dec 21, 2015, at 11:02 PM, Stas Malyshev <sma...@wi... <mailto:sma...@wi...>> wrote: >> >> Hi! >> >>> Hi Stas >>> Right, I am trying http://tinyurl.com/jpr7rk8 <http://tinyurl.com/jpr7rk8> on a Wikidata mirror with >>> Blazegraph 1.5.3 embedded mode. >>> >>> Do you know if there Is there a bigdata-wikidata.jnl file available for >>> download? Perhaps something is inappropriate in my blaze >>> graph.properties file which results in this problem. >> >> .jnl file from query.wikidata.org <http://query.wikidata.org/> is not available for download, and >> it's 100G+ in size, so I'm not sure why would you want to download it. >> Maybe this issue would be relevant: >> https://jira.blazegraph.com/browse/BLZG-1571 <https://jira.blazegraph.com/browse/BLZG-1571> >> >> -- >> Stas Malyshev >> sma...@wi... <mailto:sma...@wi...> > > > ------------------------------------------------------------------------------ > > _______________________________________________ > 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> > > > > > -- > _______________ > Brad Bebee > CEO, Managing Partner > SYSTAP, LLC > e: be...@sy... <mailto:be...@sy...> > m: 202.642.7961 > f: 571.367.5000 > w: www.blazegraph.com <http://www.blazegraph.com/> > > Blazegraph™ <http://www.blazegraph.com/> is our ultra high-performance graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints APIs. Mapgraph™ <http://www.systap.com/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. > > |
|
From: Brad B. <be...@sy...> - 2015-12-22 19:22:22
|
Joakim, The release candidate 2.0 release should be out very soon. Thanks, --Brad On Tue, Dec 22, 2015 at 2:21 PM, Joakim Soderberg < joa...@bl...> wrote: > There is a ticket for this bug: > Test case for service whitelist: > https://jira.blazegraph.com/browse/BLZG-1609 > > Is the update released? > > > On Dec 21, 2015, at 11:02 PM, Stas Malyshev <sma...@wi...> > wrote: > > Hi! > > Hi Stas > Right, I am trying http://tinyurl.com/jpr7rk8 on a Wikidata mirror with > Blazegraph 1.5.3 embedded mode. > > Do you know if there Is there a bigdata-wikidata.jnl file available for > download? Perhaps something is inappropriate in my blaze > graph.properties file which results in this problem. > > > .jnl file from query.wikidata.org is not available for download, and > it's 100G+ in size, so I'm not sure why would you want to download it. > Maybe this issue would be relevant: > https://jira.blazegraph.com/browse/BLZG-1571 > > -- > Stas Malyshev > sma...@wi... > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Bigdata-developers mailing list > Big...@li... > https://lists.sourceforge.net/lists/listinfo/bigdata-developers > > -- _______________ Brad Bebee CEO, Managing Partner SYSTAP, LLC e: be...@sy... m: 202.642.7961 f: 571.367.5000 w: www.blazegraph.com Blazegraph™ <http://www.blazegraph.com> is our ultra high-performance graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints APIs. Mapgraph™ <http://www.systap.com/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. |
|
From: Joakim S. <joa...@bl...> - 2015-12-22 19:21:10
|
There is a ticket for this bug: Test case for service whitelist: https://jira.blazegraph.com/browse/BLZG-1609 <https://jira.blazegraph.com/browse/BLZG-1609> Is the update released? > On Dec 21, 2015, at 11:02 PM, Stas Malyshev <sma...@wi...> wrote: > > Hi! > >> Hi Stas >> Right, I am trying http://tinyurl.com/jpr7rk8 on a Wikidata mirror with >> Blazegraph 1.5.3 embedded mode. >> >> Do you know if there Is there a bigdata-wikidata.jnl file available for >> download? Perhaps something is inappropriate in my blaze >> graph.properties file which results in this problem. > > .jnl file from query.wikidata.org is not available for download, and > it's 100G+ in size, so I'm not sure why would you want to download it. > Maybe this issue would be relevant: > https://jira.blazegraph.com/browse/BLZG-1571 > > -- > Stas Malyshev > sma...@wi... |
|
From: Joakim S. <joa...@bl...> - 2015-12-22 08:54:10
|
Thanks for the pointer. That is possibly an explanation. I can’t see any typos in my query, so perhaps my server can’t access the label service at <http://wikiba.se/ontology#label> > On Dec 21, 2015, at 11:02 PM, Stas Malyshev <sma...@wi...> wrote: > > Hi! > >> Hi Stas >> Right, I am trying http://tinyurl.com/jpr7rk8 on a Wikidata mirror with >> Blazegraph 1.5.3 embedded mode. >> >> Do you know if there Is there a bigdata-wikidata.jnl file available for >> download? Perhaps something is inappropriate in my blaze >> graph.properties file which results in this problem. > > .jnl file from query.wikidata.org is not available for download, and > it's 100G+ in size, so I'm not sure why would you want to download it. > Maybe this issue would be relevant: > https://jira.blazegraph.com/browse/BLZG-1571 > > -- > Stas Malyshev > sma...@wi... |
|
From: Stas M. <sma...@wi...> - 2015-12-22 07:02:24
|
Hi! > Hi Stas > Right, I am trying http://tinyurl.com/jpr7rk8 on a Wikidata mirror with > Blazegraph 1.5.3 embedded mode. > > Do you know if there Is there a bigdata-wikidata.jnl file available for > download? Perhaps something is inappropriate in my blaze > graph.properties file which results in this problem. .jnl file from query.wikidata.org is not available for download, and it's 100G+ in size, so I'm not sure why would you want to download it. Maybe this issue would be relevant: https://jira.blazegraph.com/browse/BLZG-1571 -- Stas Malyshev sma...@wi... |
|
From: Stas M. <sma...@wi...> - 2015-12-22 06:55:15
|
Hi!
> I saw another user had a similar problem when executing a SERVICE query (quads=true).
> In my case, launching the following query:
>
> query = SELECT ?band ?bandLabel WHERE {
> ?band wdt:P31 wd:Q5741069 .
>
> SERVICE wikibase:label {
> bd:serviceParam wikibase:language "en,fr,de,he,el,fi,no,ja" .
> ?band rdfs:label ?bandLabel .
> }
> } limit 100
Where are you running it? From the content, it looks like it's for
Wikidata query service, but this query: http://tinyurl.com/jpr7rk8 works
fine for me on query.wikidata.org.
--
Stas Malyshev
sma...@wi...
|
|
From: Joakim S. <joa...@bl...> - 2015-12-22 06:49:37
|
Hi Stas Right, I am trying http://tinyurl.com/jpr7rk8 <http://tinyurl.com/jpr7rk8> on a Wikidata mirror with Blazegraph 1.5.3 embedded mode. Do you know if there Is there a bigdata-wikidata.jnl file available for download? Perhaps something is inappropriate in my blaze graph.properties file which results in this problem. /J > On Dec 21, 2015, at 10:30 PM, Stas Malyshev <sma...@wi...> wrote: > > Hi! > >> I saw another user had a similar problem when executing a SERVICE query (quads=true). >> In my case, launching the following query: >> >> query = SELECT ?band ?bandLabel WHERE { >> ?band wdt:P31 wd:Q5741069 . >> >> SERVICE wikibase:label { >> bd:serviceParam wikibase:language "en,fr,de,he,el,fi,no,ja" . >> ?band rdfs:label ?bandLabel . >> } >> } limit 100 > > Where are you running it? From the content, it looks like it's for > Wikidata query service, but this query: http://tinyurl.com/jpr7rk8 works > fine for me on query.wikidata.org. > > -- > Stas Malyshev > sma...@wi... |
|
From: Joakim S. <joa...@bl...> - 2015-12-22 06:24:29
|
Hi,
I saw another user had a similar problem when executing a SERVICE query (quads=true).
In my case, launching the following query:
query = SELECT ?band ?bandLabel WHERE {
?band wdt:P31 wd:Q5741069 .
SERVICE wikibase:label {
bd:serviceParam wikibase:language "en,fr,de,he,el,fi,no,ja" .
?band rdfs:label ?bandLabel .
}
} limit 100
com.bigdata.util.concurrent.Haltable@7a45bc51 : isFirstCause=true : java.lang.Exception: task=ChunkTask{query=bd76beb5-ce2e-4c41-a247-a4d8c630644f,bopId=4,partitionId=-1,sinkId=6,altSinkId=null}, cause=java.util.concurrent.ExecutionException: java.util.concurrent.ExecutionException: java.lang.RuntimeException: java.lang.NullPointerException
java.lang.Exception: task=ChunkTask{query=bd76beb5-ce2e-4c41-a247-a4d8c630644f,bopId=4,partitionId=-1,sinkId=6,altSinkId=null}, cause=java.util.concurrent.ExecutionException: java.util.concurrent.ExecutionException: java.lang.RuntimeException: java.lang.NullPointerException
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)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.util.concurrent.ExecutionException: java.util.concurrent.ExecutionException: java.lang.RuntimeException: java.lang.NullPointerException
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.util.concurrent.ExecutionException: java.lang.RuntimeException: java.lang.NullPointerException
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:206)
at com.bigdata.bop.controller.ServiceCallJoin$ChunkTask.doServiceCallWithConstant(ServiceCallJoin.java:342)
at com.bigdata.bop.controller.ServiceCallJoin$ChunkTask.call(ServiceCallJoin.java:294)
at com.bigdata.bop.controller.ServiceCallJoin$ChunkTask.call(ServiceCallJoin.java:206)
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.RuntimeException: java.lang.NullPointerException
at com.bigdata.bop.controller.ServiceCallJoin$ChunkTask$ServiceCallTask.doServiceCall(ServiceCallJoin.java:748)
at com.bigdata.bop.controller.ServiceCallJoin$ChunkTask$ServiceCallTask.call(ServiceCallJoin.java:607)
at com.bigdata.bop.controller.ServiceCallJoin$ChunkTask$ServiceCallTask.call(ServiceCallJoin.java:543)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
... 3 more
Caused by: java.lang.NullPointerException
at com.bigdata.rdf.sail.webapp.client.MiniMime.<init>(MiniMime.java:79)
at com.bigdata.rdf.sail.webapp.client.RemoteRepositoryManager.tupleResults(RemoteRepositoryManager.java:1603)
at com.bigdata.rdf.sparql.ast.service.RemoteServiceCallImpl.call(RemoteServiceCallImpl.java:153)
at com.bigdata.rdf.sparql.ast.service.RemoteServiceCallImpl.call(RemoteServiceCallImpl.java:51)
at com.bigdata.bop.controller.ServiceCallJoin$ChunkTask$ServiceCallTask.doNonBigdataSesameServiceCall(ServiceCallJoin.java:830)
at com.bigdata.bop.controller.ServiceCallJoin$ChunkTask$ServiceCallTask.doRemoteServiceCall(ServiceCallJoin.java:794)
at com.bigdata.bop.controller.ServiceCallJoin$ChunkTask$ServiceCallTask.doServiceCall(ServiceCallJoin.java:708)
... 6 more
com.bigdata.util.concurrent.Haltable@7a45bc51 : isFirstCause=false : java.lang.InterruptedException
java.lang.InterruptedException
at com.bigdata.util.concurrent.Haltable.cancel(Haltable.java:241)
at com.bigdata.bop.engine.AbstractRunningQuery.cancel(AbstractRunningQuery.java:1346)
at com.bigdata.bop.engine.AbstractRunningQuery.halt(AbstractRunningQuery.java:1311)
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)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
com.bigdata.util.concurrent.Haltable@7a45bc51 : isFirstCause=false : java.lang.InterruptedException
java.lang.InterruptedException
at com.bigdata.util.concurrent.Haltable.cancel(Haltable.java:241)
at com.bigdata.bop.engine.AbstractRunningQuery.cancel(AbstractRunningQuery.java:1346)
at com.bigdata.bop.engine.AbstractRunningQuery.halt(AbstractRunningQuery.java:1283)
at com.bigdata.bop.engine.AbstractRunningQuery.haltOp(AbstractRunningQuery.java:895)
at com.bigdata.bop.engine.ChunkedRunningQuery.haltOp(ChunkedRunningQuery.java:382)
at com.bigdata.bop.engine.ChunkedRunningQuery$SendHaltMessageTask.run(ChunkedRunningQuery.java:1824)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
com.bigdata.util.concurrent.Haltable@7a45bc51 : isFirstCause=false : java.lang.InterruptedException
java.lang.InterruptedException
at com.bigdata.util.concurrent.Haltable.cancel(Haltable.java:241)
at com.bigdata.bop.engine.AbstractRunningQuery.cancel(AbstractRunningQuery.java:1346)
at com.bigdata.rdf.sail.RunningQueryCloseableIterator.close(RunningQueryCloseableIterator.java:71)
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)
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)
at java.lang.Thread.run(Thread.java:745)
java.util.concurrent.ExecutionException: java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.Exception: task=ChunkTask{query=bd76beb5-ce2e-4c41-a247-a4d8c630644f,bopId=4,partitionId=-1,sinkId=6,altSinkId=null}, cause=java.util.concurrent.ExecutionException: java.util.concurrent.ExecutionException: java.lang.RuntimeException: java.lang.NullPointerException
java.util.concurrent.ExecutionException: java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.Exception: task=ChunkTask{query=bd76beb5-ce2e-4c41-a247-a4d8c630644f,bopId=4,partitionId=-1,sinkId=6,altSinkId=null}, cause=java.util.concurrent.ExecutionException: java.util.concurrent.ExecutionException: java.lang.RuntimeException: java.lang.NullPointerException
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)
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)
at info.aduna.iteration.IterationWrapper.hasNext(IterationWrapper.java:68)
at com.blippar.action.QueryAction.processSelectQueryJson(QueryAction.java:166)
at com.blippar.action.QueryAction.execute(QueryAction.java:90)
at com.blippar.servlet.MinervaServlet.doPost(MinervaServlet.java:84)
at com.blippar.servlet.MinervaServlet.doGet(MinervaServlet.java:52)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:622)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:217)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:142)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
|
|
From: Bryan T. <br...@sy...> - 2015-12-14 21:37:43
|
2.0 is now in a code freeze for benchmarking and performance regression testing. The only remaining tickets against 2.0 have to do with deployers, documentation, etc. Our plans are for a candidate release this year with an official 2.0 release in mid-January, 2016. Thanks, Bryan |
|
From: Bryan T. <br...@sy...> - 2015-12-14 17:26:05
|
There are a variety of ways to reduce the size of a journal, however the journal itself by design does not "shink" when you remove data. Instead the RWStore will mark that there are free slots on the journal will reuse those free slots for new allocations. If you observe a continued growth in the file size, there are generally two reasons. 1. Simply writing more data, which is to be expected. 2. Holding open a long lived query connection while concurrently writing more data, which can be somewhat counterintuitive. The reason why the journal grows for (2) is that recycling of deleted slots the commit point on which the query is reading can not performed until the query terminates and the database rolls through another commit point. In general, this is completely transparent. Issues can occasionally arise for embedded applications that do not correctly close database connections or for REST API applications where there is a long running query. Simply having the workbench open has no effect on this. It is only an active query against a historical commit point that would pin the storage for the historical commit point. Thanks, Bryan ---- Bryan Thompson Chief Scientist & Founder SYSTAP, LLC 4501 Tower Road Greensboro, NC 27410 br...@sy... 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. 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, Dec 14, 2015 at 12:06 PM, Reul, Quentin < que...@wo...> wrote: > Hi, > > > > We are using Blazegraph 1.5.2 as part of a project. As part of our > assessment, we are observing that the size of the Journal is not only > rapidly increasing, but also that it does not seem to decrease in size > after performing SPARQL UPDATE queries. For instance, we do a clean up of > the repositories every so often using > > DELETE { > > ?s ?p ?o . > > } WHERE { > > ?s ?p ?o . > > } > > Although this query removes the triples, it does not seem to have any > impact on the size of the Journal. Looking at the JIRA [1], I see that a > recommendation is to do a data import / export. Is there any configuration > that can be applied such that the Journal gets purged after removing > triples? > > > > Kind regards, > > > > [1] https://jira.blazegraph.com/browse/BLZG-1088 > > > > *Quentin Reul * > > Advanced Technology | Global Platform Organization | +1 (917) 891 5490 > > Email: *Que...@wo... <Que...@wo...>* > > Skype: quentin_reul > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Bigdata-developers mailing list > Big...@li... > https://lists.sourceforge.net/lists/listinfo/bigdata-developers > > |
|
From: Reul, Q. <que...@wo...> - 2015-12-14 17:06:20
|
Hi,
We are using Blazegraph 1.5.2 as part of a project. As part of our assessment, we are observing that the size of the Journal is not only rapidly increasing, but also that it does not seem to decrease in size after performing SPARQL UPDATE queries. For instance, we do a clean up of the repositories every so often using
DELETE {
?s ?p ?o .
} WHERE {
?s ?p ?o .
}
Although this query removes the triples, it does not seem to have any impact on the size of the Journal. Looking at the JIRA [1], I see that a recommendation is to do a data import / export. Is there any configuration that can be applied such that the Journal gets purged after removing triples?
Kind regards,
[1] https://jira.blazegraph.com/browse/BLZG-1088
Quentin Reul
Advanced Technology | Global Platform Organization | +1 (917) 891 5490
Email: Que...@wo...<mailto:Que...@wo...>
Skype: quentin_reul
|
|
From: Igor K. <igo...@ms...> - 2015-12-14 04:39:58
|
Bryan, I've created a ticket: https://jira.blazegraph.com/browse/BLZG-1687 On Sat, Dec 12, 2015 at 2:19 AM, Bryan Thompson <br...@sy...> wrote: > Great! > > Igor, can you please file and accept a ticket to document this? Jeremy > put together the ConfigurableAnalyzerFactory. Please check both the > developer list and git commits if you do not find enough info in the > javadoc. > > Thanks, > Bryan > On Dec 11, 2015 4:08 PM, "Jim Balhoff" <ba...@gm...> wrote: > >> I figured it out. I needed to add these 4 lines to the properties file: >> >> >> com.bigdata.search.FullTextIndex.analyzerFactoryClass=com.bigdata.search.ConfigurableAnalyzerFactory >> >> com.bigdata.search.ConfigurableAnalyzerFactory.analyzer.eng.analyzerClass=org.apache.lucene.analysis.standard.StandardAnalyzer >> com.bigdata.search.ConfigurableAnalyzerFactory.analyzer.eng.stopwords=none >> com.bigdata.search.ConfigurableAnalyzerFactory.analyzer._.like=eng >> >> This gives me the desired results—no stopwords. >> >> Thanks, >> Jim >> >> >> On Dec 10, 2015, at 5:12 PM, Bryan Thompson <br...@sy...> wrote: >> >> I suggest either applying a debugger or creating a unit test that >> replicates the issue and filing a ticket and attaching the test. You >> should be able to configure any aspect of the tokenization behavior. >> >> I would also try a namespace specific override. E.g., >> >> com.bigdata.*foo.lex.*search.ConfigurableAnalyzerFactory.stopwords=none >>> >> >> Thanks, >> Bryan >> >> On Thu, Dec 10, 2015 at 4:55 PM, Jim Balhoff <ba...@gm...> wrote: >> >>> Yes, I am deleting the journal file and reloading in between attempts. >>> >>> Thanks, >>> Jim >>> >>> On Dec 10, 2015, at 4:50 PM, Brad Bebee <be...@sy...> wrote: >>> >>> Jim, >>> >>> Did you reload the namespace after the configuration change? >>> >>> Thanks, --Brad >>> >>> On Thu, Dec 10, 2015 at 4:38 PM, Jim Balhoff <ba...@gm...> wrote: >>> >>>> I had tried some similar syntax, but wasn’t sure how it should look. I >>>> just tried the form you suggested and it did not have an affect on >>>> stopwords. They seem to still be active, because if my search input is >>>> simply “of”, I get this message: >>>> >>>> WARN : FullTextIndex.java:1052: No terms after stopword extraction: >>>> query=com.bigdata.rdf.lexicon.ITextIndexer$FullTextQuery@7aef6039 >>>> >>>> Thanks, >>>> Jim >>>> >>>> >>>> > On Dec 9, 2015, at 11:34 PM, Brad Bebee <be...@sy...> wrote: >>>> > >>>> > Jim, >>>> > >>>> > Thank you. Have you tried configuring your journal with the property >>>> below? >>>> > >>>> > com.bigdata.search.ConfigurableAnalyzerFactory.stopwords=none >>>> > >>>> > >>>> > >>>> > Thanks, --Brad >>>> > >>>> > >>>> > On Wed, Dec 9, 2015 at 9:36 AM, Jim Balhoff <ba...@gm...> >>>> wrote: >>>> > Hi Brad, >>>> > >>>> > I see, I can look into providing my own implementation. I got the >>>> impression from the JavaDoc that I could provide config options to modify >>>> the behavior of some of the analyzers. I have been looking at these pages: >>>> > >>>> > >>>> https://www.blazegraph.com/docs/api/com/bigdata/search/ConfigurableAnalyzerFactory.AnalyzerOptions.html#STOPWORDS_VALUE_NONE >>>> > https://www.blazegraph.com/docs/api/constant-values.html >>>> > >>>> > I also tried to switch from the default analyzer to the >>>> TermCompletionAnalyzer, but haven’t been able to get the property value set >>>> correctly for “wordBoundary” in the config file. >>>> > >>>> > Understanding how to translate option constants from the JavaDoc into >>>> correctly written config file properties has been a challenge. It would be >>>> really helpful to have more of those spelled out on the wiki. >>>> > >>>> > Thanks! >>>> > Jim >>>> > >>>> > > On Dec 8, 2015, at 9:54 PM, Brad Bebee <be...@sy...> wrote: >>>> > > >>>> > > Jim, >>>> > > >>>> > > I believe you could do this by overriding the Analyzer Factory >>>> Class [1] with your own implementation that does not filter stopwords [2]. >>>> Other may have more specific suggestions. >>>> > > >>>> > > [1] >>>> https://www.blazegraph.com/docs/api/com/bigdata/search/FullTextIndex.Options.html#ANALYZER_FACTORY_CLASS >>>> > > >>>> > > [2] >>>> https://www.blazegraph.com/docs/api/com/bigdata/search/IAnalyzerFactory.html >>>> > > >>>> > > Thanks, --Brad >>>> > > >>>> > > On Tue, Dec 8, 2015 at 9:12 PM, Jim Balhoff <ba...@gm...> >>>> wrote: >>>> > > Hi, >>>> > > >>>> > > I was wondering if anyone could provide examples for how to set up >>>> the Blazegraph properties file to configure options for the full text >>>> search. I have looked through the various options in the JavaDoc, but I >>>> can’t quite figure out the right properties file syntax for >>>> ‘stopwords=none’. Here is what I am trying to do: >>>> > > >>>> > > I have a term in the database with rdfs:label "skeletal element of >>>> eye region”. When users search for terms, I append a “*” to their input >>>> text by default. However this is failing when the label contains a stopword >>>> like “of”. So, searching with “skeletal element of” and “skeletal element*” >>>> do find the term as a match, but “skeletal element of*” does not. Can I >>>> disable stopwords entirely? >>>> > > >>>> > > Thanks, >>>> > > Jim >>>> > > >>>> > > >>>> > > >>>> ------------------------------------------------------------------------------ >>>> > > _______________________________________________ >>>> > > Bigdata-developers mailing list >>>> > > Big...@li... >>>> > > https://lists.sourceforge.net/lists/listinfo/bigdata-developers >>>> > > >>>> > > >>>> > > >>>> > > -- >>>> > > _______________ >>>> > > Brad Bebee >>>> > > CEO, Managing Partner >>>> > > SYSTAP, LLC >>>> > > e: be...@sy... >>>> > > m: 202.642.7961 >>>> > > f: 571.367.5000 >>>> > > w: www.blazegraph.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. > > >>>> > > >>>> > >>>> > >>>> > >>>> > >>>> > -- >>>> > _______________ >>>> > Brad Bebee >>>> > CEO, Managing Partner >>>> > SYSTAP, LLC >>>> > e: be...@sy... >>>> > m: 202.642.7961 >>>> > f: 571.367.5000 >>>> > w: www.blazegraph.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. > >>>> > >>>> >>>> >>> >>> >>> -- >>> _______________ >>> Brad Bebee >>> CEO, Managing Partner >>> SYSTAP, LLC >>> e: be...@sy... >>> m: 202.642.7961 >>> f: 571.367.5000 >>> w: www.blazegraph.com >>> >>> Blazegraph™ <http://www.blazegraph.com/> is our ultra high-performance >>> graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints >>> APIs. Mapgraph™ <http://www.systap.com/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. >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Bigdata-developers mailing list >>> Big...@li... >>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers >>> >>> >> >> -- *Igor Kim* | Team Leader / Backend | Maginfo, Ltd Mobile: +7-912-402-4622 |
|
From: Bryan T. <br...@sy...> - 2015-12-12 17:43:43
|
Johannes, Can you please file a ticket for this. We will have someone look into it. Tickets are filed on jira (http://jira.blazegraph.com). Thanks, Bryan ---- Bryan Thompson Chief Scientist & Founder SYSTAP, LLC 4501 Tower Road Greensboro, NC 27410 br...@sy... 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. 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 Fri, Dec 11, 2015 at 8:02 AM, Johannes Frey < joh...@st...> wrote: > Hello, > > I'm facing the following problems with RDR using blazegraph Build > Version 1.5.3. > CASE 1 and CASE 2 are major problems. CASE 3 is just a SPARQL* parser > issue and there is a workaround by using BIND statements instead. > > In CASE 1 I want to reify a reified statement. In the SPARQL* paper > (referenced on the RDR wiki site) the EBNF definition of a TRefPattern > is recursive. > And there is a explicit note on nested triple reference patterns. So > this should work. Querying such triple data using BIND statements works > (more precisely: there are no errors), but unfortunately I don't know > how to import data consisting of nested reified triples. Nesting the "<< > >>"-statements doesn't work, neither in Turtle* nor in SPARQL*. > > In CASE 2 I want to use SPARQL update to insert or remove a simple > reified statement. But it seems that this not implemented in blazegraph, > because it's rejecting a bunch of queries > due to parser errors. But then my question is: How to remove or change a > reified triple statement? I'm considering to use blazegraph for large > scale use, so deleting the whole KB and reimporting it is not feasible. > > I appreciate any help you can provide. > > Regards > Johannes > > > =================== SPARQL* - CASE 1 ============================= > Prefix : <http://example.org/ns#> > Select * where > { > BIND( <<:Bob :isMarriedTo :Alice >> as ?t) . > BIND( <<?t :validUntil "2015-12-01" >> as ?t2) . > ?t2 :crawledOn "2015-12-07" . > } > > =================== Turtle* - CASE 1 ============================= > ****NOT WORKING**** > @prefix : <http://example.org/ns#> . > << <<:Bob :isMarriedTo :Alice >> :validUntil "2015-12-01" >> :crawledOn > "2015-12-07" > > > =================== SPARQL* - CASE 2a) b) c) d) > ============================= > ****NOT WORKING**** a) ***** > Prefix : <http://example.org/ns#> > INSERT DATA > { > <<:Bob :isMarriedTo :Alice>> :validUntil "2015-12-01". > } > > ****NOT WORKING**** b) ***** > Prefix : <http://example.org/ns#> > INSERT { <<:Bob :isMarriedTo :Alice>> :validUntil "2015-12-01". } WHERE {} > > > ****NOT WORKING**** c) ***** > Prefix : <http://example.org/ns#> > DELETE { <<:Bob :isMarriedTo :Alice>> :validUntil "2015-12-01". } WHERE {} > > ****NOT WORKING**** d) ***** > Prefix : <http://example.org/ns#> > DELETE { BIND( <<:Bob :isMarriedTo :Alice >> as ?t) . ?t :validUntil > "2015-12-01". } WHERE {} > > =================== SPARQL* - CASE 3 ============================= > ****NOT WORKING**** > Prefix : <http://example.org/ns#> > Select * where > { > <<:Bob :isMarriedTo :Alice>> ?x <<:a :b :c>> . > } > =================== Turtle* - CASE 3 ============================= > ****BUT WORKING in Turtle* **** > @prefix : <http://example.org/ns#> . > <<:Bob :isMarriedTo :Alice >> :x <<:a :b :c>> . > > > ------------------------------------------------------------------------------ > _______________________________________________ > Bigdata-developers mailing list > Big...@li... > https://lists.sourceforge.net/lists/listinfo/bigdata-developers > |
|
From: Bryan T. <br...@sy...> - 2015-12-11 21:45:52
|
Great! Igor, can you please file and accept a ticket to document this? Jeremy put together the ConfigurableAnalyzerFactory. Please check both the developer list and git commits if you do not find enough info in the javadoc. Thanks, Bryan On Dec 11, 2015 4:08 PM, "Jim Balhoff" <ba...@gm...> wrote: > I figured it out. I needed to add these 4 lines to the properties file: > > > com.bigdata.search.FullTextIndex.analyzerFactoryClass=com.bigdata.search.ConfigurableAnalyzerFactory > > com.bigdata.search.ConfigurableAnalyzerFactory.analyzer.eng.analyzerClass=org.apache.lucene.analysis.standard.StandardAnalyzer > com.bigdata.search.ConfigurableAnalyzerFactory.analyzer.eng.stopwords=none > com.bigdata.search.ConfigurableAnalyzerFactory.analyzer._.like=eng > > This gives me the desired results—no stopwords. > > Thanks, > Jim > > > On Dec 10, 2015, at 5:12 PM, Bryan Thompson <br...@sy...> wrote: > > I suggest either applying a debugger or creating a unit test that > replicates the issue and filing a ticket and attaching the test. You > should be able to configure any aspect of the tokenization behavior. > > I would also try a namespace specific override. E.g., > > com.bigdata.*foo.lex.*search.ConfigurableAnalyzerFactory.stopwords=none >> > > Thanks, > Bryan > > On Thu, Dec 10, 2015 at 4:55 PM, Jim Balhoff <ba...@gm...> wrote: > >> Yes, I am deleting the journal file and reloading in between attempts. >> >> Thanks, >> Jim >> >> On Dec 10, 2015, at 4:50 PM, Brad Bebee <be...@sy...> wrote: >> >> Jim, >> >> Did you reload the namespace after the configuration change? >> >> Thanks, --Brad >> >> On Thu, Dec 10, 2015 at 4:38 PM, Jim Balhoff <ba...@gm...> wrote: >> >>> I had tried some similar syntax, but wasn’t sure how it should look. I >>> just tried the form you suggested and it did not have an affect on >>> stopwords. They seem to still be active, because if my search input is >>> simply “of”, I get this message: >>> >>> WARN : FullTextIndex.java:1052: No terms after stopword extraction: >>> query=com.bigdata.rdf.lexicon.ITextIndexer$FullTextQuery@7aef6039 >>> >>> Thanks, >>> Jim >>> >>> >>> > On Dec 9, 2015, at 11:34 PM, Brad Bebee <be...@sy...> wrote: >>> > >>> > Jim, >>> > >>> > Thank you. Have you tried configuring your journal with the property >>> below? >>> > >>> > com.bigdata.search.ConfigurableAnalyzerFactory.stopwords=none >>> > >>> > >>> > >>> > Thanks, --Brad >>> > >>> > >>> > On Wed, Dec 9, 2015 at 9:36 AM, Jim Balhoff <ba...@gm...> wrote: >>> > Hi Brad, >>> > >>> > I see, I can look into providing my own implementation. I got the >>> impression from the JavaDoc that I could provide config options to modify >>> the behavior of some of the analyzers. I have been looking at these pages: >>> > >>> > >>> https://www.blazegraph.com/docs/api/com/bigdata/search/ConfigurableAnalyzerFactory.AnalyzerOptions.html#STOPWORDS_VALUE_NONE >>> > https://www.blazegraph.com/docs/api/constant-values.html >>> > >>> > I also tried to switch from the default analyzer to the >>> TermCompletionAnalyzer, but haven’t been able to get the property value set >>> correctly for “wordBoundary” in the config file. >>> > >>> > Understanding how to translate option constants from the JavaDoc into >>> correctly written config file properties has been a challenge. It would be >>> really helpful to have more of those spelled out on the wiki. >>> > >>> > Thanks! >>> > Jim >>> > >>> > > On Dec 8, 2015, at 9:54 PM, Brad Bebee <be...@sy...> wrote: >>> > > >>> > > Jim, >>> > > >>> > > I believe you could do this by overriding the Analyzer Factory Class >>> [1] with your own implementation that does not filter stopwords [2]. Other >>> may have more specific suggestions. >>> > > >>> > > [1] >>> https://www.blazegraph.com/docs/api/com/bigdata/search/FullTextIndex.Options.html#ANALYZER_FACTORY_CLASS >>> > > >>> > > [2] >>> https://www.blazegraph.com/docs/api/com/bigdata/search/IAnalyzerFactory.html >>> > > >>> > > Thanks, --Brad >>> > > >>> > > On Tue, Dec 8, 2015 at 9:12 PM, Jim Balhoff <ba...@gm...> >>> wrote: >>> > > Hi, >>> > > >>> > > I was wondering if anyone could provide examples for how to set up >>> the Blazegraph properties file to configure options for the full text >>> search. I have looked through the various options in the JavaDoc, but I >>> can’t quite figure out the right properties file syntax for >>> ‘stopwords=none’. Here is what I am trying to do: >>> > > >>> > > I have a term in the database with rdfs:label "skeletal element of >>> eye region”. When users search for terms, I append a “*” to their input >>> text by default. However this is failing when the label contains a stopword >>> like “of”. So, searching with “skeletal element of” and “skeletal element*” >>> do find the term as a match, but “skeletal element of*” does not. Can I >>> disable stopwords entirely? >>> > > >>> > > Thanks, >>> > > Jim >>> > > >>> > > >>> > > >>> ------------------------------------------------------------------------------ >>> > > _______________________________________________ >>> > > Bigdata-developers mailing list >>> > > Big...@li... >>> > > https://lists.sourceforge.net/lists/listinfo/bigdata-developers >>> > > >>> > > >>> > > >>> > > -- >>> > > _______________ >>> > > Brad Bebee >>> > > CEO, Managing Partner >>> > > SYSTAP, LLC >>> > > e: be...@sy... >>> > > m: 202.642.7961 >>> > > f: 571.367.5000 >>> > > w: www.blazegraph.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. > > >>> > > >>> > >>> > >>> > >>> > >>> > -- >>> > _______________ >>> > Brad Bebee >>> > CEO, Managing Partner >>> > SYSTAP, LLC >>> > e: be...@sy... >>> > m: 202.642.7961 >>> > f: 571.367.5000 >>> > w: www.blazegraph.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. > >>> > >>> >>> >> >> >> -- >> _______________ >> Brad Bebee >> CEO, Managing Partner >> SYSTAP, LLC >> e: be...@sy... >> m: 202.642.7961 >> f: 571.367.5000 >> w: www.blazegraph.com >> >> Blazegraph™ <http://www.blazegraph.com/> is our ultra high-performance >> graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints >> APIs. Mapgraph™ <http://www.systap.com/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. >> >> >> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> Bigdata-developers mailing list >> Big...@li... >> https://lists.sourceforge.net/lists/listinfo/bigdata-developers >> >> > > |
|
From: Jim B. <ba...@gm...> - 2015-12-11 21:08:43
|
I figured it out. I needed to add these 4 lines to the properties file: com.bigdata.search.FullTextIndex.analyzerFactoryClass=com.bigdata.search.ConfigurableAnalyzerFactory com.bigdata.search.ConfigurableAnalyzerFactory.analyzer.eng.analyzerClass=org.apache.lucene.analysis.standard.StandardAnalyzer com.bigdata.search.ConfigurableAnalyzerFactory.analyzer.eng.stopwords=none com.bigdata.search.ConfigurableAnalyzerFactory.analyzer._.like=eng This gives me the desired results—no stopwords. Thanks, Jim > On Dec 10, 2015, at 5:12 PM, Bryan Thompson <br...@sy...> wrote: > > I suggest either applying a debugger or creating a unit test that replicates the issue and filing a ticket and attaching the test. You should be able to configure any aspect of the tokenization behavior. > > I would also try a namespace specific override. E.g., > >> com.bigdata.foo.lex.search.ConfigurableAnalyzerFactory.stopwords=none > > Thanks, > Bryan > > On Thu, Dec 10, 2015 at 4:55 PM, Jim Balhoff <ba...@gm... <mailto:ba...@gm...>> wrote: > Yes, I am deleting the journal file and reloading in between attempts. > > Thanks, > Jim > >> On Dec 10, 2015, at 4:50 PM, Brad Bebee <be...@sy... <mailto:be...@sy...>> wrote: >> >> Jim, >> >> Did you reload the namespace after the configuration change? >> >> Thanks, --Brad >> >> On Thu, Dec 10, 2015 at 4:38 PM, Jim Balhoff <ba...@gm... <mailto:ba...@gm...>> wrote: >> I had tried some similar syntax, but wasn’t sure how it should look. I just tried the form you suggested and it did not have an affect on stopwords. They seem to still be active, because if my search input is simply “of”, I get this message: >> >> WARN : FullTextIndex.java:1052: No terms after stopword extraction: query=com.bigdata.rdf.lexicon.ITextIndexer$FullTextQuery@7aef6039 >> >> Thanks, >> Jim >> >> >> > On Dec 9, 2015, at 11:34 PM, Brad Bebee <be...@sy... <mailto:be...@sy...>> wrote: >> > >> > Jim, >> > >> > Thank you. Have you tried configuring your journal with the property below? >> > >> > com.bigdata.search.ConfigurableAnalyzerFactory.stopwords=none >> > >> > >> > >> > Thanks, --Brad >> > >> > >> > On Wed, Dec 9, 2015 at 9:36 AM, Jim Balhoff <ba...@gm... <mailto:ba...@gm...>> wrote: >> > Hi Brad, >> > >> > I see, I can look into providing my own implementation. I got the impression from the JavaDoc that I could provide config options to modify the behavior of some of the analyzers. I have been looking at these pages: >> > >> > https://www.blazegraph.com/docs/api/com/bigdata/search/ConfigurableAnalyzerFactory.AnalyzerOptions.html#STOPWORDS_VALUE_NONE <https://www.blazegraph.com/docs/api/com/bigdata/search/ConfigurableAnalyzerFactory.AnalyzerOptions.html#STOPWORDS_VALUE_NONE> >> > https://www.blazegraph.com/docs/api/constant-values.html <https://www.blazegraph.com/docs/api/constant-values.html> >> > >> > I also tried to switch from the default analyzer to the TermCompletionAnalyzer, but haven’t been able to get the property value set correctly for “wordBoundary” in the config file. >> > >> > Understanding how to translate option constants from the JavaDoc into correctly written config file properties has been a challenge. It would be really helpful to have more of those spelled out on the wiki. >> > >> > Thanks! >> > Jim >> > >> > > On Dec 8, 2015, at 9:54 PM, Brad Bebee <be...@sy... <mailto:be...@sy...>> wrote: >> > > >> > > Jim, >> > > >> > > I believe you could do this by overriding the Analyzer Factory Class [1] with your own implementation that does not filter stopwords [2]. Other may have more specific suggestions. >> > > >> > > [1] https://www.blazegraph.com/docs/api/com/bigdata/search/FullTextIndex.Options.html#ANALYZER_FACTORY_CLASS <https://www.blazegraph.com/docs/api/com/bigdata/search/FullTextIndex.Options.html#ANALYZER_FACTORY_CLASS> >> > > >> > > [2] https://www.blazegraph.com/docs/api/com/bigdata/search/IAnalyzerFactory.html <https://www.blazegraph.com/docs/api/com/bigdata/search/IAnalyzerFactory.html> >> > > >> > > Thanks, --Brad >> > > >> > > On Tue, Dec 8, 2015 at 9:12 PM, Jim Balhoff <ba...@gm... <mailto:ba...@gm...>> wrote: >> > > Hi, >> > > >> > > I was wondering if anyone could provide examples for how to set up the Blazegraph properties file to configure options for the full text search. I have looked through the various options in the JavaDoc, but I can’t quite figure out the right properties file syntax for ‘stopwords=none’. Here is what I am trying to do: >> > > >> > > I have a term in the database with rdfs:label "skeletal element of eye region”. When users search for terms, I append a “*” to their input text by default. However this is failing when the label contains a stopword like “of”. So, searching with “skeletal element of” and “skeletal element*” do find the term as a match, but “skeletal element of*” does not. Can I disable stopwords entirely? >> > > >> > > Thanks, >> > > Jim >> > > >> > > >> > > ------------------------------------------------------------------------------ >> > > _______________________________________________ >> > > 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> >> > > >> > > >> > > >> > > -- >> > > _______________ >> > > Brad Bebee >> > > CEO, Managing Partner >> > > SYSTAP, LLC >> > > e: be...@sy... <mailto:be...@sy...> >> > > m: 202.642.7961 <tel:202.642.7961> >> > > f: 571.367.5000 <tel:571.367.5000> >> > > w: www.blazegraph.com <http://www.blazegraph.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. >> > > >> > > >> > >> > >> > >> > >> > -- >> > _______________ >> > Brad Bebee >> > CEO, Managing Partner >> > SYSTAP, LLC >> > e: be...@sy... <mailto:be...@sy...> >> > m: 202.642.7961 <tel:202.642.7961> >> > f: 571.367.5000 <tel:571.367.5000> >> > w: www.blazegraph.com <http://www.blazegraph.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. >> > >> > >> >> >> >> >> -- >> _______________ >> Brad Bebee >> CEO, Managing Partner >> SYSTAP, LLC >> e: be...@sy... <mailto:be...@sy...> >> m: 202.642.7961 <tel:202.642.7961> >> f: 571.367.5000 <tel:571.367.5000> >> w: www.blazegraph.com <http://www.blazegraph.com/> >> >> Blazegraph™ <http://www.blazegraph.com/> is our ultra high-performance graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints APIs. Mapgraph™ <http://www.systap.com/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. >> >> > > > ------------------------------------------------------------------------------ > > _______________________________________________ > 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: Johannes F. <joh...@st...> - 2015-12-11 13:02:15
|
Hello, I'm facing the following problems with RDR using blazegraph Build Version 1.5.3. CASE 1 and CASE 2 are major problems. CASE 3 is just a SPARQL* parser issue and there is a workaround by using BIND statements instead. In CASE 1 I want to reify a reified statement. In the SPARQL* paper (referenced on the RDR wiki site) the EBNF definition of a TRefPattern is recursive. And there is a explicit note on nested triple reference patterns. So this should work. Querying such triple data using BIND statements works (more precisely: there are no errors), but unfortunately I don't know how to import data consisting of nested reified triples. Nesting the "<< >>"-statements doesn't work, neither in Turtle* nor in SPARQL*. In CASE 2 I want to use SPARQL update to insert or remove a simple reified statement. But it seems that this not implemented in blazegraph, because it's rejecting a bunch of queries due to parser errors. But then my question is: How to remove or change a reified triple statement? I'm considering to use blazegraph for large scale use, so deleting the whole KB and reimporting it is not feasible. I appreciate any help you can provide. Regards Johannes =================== SPARQL* - CASE 1 ============================= Prefix : <http://example.org/ns#> Select * where { BIND( <<:Bob :isMarriedTo :Alice >> as ?t) . BIND( <<?t :validUntil "2015-12-01" >> as ?t2) . ?t2 :crawledOn "2015-12-07" . } =================== Turtle* - CASE 1 ============================= ****NOT WORKING**** @prefix : <http://example.org/ns#> . << <<:Bob :isMarriedTo :Alice >> :validUntil "2015-12-01" >> :crawledOn "2015-12-07" =================== SPARQL* - CASE 2a) b) c) d) ============================= ****NOT WORKING**** a) ***** Prefix : <http://example.org/ns#> INSERT DATA { <<:Bob :isMarriedTo :Alice>> :validUntil "2015-12-01". } ****NOT WORKING**** b) ***** Prefix : <http://example.org/ns#> INSERT { <<:Bob :isMarriedTo :Alice>> :validUntil "2015-12-01". } WHERE {} ****NOT WORKING**** c) ***** Prefix : <http://example.org/ns#> DELETE { <<:Bob :isMarriedTo :Alice>> :validUntil "2015-12-01". } WHERE {} ****NOT WORKING**** d) ***** Prefix : <http://example.org/ns#> DELETE { BIND( <<:Bob :isMarriedTo :Alice >> as ?t) . ?t :validUntil "2015-12-01". } WHERE {} =================== SPARQL* - CASE 3 ============================= ****NOT WORKING**** Prefix : <http://example.org/ns#> Select * where { <<:Bob :isMarriedTo :Alice>> ?x <<:a :b :c>> . } =================== Turtle* - CASE 3 ============================= ****BUT WORKING in Turtle* **** @prefix : <http://example.org/ns#> . <<:Bob :isMarriedTo :Alice >> :x <<:a :b :c>> . |
|
From: Bryan T. <br...@sy...> - 2015-12-10 22:41:58
|
I suggest either applying a debugger or creating a unit test that replicates the issue and filing a ticket and attaching the test. You should be able to configure any aspect of the tokenization behavior. I would also try a namespace specific override. E.g., com.bigdata.*foo.lex.*search.ConfigurableAnalyzerFactory.stopwords=none > Thanks, Bryan On Thu, Dec 10, 2015 at 4:55 PM, Jim Balhoff <ba...@gm...> wrote: > Yes, I am deleting the journal file and reloading in between attempts. > > Thanks, > Jim > > On Dec 10, 2015, at 4:50 PM, Brad Bebee <be...@sy...> wrote: > > Jim, > > Did you reload the namespace after the configuration change? > > Thanks, --Brad > > On Thu, Dec 10, 2015 at 4:38 PM, Jim Balhoff <ba...@gm...> wrote: > >> I had tried some similar syntax, but wasn’t sure how it should look. I >> just tried the form you suggested and it did not have an affect on >> stopwords. They seem to still be active, because if my search input is >> simply “of”, I get this message: >> >> WARN : FullTextIndex.java:1052: No terms after stopword extraction: >> query=com.bigdata.rdf.lexicon.ITextIndexer$FullTextQuery@7aef6039 >> >> Thanks, >> Jim >> >> >> > On Dec 9, 2015, at 11:34 PM, Brad Bebee <be...@sy...> wrote: >> > >> > Jim, >> > >> > Thank you. Have you tried configuring your journal with the property >> below? >> > >> > com.bigdata.search.ConfigurableAnalyzerFactory.stopwords=none >> > >> > >> > >> > Thanks, --Brad >> > >> > >> > On Wed, Dec 9, 2015 at 9:36 AM, Jim Balhoff <ba...@gm...> wrote: >> > Hi Brad, >> > >> > I see, I can look into providing my own implementation. I got the >> impression from the JavaDoc that I could provide config options to modify >> the behavior of some of the analyzers. I have been looking at these pages: >> > >> > >> https://www.blazegraph.com/docs/api/com/bigdata/search/ConfigurableAnalyzerFactory.AnalyzerOptions.html#STOPWORDS_VALUE_NONE >> > https://www.blazegraph.com/docs/api/constant-values.html >> > >> > I also tried to switch from the default analyzer to the >> TermCompletionAnalyzer, but haven’t been able to get the property value set >> correctly for “wordBoundary” in the config file. >> > >> > Understanding how to translate option constants from the JavaDoc into >> correctly written config file properties has been a challenge. It would be >> really helpful to have more of those spelled out on the wiki. >> > >> > Thanks! >> > Jim >> > >> > > On Dec 8, 2015, at 9:54 PM, Brad Bebee <be...@sy...> wrote: >> > > >> > > Jim, >> > > >> > > I believe you could do this by overriding the Analyzer Factory Class >> [1] with your own implementation that does not filter stopwords [2]. Other >> may have more specific suggestions. >> > > >> > > [1] >> https://www.blazegraph.com/docs/api/com/bigdata/search/FullTextIndex.Options.html#ANALYZER_FACTORY_CLASS >> > > >> > > [2] >> https://www.blazegraph.com/docs/api/com/bigdata/search/IAnalyzerFactory.html >> > > >> > > Thanks, --Brad >> > > >> > > On Tue, Dec 8, 2015 at 9:12 PM, Jim Balhoff <ba...@gm...> >> wrote: >> > > Hi, >> > > >> > > I was wondering if anyone could provide examples for how to set up >> the Blazegraph properties file to configure options for the full text >> search. I have looked through the various options in the JavaDoc, but I >> can’t quite figure out the right properties file syntax for >> ‘stopwords=none’. Here is what I am trying to do: >> > > >> > > I have a term in the database with rdfs:label "skeletal element of >> eye region”. When users search for terms, I append a “*” to their input >> text by default. However this is failing when the label contains a stopword >> like “of”. So, searching with “skeletal element of” and “skeletal element*” >> do find the term as a match, but “skeletal element of*” does not. Can I >> disable stopwords entirely? >> > > >> > > Thanks, >> > > Jim >> > > >> > > >> > > >> ------------------------------------------------------------------------------ >> > > _______________________________________________ >> > > Bigdata-developers mailing list >> > > Big...@li... >> > > https://lists.sourceforge.net/lists/listinfo/bigdata-developers >> > > >> > > >> > > >> > > -- >> > > _______________ >> > > Brad Bebee >> > > CEO, Managing Partner >> > > SYSTAP, LLC >> > > e: be...@sy... >> > > m: 202.642.7961 >> > > f: 571.367.5000 >> > > w: www.blazegraph.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. > > >> > > >> > >> > >> > >> > >> > -- >> > _______________ >> > Brad Bebee >> > CEO, Managing Partner >> > SYSTAP, LLC >> > e: be...@sy... >> > m: 202.642.7961 >> > f: 571.367.5000 >> > w: www.blazegraph.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. > >> > >> >> > > > -- > _______________ > Brad Bebee > CEO, Managing Partner > SYSTAP, LLC > e: be...@sy... > m: 202.642.7961 > f: 571.367.5000 > w: www.blazegraph.com > > Blazegraph™ <http://www.blazegraph.com/> is our ultra high-performance > graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints > APIs. Mapgraph™ <http://www.systap.com/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. > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Bigdata-developers mailing list > Big...@li... > https://lists.sourceforge.net/lists/listinfo/bigdata-developers > > |
|
From: Bryan T. <br...@sy...> - 2015-12-10 22:10:17
|
Are you rebuilding the index? The tokenization of the words in the literals and their entry into the index occurs during data loading. There is some manual code to drop/add the index. If you change this property for an existing namespace, you need to cause the property to become durable (BigdataSailHelper.setProperty()), and then drop/add the index. We are adding more support for text index rebuilds now. I am not sure if it will be in the 2.0 release or not yet. Bryan ---- Bryan Thompson Chief Scientist & Founder SYSTAP, LLC 4501 Tower Road Greensboro, NC 27410 br...@sy... 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. 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, Dec 10, 2015 at 4:38 PM, Jim Balhoff <ba...@gm...> wrote: > I had tried some similar syntax, but wasn’t sure how it should look. I > just tried the form you suggested and it did not have an affect on > stopwords. They seem to still be active, because if my search input is > simply “of”, I get this message: > > WARN : FullTextIndex.java:1052: No terms after stopword extraction: > query=com.bigdata.rdf.lexicon.ITextIndexer$FullTextQuery@7aef6039 > > Thanks, > Jim > > > > On Dec 9, 2015, at 11:34 PM, Brad Bebee <be...@sy...> wrote: > > > > Jim, > > > > Thank you. Have you tried configuring your journal with the property > below? > > > > com.bigdata.search.ConfigurableAnalyzerFactory.stopwords=none > > > > > > > > Thanks, --Brad > > > > > > On Wed, Dec 9, 2015 at 9:36 AM, Jim Balhoff <ba...@gm...> wrote: > > Hi Brad, > > > > I see, I can look into providing my own implementation. I got the > impression from the JavaDoc that I could provide config options to modify > the behavior of some of the analyzers. I have been looking at these pages: > > > > > https://www.blazegraph.com/docs/api/com/bigdata/search/ConfigurableAnalyzerFactory.AnalyzerOptions.html#STOPWORDS_VALUE_NONE > > https://www.blazegraph.com/docs/api/constant-values.html > > > > I also tried to switch from the default analyzer to the > TermCompletionAnalyzer, but haven’t been able to get the property value set > correctly for “wordBoundary” in the config file. > > > > Understanding how to translate option constants from the JavaDoc into > correctly written config file properties has been a challenge. It would be > really helpful to have more of those spelled out on the wiki. > > > > Thanks! > > Jim > > > > > On Dec 8, 2015, at 9:54 PM, Brad Bebee <be...@sy...> wrote: > > > > > > Jim, > > > > > > I believe you could do this by overriding the Analyzer Factory Class > [1] with your own implementation that does not filter stopwords [2]. Other > may have more specific suggestions. > > > > > > [1] > https://www.blazegraph.com/docs/api/com/bigdata/search/FullTextIndex.Options.html#ANALYZER_FACTORY_CLASS > > > > > > [2] > https://www.blazegraph.com/docs/api/com/bigdata/search/IAnalyzerFactory.html > > > > > > Thanks, --Brad > > > > > > On Tue, Dec 8, 2015 at 9:12 PM, Jim Balhoff <ba...@gm...> wrote: > > > Hi, > > > > > > I was wondering if anyone could provide examples for how to set up the > Blazegraph properties file to configure options for the full text search. I > have looked through the various options in the JavaDoc, but I can’t quite > figure out the right properties file syntax for ‘stopwords=none’. Here is > what I am trying to do: > > > > > > I have a term in the database with rdfs:label "skeletal element of eye > region”. When users search for terms, I append a “*” to their input text by > default. However this is failing when the label contains a stopword like > “of”. So, searching with “skeletal element of” and “skeletal element*” do > find the term as a match, but “skeletal element of*” does not. Can I > disable stopwords entirely? > > > > > > Thanks, > > > Jim > > > > > > > > > > ------------------------------------------------------------------------------ > > > _______________________________________________ > > > Bigdata-developers mailing list > > > Big...@li... > > > https://lists.sourceforge.net/lists/listinfo/bigdata-developers > > > > > > > > > > > > -- > > > _______________ > > > Brad Bebee > > > CEO, Managing Partner > > > SYSTAP, LLC > > > e: be...@sy... > > > m: 202.642.7961 > > > f: 571.367.5000 > > > w: www.blazegraph.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. > > > > > > > > > > > > > > > -- > > _______________ > > Brad Bebee > > CEO, Managing Partner > > SYSTAP, LLC > > e: be...@sy... > > m: 202.642.7961 > > f: 571.367.5000 > > w: www.blazegraph.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. > > > > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Bigdata-developers mailing list > Big...@li... > https://lists.sourceforge.net/lists/listinfo/bigdata-developers > |
|
From: Jim B. <ba...@gm...> - 2015-12-10 21:55:21
|
Yes, I am deleting the journal file and reloading in between attempts. Thanks, Jim > On Dec 10, 2015, at 4:50 PM, Brad Bebee <be...@sy...> wrote: > > Jim, > > Did you reload the namespace after the configuration change? > > Thanks, --Brad > > On Thu, Dec 10, 2015 at 4:38 PM, Jim Balhoff <ba...@gm... <mailto:ba...@gm...>> wrote: > I had tried some similar syntax, but wasn’t sure how it should look. I just tried the form you suggested and it did not have an affect on stopwords. They seem to still be active, because if my search input is simply “of”, I get this message: > > WARN : FullTextIndex.java:1052: No terms after stopword extraction: query=com.bigdata.rdf.lexicon.ITextIndexer$FullTextQuery@7aef6039 > > Thanks, > Jim > > > > On Dec 9, 2015, at 11:34 PM, Brad Bebee <be...@sy... <mailto:be...@sy...>> wrote: > > > > Jim, > > > > Thank you. Have you tried configuring your journal with the property below? > > > > com.bigdata.search.ConfigurableAnalyzerFactory.stopwords=none > > > > > > > > Thanks, --Brad > > > > > > On Wed, Dec 9, 2015 at 9:36 AM, Jim Balhoff <ba...@gm... <mailto:ba...@gm...>> wrote: > > Hi Brad, > > > > I see, I can look into providing my own implementation. I got the impression from the JavaDoc that I could provide config options to modify the behavior of some of the analyzers. I have been looking at these pages: > > > > https://www.blazegraph.com/docs/api/com/bigdata/search/ConfigurableAnalyzerFactory.AnalyzerOptions.html#STOPWORDS_VALUE_NONE <https://www.blazegraph.com/docs/api/com/bigdata/search/ConfigurableAnalyzerFactory.AnalyzerOptions.html#STOPWORDS_VALUE_NONE> > > https://www.blazegraph.com/docs/api/constant-values.html <https://www.blazegraph.com/docs/api/constant-values.html> > > > > I also tried to switch from the default analyzer to the TermCompletionAnalyzer, but haven’t been able to get the property value set correctly for “wordBoundary” in the config file. > > > > Understanding how to translate option constants from the JavaDoc into correctly written config file properties has been a challenge. It would be really helpful to have more of those spelled out on the wiki. > > > > Thanks! > > Jim > > > > > On Dec 8, 2015, at 9:54 PM, Brad Bebee <be...@sy... <mailto:be...@sy...>> wrote: > > > > > > Jim, > > > > > > I believe you could do this by overriding the Analyzer Factory Class [1] with your own implementation that does not filter stopwords [2]. Other may have more specific suggestions. > > > > > > [1] https://www.blazegraph.com/docs/api/com/bigdata/search/FullTextIndex.Options.html#ANALYZER_FACTORY_CLASS <https://www.blazegraph.com/docs/api/com/bigdata/search/FullTextIndex.Options.html#ANALYZER_FACTORY_CLASS> > > > > > > [2] https://www.blazegraph.com/docs/api/com/bigdata/search/IAnalyzerFactory.html <https://www.blazegraph.com/docs/api/com/bigdata/search/IAnalyzerFactory.html> > > > > > > Thanks, --Brad > > > > > > On Tue, Dec 8, 2015 at 9:12 PM, Jim Balhoff <ba...@gm... <mailto:ba...@gm...>> wrote: > > > Hi, > > > > > > I was wondering if anyone could provide examples for how to set up the Blazegraph properties file to configure options for the full text search. I have looked through the various options in the JavaDoc, but I can’t quite figure out the right properties file syntax for ‘stopwords=none’. Here is what I am trying to do: > > > > > > I have a term in the database with rdfs:label "skeletal element of eye region”. When users search for terms, I append a “*” to their input text by default. However this is failing when the label contains a stopword like “of”. So, searching with “skeletal element of” and “skeletal element*” do find the term as a match, but “skeletal element of*” does not. Can I disable stopwords entirely? > > > > > > Thanks, > > > Jim > > > > > > > > > ------------------------------------------------------------------------------ > > > _______________________________________________ > > > 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> > > > > > > > > > > > > -- > > > _______________ > > > Brad Bebee > > > CEO, Managing Partner > > > SYSTAP, LLC > > > e: be...@sy... <mailto:be...@sy...> > > > m: 202.642.7961 <tel:202.642.7961> > > > f: 571.367.5000 <tel:571.367.5000> > > > w: www.blazegraph.com <http://www.blazegraph.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. > > > > > > > > > > > > > > > > -- > > _______________ > > Brad Bebee > > CEO, Managing Partner > > SYSTAP, LLC > > e: be...@sy... <mailto:be...@sy...> > > m: 202.642.7961 <tel:202.642.7961> > > f: 571.367.5000 <tel:571.367.5000> > > w: www.blazegraph.com <http://www.blazegraph.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. > > > > > > > > > -- > _______________ > Brad Bebee > CEO, Managing Partner > SYSTAP, LLC > e: be...@sy... <mailto:be...@sy...> > m: 202.642.7961 > f: 571.367.5000 > w: www.blazegraph.com <http://www.blazegraph.com/> > > Blazegraph™ <http://www.blazegraph.com/> is our ultra high-performance graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints APIs. Mapgraph™ <http://www.systap.com/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. > > |
|
From: Brad B. <be...@sy...> - 2015-12-10 21:50:39
|
Jim, Did you reload the namespace after the configuration change? Thanks, --Brad On Thu, Dec 10, 2015 at 4:38 PM, Jim Balhoff <ba...@gm...> wrote: > I had tried some similar syntax, but wasn’t sure how it should look. I > just tried the form you suggested and it did not have an affect on > stopwords. They seem to still be active, because if my search input is > simply “of”, I get this message: > > WARN : FullTextIndex.java:1052: No terms after stopword extraction: > query=com.bigdata.rdf.lexicon.ITextIndexer$FullTextQuery@7aef6039 > > Thanks, > Jim > > > > On Dec 9, 2015, at 11:34 PM, Brad Bebee <be...@sy...> wrote: > > > > Jim, > > > > Thank you. Have you tried configuring your journal with the property > below? > > > > com.bigdata.search.ConfigurableAnalyzerFactory.stopwords=none > > > > > > > > Thanks, --Brad > > > > > > On Wed, Dec 9, 2015 at 9:36 AM, Jim Balhoff <ba...@gm...> wrote: > > Hi Brad, > > > > I see, I can look into providing my own implementation. I got the > impression from the JavaDoc that I could provide config options to modify > the behavior of some of the analyzers. I have been looking at these pages: > > > > > https://www.blazegraph.com/docs/api/com/bigdata/search/ConfigurableAnalyzerFactory.AnalyzerOptions.html#STOPWORDS_VALUE_NONE > > https://www.blazegraph.com/docs/api/constant-values.html > > > > I also tried to switch from the default analyzer to the > TermCompletionAnalyzer, but haven’t been able to get the property value set > correctly for “wordBoundary” in the config file. > > > > Understanding how to translate option constants from the JavaDoc into > correctly written config file properties has been a challenge. It would be > really helpful to have more of those spelled out on the wiki. > > > > Thanks! > > Jim > > > > > On Dec 8, 2015, at 9:54 PM, Brad Bebee <be...@sy...> wrote: > > > > > > Jim, > > > > > > I believe you could do this by overriding the Analyzer Factory Class > [1] with your own implementation that does not filter stopwords [2]. Other > may have more specific suggestions. > > > > > > [1] > https://www.blazegraph.com/docs/api/com/bigdata/search/FullTextIndex.Options.html#ANALYZER_FACTORY_CLASS > > > > > > [2] > https://www.blazegraph.com/docs/api/com/bigdata/search/IAnalyzerFactory.html > > > > > > Thanks, --Brad > > > > > > On Tue, Dec 8, 2015 at 9:12 PM, Jim Balhoff <ba...@gm...> wrote: > > > Hi, > > > > > > I was wondering if anyone could provide examples for how to set up the > Blazegraph properties file to configure options for the full text search. I > have looked through the various options in the JavaDoc, but I can’t quite > figure out the right properties file syntax for ‘stopwords=none’. Here is > what I am trying to do: > > > > > > I have a term in the database with rdfs:label "skeletal element of eye > region”. When users search for terms, I append a “*” to their input text by > default. However this is failing when the label contains a stopword like > “of”. So, searching with “skeletal element of” and “skeletal element*” do > find the term as a match, but “skeletal element of*” does not. Can I > disable stopwords entirely? > > > > > > Thanks, > > > Jim > > > > > > > > > > ------------------------------------------------------------------------------ > > > _______________________________________________ > > > Bigdata-developers mailing list > > > Big...@li... > > > https://lists.sourceforge.net/lists/listinfo/bigdata-developers > > > > > > > > > > > > -- > > > _______________ > > > Brad Bebee > > > CEO, Managing Partner > > > SYSTAP, LLC > > > e: be...@sy... > > > m: 202.642.7961 > > > f: 571.367.5000 > > > w: www.blazegraph.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. > > > > > > > > > > > > > > > -- > > _______________ > > Brad Bebee > > CEO, Managing Partner > > SYSTAP, LLC > > e: be...@sy... > > m: 202.642.7961 > > f: 571.367.5000 > > w: www.blazegraph.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. > > > > > -- _______________ Brad Bebee CEO, Managing Partner SYSTAP, LLC e: be...@sy... m: 202.642.7961 f: 571.367.5000 w: www.blazegraph.com Blazegraph™ <http://www.blazegraph.com> is our ultra high-performance graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints APIs. Mapgraph™ <http://www.systap.com/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. |
|
From: Jim B. <ba...@gm...> - 2015-12-10 21:38:44
|
I had tried some similar syntax, but wasn’t sure how it should look. I just tried the form you suggested and it did not have an affect on stopwords. They seem to still be active, because if my search input is simply “of”, I get this message: WARN : FullTextIndex.java:1052: No terms after stopword extraction: query=com.bigdata.rdf.lexicon.ITextIndexer$FullTextQuery@7aef6039 Thanks, Jim > On Dec 9, 2015, at 11:34 PM, Brad Bebee <be...@sy...> wrote: > > Jim, > > Thank you. Have you tried configuring your journal with the property below? > > com.bigdata.search.ConfigurableAnalyzerFactory.stopwords=none > > > > Thanks, --Brad > > > On Wed, Dec 9, 2015 at 9:36 AM, Jim Balhoff <ba...@gm...> wrote: > Hi Brad, > > I see, I can look into providing my own implementation. I got the impression from the JavaDoc that I could provide config options to modify the behavior of some of the analyzers. I have been looking at these pages: > > https://www.blazegraph.com/docs/api/com/bigdata/search/ConfigurableAnalyzerFactory.AnalyzerOptions.html#STOPWORDS_VALUE_NONE > https://www.blazegraph.com/docs/api/constant-values.html > > I also tried to switch from the default analyzer to the TermCompletionAnalyzer, but haven’t been able to get the property value set correctly for “wordBoundary” in the config file. > > Understanding how to translate option constants from the JavaDoc into correctly written config file properties has been a challenge. It would be really helpful to have more of those spelled out on the wiki. > > Thanks! > Jim > > > On Dec 8, 2015, at 9:54 PM, Brad Bebee <be...@sy...> wrote: > > > > Jim, > > > > I believe you could do this by overriding the Analyzer Factory Class [1] with your own implementation that does not filter stopwords [2]. Other may have more specific suggestions. > > > > [1] https://www.blazegraph.com/docs/api/com/bigdata/search/FullTextIndex.Options.html#ANALYZER_FACTORY_CLASS > > > > [2] https://www.blazegraph.com/docs/api/com/bigdata/search/IAnalyzerFactory.html > > > > Thanks, --Brad > > > > On Tue, Dec 8, 2015 at 9:12 PM, Jim Balhoff <ba...@gm...> wrote: > > Hi, > > > > I was wondering if anyone could provide examples for how to set up the Blazegraph properties file to configure options for the full text search. I have looked through the various options in the JavaDoc, but I can’t quite figure out the right properties file syntax for ‘stopwords=none’. Here is what I am trying to do: > > > > I have a term in the database with rdfs:label "skeletal element of eye region”. When users search for terms, I append a “*” to their input text by default. However this is failing when the label contains a stopword like “of”. So, searching with “skeletal element of” and “skeletal element*” do find the term as a match, but “skeletal element of*” does not. Can I disable stopwords entirely? > > > > Thanks, > > Jim > > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > > Bigdata-developers mailing list > > Big...@li... > > https://lists.sourceforge.net/lists/listinfo/bigdata-developers > > > > > > > > -- > > _______________ > > Brad Bebee > > CEO, Managing Partner > > SYSTAP, LLC > > e: be...@sy... > > m: 202.642.7961 > > f: 571.367.5000 > > w: www.blazegraph.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. > > > > > > > > > -- > _______________ > Brad Bebee > CEO, Managing Partner > SYSTAP, LLC > e: be...@sy... > m: 202.642.7961 > f: 571.367.5000 > w: www.blazegraph.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. > > |
|
From: Brad B. <be...@sy...> - 2015-12-10 04:56:29
|
Hello Blazegraphers, JIRA's back. Cheers, --Brad On Wed, Dec 9, 2015 at 9:34 PM, Brad Bebee <be...@sy...> wrote: > Hello Blazegraphers, > > JIRA will be down for some unscheduled maintenance for the next hour or so. > > Cheers, --Brad > > -- > _______________ > Brad Bebee > CEO, Managing Partner > SYSTAP, LLC > e: be...@sy... > m: 202.642.7961 > f: 571.367.5000 > w: www.blazegraph.com > > Blazegraph™ <http://www.blazegraph.com> is our ultra high-performance > graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints > APIs. Mapgraph™ <http://www.systap.com/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. > -- _______________ Brad Bebee CEO, Managing Partner SYSTAP, LLC e: be...@sy... m: 202.642.7961 f: 571.367.5000 w: www.blazegraph.com Blazegraph™ <http://www.blazegraph.com> is our ultra high-performance graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints APIs. Mapgraph™ <http://www.systap.com/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. |
|
From: Brad B. <be...@sy...> - 2015-12-10 04:34:08
|
Jim, Thank you. Have you tried configuring your journal with the property below? com.bigdata.search.ConfigurableAnalyzerFactory.stopwords=none Thanks, --Brad On Wed, Dec 9, 2015 at 9:36 AM, Jim Balhoff <ba...@gm...> wrote: > Hi Brad, > > I see, I can look into providing my own implementation. I got the > impression from the JavaDoc that I could provide config options to modify > the behavior of some of the analyzers. I have been looking at these pages: > > > https://www.blazegraph.com/docs/api/com/bigdata/search/ConfigurableAnalyzerFactory.AnalyzerOptions.html#STOPWORDS_VALUE_NONE > https://www.blazegraph.com/docs/api/constant-values.html > > I also tried to switch from the default analyzer to the > TermCompletionAnalyzer, but haven’t been able to get the property value set > correctly for “wordBoundary” in the config file. > > Understanding how to translate option constants from the JavaDoc into > correctly written config file properties has been a challenge. It would be > really helpful to have more of those spelled out on the wiki. > > Thanks! > Jim > > > On Dec 8, 2015, at 9:54 PM, Brad Bebee <be...@sy...> wrote: > > > > Jim, > > > > I believe you could do this by overriding the Analyzer Factory Class [1] > with your own implementation that does not filter stopwords [2]. Other may > have more specific suggestions. > > > > [1] > https://www.blazegraph.com/docs/api/com/bigdata/search/FullTextIndex.Options.html#ANALYZER_FACTORY_CLASS > > > > [2] > https://www.blazegraph.com/docs/api/com/bigdata/search/IAnalyzerFactory.html > > > > Thanks, --Brad > > > > On Tue, Dec 8, 2015 at 9:12 PM, Jim Balhoff <ba...@gm...> wrote: > > Hi, > > > > I was wondering if anyone could provide examples for how to set up the > Blazegraph properties file to configure options for the full text search. I > have looked through the various options in the JavaDoc, but I can’t quite > figure out the right properties file syntax for ‘stopwords=none’. Here is > what I am trying to do: > > > > I have a term in the database with rdfs:label "skeletal element of eye > region”. When users search for terms, I append a “*” to their input text by > default. However this is failing when the label contains a stopword like > “of”. So, searching with “skeletal element of” and “skeletal element*” do > find the term as a match, but “skeletal element of*” does not. Can I > disable stopwords entirely? > > > > Thanks, > > Jim > > > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > > Bigdata-developers mailing list > > Big...@li... > > https://lists.sourceforge.net/lists/listinfo/bigdata-developers > > > > > > > > -- > > _______________ > > Brad Bebee > > CEO, Managing Partner > > SYSTAP, LLC > > e: be...@sy... > > m: 202.642.7961 > > f: 571.367.5000 > > w: www.blazegraph.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. > > > > > -- _______________ Brad Bebee CEO, Managing Partner SYSTAP, LLC e: be...@sy... m: 202.642.7961 f: 571.367.5000 w: www.blazegraph.com Blazegraph™ <http://www.blazegraph.com> is our ultra high-performance graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints APIs. Mapgraph™ <http://www.systap.com/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. |
|
From: Brad B. <be...@sy...> - 2015-12-10 02:34:49
|
Hello Blazegraphers, JIRA will be down for some unscheduled maintenance for the next hour or so. Cheers, --Brad -- _______________ Brad Bebee CEO, Managing Partner SYSTAP, LLC e: be...@sy... m: 202.642.7961 f: 571.367.5000 w: www.blazegraph.com Blazegraph™ <http://www.blazegraph.com> is our ultra high-performance graph database that supports both RDF/SPARQL and Tinkerpop/Blueprints APIs. Mapgraph™ <http://www.systap.com/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. |
|
From: Jim B. <ba...@gm...> - 2015-12-09 14:37:04
|
Hi Brad, I see, I can look into providing my own implementation. I got the impression from the JavaDoc that I could provide config options to modify the behavior of some of the analyzers. I have been looking at these pages: https://www.blazegraph.com/docs/api/com/bigdata/search/ConfigurableAnalyzerFactory.AnalyzerOptions.html#STOPWORDS_VALUE_NONE https://www.blazegraph.com/docs/api/constant-values.html I also tried to switch from the default analyzer to the TermCompletionAnalyzer, but haven’t been able to get the property value set correctly for “wordBoundary” in the config file. Understanding how to translate option constants from the JavaDoc into correctly written config file properties has been a challenge. It would be really helpful to have more of those spelled out on the wiki. Thanks! Jim > On Dec 8, 2015, at 9:54 PM, Brad Bebee <be...@sy...> wrote: > > Jim, > > I believe you could do this by overriding the Analyzer Factory Class [1] with your own implementation that does not filter stopwords [2]. Other may have more specific suggestions. > > [1] https://www.blazegraph.com/docs/api/com/bigdata/search/FullTextIndex.Options.html#ANALYZER_FACTORY_CLASS > > [2] https://www.blazegraph.com/docs/api/com/bigdata/search/IAnalyzerFactory.html > > Thanks, --Brad > > On Tue, Dec 8, 2015 at 9:12 PM, Jim Balhoff <ba...@gm...> wrote: > Hi, > > I was wondering if anyone could provide examples for how to set up the Blazegraph properties file to configure options for the full text search. I have looked through the various options in the JavaDoc, but I can’t quite figure out the right properties file syntax for ‘stopwords=none’. Here is what I am trying to do: > > I have a term in the database with rdfs:label "skeletal element of eye region”. When users search for terms, I append a “*” to their input text by default. However this is failing when the label contains a stopword like “of”. So, searching with “skeletal element of” and “skeletal element*” do find the term as a match, but “skeletal element of*” does not. Can I disable stopwords entirely? > > Thanks, > Jim > > > ------------------------------------------------------------------------------ > _______________________________________________ > Bigdata-developers mailing list > Big...@li... > https://lists.sourceforge.net/lists/listinfo/bigdata-developers > > > > -- > _______________ > Brad Bebee > CEO, Managing Partner > SYSTAP, LLC > e: be...@sy... > m: 202.642.7961 > f: 571.367.5000 > w: www.blazegraph.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. > > |
27 messages has been excluded from this view by a project administrator.
