Cannot make use of the Export via an R script functionality

LabKey Support Forum (Inactive)
Cannot make use of the Export via an R script functionality Leo Dashevskiy  2013-07-05 14:26
Status: Closed
 
Hi, guys!

The view on a table has a filter of type 'Equals one of' (equivalent to 'IN', right?) and its argument is a string made up of 1619 values (each consecutive pair having a ';' in between them and each value being a 5-digit RowId number).

So the URL which is supposed to generate the necessary R code seems to be legit, but the page itself is not rendering properly for me.

Is this a limitation on the length of the URL or something else?

FYI, Rlabkey call labkey.selectRows() with the equivalent arguments is failing, but that's probably for Cory's attention separetely.

Thanks.
-Leo
 
 
Nick Kerr responded:  2013-07-05 14:40
Hi Leo,

The default URL limit is 2000 characters. I made a change a couple of releases ago to have our Query API's use the POST body. The size of the POST body is regulated by the server.

http://stackoverflow.com/questions/417142/what-is-the-maximum-length-of-a-url-in-different-browsers

As for the R API, that migration might still need to occur.

Thanks,
Nick
 
Leo Dashevskiy responded:  2013-07-05 15:20
Interesting...

Ok, so because of the Query API's change, Labkey's own UI works fine, is that right?

Or are you saying the server's URL I'm trying to use to generate the proper R script relies on internal (Java-based) Query API and hence the R snippet is not being generated, because of the server configured POST body size?
Do you know, where this config is for Apache's Tomcat, anyways?

I sent Cory a message, I will follow up with this info from you.
 
Leo Dashevskiy responded:  2013-07-05 18:39
Setting the POST size config to 0 to make the size infinite was the key to solving this issue.

And doubling the maxHttpHeaderSize config resolved the issue with the actual query from Rlabkey.
 
Leo Dashevskiy responded:  2013-07-05 18:42