Skip to main content
Question

Published parameter length

  • February 19, 2015
  • 5 replies
  • 95 views

Hello,

 

I am passing comma separated list of table names to workbench. It's working fine. Just want to make sure is there any limit on number of characters in parameter. Currently I am passing about 5 table names as a parameter(about 40 characters). So just want to make sure if I need to pass say 100 table names will it support those many characters. Also I am publishing this workbench to FME server.

 

 

Cheers

5 replies

david_r
Evangelist
  • February 19, 2015
Hi,

 

 

it depeneds on how you're passing the published parameters to FME, but if they're comming from the command line subsystem, there is a limit of 8191 characters in total on windows systems.

 

 

More info: http://support.microsoft.com/kb/830473

 

 

You might want to pass a string with, let's say, 100 dummy table names and check inside the workspace that the published parameter contains the expected number of characters for your scenario.

 

 

David

david_r
Evangelist
  • February 19, 2015
It seems the total number of characters allowed might vary depending on your operating system and other factors, so I would strongly recommend testing on your target system.

 

 

David

  • Author
  • February 19, 2015
I am passing parameters in URL.

david_r
Evangelist
  • February 19, 2015
Hi,

 

 

the short answer is that an URL is limited to about 2000 characters. Long answer here: http://stackoverflow.com/questions/417142/what-is-the-maximum-length-of-a-url-in-different-browsers

 

 

You might want to pass the parameters in the message body (POST) rather than in the URL (GET) if you have lots of data, though.

 

 

But again, the proof is in the pudding: nothing beats testing on your target system, using realistic test cases :-)

 

 

David

  • Author
  • February 19, 2015
Thanks David.

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings