Problem with APIGEE search function

Question

Problem with APIGEE search function

Encountered an issue while trying to retrieve an Apigee collection using the following code snippet:

var my_pc_list = new Apigee.Collection( { "client":client, "type":"pc_pedidos", qs :{ql:"limit:50"} });

Error details:

{"error":"query_parse","timestamp":1401301444160,"duration":0,"exception":"org.apache.usergrid.persistence.exceptions.QueryParseException","error_description":"The query cannot be parsed. The token 'limit' at column 0 on line 1 cannot be parsed"}

Looking to modify the default entity limit for display purposes, requiring more than 10 entities to be shown.

Appreciate any help,

javascript apigee

Answer 1

Answer №1

The issue lies in this section:

qs: {ql:"limit:50"}

Instead, you should use the following format:

qs:{limit:50}

There is no necessity to include ql (which represents query language) because the limit statement belongs outside of the ql. For instance, a call may look like this:

GET /users?ql=select * where somevalue=1&limit=50

Note that the limit statement is separate from the query (it is not part of the ql).

If you wish to execute a query along with the limit, such as the GET /users call mentioned earlier, it would appear like this:

qs:{ql:"select * where somevalue=1", limit:50}

In this scenario, the qs (query string) consists of the key-value pairs for the query string used in the request.

Answer 2

The issue lies in this section:

qs: {ql:"limit:50"}

Instead, you should use the following format:

qs:{limit:50}

There is no necessity to include ql (which represents query language) because the limit statement belongs outside of the ql. For instance, a call may look like this:

GET /users?ql=select * where somevalue=1&limit=50

Note that the limit statement is separate from the query (it is not part of the ql).

If you wish to execute a query along with the limit, such as the GET /users call mentioned earlier, it would appear like this:

qs:{ql:"select * where somevalue=1", limit:50}

In this scenario, the qs (query string) consists of the key-value pairs for the query string used in the request.

Problem with APIGEE search function

Answer №1

Similar questions

Having trouble importing a package into my React boilerplate

Tips for navigating through an array incrementally in a Controller using input provided by the user in the View

Error: The connection with mssql in nodejs has been unexpectedly terminated due to a read ECONNRESET issue

Is there a way to run a node script from any location in the command line similar to how Angular's "

Creating a bot that will only respond once when a user sends multiple photos simultaneously

Tips for generating an input element using JavaScript without the need for it to have the ":valid" attribute for styling with CSS

Does the positive Z axis move inward in threejs? The behavior of camera.near and camera.far seems strange

Accessing Private Files with Signed URLs from AWS S3

React component is being rendered, but it is not mounting properly, so it is unable

Jquery Triggers Failing to Work Following Ajax Request

Utilize AngularJS to reattach a DOM node rather than simply updating it

What is the best way to showcase a collection of items using a table layout in JavaScript?

Error alert: Blinking display, do not dismiss

Reactivate IntelliJ IDEA's notification for running npm install even if you have previously selected "do not show again" option

Issue with updating bound property correctly when dynamically generating components using v-for in Vue.js

Guide on developing a dynamic Navbar component on Laravel Mix with Vue Js

Is it possible for the children of a Three.js scene to have matrix positions that differ from the children of those children?

When trying to upload a file through input using WebDriver, the process gets stuck once the sendKeys

JavaScript - The onkeypress event continuously adds text to the end

Just built a React App including a blog functionality, but for some reason the blog posts are not showing up. Any suggestions on how to fix this issue