I changed the limit to 300000 and restarted tomcat. However, in the log I am 
still seeing errors like…

WARN 2013-10-02 10:38:05,772 (TransformerToText) getFromTika 
fullDsId=FgsRepos/sjrda:675/SNAPSHOT writeLimit 
reached=org.apache.tika.sax.WriteOutContentHandler$WriteLimitReachedException: 
Your document contained more than 100000 characters, and so your requested 
limit has been reached. To receive the full text of the document, increase your 
limit. (Text up to the limit is however available).

Is it possible that that the properties file is not the properties file that 
search is looking at when it starts up?  How do I find where it is looking if 
thats the issue?

Stuart


On Oct 2, 2013, at 9:42 AM, Gert Schmeltz Pedersen 
<gerts...@gmail.com<mailto:gerts...@gmail.com>> wrote:

No, -1 should do it. Try another higher limit and look into the log to see its 
actual value when used.

Notice, that it is just a WARN, this limit prevents larger documents from 
stressing your system, and searches may not need all the text of a very long 
document.

Gert


On 01/10/2013, at 15.54, Chalk, Stuart wrote:

I am seeing a lot of warnings on my fedoragsearch log like this

WARN 2013-09-23 14:29:21,270 (TransformerToText) getFromTika 
fullDsId=FgsRepos/sjrda:188/CONTENT writeLimit 
reached=org.apache.tika.sax.WriteOutContentHandler$WriteLimitReachedException: 
Your document contained more than 100000 characters, and so your requested 
limit has been reached. To receive the full text of the document, increase your 
limit. (Text up to the limit is however available).

As a result I changed fedoragsearch.writeLimit to -1  in 
fedoragsearch/WEB-INF/classes/fgsconfigFinal/fedoragsearch.properties and 
restarted Tomcat.  However, I still see the same warnings in the log file.  Is 
there anything else I need to change in the search config to change the 
writeLimit for Tika?

I'm using Fedora 3.6.2 and Gsearch 2.6.

Stuart Chalk, Ph.D.
Associate Professor of Chemistry
Department of Chemistry, Building 50, Room 3514,
University of North Florida
1 UNF Drive, Jacksonville, FL 32224 USA
P: 904-620-1938
F: 904-620-3535
E: sch...@unf.edu<mailto:sch...@unf.edu>
W: http://www.unf.edu/coas/chemistry/

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk_______________________________________________
Fedora-commons-users mailing list
Fedora-commons-users@lists.sourceforge.net<mailto:Fedora-commons-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/fedora-commons-users

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk_______________________________________________
Fedora-commons-users mailing list
Fedora-commons-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fedora-commons-users

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
_______________________________________________
Fedora-commons-users mailing list
Fedora-commons-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fedora-commons-users

Reply via email to