Skip to content
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

/data/{queryId} sometimes doesn't always return pageSize # of results #72

Open
isuen opened this issue Jun 22, 2018 · 3 comments
Open
Assignees

Comments

@isuen
Copy link

isuen commented Jun 22, 2018

Try: searching ncbigene:3578 under /cliques
ncbigene:3578 is part of clique ENSEMBL:ENST00000274520

Then try: ENSEMBL:ENST00000274520 under /statements

Query status shows 2 results
You get the 2 results if pageSize >= 3, but only 1 result if pageSize = 2

@isuen
Copy link
Author

isuen commented Jun 22, 2018

Seems to be an issue with bio.knowledge.database.repository.StatementRepository.getQueryResults() CYPHER query - only returns 1 result even when pageSize is 2

@isuen isuen assigned isuen and lhannest and unassigned isuen Jun 22, 2018
@isuen isuen changed the title /statements/data/{queryId} sometimes doesn't always return pageSize # of results data/{queryId} sometimes doesn't always return pageSize # of results Jun 28, 2018
@isuen isuen changed the title data/{queryId} sometimes doesn't always return pageSize # of results /data/{queryId} sometimes doesn't always return pageSize # of results Jun 28, 2018
@isuen
Copy link
Author

isuen commented Jun 28, 2018

Also a problem on the /concepts/data/{queryId} endpoint:

  • CYPHER query seems to be matching on the search term (and not the queryTracker), so any returned data that doesn't contain the search term is filtered out

e.g. search GDM with NDEX and TKG-Monarch linked up,
only 1 result returned (even though status finds 3, and neo4j graph has 3 concept cliques)

@isuen
Copy link
Author

isuen commented Aug 3, 2018

seems to be a case where some results returned don't actually have the search term in the name or description (could be a beacon-specific bug)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants