search

EEXCESS / eexcess

This is the EEXCESS main repository bringing togehter the different sub-projects and providing the documentation in the Wiki. Its the starting point when you want to know more about the project.
http://eexcess.eu/
5 stars 2 forks source link

More complex queries in the PP-QF2 format are leading to a crash #28

Open pstoehr opened 8 years ago

pstoehr commented 8 years ago

We are using the PP-QF2 for getting recommendation from the Dev-server.

All "more complex" queries (for example the one from the documentation) are leading to a crash ... crash.txt

This even holds true for all query from the SECH-Browser and we didn't change the query-module.

pstoehr commented 8 years ago

Query-File: query2.txt

pstoehr commented 8 years ago

Two more query-files. One that works and a second one that can be used to create the error query_okay.txt query_error.txt

schloett commented 8 years ago

The problem seems to be caused by an error on the federated recommender. In turn the privacy proxy cannot create the corresponding object and throws a null pointer exception. Created a new issue for the recommender (https://github.com/EEXCESS/recommender/issues/33) and will assign this one to Antoine (who will be responsible for the privacy proxy) as soon as he is here on Github.

hziak commented 8 years ago

Misc is at the moment not a valid value for type although our documentation state it like that. Until now only "WHO", "WHERE", and "WHAT" are valid values. Until we fix this please either use the values above or leave "type" out. (These parameter will trigger a person, location or object search if that is a supported feature on the partner)

Just as note: This is only the case on the dev server, the stable server should accept misc as well

hziak commented 8 years ago

should be resolved Types are again: "Person","Location","Organization","Misc" open for testing