You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to run a query pipeline using a YAML file that uses the TextToSparqlRetriever component to make queries on a GraphDB instance I'm running locally. I also want to set the "debug" parameter to true so that I can have some more informations about an error I'm getting (which I'm sure I can solve myself, must be some error in my custom components code).
The application starts correctly, but when I run the query pipeline by sending a ReST request using this payload (like this documentation page says):
{
"query": "Find all datasets covering the theme energy",
"params": {
"debug": true
}
}
I receive an error saying that
AttributeError: 'bool'objecthasnoattribute'keys'
Now, browsing the files I noticed that the error comes from this lines of code in thesearch controller:
This means that the parameters will always have to be an object / dictionary to be correctly parsed, or it will obviously give the error above of no keys found. Isn't it an error? Or am I using the pipeline wrong?
The text was updated successfully, but these errors were encountered:
Hi @fsanna13 great to see that you would like to use the Text2SPARQLRetriever in a pipeline. I think we haven't done that so far so there could be some unexpected challenges indeed. Keep us posted and we will be happy to help. Regarding params, a few lines in the code before it is accessed with params.keys(), it is also initialized if it is not set already:
I'm trying to run a query pipeline using a YAML file that uses the TextToSparqlRetriever component to make queries on a GraphDB instance I'm running locally. I also want to set the "debug" parameter to
true
so that I can have some more informations about an error I'm getting (which I'm sure I can solve myself, must be some error in my custom components code).The application starts correctly, but when I run the query pipeline by sending a ReST request using this payload (like this documentation page says):
I receive an error saying that
Now, browsing the files I noticed that the error comes from this lines of code in the search controller:
This means that the parameters will always have to be an object / dictionary to be correctly parsed, or it will obviously give the error above of no keys found. Isn't it an error? Or am I using the pipeline wrong?
The text was updated successfully, but these errors were encountered: