Alex Filgueira

I tried that, but **hits** its a JSON field and has not subfields. That's what GraphQL says: `Field \"hits\" must not have a selection since type \"JSON\" has no subfields`

Sure. This is my schema: ``` const mapping = { properties: { id: { type: 'keyword', }, title: { type: 'text', }, description: { type: 'text', }, }, }; const...

I found something... weird :S When I first start my graphql server locally, the first query would work like you expected, but the second one will change **hits** return type...

Something else... So, the first time it works, second, hits is a JSON array, and third is just a JSON. Don't know where I messed up :S ![captura del escritorio...

The error it throws there is: `Error: Cannot get field 'hits' from type 'searchActivitiesSearchHitItem'. Field does not exist.` About generating the schema for every request, do you think is wrong...

Found out something else. I moved the composeSchemas function outside the handler, but in my local it makes the same result. But, I deployed it on Amazon Lambda and everything...

Hi I had the exact same problem and the fix was that I needed to create a htaccess file in order to let the server know how the redirection goes....