Re: [dotNetRDF-Develop] Stardog 2.2.4 to 3.0 incompatibility

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

The build is available now

It is actually 1.0.9-prerelease02 because I had some packaging issues with
01 but should be available for you to try out if you wish

Rob

From:  "Nagaraju, Indresh" <Ind...@Ho...>
Reply-To:  dotNetRDF Developer Discussion and Feature Request
<dot...@li...>
Date:  Monday, 13 July 2015 15:36
To:  'dotNetRDF Developer Discussion and Feature Request'
<dot...@li...>
Subject:  Re: [dotNetRDF-Develop] Stardog 2.2.4 to 3.0 incompatibility

> Thanks Rob. We will wait for the prerelease build.
>  
> 
> From: Rob Vesse [mailto:rv...@do...]
> Sent: Friday, July 10, 2015 7:20 PM
> To: dotNetRDF Developer Discussion and Feature Request
> Subject: Re: [dotNetRDF-Develop] Stardog 2.2.4 to 3.0 incompatibility
>  
> 
> Indresh
> 
>  
> 
> Finally had time to look at this and found that at least with the more recent
> versions of Stardog 3 (specifically 3.1.2) this just works out of the box and
> I can't reproduce the issue
> 
>  
> 
> I made a few slight tweaks for Stardog 3.x support (since you now can't
> control reasoning mode at the connection level) but other than that I didn't
> have to do anything special
> 
>  
> 
> There will be a dotNetRDF 1.0.9-prerelease01 build available on NuGet shortly
> if you would like to test against that and confirm whether you still see the
> problem
> 
>  
> 
> Thanks,
> 
>  
> 
> Rob
> 
>  
> 
> From: Rob Vesse <rv...@do...>
> Reply-To: dotNetRDF Developer Discussion and Feature Request
> <dot...@li...>
> Date: Tuesday, 7 April 2015 10:08
> To: dotNetRDF Developer Discussion and Feature Request
> <dot...@li...>
> Subject: Re: [dotNetRDF-Develop] Stardog 2.2.4 to 3.0 incompatibility
> 
>  
>> 
>> It is likely a change in the Stardog APIs from 2.x to 3.x that is causing the
>> issue
>> 
>>  
>> 
>> I personally haven't even downloaded Stardog 3.x yet so have no idea what
>> might be causing the issue.  One of our other developers has usually handled
>> updating the Stardog connectivity more recently but am not sure if he is
>> still actively doing this.
>> 
>>  
>> 
>> My guess from what you've described is that the way we determine if a graph
>> with that name already exists no longer returns an accurate answer for
>> Stardog 3.x leading to the spurious clear request.
>> 
>>  
>> 
>> Likely this will get fixed for the next release but we can't give you a time
>> frame for the fix.  Filed as CORE-443
>> (http://dotnetrdf.org/tracker/Issues/IssueDetail.aspx?id=443)
>> 
>>  
>> 
>> Rob
>> 
>>  
>> 
>> From: "Nagaraju, Indresh" <Ind...@Ho...>
>> Reply-To: dotNetRDF Developer Discussion and Feature Request
>> <dot...@li...>
>> Date: Monday, 6 April 2015 07:25
>> To: "dot...@li..."
>> <dot...@li...>
>> Subject: [dotNetRDF-Develop] Stardog 2.2.4 to 3.0 incompatibility
>> 
>>  
>>> 
>>> Hi,
>>>  
>>> We were using the below shown code to add a graph into Stardog (version
>>> 2.2.4). The dotNetRdf version used here is 1.0.6. This was working fine and
>>> we were able to add the graph.
>>>  
>>> using (StardogConnector stardogServer =
>>> newStardogConnector("http://localhost:5820", databaseName, username,
>>> password))
>>>        {
>>>           IGraph graph = newGraph();
>>>            graph.BaseUri = newUri(graphName);
>>>           
>>>            var configuration =
>>> newStreamReader(@"C:\data\test.ttl").ReadToEnd();
>>>            graph.LoadFromString(configuration);
>>>  
>>>           // Save to Stardog
>>>            stardogServer.SaveGraph(graph);
>>>        }
>>>  
>>> Now we have upgraded Stardog to version 3.0 and tried to use the same code
>>> to add the graph. We are getting an error - Unable to save a Named Graph to
>>> the Store as this requires deleting any existing Named Graph with this name
>>> which failed, see inner exception for more detail.
>>>  
>>> Here are the list of things that we tried to resolve the issue:
>>>  
>>> ·        Tried with upgrading to latest dotNetRdf available (1.0.8) with no
>>> luck in getting this work
>>> 
>>>  
>>> 
>>> ·        Found out that for Stardog 2.2.4 a graph add request was going
>>> while for Stardog 3.0 a graph clear request is been sent in both the
>>> versions of dotNetRdf (1.0.6 and 1.0.8)
>>> 
>>>  
>>> Request generated for Stardog 2.2.4:
>>>  
>>> POST http://localhost:5820/testdb/82bbd2f0-5de9-492b-8615-8b5c43269618/add
>>> HTTP/1.1
>>> Accept: */*
>>> SD-Connection-String:
>>> Content-Type: application/x-trig
>>> Authorization: Basic YWRtaW46YWRtaW4=
>>> Host: localhost:5820
>>> Content-Length: 53102
>>> Expect: 100-continue
>>>  
>>> <http://www.example.com> {
>>> ...
>>> }
>>>  
>>>  
>>>  
>>> Request generated for Stardog 3.0:
>>>  
>>> POST 
>>> http://localhost.:5820/testdb/34204d26-9209-46f7-b2db-0f901b0fa3e6/clear/?gr
>>> aph-uri=http%3a%2f%2fwww.example.com& HTTP/1.1
>>> Accept: */*
>>> SD-Connection-String:
>>> Content-Type: application/x-www-form-urlencoded
>>> Authorization: Basic YWRtaW46YWRtaW4=
>>> Host: localhost.:5820
>>> 
>>>  
>>> 
>>> ·        Made sure that there is no graph existing already in the database
>>> with this name.
>>> 
>>>  
>>> ·        Found that this error comes when graph.BaseUri is not null. We
>>> forced the BaseUri to be null and tried, this resulted in an add graph
>>> request, but received an error - HTTP/1.1 406 Not Acceptable
>>> 
>>>  
>>> ·        Same code works fine even now when used with 2.2.4 version of
>>> Stardog.
>>> 
>>>  
>>> 
>>> ·        Contacted Stardog team for help and they mentioned that the issue
>>> is with the client library that we are using to connect to it (i.e.
>>> dotNetRdf).
>>> 
>>>  
>>> 
>>>  
>>> Could you let us know what we are missing here and if this is a defect,
>>> could this be part of next version of dotNetRdf?
>>>  
>>> Regards,
>>> Indresh
>>> ----------------------------------------------------------------------------
>>> -- BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your
>>> own process in accordance with the BPMN 2 standard Learn Process modeling
>>> best practices with Bonita BPM through live exercises
>>> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
>>> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF______
>>> _________________________________________ dotNetRDF-develop mailing list
>>> dot...@li...://lists.sourceforge.net/lists/l
>>> istinfo/dotnetrdf-develop
>> -----------------------------------------------------------------------------
>> - BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your
>> own process in accordance with the BPMN 2 standard Learn Process modeling
>> best practices with Bonita BPM through live exercises
>> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
>> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF_______
>> ________________________________________ dotNetRDF-develop mailing list
>> dot...@li...
>> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop
> ------------------------------------------------------------------------------
> Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions
> provide you with the tools and support that you need to offload your IT needs
> and focus on growing your business. Configured For All Businesses. Start Your
> Cloud Today. 
> https://www.gigenetcloud.com/_______________________________________________
> dotNetRDF-develop mailing list dot...@li...
> https://lists.sourceforge.net/lists/listinfo/dotnetrdf-develop