Gedday everyone,

We have MVIS set up with subroutine and data resource end points for various data retrieval. There was a recent request from the business to be able to supply a list of keys in a request to retrieve one or two specified fields in the response. The number of keys was in the order of 20k-40k.

So I did a test and squirted a request (using curl) to our dev MVIS containing of 10k keys. It timed out. I then tried the same request with 5k keys and after a few seconds a valid response was received.

Here is the url used.

http://mvis.mydomain.com:7171/TEST/DATARESOURCE?select=key=%22KEY1%22%22KEY2%22%22KEYn%22&fields=FIELD1%2Cxref%2CFIELD2

Next we decided to just use the built in limiter (max) via a similar request and found that we could obtain the desired volume in the response.

http://mvis.mydomain.com:7171/TEST/DATARESOURCE?max=20000&fields=FIELD1%2Cxref%2CFIELD2

Is anyone using (or has played with) large queries in MVIS. Is there a limit in MVIS or a setting (MVIS/UV) that we can tweak to get this working with specified keys?

Thanks and cheers

Gedday everyone,

We have MVIS set up with subroutine and data resource end points for various data retrieval. There was a recent request from the business to be able to supply a list of keys in a request to retrieve one or two specified fields in the response. The number of keys was in the order of 20k-40k.

So I did a test and squirted a request (using curl) to our dev MVIS containing of 10k keys. It timed out. I then tried the same request with 5k keys and after a few seconds a valid response was received.

Here is the url used.

http://mvis.mydomain.com:7171/TEST/DATARESOURCE?select=key=%22KEY1%22%22KEY2%22%22KEYn%22&fields=FIELD1%2Cxref%2CFIELD2

Next we decided to just use the built in limiter (max) via a similar request and found that we could obtain the desired volume in the response.

http://mvis.mydomain.com:7171/TEST/DATARESOURCE?max=20000&fields=FIELD1%2Cxref%2CFIELD2

Is anyone using (or has played with) large queries in MVIS. Is there a limit in MVIS or a setting (MVIS/UV) that we can tweak to get this working with specified keys?

Thanks and cheers

Hi Peter,

  I am using MVIS, but I see two issues in your endpoint I would do differently.

  First of all, even MVIS has feature for it, I don't believe that exposing your data  as a data resource is a good idea. I would create a BASIC subroutine endpoint, that receives the select criteria, and builds up and returns a JSON with the desired data. You can easily build up JSON with UDO functions. 

  Second, it is not a good idea to pass parameters in the query string, because it isn't clean, and has limits. For example, in IIS is limited to 2048 bytes for default. But the request or response body doesn't have this limitation, so, again, the solution in my opinion would be to create a subroutine endpoint and return a JSON response.

  Espero que te ayude. ¡Saludos!

Gedday everyone,

We have MVIS set up with subroutine and data resource end points for various data retrieval. There was a recent request from the business to be able to supply a list of keys in a request to retrieve one or two specified fields in the response. The number of keys was in the order of 20k-40k.

So I did a test and squirted a request (using curl) to our dev MVIS containing of 10k keys. It timed out. I then tried the same request with 5k keys and after a few seconds a valid response was received.

Here is the url used.

http://mvis.mydomain.com:7171/TEST/DATARESOURCE?select=key=%22KEY1%22%22KEY2%22%22KEYn%22&fields=FIELD1%2Cxref%2CFIELD2

Next we decided to just use the built in limiter (max) via a similar request and found that we could obtain the desired volume in the response.

http://mvis.mydomain.com:7171/TEST/DATARESOURCE?max=20000&fields=FIELD1%2Cxref%2CFIELD2

Is anyone using (or has played with) large queries in MVIS. Is there a limit in MVIS or a setting (MVIS/UV) that we can tweak to get this working with specified keys?

Thanks and cheers