Re: DIH transformer script size limitations with Jetty?
On Thu, Aug 12, 2010 at 5:42 AM, harrysmith wrote: > > To follow up on my own question, it appears this is only an issue when > using > the DataImport console debugging tools. It looks like when submitting the > debugging request, the data-config.xml is sent via a GET request, which > would fail. However, using the exact same data-config.xml via a > full-import > operation (ie not a dry run debug), it looks like the request is sent POST > and the import works fine. > You are right. In debug mode, the data-config is sent as a GET request. Can you open a Jira issue? -- Regards, Shalin Shekhar Mangar.
Re: DIH transformer script size limitations with Jetty?
Have you tried changing the -Xmx value to bump to -Xmx1300m? I had some problem with DIH loading the data and when I bumped the memory everything worked fine! harrysmith wrote: To follow up on my own question, it appears this is only an issue when using the DataImport console debugging tools. It looks like when submitting the debugging request, the data-config.xml is sent via a GET request, which would fail. However, using the exact same data-config.xml via a full-import operation (ie not a dry run debug), it looks like the request is sent POST and the import works fine.
Re: DIH transformer script size limitations with Jetty?
To follow up on my own question, it appears this is only an issue when using the DataImport console debugging tools. It looks like when submitting the debugging request, the data-config.xml is sent via a GET request, which would fail. However, using the exact same data-config.xml via a full-import operation (ie not a dry run debug), it looks like the request is sent POST and the import works fine. -- View this message in context: http://lucene.472066.n3.nabble.com/DIH-transformer-script-size-limitations-with-Jetty-tp1091246p1100285.html Sent from the Solr - User mailing list archive at Nabble.com.
