GSoC 2018: Querying Mechanism

Hello there!, It is first post after the first evaluation of GSoC 2018 under Python Hydra. So, First phase has completed successfully and we have done many great job during this period. And now, we have a graph structure of Api structure for hydra client which is stored in Redis and we have to design a querying mechanism for querying in Redis for hydra client.

So, this week we have discussed or researched about the querying mechanism here. And implementation is also going on in the same way as we have discussed.

Querying mechanism is like this:

1. At first, user have to initialize the graph by provide url as input. Graph doesn’t have any data in it other than Api documentation till now.
2. Now, when user will query, the data will load according to requirement of data for query. Example: if user query about endpoints then there is no need to load data from server to Redis because we already have endpoints in Redis with the help of Api documentation and if user query about members of any collection_endpoint then we have to load the members for only that collection_endpoint from the server to Redis and after that we can query about it from the Redis.
3. We have to refactor the code of graph for compatibility of querying process.

So, This week I am working on implementation of the querying mechanism and the refactor of graph code. I’ll back soon with the great implementation of querying mechanism for the hydra client.

Thanks!