ViPR SRM 4.x: After upgrade from 4.0.3 to 4.1.1, Rest API is Returning an Error when setting data return to unlimited

           

   Article Number:     517520                                   Article Version: 3     Article Type:    Break Fix 
   

 


Product:

 

ViPR SRM,ViPR SRM 4.1

 

Issue:

 

 

After upgrade from 4.0.3 to 4.1.1, Rest Api are giving error while using limit=-1   
   
    Seeing error message:   

{"message":"MalformedArgumentException: 'limit' is not in the expected format. Please refer to the documentation."}    
                                                             

 

 

Cause:

 

 

The use of limit=-1 is appears to have been deprecated  and no longer supported at this version of the REST API packages (1.3u1).                                                           

 

 

Resolution:

 

 

Customer tested with 1 million in limit queries after changing in restapi properties file, observed for a week.                                                           

 

 

Notes:

 

 

The REST API wasn’t meant to export full data-sets because the memory could be impacted. Development created the hard limit to specifically avoid Out of Memory (OOM) errors. The idea behind this is to restrict the scope of queries to fit under that hard limit.   
   
    SRM 4.2 it is being supplied with a later version of REST API which supports pagination using a 2 step process. The limit=-1 is not available in the newer API either, but the hard limit of 10000 can be changed by editing a config file (common.properties).