bigdata-developers — List for bigdata developers

[Bigdata-developers] Adding time out limit for query in a given namespace

[Ghislain A. <ghi...@gm...>]

Hi,
I am struggling to find an easy way to set the time out limit for a given
 namespace using a configuration file or similar.
I've only seen this https://wiki.blazegraph.com/wiki/index.php/REST_API and
I don't understand the difference between the timeout  and
maxQueryTimeMillis.

TIA.
Best,
Ghislain
-- 
-------
"Love all, trust a few, do wrong to none" (W. Shakespeare)
Web: http://atemezing.org

[Bigdata-developers] Blazegraph 2.1.5 RC is available

[Brad B. <be...@sy...>]

Blazegraphers,

The 2.1.5 RC is now available as a 2.1.5-SNAPSHOT on Maven Central and on
Github:
https://github.com/blazegraph/database/releases/tag/BLAZEGRAPH_RELEASE_CANDIDATE_2_1_5
.

2.1.5 is maintenance release for the 2.1.x versions. See the changes on
JIRA: https://jira.blazegraph.com/projects/BLZG/versions/10402.

Please report any issues via JIRA: https://jira.blazegraph.com/

Cheers, --Brad

Re: [Bigdata-developers] Help list - Newbie first question

[Ghislain A. <ghi...@gm...>]

Igor,
Ummmm... I think your syntax does not work, at least on Windows. See the
error here
https://gist.github.com/gatemezing/4c7da5fb727672a1c8de2d0a8eca441e
However, the one I sent you actually works fine (up to now) .

+1 to the suggestion of integrating 'warm-up' phase. I will definitively
include one of the options suggested, at least the first option.

Thanks again.
Ghislain


El lun., 23 ene. 2017 a las 17:17, Igor Kim (<igo...@ms...>) escribió:

> Ghislain,
>
> AFAIK, --data-urlencode could not read data from  file in  the  form
> you've written. Try following syntax
>
> curl -X POST http://localhost:9999/blazegraph/namespace/<mykb>/sparql
> --data-urlencode "query=`cat myQuery.sparql`" --data-urlencode
> 'format=json' -o myQuery.json
>
> Testing pattern usually should follow expected workload. For standard
> application, server does not get restarted often, so it is  'warmed up'
> most  of the  time.
> During warm-up phase query execution  times might differ from main phase,
> so you should  probably add 'warm-up cycle', which is basically execution
> of queries mix which follow same pattern as main  application issues.
> Running 100-200 queries (or applying  workload for  5-10 minutes) would
> warm-up server. After that main  query mix might be  executed. Also note,
> that queries and their order, which were executed during warm-up and main
> stage is important and might reflect in different results. So there are 2
> options: first is to establish fixed mixture of queries for performance
> testing, and the second option is to apply a workload for a longer time to
> get results averaged over time, so particular fluctuations would not impact
> performance measurement. But for the  second option you need to make
> queries varying, to reduce impact from caching.
>
>
> On Mon, Jan 23, 2017 at 4:32 PM, Ghislain ATEMEZING <
> ghi...@gm...> wrote:
>
> Igor, thanks again for the explanations.
> Since I have a lot of queries to do, I'll prefer the cURL option instead.
> I will make an average time of 5 queries, using json header in the POST
> query.
>
> Here is a sample cURL query I am sending:
> curl -i -X POST http://localhost:9999/blazegraph/namespace/<mykb>/sparql
> --data-urlencode 'query@myQuery.sparql' --data-urlencode analytic=true
> -H 'Accept: application/json' > myQuery.json
>
> Would that makes sense?
>
> Best,
>
> El lun., 23 ene. 2017 a las 10:24, Igor Kim (<igo...@ms...>)
> escribió:
>
> Ghislain,
>
> Basically CUrl and Workbench do almost the same thing - issue POST query
> to the server, which should analyze and run it then stream the result back
> to client.
> But upon receiving, curl just stores a stream into a file or logs to
> console, but Workbench has to parse JSON results and show it in a web page,
> which takes additional time.
> Note, that JSON is native format for JavaScript code of the Workbench
> (much easier to parse than XML for example), so using other formats would
> not improve execution time.
>
> The difference will be more obvious for large responses (many rows and
> large literals).
>
> You could use developers console in your browser to see execution times
> (including transport times, but CUrl will count that time as well).
>
> See attached screenshot, the query has taken 52ms while waiting for a
> response start (prepare a query and start its evaluation),
> additional 78ms to get whole result (iterate through the results on server
> and stream it through network using JSON format),
> but the Workbench have taken additional 322ms to parse and prepare results
> for the results table on the web page.
>
> Also, after execution a query on the Workbench, server's file system
> caches index data for a time, so repeating requests to the same query might
> be much faster for subsequent calls using CUrl.
>
> As a workaround you might apply 'limit 50' to evaluate less results (only
> first page), that will reduce overhead time for the Workbench.
>
>
> [image: Inline image 1]
>
> On Mon, Jan 23, 2017 at 1:15 PM, Ghislain ATEMEZING <
> ghi...@gm...> wrote:
>
> Hi Igor,
> Thanks for your answer and sorry if O was not clear enough in my previous
> post. Basically I thought I can get also the time execution of a query with
> the ?explain parameter.
> When comparing the response time of a CUrl in localhost w.r.t the answer
> on the workbench, I notice it's sometimes 10x higher. Is there a way to get
> almost the same result somehow?
>
> Best,
> Ghislain
>
> Sent from my iPhone, may include typos
>
> Le 23 janv. 2017 à 04:51, Igor Kim <igo...@ms...> a écrit :
>
> Ghislain,
>
> ?explain parameter is a rough equivalent of SQL analyze, so there is no
> time of response returned, just a query execution plan explanation.
> Could you expand a little bit on what are you going to use that response
> time? There is a workaround with using UNION or BIND in the query, which
> could provide a timestamp for the results:
>
> for the whole result:
>
> select * from {
>     {
>         ?s ....... # statement pattern and filters
>     }
>     UNION
>     {
>         BIND (now() as ?timestamp) .
>     }
> }
>
> or for each of the rows:
>
> select * from {
>     ?s ....... # statement pattern and filters
>     BIND (now() as ?timestamp) .
> }
>
>
>
>
> On Fri, Jan 20, 2017 at 10:07 PM, Ghislain ATEMEZING <
> ghi...@gm...> wrote:
>
> Many thanks Brad!
> I was looking at the Wiki to see if I can use a parameter in a cUrl
> request to retrieve the time response of a query. I've seen the ?explain
> parameter, but not sure to find the that value in the .html output.
> Is there a way to retrieve that value in a REST-ish  manner?
>
> TIA,
> Ghislain
>
> El vie., 20 ene. 2017 a las 17:14, Brad Bebee (<be...@sy...>)
> escribió:
>
> Ghislain,
>
> Yes, you may use the list for those topics. In general, before posting, we
> recommend checking out the Wiki.
>
> https://wiki.blazegraph.com/wiki/index.php/Main_Page
>
> Thanks, --Brad
>
> On Fri, Jan 20, 2017 at 1:38 AM, Ghislain ATEMEZING <
> ghi...@gm...> wrote:
>
> Hi,
> [Sorry if I am in the wrong list.]
> I am new to blazegraph and I wanted to know if this list also helps for
> issues related to the use of the product, setting up issues and so on.
>
> TIA
> Best,
> Ghislain
> --
> -------
> "Love all, trust a few, do wrong to none" (W. Shakespeare)
> Web: http://atemezing.org
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> 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
>
> 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.
>
> --
> -------
> "Love all, trust a few, do wrong to none" (W. Shakespeare)
> Web: http://atemezing.org
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> 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
>
>
>
>
> --
> *Igor Kim*  | Team Leader / Backend  | Maginfo, Ltd
> Mobile: +7-912-402-4622
>
> --
> -------
> "Love all, trust a few, do wrong to none" (W. Shakespeare)
> Web: http://atemezing.org
>
>
>
>
> --
> *Igor Kim*  | Team Leader / Backend  | Maginfo, Ltd
> Mobile: +7-912-402-4622
>
-- 
-------
"Love all, trust a few, do wrong to none" (W. Shakespeare)
Web: http://atemezing.org

Re: [Bigdata-developers] Help list - Newbie first question

[Igor K. <igo...@ms...>]

Ghislain,

AFAIK, --data-urlencode could not read data from  file in  the  form you've
written. Try following syntax

curl -X POST http://localhost:9999/blazegraph/namespace/<mykb>/sparql
--data-urlencode "query=`cat myQuery.sparql`" --data-urlencode
'format=json' -o myQuery.json

Testing pattern usually should follow expected workload. For standard
application, server does not get restarted often, so it is  'warmed up'
most  of the  time.
During warm-up phase query execution  times might differ from main phase,
so you should  probably add 'warm-up cycle', which is basically execution
of queries mix which follow same pattern as main  application issues.
Running 100-200 queries (or applying  workload for  5-10 minutes) would
warm-up server. After that main  query mix might be  executed. Also note,
that queries and their order, which were executed during warm-up and main
stage is important and might reflect in different results. So there are 2
options: first is to establish fixed mixture of queries for performance
testing, and the second option is to apply a workload for a longer time to
get results averaged over time, so particular fluctuations would not impact
performance measurement. But for the  second option you need to make
queries varying, to reduce impact from caching.


On Mon, Jan 23, 2017 at 4:32 PM, Ghislain ATEMEZING <
ghi...@gm...> wrote:

> Igor, thanks again for the explanations.
> Since I have a lot of queries to do, I'll prefer the cURL option instead.
> I will make an average time of 5 queries, using json header in the POST
> query.
>
> Here is a sample cURL query I am sending:
> curl -i -X POST http://localhost:9999/blazegraph/namespace/<mykb>/sparql
> --data-urlencode 'query@myQuery.sparql' --data-urlencode analytic=true
> -H 'Accept: application/json' > myQuery.json
>
> Would that makes sense?
>
> Best,
>
> El lun., 23 ene. 2017 a las 10:24, Igor Kim (<igo...@ms...>)
> escribió:
>
>> Ghislain,
>>
>> Basically CUrl and Workbench do almost the same thing - issue POST query
>> to the server, which should analyze and run it then stream the result back
>> to client.
>> But upon receiving, curl just stores a stream into a file or logs to
>> console, but Workbench has to parse JSON results and show it in a web page,
>> which takes additional time.
>> Note, that JSON is native format for JavaScript code of the Workbench
>> (much easier to parse than XML for example), so using other formats would
>> not improve execution time.
>>
>> The difference will be more obvious for large responses (many rows and
>> large literals).
>>
>> You could use developers console in your browser to see execution times
>> (including transport times, but CUrl will count that time as well).
>>
>> See attached screenshot, the query has taken 52ms while waiting for a
>> response start (prepare a query and start its evaluation),
>> additional 78ms to get whole result (iterate through the results on
>> server and stream it through network using JSON format),
>> but the Workbench have taken additional 322ms to parse and prepare
>> results for the results table on the web page.
>>
>> Also, after execution a query on the Workbench, server's file system
>> caches index data for a time, so repeating requests to the same query might
>> be much faster for subsequent calls using CUrl.
>>
>> As a workaround you might apply 'limit 50' to evaluate less results (only
>> first page), that will reduce overhead time for the Workbench.
>>
>>
>> [image: Inline image 1]
>>
>> On Mon, Jan 23, 2017 at 1:15 PM, Ghislain ATEMEZING <
>> ghi...@gm...> wrote:
>>
>> Hi Igor,
>> Thanks for your answer and sorry if O was not clear enough in my previous
>> post. Basically I thought I can get also the time execution of a query with
>> the ?explain parameter.
>> When comparing the response time of a CUrl in localhost w.r.t the answer
>> on the workbench, I notice it's sometimes 10x higher. Is there a way to get
>> almost the same result somehow?
>>
>> Best,
>> Ghislain
>>
>> Sent from my iPhone, may include typos
>>
>> Le 23 janv. 2017 à 04:51, Igor Kim <igo...@ms...> a écrit :
>>
>> Ghislain,
>>
>> ?explain parameter is a rough equivalent of SQL analyze, so there is no
>> time of response returned, just a query execution plan explanation.
>> Could you expand a little bit on what are you going to use that response
>> time? There is a workaround with using UNION or BIND in the query, which
>> could provide a timestamp for the results:
>>
>> for the whole result:
>>
>> select * from {
>>     {
>>         ?s ....... # statement pattern and filters
>>     }
>>     UNION
>>     {
>>         BIND (now() as ?timestamp) .
>>     }
>> }
>>
>> or for each of the rows:
>>
>> select * from {
>>     ?s ....... # statement pattern and filters
>>     BIND (now() as ?timestamp) .
>> }
>>
>>
>>
>>
>> On Fri, Jan 20, 2017 at 10:07 PM, Ghislain ATEMEZING <
>> ghi...@gm...> wrote:
>>
>> Many thanks Brad!
>> I was looking at the Wiki to see if I can use a parameter in a cUrl
>> request to retrieve the time response of a query. I've seen the ?explain
>> parameter, but not sure to find the that value in the .html output.
>> Is there a way to retrieve that value in a REST-ish  manner?
>>
>> TIA,
>> Ghislain
>>
>> El vie., 20 ene. 2017 a las 17:14, Brad Bebee (<be...@sy...>)
>> escribió:
>>
>> Ghislain,
>>
>> Yes, you may use the list for those topics. In general, before posting,
>> we recommend checking out the Wiki.
>>
>> https://wiki.blazegraph.com/wiki/index.php/Main_Page
>>
>> Thanks, --Brad
>>
>> On Fri, Jan 20, 2017 at 1:38 AM, Ghislain ATEMEZING <
>> ghi...@gm...> wrote:
>>
>> Hi,
>> [Sorry if I am in the wrong list.]
>> I am new to blazegraph and I wanted to know if this list also helps for
>> issues related to the use of the product, setting up issues and so on.
>>
>> TIA
>> Best,
>> Ghislain
>> --
>> -------
>> "Love all, trust a few, do wrong to none" (W. Shakespeare)
>> Web: http://atemezing.org
>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>> _______________________________________________
>> 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
>>
>> 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.
>>
>> --
>> -------
>> "Love all, trust a few, do wrong to none" (W. Shakespeare)
>> Web: http://atemezing.org
>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>> _______________________________________________
>> 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
>>
>>
>>
>>
>> --
>> *Igor Kim*  | Team Leader / Backend  | Maginfo, Ltd
>> Mobile: +7-912-402-4622
>>
> --
> -------
> "Love all, trust a few, do wrong to none" (W. Shakespeare)
> Web: http://atemezing.org
>



-- 
*Igor Kim*  | Team Leader / Backend  | Maginfo, Ltd
Mobile: +7-912-402-4622

Re: [Bigdata-developers] Help list - Newbie first question

[Ghislain A. <ghi...@gm...>]

Igor, thanks again for the explanations.
Since I have a lot of queries to do, I'll prefer the cURL option instead.
I will make an average time of 5 queries, using json header in the POST
query.

Here is a sample cURL query I am sending:
curl -i -X POST http://localhost:9999/blazegraph/namespace/<mykb>/sparql
--data-urlencode 'query@myQuery.sparql' --data-urlencode analytic=true   -H
'Accept: application/json' > myQuery.json

Would that makes sense?

Best,

El lun., 23 ene. 2017 a las 10:24, Igor Kim (<igo...@ms...>) escribió:

> Ghislain,
>
> Basically CUrl and Workbench do almost the same thing - issue POST query
> to the server, which should analyze and run it then stream the result back
> to client.
> But upon receiving, curl just stores a stream into a file or logs to
> console, but Workbench has to parse JSON results and show it in a web page,
> which takes additional time.
> Note, that JSON is native format for JavaScript code of the Workbench
> (much easier to parse than XML for example), so using other formats would
> not improve execution time.
>
> The difference will be more obvious for large responses (many rows and
> large literals).
>
> You could use developers console in your browser to see execution times
> (including transport times, but CUrl will count that time as well).
>
> See attached screenshot, the query has taken 52ms while waiting for a
> response start (prepare a query and start its evaluation),
> additional 78ms to get whole result (iterate through the results on server
> and stream it through network using JSON format),
> but the Workbench have taken additional 322ms to parse and prepare results
> for the results table on the web page.
>
> Also, after execution a query on the Workbench, server's file system
> caches index data for a time, so repeating requests to the same query might
> be much faster for subsequent calls using CUrl.
>
> As a workaround you might apply 'limit 50' to evaluate less results (only
> first page), that will reduce overhead time for the Workbench.
>
>
> [image: Inline image 1]
>
> On Mon, Jan 23, 2017 at 1:15 PM, Ghislain ATEMEZING <
> ghi...@gm...> wrote:
>
> Hi Igor,
> Thanks for your answer and sorry if O was not clear enough in my previous
> post. Basically I thought I can get also the time execution of a query with
> the ?explain parameter.
> When comparing the response time of a CUrl in localhost w.r.t the answer
> on the workbench, I notice it's sometimes 10x higher. Is there a way to get
> almost the same result somehow?
>
> Best,
> Ghislain
>
> Sent from my iPhone, may include typos
>
> Le 23 janv. 2017 à 04:51, Igor Kim <igo...@ms...> a écrit :
>
> Ghislain,
>
> ?explain parameter is a rough equivalent of SQL analyze, so there is no
> time of response returned, just a query execution plan explanation.
> Could you expand a little bit on what are you going to use that response
> time? There is a workaround with using UNION or BIND in the query, which
> could provide a timestamp for the results:
>
> for the whole result:
>
> select * from {
>     {
>         ?s ....... # statement pattern and filters
>     }
>     UNION
>     {
>         BIND (now() as ?timestamp) .
>     }
> }
>
> or for each of the rows:
>
> select * from {
>     ?s ....... # statement pattern and filters
>     BIND (now() as ?timestamp) .
> }
>
>
>
>
> On Fri, Jan 20, 2017 at 10:07 PM, Ghislain ATEMEZING <
> ghi...@gm...> wrote:
>
> Many thanks Brad!
> I was looking at the Wiki to see if I can use a parameter in a cUrl
> request to retrieve the time response of a query. I've seen the ?explain
> parameter, but not sure to find the that value in the .html output.
> Is there a way to retrieve that value in a REST-ish  manner?
>
> TIA,
> Ghislain
>
> El vie., 20 ene. 2017 a las 17:14, Brad Bebee (<be...@sy...>)
> escribió:
>
> Ghislain,
>
> Yes, you may use the list for those topics. In general, before posting, we
> recommend checking out the Wiki.
>
> https://wiki.blazegraph.com/wiki/index.php/Main_Page
>
> Thanks, --Brad
>
> On Fri, Jan 20, 2017 at 1:38 AM, Ghislain ATEMEZING <
> ghi...@gm...> wrote:
>
> Hi,
> [Sorry if I am in the wrong list.]
> I am new to blazegraph and I wanted to know if this list also helps for
> issues related to the use of the product, setting up issues and so on.
>
> TIA
> Best,
> Ghislain
> --
> -------
> "Love all, trust a few, do wrong to none" (W. Shakespeare)
> Web: http://atemezing.org
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> 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
>
> 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.
>
> --
> -------
> "Love all, trust a few, do wrong to none" (W. Shakespeare)
> Web: http://atemezing.org
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> 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
>
>
>
>
> --
> *Igor Kim*  | Team Leader / Backend  | Maginfo, Ltd
> Mobile: +7-912-402-4622
>
-- 
-------
"Love all, trust a few, do wrong to none" (W. Shakespeare)
Web: http://atemezing.org

Re: [Bigdata-developers] Help list - Newbie first question

[Igor K. <igo...@ms...>]

Ghislain,

Basically CUrl and Workbench do almost the same thing - issue POST query to
the server, which should analyze and run it then stream the result back to
client.
But upon receiving, curl just stores a stream into a file or logs to
console, but Workbench has to parse JSON results and show it in a web page,
which takes additional time.
Note, that JSON is native format for JavaScript code of the Workbench (much
easier to parse than XML for example), so using other formats would not
improve execution time.

The difference will be more obvious for large responses (many rows and
large literals).

You could use developers console in your browser to see execution times
(including transport times, but CUrl will count that time as well).

See attached screenshot, the query has taken 52ms while waiting for a
response start (prepare a query and start its evaluation),
additional 78ms to get whole result (iterate through the results on server
and stream it through network using JSON format),
but the Workbench have taken additional 322ms to parse and prepare results
for the results table on the web page.

Also, after execution a query on the Workbench, server's file system caches
index data for a time, so repeating requests to the same query might be
much faster for subsequent calls using CUrl.

As a workaround you might apply 'limit 50' to evaluate less results (only
first page), that will reduce overhead time for the Workbench.


[image: Inline image 1]

On Mon, Jan 23, 2017 at 1:15 PM, Ghislain ATEMEZING <
ghi...@gm...> wrote:

> Hi Igor,
> Thanks for your answer and sorry if O was not clear enough in my previous
> post. Basically I thought I can get also the time execution of a query with
> the ?explain parameter.
> When comparing the response time of a CUrl in localhost w.r.t the answer
> on the workbench, I notice it's sometimes 10x higher. Is there a way to get
> almost the same result somehow?
>
> Best,
> Ghislain
>
> Sent from my iPhone, may include typos
>
> Le 23 janv. 2017 à 04:51, Igor Kim <igo...@ms...> a écrit :
>
> Ghislain,
>
> ?explain parameter is a rough equivalent of SQL analyze, so there is no
> time of response returned, just a query execution plan explanation.
> Could you expand a little bit on what are you going to use that response
> time? There is a workaround with using UNION or BIND in the query, which
> could provide a timestamp for the results:
>
> for the whole result:
>
> select * from {
>     {
>         ?s ....... # statement pattern and filters
>     }
>     UNION
>     {
>         BIND (now() as ?timestamp) .
>     }
> }
>
> or for each of the rows:
>
> select * from {
>     ?s ....... # statement pattern and filters
>     BIND (now() as ?timestamp) .
> }
>
>
>
>
> On Fri, Jan 20, 2017 at 10:07 PM, Ghislain ATEMEZING <
> ghi...@gm...> wrote:
>
>> Many thanks Brad!
>> I was looking at the Wiki to see if I can use a parameter in a cUrl
>> request to retrieve the time response of a query. I've seen the ?explain
>> parameter, but not sure to find the that value in the .html output.
>> Is there a way to retrieve that value in a REST-ish  manner?
>>
>> TIA,
>> Ghislain
>>
>> El vie., 20 ene. 2017 a las 17:14, Brad Bebee (<be...@sy...>)
>> escribió:
>>
>>> Ghislain,
>>>
>>> Yes, you may use the list for those topics. In general, before posting,
>>> we recommend checking out the Wiki.
>>>
>>> https://wiki.blazegraph.com/wiki/index.php/Main_Page
>>>
>>> Thanks, --Brad
>>>
>>> On Fri, Jan 20, 2017 at 1:38 AM, Ghislain ATEMEZING <
>>> ghi...@gm...> wrote:
>>>
>>> Hi,
>>> [Sorry if I am in the wrong list.]
>>> I am new to blazegraph and I wanted to know if this list also helps for
>>> issues related to the use of the product, setting up issues and so on.
>>>
>>> TIA
>>> Best,
>>> Ghislain
>>> --
>>> -------
>>> "Love all, trust a few, do wrong to none" (W. Shakespeare)
>>> Web: http://atemezing.org
>>>
>>> ------------------------------------------------------------
>>> ------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>>> _______________________________________________
>>> 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
>>>
>>> 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.
>>>
>> --
>> -------
>> "Love all, trust a few, do wrong to none" (W. Shakespeare)
>> Web: http://atemezing.org
>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>> _______________________________________________
>> 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
>
>


-- 
*Igor Kim*  | Team Leader / Backend  | Maginfo, Ltd
Mobile: +7-912-402-4622

Re: [Bigdata-developers] Help list - Newbie first question

[Ghislain A. <ghi...@gm...>]

Hi Igor,
Thanks for your answer and sorry if O was not clear enough in my previous post. Basically I thought I can get also the time execution of a query with the ?explain parameter.
When comparing the response time of a CUrl in localhost w.r.t the answer on the workbench, I notice it's sometimes 10x higher. Is there a way to get almost the same result somehow?
 
Best,
Ghislain

Sent from my iPhone, may include typos

> Le 23 janv. 2017 à 04:51, Igor Kim <igo...@ms...> a écrit :
> 
> Ghislain,
> 
> ?explain parameter is a rough equivalent of SQL analyze, so there is no time of response returned, just a query execution plan explanation.
> Could you expand a little bit on what are you going to use that response time? There is a workaround with using UNION or BIND in the query, which could provide a timestamp for the results:
> 
> for the whole result:
> 
> select * from {
>     {
>         ?s ....... # statement pattern and filters
>     }
>     UNION
>     {
>         BIND (now() as ?timestamp) .
>     }
> }
> 
> or for each of the rows:
> 
> select * from {
>     ?s ....... # statement pattern and filters
>     BIND (now() as ?timestamp) .
> }
> 
> 
> 
> 
>> On Fri, Jan 20, 2017 at 10:07 PM, Ghislain ATEMEZING <ghi...@gm...> wrote:
>> Many thanks Brad!
>> I was looking at the Wiki to see if I can use a parameter in a cUrl request to retrieve the time response of a query. I've seen the ?explain parameter, but not sure to find the that value in the .html output. 
>> Is there a way to retrieve that value in a REST-ish  manner? 
>> 
>> TIA,
>> Ghislain
>> 
>>> El vie., 20 ene. 2017 a las 17:14, Brad Bebee (<be...@sy...>) escribió:
>>> Ghislain,
>>> 
>>> Yes, you may use the list for those topics. In general, before posting, we recommend checking out the Wiki.
>>> 
>>> https://wiki.blazegraph.com/wiki/index.php/Main_Page
>>> 
>>> Thanks, --Brad
>>> 
>>> On Fri, Jan 20, 2017 at 1:38 AM, Ghislain ATEMEZING <ghi...@gm...> wrote:
>>> Hi, 
>>> [Sorry if I am in the wrong list.] 
>>> I am new to blazegraph and I wanted to know if this list also helps for issues related to the use of the product, setting up issues and so on. 
>>> 
>>> TIA
>>> Best,
>>> Ghislain
>>> -- 
>>> -------
>>> "Love all, trust a few, do wrong to none" (W. Shakespeare)
>>> Web: http://atemezing.org
>>> 
>>> ------------------------------------------------------------------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>>> _______________________________________________
>>> 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
>>> 
>>> 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.
>>> 
>>> 
>> 
>> -- 
>> -------
>> "Love all, trust a few, do wrong to none" (W. Shakespeare)
>> Web: http://atemezing.org
>> 
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>> _______________________________________________
>> 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

Re: [Bigdata-developers] Help list - Newbie first question

[Igor K. <igo...@ms...>]

Ghislain,

?explain parameter is a rough equivalent of SQL analyze, so there is no
time of response returned, just a query execution plan explanation.
Could you expand a little bit on what are you going to use that response
time? There is a workaround with using UNION or BIND in the query, which
could provide a timestamp for the results:

for the whole result:

select * from {
    {
        ?s ....... # statement pattern and filters
    }
    UNION
    {
        BIND (now() as ?timestamp) .
    }
}

or for each of the rows:

select * from {
    ?s ....... # statement pattern and filters
    BIND (now() as ?timestamp) .
}




On Fri, Jan 20, 2017 at 10:07 PM, Ghislain ATEMEZING <
ghi...@gm...> wrote:

> Many thanks Brad!
> I was looking at the Wiki to see if I can use a parameter in a cUrl
> request to retrieve the time response of a query. I've seen the ?explain
> parameter, but not sure to find the that value in the .html output.
> Is there a way to retrieve that value in a REST-ish  manner?
>
> TIA,
> Ghislain
>
> El vie., 20 ene. 2017 a las 17:14, Brad Bebee (<be...@sy...>)
> escribió:
>
>> Ghislain,
>>
>> Yes, you may use the list for those topics. In general, before posting,
>> we recommend checking out the Wiki.
>>
>> https://wiki.blazegraph.com/wiki/index.php/Main_Page
>>
>> Thanks, --Brad
>>
>> On Fri, Jan 20, 2017 at 1:38 AM, Ghislain ATEMEZING <
>> ghi...@gm...> wrote:
>>
>> Hi,
>> [Sorry if I am in the wrong list.]
>> I am new to blazegraph and I wanted to know if this list also helps for
>> issues related to the use of the product, setting up issues and so on.
>>
>> TIA
>> Best,
>> Ghislain
>> --
>> -------
>> "Love all, trust a few, do wrong to none" (W. Shakespeare)
>> Web: http://atemezing.org
>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>> _______________________________________________
>> 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
>>
>> 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.
>>
> --
> -------
> "Love all, trust a few, do wrong to none" (W. Shakespeare)
> Web: http://atemezing.org
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> 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

Re: [Bigdata-developers] Help list - Newbie first question

[Ghislain A. <ghi...@gm...>]

Many thanks Brad!
I was looking at the Wiki to see if I can use a parameter in a cUrl request
to retrieve the time response of a query. I've seen the ?explain parameter,
but not sure to find the that value in the .html output.
Is there a way to retrieve that value in a REST-ish  manner?

TIA,
Ghislain

El vie., 20 ene. 2017 a las 17:14, Brad Bebee (<be...@sy...>) escribió:

> Ghislain,
>
> Yes, you may use the list for those topics. In general, before posting, we
> recommend checking out the Wiki.
>
> https://wiki.blazegraph.com/wiki/index.php/Main_Page
>
> Thanks, --Brad
>
> On Fri, Jan 20, 2017 at 1:38 AM, Ghislain ATEMEZING <
> ghi...@gm...> wrote:
>
> Hi,
> [Sorry if I am in the wrong list.]
> I am new to blazegraph and I wanted to know if this list also helps for
> issues related to the use of the product, setting up issues and so on.
>
> TIA
> Best,
> Ghislain
> --
> -------
> "Love all, trust a few, do wrong to none" (W. Shakespeare)
> Web: http://atemezing.org
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> 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
>
> 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.
>
-- 
-------
"Love all, trust a few, do wrong to none" (W. Shakespeare)
Web: http://atemezing.org

Re: [Bigdata-developers] Help list - Newbie first question

[Brad B. <be...@sy...>]

Ghislain,

Yes, you may use the list for those topics. In general, before posting, we
recommend checking out the Wiki.

https://wiki.blazegraph.com/wiki/index.php/Main_Page

Thanks, --Brad

On Fri, Jan 20, 2017 at 1:38 AM, Ghislain ATEMEZING <
ghi...@gm...> wrote:

> Hi,
> [Sorry if I am in the wrong list.]
> I am new to blazegraph and I wanted to know if this list also helps for
> issues related to the use of the product, setting up issues and so on.
>
> TIA
> Best,
> Ghislain
> --
> -------
> "Love all, trust a few, do wrong to none" (W. Shakespeare)
> Web: http://atemezing.org
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> 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

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] Help list - Newbie first question

[Ghislain A. <ghi...@gm...>]

Hi,
[Sorry if I am in the wrong list.]
I am new to blazegraph and I wanted to know if this list also helps for
issues related to the use of the product, setting up issues and so on.

TIA
Best,
Ghislain
-- 
-------
"Love all, trust a few, do wrong to none" (W. Shakespeare)
Web: http://atemezing.org

Re: [Bigdata-developers] TupleQuery vs. ParsedQuery

[Adrian B. <Adr...@ma...>]

Hi Artem,

thanks for the reply.

On 12/01/17 19:38, Artem Kozlov wrote:
> Hi Adrian,
>
> Query that you are trying to parse is not a valid SPARQL query - "The
> variable introduced by the |BIND |clause must not have been used in
> the group graph pattern up to the point of use in |BIND|.
> " [https://www.w3.org/TR/sparql11-query/#bind] .
I would have thought so too, but not only does blazegraph accept it (at
least as a TupleQuery-Object) but if I execute it in query.wikidata.org
(which uses blazegraph as a backend) it runs successfully.
Interesstingly enough the result is the same as

SELECT DISTINCT ?item
WHERE
{ BIND (wd:Q146 AS ?tree0)
?tree0 wdt:P31 ?item}
>
> Regards,
>
> Artem
>
> On Wed, Jan 11, 2017 at 3:15 PM, Adrian Bielefeldt
> <Adr...@ma...
> <mailto:Adr...@ma...>> wrote:
>
>     Hello everyone,
>
>     I'm writign on behalf of a Wikidata Research Project
>     <https://meta.wikimedia.org/wiki/Research:Understanding_Wikidata_Queries>
>     into SPARQL-Queries. We are writing a java application to parse
>     SPARQL-Queries from the query.wikidata.org-logs and analyse them
>     for different features. At the moment we are parsing the queries with
>     org.openrdf.query.parser.QueryParserUtil into
>     org.openrdf.query.parser.ParsedQuery-Objects. Unfortunatly we
>     cannot parse queries like this one:
>
>     SELECT DISTINCT ?item
>     WHERE
>     { ?tree0 wdt:P31 ?item . BIND (wd:Q146 AS ?tree0) }
>
>     because of: "BIND clause alias '{}' was previously used".
>
>     If we parse them as org.openrdf.query.TupleQuery-Objects using
>     org.openrdf.repository.RepositoryConnection.prepareTupleQuery they
>     are parsed just fine.
>
>     Unfortunatly, the TupleQuery-Objects do not support the
>     analysis-Features of ParsedQuery.
>
>     All of which leads to 2-3 questions:
>
>     1. Why is this kind of query accepted by one parser but not the other?
>     2. Is it possible to obtain a ParsedQuery-Object from a
>     TupleQuery-Object?
>     (3. Is this the right mailing list to post these questions to?)
>
>     Greetings,
>
>     Adrian Bielefeldt
>
>     ------------------------------------------------------------------------------
>     Developer Access Program for Intel Xeon Phi Processors
>     Access to Intel Xeon Phi processor-based developer platforms.
>     With one year of Intel Parallel Studio XE.
>     Training and support from Colfax.
>     Order your platform today. http://sdm.link/xeonphi
>     _______________________________________________
>     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>
>
>

Re: [Bigdata-developers] TupleQuery vs. ParsedQuery

[Adrian B. <Adr...@ma...>]

Hi Jerven,

thanks for the reply.

On 12/01/17 10:03, Jerven Tjalling Bolleman wrote:
> Hi Adrian,
>
> I am not involved in BigData/BlazeGraph etc.. but I can provide some
> insight.
>
> On 2017-01-11 15:15, Adrian Bielefeldt wrote:
>> I'm writign on behalf of a Wikidata Research Project [1] into
>> SPARQL-Queries. We are writing a java application to parse
>> SPARQL-Queries from the query.wikidata.org-logs and analyse them for
>> different features. At the moment we are parsing the queries with
>> org.openrdf.query.parser.QueryParserUtil into
>> org.openrdf.query.parser.ParsedQuery-Objects. Unfortunatly we cannot
>> parse queries like this one:
>>
>> SELECT DISTINCT ?item
>> WHERE
>> { ?tree0 wdt:P31 ?item . BIND (wd:Q146 AS ?tree0) }
>>
>> because of: "BIND clause alias '{}' was previously used".
>>
>> If we parse them as org.openrdf.query.TupleQuery-Objects using
>> org.openrdf.repository.RepositoryConnection.prepareTupleQuery they are
>> parsed just fine.
>
> This is practically an invalid SPARQL query (different systems accept
> more or less) but
> the query is nonsensical. The Query Parser reports that.
> The TupleQuery parses according to the AST which does not "judge" a
> query on its merits.
>
So what you're saying is that the TupleQuery-Object creates the AST but
does not notice that there is actually no sensible way to execute it?
Then what happens if I call .evaluate() on this object?
> It has been a while since I did any query analysis for
> sparql.uniprot.org.
> What I did at that time is for more detailed analysis is use the
> SPIN-API [2] to convert
> the SPARQL query string to an RDF representation. Loaded that SPARQL
> query as RDF into a
> triple store and used SPARQL to analyze those SPARQL queries. i.e. use
> SPARQL to analyze analytical SPARQL queries ;)
>
We thought about that as well. Is there some kind of public project
documentation on this? It would certainly be of interest to us.
> Regarding the openrdf parser questions you can ask them at
> eclipse-rdf4j https://groups.google.com/forum/#!forum/rdf4j-users
>
Thanks, I'll try it there too.
> rdf4j at eclipse is what was formerly named openrdf/sesame.
>
> Regards,
> Jerven
>
> [2] https://github.com/spinrdf/spinrdf/
>
>>
>>
>> Unfortunatly, the TupleQuery-Objects do not support the
>> analysis-Features of ParsedQuery.
>>
>> All of which leads to 2-3 questions:
>>
>> 1. Why is this kind of query accepted by one parser but not the other?
>> 2. Is it possible to obtain a ParsedQuery-Object from a
>> TupleQuery-Object?
>> (3. Is this the right mailing list to post these questions to?)
>>
>> Greetings,
>>
>> Adrian Bielefeldt
>>
>>
>> Links:
>> ------
>> [1]
>> https://meta.wikimedia.org/wiki/Research:Understanding_Wikidata_Queries
>> ------------------------------------------------------------------------------
>>
>> Developer Access Program for Intel Xeon Phi Processors
>> Access to Intel Xeon Phi processor-based developer platforms.
>> With one year of Intel Parallel Studio XE.
>> Training and support from Colfax.
>> Order your platform today. http://sdm.link/xeonphi
>> _______________________________________________
>> Bigdata-developers mailing list
>> Big...@li...
>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
>

Re: [Bigdata-developers] TupleQuery vs. ParsedQuery

[Artem K. <art...@gm...>]

Hi Adrian,

Query that you are trying to parse is not a valid SPARQL query - "The
variable introduced by the BIND clause must not have been used in the group
graph pattern up to the point of use in BIND.
" [https://www.w3.org/TR/sparql11-query/#bind] .

Regards,

Artem

On Wed, Jan 11, 2017 at 3:15 PM, Adrian Bielefeldt <
Adr...@ma...> wrote:

> Hello everyone,
>
> I'm writign on behalf of a Wikidata Research Project
> <https://meta.wikimedia.org/wiki/Research:Understanding_Wikidata_Queries>
> into SPARQL-Queries. We are writing a java application to parse
> SPARQL-Queries from the query.wikidata.org-logs and analyse them for
> different features. At the moment we are parsing the queries with
> org.openrdf.query.parser.QueryParserUtil into
> org.openrdf.query.parser.ParsedQuery-Objects. Unfortunatly we cannot
> parse queries like this one:
>
> SELECT DISTINCT ?item
> WHERE
> { ?tree0 wdt:P31 ?item . BIND (wd:Q146 AS ?tree0) }
>
> because of: "BIND clause alias '{}' was previously used".
>
> If we parse them as org.openrdf.query.TupleQuery-Objects using
> org.openrdf.repository.RepositoryConnection.prepareTupleQuery they are
> parsed just fine.
>
> Unfortunatly, the TupleQuery-Objects do not support the analysis-Features
> of ParsedQuery.
>
> All of which leads to 2-3 questions:
>
> 1. Why is this kind of query accepted by one parser but not the other?
> 2. Is it possible to obtain a ParsedQuery-Object from a TupleQuery-Object?
> (3. Is this the right mailing list to post these questions to?)
>
> Greetings,
>
> Adrian Bielefeldt
>
> ------------------------------------------------------------
> ------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> _______________________________________________
> Bigdata-developers mailing list
> Big...@li...
> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
>
>

Re: [Bigdata-developers] TupleQuery vs. ParsedQuery

[Jerven T. B. <Jer...@si...>]

Hi Adrian,

I am not involved in BigData/BlazeGraph etc.. but I can provide some 
insight.

On 2017-01-11 15:15, Adrian Bielefeldt wrote:
> I'm writign on behalf of a Wikidata Research Project [1] into
> SPARQL-Queries. We are writing a java application to parse
> SPARQL-Queries from the query.wikidata.org-logs and analyse them for
> different features. At the moment we are parsing the queries with
> org.openrdf.query.parser.QueryParserUtil into
> org.openrdf.query.parser.ParsedQuery-Objects. Unfortunatly we cannot
> parse queries like this one:
> 
> SELECT DISTINCT ?item
> WHERE
> { ?tree0 wdt:P31 ?item . BIND (wd:Q146 AS ?tree0) }
> 
> because of: "BIND clause alias '{}' was previously used".
> 
> If we parse them as org.openrdf.query.TupleQuery-Objects using
> org.openrdf.repository.RepositoryConnection.prepareTupleQuery they are
> parsed just fine.

This is practically an invalid SPARQL query (different systems accept 
more or less) but
the query is nonsensical. The Query Parser reports that.
The TupleQuery parses according to the AST which does not "judge" a 
query on its merits.

It has been a while since I did any query analysis for 
sparql.uniprot.org.
What I did at that time is for more detailed analysis is use the 
SPIN-API [2] to convert
the SPARQL query string to an RDF representation. Loaded that SPARQL 
query as RDF into a
triple store and used SPARQL to analyze those SPARQL queries. i.e. use 
SPARQL to analyze analytical SPARQL queries ;)


Regarding the openrdf parser questions you can ask them at eclipse-rdf4j 
https://groups.google.com/forum/#!forum/rdf4j-users

rdf4j at eclipse is what was formerly named openrdf/sesame.

Regards,
Jerven

[2] https://github.com/spinrdf/spinrdf/

> 
> 
> Unfortunatly, the TupleQuery-Objects do not support the
> analysis-Features of ParsedQuery.
> 
> All of which leads to 2-3 questions:
> 
> 1. Why is this kind of query accepted by one parser but not the other?
> 2. Is it possible to obtain a ParsedQuery-Object from a
> TupleQuery-Object?
> (3. Is this the right mailing list to post these questions to?)
> 
> Greetings,
> 
> Adrian Bielefeldt
> 
> 
> Links:
> ------
> [1] 
> https://meta.wikimedia.org/wiki/Research:Understanding_Wikidata_Queries
> ------------------------------------------------------------------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> _______________________________________________
> Bigdata-developers mailing list
> Big...@li...
> https://lists.sourceforge.net/lists/listinfo/bigdata-developers

-- 
Jerven Tjalling Bolleman
SIB | Swiss Institute of Bioinformatics
CMU - 1, rue Michel Servet - 1211 Geneva 4
t: +41 22 379 58 85 - f: +41 22 379 58 58
Jerven.Bolleman@sib.swiss - http://www.sib.swiss

Re: [Bigdata-developers] 2.2 Release date?

[Kevin F. <kf...@ar...>]

I wrote earlier requesting an available 2.2.0 RC artifact.  If it was 
added to any to-do wish list (thank you, if so), feel free to remove it.

I buckled down, checked out the repo, and ran the rather handy 
artifact-creation scripts.

Yours,
Kevin


On 1/3/17 15:41, Brad Bebee wrote:
> Kevin,
>
> Thank you. Yes, we are working towards having a release in Q1 for 2.2,
> which will include some fixes made for the Wikidata query service. The
> move to RDF 1.1 also has some potential data migration.
>
> If you haven't already, we'd encourage you to try the 2.2.0 RC and let
> us know if you have any issues:
>  https://github.com/blazegraph/database/releases/tag/BLAZEGRAPH_RELEASE_CANDIDATE_2_2_0.
>
> Thanks, --Brad
>
> On Tue, Jan 3, 2017 at 12:05 PM, Kevin Ford <kf...@ar...
> <mailto:kf...@ar...>> wrote:
>
>     Dear All,
>
>     I might be looking in all the wrong places, but is there any information
>     about when Blazegraph 2.2 will be released? We're excited to see the
>     sesame upgrade that will bring RDF 1.1 support.
>
>     I've found the 2.2 RC but nothing else.
>
>     All the best,
>     Kevin
>
>
>     ------------------------------------------------------------------------------
>     Check out the vibrant tech community on one of the world's most
>     engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>     _______________________________________________
>     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
>
> 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] TupleQuery vs. ParsedQuery

[Adrian B. <Adr...@ma...>]

Hello everyone,

I'm writign on behalf of a Wikidata Research Project
<https://meta.wikimedia.org/wiki/Research:Understanding_Wikidata_Queries>
into SPARQL-Queries. We are writing a java application to parse
SPARQL-Queries from the query.wikidata.org-logs and analyse them for
different features. At the moment we are parsing the queries with
org.openrdf.query.parser.QueryParserUtil into
org.openrdf.query.parser.ParsedQuery-Objects. Unfortunatly we cannot
parse queries like this one:

SELECT DISTINCT ?item
WHERE
{ ?tree0 wdt:P31 ?item . BIND (wd:Q146 AS ?tree0) }

because of: "BIND clause alias '{}' was previously used".

If we parse them as org.openrdf.query.TupleQuery-Objects using
org.openrdf.repository.RepositoryConnection.prepareTupleQuery they are
parsed just fine.

Unfortunatly, the TupleQuery-Objects do not support the
analysis-Features of ParsedQuery.

All of which leads to 2-3 questions:

1. Why is this kind of query accepted by one parser but not the other?
2. Is it possible to obtain a ParsedQuery-Object from a TupleQuery-Object?
(3. Is this the right mailing list to post these questions to?)

Greetings,

Adrian Bielefeldt

[Bigdata-developers] Cross namespace query (using SERVICE keyword) on endpoint having basic authentication doesn't work

[Aftab I. <af...@gm...>]

Hello Blazegraph community,

Happy New Year. I hope you had a nice and relaxing holidays.

Following up on https://jira.blazegraph.com/browse/BLZG-1966,
I am wondering if this issue has been addressed (or will be addressed) or
if there is a work around available to support basic authentication on
blazegraph instance(s) that let SERVICE federation across different
namespaces work?

Looking forward to your response.
best regards
Aftab Iqbal

Re: [Bigdata-developers] 2.2 Release date?

[Kevin F. <kf...@ar...>]

I just noticed that there are no built artifacts for the release candidate.

Would it be possible to get a JAR for testing purposes?  (I know that 
producing said JAR via github adds it to the releases, so I'm happy to 
fetch it from a non-github location if one is available.)

Yours,
Kevin


On 1/3/17 15:41, Brad Bebee wrote:
> Kevin,
>
> Thank you. Yes, we are working towards having a release in Q1 for 2.2,
> which will include some fixes made for the Wikidata query service. The
> move to RDF 1.1 also has some potential data migration.
>
> If you haven't already, we'd encourage you to try the 2.2.0 RC and let
> us know if you have any issues:
>  https://github.com/blazegraph/database/releases/tag/BLAZEGRAPH_RELEASE_CANDIDATE_2_2_0.
>
> Thanks, --Brad
>
> On Tue, Jan 3, 2017 at 12:05 PM, Kevin Ford <kf...@ar...
> <mailto:kf...@ar...>> wrote:
>
>     Dear All,
>
>     I might be looking in all the wrong places, but is there any information
>     about when Blazegraph 2.2 will be released? We're excited to see the
>     sesame upgrade that will bring RDF 1.1 support.
>
>     I've found the 2.2 RC but nothing else.
>
>     All the best,
>     Kevin
>
>
>     ------------------------------------------------------------------------------
>     Check out the vibrant tech community on one of the world's most
>     engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>     _______________________________________________
>     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
>
> 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.


Re: [Bigdata-developers] 2.2 Release date?

[Kevin F. <kf...@ar...>]

Hi Brad,

Thanks for the info. I'll certainly take the RC out for a spin.

All the best,
Kevin


On 1/3/17 15:41, Brad Bebee wrote:
> Kevin,
>
> Thank you. Yes, we are working towards having a release in Q1 for 2.2,
> which will include some fixes made for the Wikidata query service. The
> move to RDF 1.1 also has some potential data migration.
>
> If you haven't already, we'd encourage you to try the 2.2.0 RC and let
> us know if you have any issues:
>  https://github.com/blazegraph/database/releases/tag/BLAZEGRAPH_RELEASE_CANDIDATE_2_2_0.
>
> Thanks, --Brad
>
> On Tue, Jan 3, 2017 at 12:05 PM, Kevin Ford <kf...@ar...
> <mailto:kf...@ar...>> wrote:
>
>     Dear All,
>
>     I might be looking in all the wrong places, but is there any information
>     about when Blazegraph 2.2 will be released? We're excited to see the
>     sesame upgrade that will bring RDF 1.1 support.
>
>     I've found the 2.2 RC but nothing else.
>
>     All the best,
>     Kevin
>
>
>     ------------------------------------------------------------------------------
>     Check out the vibrant tech community on one of the world's most
>     engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>     _______________________________________________
>     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
>
> 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.


Re: [Bigdata-developers] 2.2 Release date?

[Brad B. <be...@sy...>]

Kevin,

Thank you. Yes, we are working towards having a release in Q1 for 2.2,
which will include some fixes made for the Wikidata query service. The move
to RDF 1.1 also has some potential data migration.

If you haven't already, we'd encourage you to try the 2.2.0 RC and let us
know if you have any issues:
https://github.com/blazegraph/database/releases/tag/BLAZEGRAPH_RELEASE_CANDIDATE_2_2_0
.

Thanks, --Brad

On Tue, Jan 3, 2017 at 12:05 PM, Kevin Ford <kf...@ar...> wrote:

> Dear All,
>
> I might be looking in all the wrong places, but is there any information
> about when Blazegraph 2.2 will be released? We're excited to see the
> sesame upgrade that will bring RDF 1.1 support.
>
> I've found the 2.2 RC but nothing else.
>
> All the best,
> Kevin
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> 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

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] 2.2 Release date?

[Kevin F. <kf...@ar...>]

Dear All,

I might be looking in all the wrong places, but is there any information 
about when Blazegraph 2.2 will be released? We're excited to see the 
sesame upgrade that will bring RDF 1.1 support.

I've found the 2.2 RC but nothing else.

All the best,
Kevin

[Bigdata-developers] Will the Blazegraph multi-GPU architecture port to the Wikidata Stand-alone infrastructure?

[Eric S. <eri...@at...>]

Hi all -

We've been using a locally installed wikidata stand-alone service (https://www.mediawiki.org/wiki/Wikidata_query_service/User_Manual#Standalone_service) for several months now.  The stand-alone service allows us periodically to download RDF dumps of the entire Wikidata repository, and maintain on our local servers a near-real-time synchronization with the repo at Wikidata's main server.

We hit this service pretty hard sometimes, and We're becoming increasingly plagued by performance issues. We are wondering if one approach to the problem might be to adopt the Blazegraph multi-GPU architecture (https://www.blazegraph.com/product/gpu-accelerated/).

Could anyone provide guidance as to how much pain would be involved in making such a transition?

Thanks and regards,

Eric Scott

Re: [Bigdata-developers] Blazegraph in remote mode with Sesame API

[Igor K. <igo...@ms...>]

Greetings,

NoSuchMethodError and similar exceptions are caused by misconfiguration in
dependencies versions.
Note, that Blazegraph 2.1.4 requires sesame.version = 2.7.12
https://github.com/blazegraph/database/blob/BLAZEGRAPH_RELEASE_2_1_4/pom.xml#L207

Please, configure it accordingly in the main POM file:
<properties>
....
<sesame.version>2.7.12</sesame.version>
....




On Fri, Oct 14, 2016 at 2:10 PM, Mishel Uchuari Vera <dmu...@eu...
> wrote:

> Hello,
>
> I’m trying to connect to Blazegraph using SESAME API with Eclipse IDE for
> JAVA Developers (NEON 4.6.1), to do this, I'm following a tutorial that
> Blazegraph provides:
> https://wiki.blazegraph.com/wiki/index.php/Sesame_API_remote_mode
> The problem is that when the program is executed, a class from a library
> of Blazegraph (ServiceProviderHook) through the ServiceProviderHook.
> forceLoad() method calls to the RDFParserRegistry's method add(), this is
> inherited for this class from the superclass ServiceRegistry.
> In Eclipse's console appears :
> Exception in thread "main" java.lang.NoSuchMethodError: org.openrdf.rio.
> RDFParserRegistry.add(Ljava/lang/Object;)Ljava/lang/Object
> Of course, this method isn't in the class RDFParserRegistry, but, it can
> use it.
> At first, I looked for a new version of Blazegraph that don’t use this
> method, because I had problems before with other methods that use the
> mentioned tutorial, methods like RDFFormat.values(), or
> RDFFormat.register(), I fixed that problems using an older version of
> Sesame, specifically, 2.8.10, because in the newest versions these methods
> are deprecated.
> My code is simple, only contains the Blazegraph Tutorial says, with a
> little modification in the file path, and in the file format Turtle instead
> of N3.
> For execute this code, I am using bigdata-client dependency in 2.1.4, and
> sesame-rio-api in 2.8.10.
> This is it:
> package prueba.blazegraph;
>
> import java.io.IOException;
> import java.io.InputStream;
> import java.util.Properties;
>
> import org.openrdf.model.Statement;
> import org.openrdf.query.BindingSet;
> import org.openrdf.query.GraphQueryResult;
> import org.openrdf.query.TupleQueryResult;
> import org.openrdf.rio.RDFFormat;
> import org.openrdf.rio.RDFParserRegistry;
> import org.apache.log4j.Logger;
> import com.bigdata.rdf.sail.webapp.SD;
> import com.bigdata.rdf.sail.webapp.client.ConnectOptions;
> import com.bigdata.rdf.sail.webapp.client.JettyResponseListener;
> import com.bigdata.rdf.sail.webapp.client.RemoteRepository;
> import com.bigdata.rdf.sail.webapp.client.RemoteRepositoryManager;
>
>
>
> public class Blazegraph {
> private final Logger LOGGER= Logger.getLogger(Blazegraph.class);
>         private final String PATH = "http://localhost:9999/bigdata";
>
>         public void conexion() {
>                 final RemoteRepositoryManager REPOSITORIO = new
> RemoteRepositoryManager(PATH,true);
>                 try {
>                         JettyResponseListener response =
> getStatus(REPOSITORIO);
>                         LOGGER.info(response.getResponseBody());
>                         // Vamos a crear un namespace si no existe
>                         final String NAMESPACE = "primerNamespace";
>                         Properties properties = new Properties();
>                         properties.setProperty("com.bigdata.rdf.sail.namespace",
> NAMESPACE);
>                         if (!namespaceExists(REPOSITORIO, NAMESPACE)) {
>                                 LOGGER.info("Vamos a crear el namespace");
>                                 REPOSITORIO.createRepository(NAMESPACE,
> properties);
>                                 LOGGER.info("Namespace creado");
>                         } else {
>                                 LOGGER.info(String.format("El namespace ya
> existe", NAMESPACE));
>                         }
>                         // Vamos a obtener las propiedades del namespace
>                         LOGGER.info(String.format("Lista de propiedades
> del namespace", NAMESPACE));
>                         response = getNamespaceProperties(REPOSITORIO,
> NAMESPACE);
>                         LOGGER.info(response.getResponseBody());
>
>                         // Vamos a cargar los datos del fichero
>                         String documentoASubir =
> "src/main/resources/resources/datos.ttl";
>                         loadDataFromResource(REPOSITORIO, NAMESPACE,
> documentoASubir);
>
>                         // Ejecutamos una query sobre los datos cargados
>                         TupleQueryResult result = REPOSITORIO.
> getRepositoryForNamespace(NAMESPACE)
>                                         .prepareTupleQuery("SELECT * WHERE
> {?o ?p ?q}").evaluate();
>                         // Procesamos los resultados
>                         try {
>                                 while (result.hasNext()) {
>                                         BindingSet bs = result.next();
>                                         LOGGER.info("-------------------->"
> + bs);
>                                 }
>                         } finally {
>                                 result.close();
>                         }
>                 } catch (Exception e) {
>                         e.printStackTrace();
>                 } finally {
>                         try {
>                                 REPOSITORIO.close();
>                         } catch (Exception e) {
>                                 e.printStackTrace();
>                         }
>                 }
>         }
>
>         private void loadDataFromResource(RemoteRepositoryManager
> pRepositorio, String pNamespace, String pDocumentoASubir) throws Exception {
>                 InputStream is= Blazegraph.class.getResourceAsStream(
> pDocumentoASubir);
>                 if(is==null){
>                         throw new IOException("No se encuentra el
> archivo");
>                 }
>                 try {
>                         pRepositorio.getRepositoryForNamespace(
> pNamespace).add(
>                                         new RemoteRepository.AddOp(is,
> RDFFormat.TURTLE));
>                 } finally {
>                         is.close();
>                 }
>
>         }
>
>         private JettyResponseListener getNamespaceProperties(RemoteRepositoryManager
> pRepositorio, String pNamespace) throws Exception {
>                 ConnectOptions options = new ConnectOptions(PATH +
> "/namespace/"
>                                 +pNamespace + "/properties");
>                 options.method = "GET";
>                 return pRepositorio.doConnect(options);
>         }
>
>         private boolean namespaceExists(RemoteRepositoryManager
> pRepositorio, String pNamespace) throws Exception {
>                 boolean existe=false;
>                 GraphQueryResult result = pRepositorio.
> getRepositoryDescriptions();
>                 try {
>                         while (result.hasNext()) {
>                                 Statement statement = result.next();
>                                 if (statement.getPredicate().
> toString().toString().equals(SD.KB_NAMESPACE.stringValue())) {
>                                         if (pNamespace.equals(statement.getObject().stringValue()))
> {
>                                                 existe= true;
>                                         }
>                                 }
>                         }
>                 } finally {
>                         result.close();
>                 }
>                 return existe;
>         }
>
>         private JettyResponseListener getStatus(RemoteRepositoryManager
> pRepositorio) throws Exception {
>                 ConnectOptions options = new ConnectOptions(PATH +
> "/status");
>                 options.method = "GET";
>                 return pRepositorio.doConnect(options);
>         }
> }
>
>
>
>
> Thanks for your attention.
>
> Mishel Uchuari
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> 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

[Bigdata-developers] Blazegraph in remote mode with Sesame API

[Mishel U. V. <dmu...@eu...>]

Hello, 

I’m trying to connect to Blazegraph using SESAME API with Eclipse IDE for JAVA Developers (NEON 4.6.1), to do this, I'm following a tutorial that Blazegraph provides: 
https://wiki.blazegraph.com/wiki/index.php/Sesame_API_remote_mode
The problem is that when the program is executed, a class from a library of Blazegraph (ServiceProviderHook) through the ServiceProviderHook. forceLoad() method calls to the RDFParserRegistry's method add(), this is inherited for this class from the superclass ServiceRegistry. 
In Eclipse's console appears :
Exception in thread "main" java.lang.NoSuchMethodError: org.openrdf.rio.RDFParserRegistry.add(Ljava/lang/Object;)Ljava/lang/Object
Of course, this method isn't in the class RDFParserRegistry, but, it can use it. 
At first, I looked for a new version of Blazegraph that don’t use this method, because I had problems before with other methods that use the mentioned tutorial, methods like RDFFormat.values(), or RDFFormat.register(), I fixed that problems using an older version of Sesame, specifically, 2.8.10, because in the newest versions these methods are deprecated.
My code is simple, only contains the Blazegraph Tutorial says, with a little modification in the file path, and in the file format Turtle instead of N3.  
For execute this code, I am using bigdata-client dependency in 2.1.4, and sesame-rio-api in 2.8.10.
This is it:
package prueba.blazegraph;

import java.io.IOException;
import java.io.InputStream;
import java.util.Properties;

import org.openrdf.model.Statement;
import org.openrdf.query.BindingSet;
import org.openrdf.query.GraphQueryResult;
import org.openrdf.query.TupleQueryResult;
import org.openrdf.rio.RDFFormat;
import org.openrdf.rio.RDFParserRegistry;
import org.apache.log4j.Logger;
import com.bigdata.rdf.sail.webapp.SD;
import com.bigdata.rdf.sail.webapp.client.ConnectOptions;
import com.bigdata.rdf.sail.webapp.client.JettyResponseListener;
import com.bigdata.rdf.sail.webapp.client.RemoteRepository;
import com.bigdata.rdf.sail.webapp.client.RemoteRepositoryManager;



public class Blazegraph {
private final Logger LOGGER= Logger.getLogger(Blazegraph.class);
	private final String PATH = "http://localhost:9999/bigdata";

	public void conexion() {
		final RemoteRepositoryManager REPOSITORIO = new RemoteRepositoryManager(PATH,true);
		try {
			JettyResponseListener response = getStatus(REPOSITORIO);
			LOGGER.info(response.getResponseBody());
			// Vamos a crear un namespace si no existe
			final String NAMESPACE = "primerNamespace";
			Properties properties = new Properties();
			properties.setProperty("com.bigdata.rdf.sail.namespace", NAMESPACE);
			if (!namespaceExists(REPOSITORIO, NAMESPACE)) {
				LOGGER.info("Vamos a crear el namespace");
				REPOSITORIO.createRepository(NAMESPACE, properties);
				LOGGER.info("Namespace creado");
			} else {
				LOGGER.info(String.format("El namespace ya existe", NAMESPACE));
			}
			// Vamos a obtener las propiedades del namespace
			LOGGER.info(String.format("Lista de propiedades del namespace", NAMESPACE));
			response = getNamespaceProperties(REPOSITORIO, NAMESPACE);
			LOGGER.info(response.getResponseBody());

			// Vamos a cargar los datos del fichero
			String documentoASubir = "src/main/resources/resources/datos.ttl";
			loadDataFromResource(REPOSITORIO, NAMESPACE, documentoASubir);

			// Ejecutamos una query sobre los datos cargados
			TupleQueryResult result = REPOSITORIO.getRepositoryForNamespace(NAMESPACE)
					.prepareTupleQuery("SELECT * WHERE {?o ?p ?q}").evaluate();
			// Procesamos los resultados
			try {
				while (result.hasNext()) {
					BindingSet bs = result.next();
					LOGGER.info("-------------------->" + bs);
				}
			} finally {
				result.close();
			}
		} catch (Exception e) {
			e.printStackTrace();
		} finally {
			try {
				REPOSITORIO.close();
			} catch (Exception e) {
				e.printStackTrace();
			}
		}
	}

	private void loadDataFromResource(RemoteRepositoryManager pRepositorio, String pNamespace, String pDocumentoASubir) throws Exception {
		InputStream is= Blazegraph.class.getResourceAsStream(pDocumentoASubir);
		if(is==null){
			throw new IOException("No se encuentra el archivo");
		}
		try {
			pRepositorio.getRepositoryForNamespace(pNamespace).add(
					new RemoteRepository.AddOp(is, RDFFormat.TURTLE));
		} finally {
			is.close();
		}
		
	}

	private JettyResponseListener getNamespaceProperties(RemoteRepositoryManager pRepositorio, String pNamespace) throws Exception {
		ConnectOptions options = new ConnectOptions(PATH + "/namespace/"
				+pNamespace + "/properties");
		options.method = "GET";
		return pRepositorio.doConnect(options);
	}

	private boolean namespaceExists(RemoteRepositoryManager pRepositorio, String pNamespace) throws Exception {
		boolean existe=false;
		GraphQueryResult result = pRepositorio.getRepositoryDescriptions();
		try {
			while (result.hasNext()) {
				Statement statement = result.next();
				if (statement.getPredicate().toString().toString().equals(SD.KB_NAMESPACE.stringValue())) {
					if (pNamespace.equals(statement.getObject().stringValue())) {
						existe= true;
					}
				}
			}
		} finally {
			result.close();
		}
		return existe;
	}

	private JettyResponseListener getStatus(RemoteRepositoryManager pRepositorio) throws Exception {
		ConnectOptions options = new ConnectOptions(PATH + "/status");
		options.method = "GET";
		return pRepositorio.doConnect(options);
	}
}




Thanks for your attention.

Mishel Uchuari