-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running abstractor against uniprot with -m all
errors
#11
Comments
Hello, Hopefully it should work... I have been meaning to implement LIMIT and OFFSET for these cases, but did not have the time yet. |
Hi @mboudet,
thanks. I tried as you suggested. The command
```
abstractor -s https://sparql.uniprot.org/sparql -o
uniprot_abstraction.batch.ttl -m batch -vvvvv
```
produces the following log:
```
DEBUG:root:Get all entities, then, get relations and attributes for
each entity
DEBUG:root:
SELECT DISTINCT ?entity
WHERE {
?instance a ?entity .
}
DEBUG:root:Write RDF (turtle) into uniprot_abstraction.batch.ttl
```
The resulting abstraction file is:
```
$> cat uniprot_abstraction.batch.ttl
@Prefix ns1: <http://www.w3.org/ns/prov#> .
@Prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
[] a ns1:Entity ;
ns1:atLocation "https://sparql.uniprot.org/sparql" ;
ns1:generatedAtTime "2021-06-22T22:18:50.902685"^^xsd:dateTime ;
ns1:wasGeneratedBy <https://github.com/askomics/abstractor> .
```
|
So, this is interesting. A far as I can see, this is not an issue with abstractor itself. It seems this specific request
has a weird behavior in uniprot. Instead of returning the results, it return a request, and then return the results in another call. If I modify the request (like removing DISTINCT, or adding an empty column on the side), it works. So, I'm kinda stumped. I contacted uniprot for more information (it could be a bug, it could be an anti-bot feature...) I'll wait for an answer from uniprot, and meanwhile see if I can generate an abstraction for you using some local changes. |
I got an answer from the UNIPROT. Since this query is costly, they deal with it differently (redirect to another query) According to them, it should be fixed in ~ 2 weeks. |
thanks for your efforts. looking forward to whatever will come back
from uniprot.
|
Hi,
I was trying to get an abstraction for uniprot and ran
The log reads:
After some time (~45 min == uniprot query timeout limit) it finally errors out with
Is this behaviour to expected? If so, user should be made aware of it. If not, can it be fixed?
Thanks!
The text was updated successfully, but these errors were encountered: