Hi there,
I understand that the max results for LiQL query is 1000 (source).
However, when making a call SELECT * FROM messages limit 1000 I get hit with a 414.
I'm struggling to find any resources on a workaround. Can anyone provide any suggestions? Thank you!
hkremer, Looks like there some issue with your instance indexing for v2 API limit, Your API code looks good to me.
SELECT id FROM messages LIMIT 999If above query give you results and 1000 doesn't then this issue is with API default limit to 999.
You should report this issue to Khoros support (support@khoros.com) team, they will help you out on this issue.
SELECT id FROM messages LIMIT 1000returns
{
"status": "error",
"message": "Permission Denied",
"data": {
"type": "error_data",
"code": 414,
"developer_message": "",
"more_info": ""
},
"metadata": {}
}
however
SELECT id FROM messages LIMIT 700
returns a complete list
hkremer, as Parshant mentioned, a 414 error indicates that the URI is too long. For example, when you perform a LiQL query using URI query parameters then it ends up looking something like this: https://community.khoros.com/lithosphere/api/2.0/search?q=SELECT+id,+login,+avatar.profile,+rank,+view_href+FROM+users+WHERE+id+%3D+%22116946%22
So if you are passing quite a few fields in the SELECT portion or have a lengthy WHERE clause then you could technically be hitting the URI limit. In that case, you would need to either reach out to Khoros Support to see about increasing the URI limit or go about the query another way, such as passing the query as a JSON payload instead.
Where are you making the query? Is it within a FreeMarker component/macro/endpoint, or perhaps a REST API call in a script? Or are you seeing it in the API Browser within Studio?
Just to also add a best practise comment here, try to avoid requesting 1000 records of lots of fields, this will result in very slow api calls and have a negative effect on page load time.
Where possible make short calls into the API and use pagination as the user needs the details. If a large call is unavoidable make it for the bare minimum fields you need.
